From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752634AbbJaCTZ (ORCPT <rfc822;w@1wt.eu>);
	Fri, 30 Oct 2015 22:19:25 -0400
Received: from szxga03-in.huawei.com ([119.145.14.66]:42887 "EHLO
	szxga03-in.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751326AbbJaCTX (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 30 Oct 2015 22:19:23 -0400
Message-ID: <563424EB.1060804@huawei.com>
Date: Sat, 31 Oct 2015 02:18:19 +0000
From: Salil Mehta <salil.mehta@huawei.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:31.0) Gecko/20100101 Thunderbird/31.1.2
MIME-Version: 1.0
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
References: <1445944594-244149-1-git-send-email-huangdaode@hisilicon.com> <4549013.K7sn8Pca5b@wuerfel> <56341C00.8080303@hisilicon.com>
In-Reply-To: <56341C00.8080303@hisilicon.com>
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.202.137.252]
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0),
	refid=str=0001.0A090201.56342508.0015,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0,
	ip=0.0.0.0,
	so=2013-05-26 15:14:31,
	dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 76e282dd4223583c608ab90fb7085de3
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


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