From: Ray Jui <ray.jui@broadcom.com>
To: Rob Herring <robh@kernel.org>
Cc: Kishon Vijay Abraham I <kishon@ti.com>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v3 1/2] dt-bindings: phy: Add binding doc for Stingray PCIe PHY
Date: Fri, 6 Jul 2018 16:56:16 -0700 [thread overview]
Message-ID: <6a9c7b49-53b0-2d85-cc43-292020bf57ed@broadcom.com> (raw)
In-Reply-To: <20180705233401.GA26079@rob-hp-laptop>
On 7/5/2018 4:34 PM, Rob Herring wrote:
> On Wed, Jul 04, 2018 at 11:22:12AM -0700, Ray Jui wrote:
>> Add binding document for Stingray PCIe PHYs for both PAXB and PAXC based
>> root complex
>>
>> Signed-off-by: Ray Jui <ray.jui@broadcom.com>
>> ---
>> .../devicetree/bindings/phy/brcm,sr-pcie-phy.txt | 41 ++++++++++++++++++++++
>> 1 file changed, 41 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt
>>
>> diff --git a/Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt b/Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt
>> new file mode 100644
>> index 0000000..5a13511
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/phy/brcm,sr-pcie-phy.txt
>> @@ -0,0 +1,41 @@
>> +Broadcom Stingray PCIe PHY
>> +
>> +Required properties:
>> +- compatible: must be "brcm,sr-pcie-phy"
>> +- reg: base address and length of the PCIe SS register space
>> +- brcm,sr-cdru: phandle to the CDRU syscon node
>> +- brcm,sr-mhb: phandle to the MHB syscon node
>> +- #phy-cells: Must be 1, denotes the PHY index
>> +
>> +For PAXB based root complex, one can have a configuration of up to 8 PHYs
>> +PHY index goes from 0 to 7
>> +
>> +For the internal PAXC based root complex, PHY index is always 8
>> +
>> +Example:
>> + mhb: syscon@60401000 {
>> + compatible = "brcm,sr-mhb", "syscon";
>> + reg = <0 0x60401000 0 0x38c>;
>> + };
>> +
>> + cdru: syscon@6641d000 {
>> + compatible = "brcm,sr-cdru", "syscon";
>> + reg = <0 0x6641d000 0 0x400>;
>> + };
>> +
>> + pcie_phy: phy {
>
> Needs a unit address.
>
> With that,
>
> Reviewed-by: Rob Herring <robh@kernel.org>
>
Yes, will address that in v4 with your Reviewed-by added.
Thanks,
Ray
>> + compatible = "brcm,sr-pcie-phy";
>> + reg = <0 0x40000000 0 0x800>;
>> + brcm,sr-cdru = <&cdru>;
>> + brcm,sr-mhb = <&mhb>;
>> + #phy-cells = <1>;
>> + };
>> +
>> + /* users of the PCIe PHY */
>> +
>> + pcie0: pcie@48000000 {
>> + ...
>> + ...
>> + phys = <&pcie_phy 0>;
>> + phy-names = "pcie-phy";
>> + };
>> --
>> 2.1.4
>>
next prev parent reply other threads:[~2018-07-06 23:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-04 18:22 [PATCH v3 0/2] Add Broadcom Stingray PCIe PHY support Ray Jui
2018-07-04 18:22 ` [PATCH v3 1/2] dt-bindings: phy: Add binding doc for Stingray PCIe PHY Ray Jui
2018-07-05 23:34 ` Rob Herring
2018-07-06 23:56 ` Ray Jui [this message]
2018-07-04 18:22 ` [PATCH v3 2/2] phy: bcm-sr-pcie: Add Stingray PCIe PHY driver Ray Jui
2018-07-05 11:39 ` Kishon Vijay Abraham I
2018-07-05 16:19 ` 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=6a9c7b49-53b0-2d85-cc43-292020bf57ed@broadcom.com \
--to=ray.jui@broadcom.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh@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
Powered by JetHome