From: huangdaode@hisilicon•com (huangdaode)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents
Date: Thu, 12 Nov 2015 10:11:24 +0800 [thread overview]
Message-ID: <5643F54C.3010303@hisilicon.com> (raw)
In-Reply-To: <4387413.QS6YM6BNWK@wuerfel>
On 2015/11/3 6:05, Arnd Bergmann wrote:
> On Saturday 31 October 2015 02:18:19 Salil Mehta wrote:
>> On 10/31/2015 1:40 AM, huangdaode wrote:
>>> On 2015/10/30 22:20, Arnd Bergmann wrote:
>>>> On Tuesday 27 October 2015 19:16:34 huangdaode wrote:
>>>>> mdio at 803c0000 {
>>>>> #address-cells = <1>;
>>>>> #size-cells = <0>;
>>>>> - compatible = "hisilicon,mdio","hisilicon,hns-mdio";
>>>>> + compatible = "hisilicon,hns-mdio","hisilicon,mdio";
>>>>> reg = <0x0 0x803c0000 0x0 0x10000>;
>>>>>
>>>> Does "hisilicon,mdio" actually have a specific meaning? Is that just
>>>> there
>>>> for legacy reasons?
>>>>
>>>> Arnd
>>>>
>>>> .
>>>>
>>> hi Arnd,
>>> "hisilicon,mdio" is the gernerical configuation compatible for the
>>> default hisilicon chip,
>>> We use generic hisilicon since our MDIO/PHY is same across flavour of
>>> SoCs.
>>>
>> Hi Arnd,
>> Yes, "hisilicon,mdio" exists for the legacy reasons to support older SoC
>> Hip04.
> I see. In that case, that compatible string should probably be mentioned
> only as 'optional' in the binding, and not used for devices other than
> hip04.
>
> Arnd
>
> .
>
Hi, Arnd
ok, ill send a patch to specify it, please Ack then.
thanks
Daode.
--
Best Regards
Daode Huang
prev parent reply other threads:[~2015-11-12 2:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 11:16 [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents huangdaode
2015-10-28 3:20 ` David Miller
2015-10-30 14:20 ` Arnd Bergmann
2015-10-31 1:40 ` huangdaode
2015-10-31 2:18 ` Salil Mehta
2015-11-02 22:05 ` Arnd Bergmann
2015-11-12 2:11 ` huangdaode [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5643F54C.3010303@hisilicon.com \
--to=huangdaode@hisilicon$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox