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]
Date:	Thu, 21 May 2015 14:59:22 -0700
From:	Ray Jui <rjui@...adcom.com>
To:	Kishon Vijay Abraham I <kishon@...com>
CC:	<linux-kernel@...r.kernel.org>,
	"JD (Jiandong) Zheng" <jdzheng@...adcom.com>,
	Arun Parameswaran <arunp@...adcom.com>,
	<bcm-kernel-feedback-list@...adcom.com>
Subject: Re: [PATCH 3/5] phy: cygnus: pcie: Define DT binding



On 5/21/2015 6:14 AM, Kishon Vijay Abraham I wrote:
> Hi,
> 
> On Wednesday 20 May 2015 06:53 AM, Ray Jui wrote:
>> Add DT binding document for Broadcom Cygnus PCIe PHY driver
>>
>> Signed-off-by: Ray Jui <rjui@...adcom.com>
>> Reviewed-by: Arun Parameswaran <aparames@...adcom.com>
>> Reviewed-by: JD (Jiandong) Zheng <jdzheng@...adcom.com>
>> Reviewed-by: Scott Branden <sbranden@...adcom.com>
>> ---
>>   .../bindings/phy/brcm,cygnus-pcie-phy.txt          |   31
>> ++++++++++++++++++++
>>   1 file changed, 31 insertions(+)
>>   create mode 100644
>> Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
>>
>> diff --git
>> a/Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
>> b/Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
>> new file mode 100644
>> index 0000000..36745ee
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/brcm,cygnus-pcie-phy.txt
> 
> brcm-cygnus-pcie-phy.txt?
>> @@ -0,0 +1,31 @@
>> +Broadcom Cygnus PCIe PHY
>> +
>> +Required properties:
>> +- compatible: Must be "brcm,cygnus-pcie-phy"
>> +- reg: base address and length of the CRMU block
>> +- #phy-cells: must be <2>
>> +The first cell is the PHY ID:
>> +0 - PCIe RC 0
>> +1 - PCIe RC 1
>> +The second cell is the internal PHY address
>> +
>> +Example:
>> +    phy: phy@...1d0a0 {
>> +        compatible = "brcm,cygnus-pcie-phy";
>> +        reg = <0x0301d0a0 0x14>;
>> +        #phy-cells = <2>;
>> +    };
> 
> IMHO these nodes should be child nodes of the mdio node. Are they
> modelled that way?
> 
> Thanks
> Kishon

Currently they are not. But you are right. It makes more sense for the
PHY nodes to be declared under the MDIO bus node. I will make that change.

Thanks,

Ray
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ