Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1519669
| From | Anurup M <anurupvasu@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver |
| Date | 2016-11-11 11:30 +0100 |
| Message-ID | <sChfQ-35W-25@gated-at.bofh.it> (permalink) |
| References | <sz5Xz-87s-3@gated-at.bofh.it> <sBglQ-2zG-35@gated-at.bofh.it> <sBsGl-2qR-9@gated-at.bofh.it> <sBIUO-4sZ-9@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thursday 10 November 2016 03:10 AM, Arnd Bergmann wrote:
> On Wednesday, November 9, 2016 9:58:38 AM CET Anurup M wrote:
>>> I also see that the compatible strings have the version included in
>>> them, and you can probably drop them by requiring them only in the
>>> fallback:
>>>
>>> compatible = "hisilicon,hip05-cpu-djtag", "hisilicon,djtag-v1";
>>> compatible = "hisilicon,hip05-io-djtag", "hisilicon,djtag-v1";
>>> compatible = "hisilicon,hip06-cpu-djtag", "hisilicon,djtag-v1";
>>> compatible = "hisilicon,hip06-io-djtag", "hisilicon,djtag-v2";
>>> compatible = "hisilicon,hip07-cpu-djtag", "hisilicon,djtag-v2";
>>> compatible = "hisilicon,hip07-io-djtag", "hisilicon,djtag-v2";
>>>
>>> We want to have the first entry be as specific as possible, but
>>> the last (second) entry is the one that can be used by the driver
>>> for matching. When a future hip08/hip09/... chip uses an existing
>>> interface, you then don't have to update the driver.
>> Thanks. I had a similar thought on this. So as I have the version string
>> in the
>> second entry "-v(1/2)".
>> I can use it in driver for matching. So i think I will change it as below.
>> Please correct me if my understanding is wrong.
>>
>> static const struct of_device_id djtag_of_match[] = {
>> - /* for hip05(D02) cpu die */
>> - { .compatible = "hisilicon,hip05-cpu-djtag-v1",
>> + /* for hisi djtag-v1 cpu die */
>> + { .compatible = "hisilicon,hisi-cpu-djtag-v1",
>> .data = djtag_readwrite_v1 },
>> - /* for hip05(D02) io die */
>> - { .compatible = "hisilicon,hip05-io-djtag-v1",
>> + /* for hisi djtag-v1 io die */
>> + { .compatible = "hisilicon,hisi-io-djtag-v1",
> From the code it looks like "hisilicon,hisi-io-djtag-v1" and
> "hisilicon,hisi-cpu-djtag-v1" have the same register-level interface,
> so we just need one compatible string for them to match the driver.
>
> Arnd
The djtag versions in CPU die and IO die can be different in the same chip.
For example in hip06, the CPU die has djtag-v1 whereas IO die has djtag-v2.
So I think it need two different compatible string
for hip06 chip CPU DIE "hisilicon,hisi-cpu-djtag-v1"
for hip06 chip IO DIE "hisilicon,hisi-io-djtag-v2"
Thanks,
Anurup
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v1 00/11] perf: arm64: Support for Hisilicon SoC Hardware event counters Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 09/11] perf: hisi: Miscellanous node(MN) event counting in perf Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 02/11] dt-bindings: hisi: Add Hisilicon HiP05/06/07 Sysctrl and Djtag dts bindings Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 06/11] perf: hisi: Update Kconfig for Hisilicon PMU support Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 10/11] perf: hisi: Support for Hisilicon DDRC PMU. Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 08/11] perf: hisi: Add sysfs attributes for L3 cache(L3C) PMU Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 04/11] Documentation: perf: hisi: Documentation for HIP05/06/07 PMU event counting. Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 01/11] arm64: MAINTAINERS: hisi: Add hisilicon SoC PMU support Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-07 14:30 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver John Garry <john.garry@huawei.com> - 2016-11-07 15:20 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-07 21:10 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver John Garry <john.garry@huawei.com> - 2016-11-08 12:40 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-08 12:50 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver John Garry <john.garry@huawei.com> - 2016-11-08 15:00 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-08 16:20 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver John Garry <john.garry@huawei.com> - 2016-11-08 16:20 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-09 12:00 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-08 17:00 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver John Garry <john.garry@huawei.com> - 2016-11-09 10:10 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-11 11:40 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Tan Xiaojun <tanxiaojun@huawei.com> - 2016-11-08 08:10 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-08 08:40 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-08 12:50 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-08 14:50 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-08 16:20 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-09 05:30 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Arnd Bergmann <arnd@arndb.de> - 2016-11-09 22:50 +0100
Re: [PATCH v1 03/11] drivers: soc: hisi: Add support for Hisilicon Djtag driver Anurup M <anurupvasu@gmail.com> - 2016-11-11 11:30 +0100
[PATCH v1 07/11] perf: hisi: Add support for Hisilicon SoC event counters Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
[PATCH v1 05/11] dt-bindings: perf: hisi: Add Devicetree bindings for Hisilicon SoC PMU Anurup M <anurupvasu@gmail.com> - 2016-11-02 16:50 +0100
csiph-web