From: Ray Jui <rjui@broadcom.com>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: <linux-kernel@vger.kernel.org>,
"JD (Jiandong) Zheng" <jdzheng@broadcom.com>,
Arun Parameswaran <arunp@broadcom.com>,
<bcm-kernel-feedback-list@broadcom.com>
Subject: Re: [PATCH 3/5] phy: cygnus: pcie: Define DT binding
Date: Thu, 21 May 2015 14:59:22 -0700 [thread overview]
Message-ID: <555E553A.3030705@broadcom.com> (raw)
In-Reply-To: <555DDA4D.5070906@ti.com>
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@broadcom.com>
>> Reviewed-by: Arun Parameswaran <aparames@broadcom.com>
>> Reviewed-by: JD (Jiandong) Zheng <jdzheng@broadcom.com>
>> Reviewed-by: Scott Branden <sbranden@broadcom.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@0301d0a0 {
>> + 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
next prev parent reply other threads:[~2015-05-21 21:59 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 1:23 [PATCH 0/5] Add Cygnus PCIe PHY support Ray Jui
2015-05-20 1:23 ` [PATCH 1/5] phy: iproc-mdio: Define DT binding Ray Jui
2015-05-21 13:07 ` Kishon Vijay Abraham I
2015-05-21 21:29 ` Ray Jui
2015-05-20 1:23 ` [PATCH 2/5] phy: iproc-mdio: Initial iProc MDC/MDIO support Ray Jui
2015-05-21 7:41 ` Paul Bolle
2015-05-21 23:52 ` Ray Jui
2015-05-22 8:39 ` Paul Bolle
2015-05-21 13:12 ` Kishon Vijay Abraham I
2015-05-21 21:35 ` Ray Jui
2015-05-21 21:51 ` Florian Fainelli
2015-05-21 22:02 ` Ray Jui
2015-05-20 1:23 ` [PATCH 3/5] phy: cygnus: pcie: Define DT binding Ray Jui
2015-05-21 13:14 ` Kishon Vijay Abraham I
2015-05-21 21:59 ` Ray Jui [this message]
2015-05-21 23:36 ` Ray Jui
2015-05-20 1:23 ` [PATCH 4/5] phy: cygnus: pcie: Add Cygnus PCIe PHY support Ray Jui
2015-05-21 7:52 ` Paul Bolle
2015-05-21 23:53 ` Ray Jui
2015-05-22 8:47 ` Paul Bolle
2015-05-21 13:19 ` Kishon Vijay Abraham I
2015-05-20 1:23 ` [PATCH 5/5] ARM: dts: enable PCIe PHY support for Cygnus Ray Jui
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=555E553A.3030705@broadcom.com \
--to=rjui@broadcom.com \
--cc=arunp@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=jdzheng@broadcom.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
/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