From: Salil Mehta <salil.mehta@huawei.com>
To: huangdaode <huangdaode@hisilicon.com>, Arnd Bergmann <arnd@arndb.de>
Cc: <davem@davemloft.net>, <robh+dt@kernel.org>, <pawel.moll@arm.com>,
<mark.rutland@arm.com>, <ijc+devicetree@hellion.org.uk>,
<galak@codeaurora.org>, <catalin.marinas@arm.com>,
<will.deacon@arm.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <liguozhu@hisilicon.com>,
<Yisen.Zhuang@huawei.com>, <netdev@vger.kernel.org>,
<linuxarm@huawei.com>, <kenneth-lee-2012@foxmail.com>,
<xuwei5@hisilicon.com>, <lisheng011@huawei.com>,
<lipeng321@huawei.com>
Subject: Re: [PATCH RESEND v2 net-next] net: hisilicon: updates HNS config and documents
Date: Sat, 31 Oct 2015 02:18:19 +0000 [thread overview]
Message-ID: <563424EB.1060804@huawei.com> (raw)
In-Reply-To: <56341C00.8080303@hisilicon.com>
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@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.
Best Regards
Salil
next prev parent reply other threads:[~2015-10-31 2:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-27 11:16 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 [this message]
2015-11-02 22:05 ` Arnd Bergmann
2015-11-12 2:11 ` huangdaode
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=563424EB.1060804@huawei.com \
--to=salil.mehta@huawei.com \
--cc=Yisen.Zhuang@huawei.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=huangdaode@hisilicon.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=kenneth-lee-2012@foxmail.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=lisheng011@huawei.com \
--cc=mark.rutland@arm.com \
--cc=netdev@vger.kernel.org \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=will.deacon@arm.com \
--cc=xuwei5@hisilicon.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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
Powered by JetHome