linux-kernel - Re: [PATCH 2/2] Documentation: bindings: add description of phy for sdhci-of-arasan

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: <55F638A9.1090100@rock-chips.com>
Date:	Mon, 14 Sep 2015 11:02:01 +0800
From:	Shawn Lin <shawn.lin@...k-chips.com>
To:	Sören Brinkmann <soren.brinkmann@...inx.com>
Cc:	shawn.lin@...k-chips.com, Michal Simek <michal.simek@...inx.com>,
	Ulf Hansson <ulf.hansson@...aro.org>,
	linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-rockchip@...ts.infradead.org, devicetree@...r.kernel.org
Subject: Re: [PATCH 2/2] Documentation: bindings: add description of phy for
 sdhci-of-arasan

在 2015/9/14 10:47, Sören Brinkmann 写道:
> Hi Shawn,
>
> On Fri, 2015-09-11 at 04:55PM +0800, Shawn Lin wrote:
>> This patch adds phys and phy-names for sdhci-of-arasan as optional
>> properties, and details the example as well.
>>
>> Signed-off-by: Shawn Lin <shawn.lin@...k-chips.com>
>> ---
>>
>>   Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 10 ++++++++--
>>   1 file changed, 8 insertions(+), 2 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
>> index da541c3..0264d5f 100644
>> --- a/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
>> +++ b/Documentation/devicetree/bindings/mmc/arasan,sdhci.txt
>> @@ -1,11 +1,12 @@
>>   Device Tree Bindings for the Arasan SDHCI Controller
>>
>> -  The bindings follow the mmc[1], clock[2] and interrupt[3] bindings. Only
>> -  deviations are documented here.
>> +  The bindings follow the mmc[1], clock[2], interrupt[3] and phy[4] bindings.
>> +  Only deviations are documented here.
>>
>>     [1] Documentation/devicetree/bindings/mmc/mmc.txt
>>     [2] Documentation/devicetree/bindings/clock/clock-bindings.txt
>>     [3] Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
>> +  [4] Documentation/devicetree/bindings/phy/phy-bindings.txt
>>
>>   Required Properties:
>>     - compatible: Compatibility string. Must be 'arasan,sdhci-8.9a' or
>> @@ -16,6 +17,9 @@ Required Properties:
>>     - interrupts: Interrupt specifier
>>     - interrupt-parent: Phandle for the interrupt controller that services
>>   		      interrupts for this device.
>> +Optional Properties:
>> +  - phys: From PHY bindings: Phandle for the Generic PHY for arasan.
>> +  - phy-names:  MUST be "phy_arasan".
>
> This might be a dumb question, but, is the external phy actually
> optional? Or is it mandatory for certain implementations of the IP.
> In the latter case, it should probably be a mandatory property depending
> on the compatible string matching an implementation that requires an
> external phy (accordingly, the implementation might have to treat it

 From my soc team's reponse, there is no way to bypass controller to IO 
if no phy supported. So it should be the latter case you mentioned for 
arasan.sdhci-5.1.

Thanks for point out it, really helpful.

I will fix it in v2.

> that way too).
>
> 	Sören
>
>
>


-- 
Best Regards
Shawn Lin

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/