netdev - Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <563424EB.1060804@huawei.com>
Date:	Sat, 31 Oct 2015 02:18:19 +0000
From:	Salil Mehta <salil.mehta@...wei.com>
To:	huangdaode <huangdaode@...ilicon.com>,
	Arnd Bergmann <arnd@...db.de>
CC:	<davem@...emloft.net>, <robh+dt@...nel.org>, <pawel.moll@....com>,
	<mark.rutland@....com>, <ijc+devicetree@...lion.org.uk>,
	<galak@...eaurora.org>, <catalin.marinas@....com>,
	<will.deacon@....com>, <devicetree@...r.kernel.org>,
	<linux-kernel@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>, <liguozhu@...ilicon.com>,
	<Yisen.Zhuang@...wei.com>, <netdev@...r.kernel.org>,
	<linuxarm@...wei.com>, <kenneth-lee-2012@...mail.com>,
	<xuwei5@...ilicon.com>, <lisheng011@...wei.com>,
	<lipeng321@...wei.com>
Subject: Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config
 and documents


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@...c0000 {
>>>                      #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.

Best Regards
Salil

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html