From: Rob Herring <robh@kernel.org>
To: Srinath Mannam <srinath.mannam@broadcom.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
Kishon Vijay Abraham I <kishon@ti.com>, Tejun Heo <tj@kernel.org>,
Jayachandran C <jnair@caviumnetworks.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH v3 1/3] dt-bindings: phy: Add Stingray USB PHY binding document
Date: Mon, 18 Feb 2019 11:22:21 -0600 [thread overview]
Message-ID: <20190218172221.GA20334@bogus> (raw)
In-Reply-To: <1549474347-7224-2-git-send-email-srinath.mannam@broadcom.com>
On Wed, Feb 06, 2019 at 11:02:25PM +0530, Srinath Mannam wrote:
> Add DT binding document for Stingray USB PHY.
>
> Signed-off-by: Srinath Mannam <srinath.mannam@broadcom.com>
> Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
> Reviewed-by: Scott Branden <scott.branden@broadcom.com>
> ---
> .../bindings/phy/brcm,stingray-usb-phy.txt | 62 ++++++++++++++++++++++
> 1 file changed, 62 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt b/Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt
> new file mode 100644
> index 0000000..bfe1367
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/brcm,stingray-usb-phy.txt
> @@ -0,0 +1,62 @@
> +Broadcom Stingray USB PHY
> +
> +Required properties:
> + - compatible : should be one of the listed compatibles
> + - "brcm,sr-usb-phy"
> + - "brcm,sr-usb-phy-v2"
SoC specific compatibles are preferred. Version numbers can be used but
should follow some documented scheme and be meaningful. What we don't
want is just Linux developers making up numbering.
> + - reg: offset and length of the PHY blocks registers
> + - address-cells: should be 1
> + - size-cells: should be 0
> +
> +Sub-nodes:
> + Each port's PHY should be represented as a sub-node.
> +
> +Sub-nodes required properties:
> + - reg: required for brcm,sr-usb-phy model phy.
> + reg value 0 is HS phy and 1 is SS phy.
> + - phy-cells: generic PHY binding; must be 0
> +
> +Refer to phy/phy-bindings.txt for the generic PHY binding properties
> +
> +Example:
> + usbphy0: usb-phy@0 {
> + compatible = "brcm,sr-usb-phy";
> + reg = <0x00000000 0x100>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + usb0_phy0: phy@0 {
> + reg = <0>;
> + #phy-cells = <0>;
Unless there's DT resources for each child node, you don't need these.
Just make #phy-cells 1 in the parent.
Rob
next prev parent reply other threads:[~2019-02-18 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:32 [PATCH v3 0/3] Stingray USB PHY driver support Srinath Mannam
2019-02-06 17:32 ` [PATCH v3 1/3] dt-bindings: phy: Add Stingray USB PHY binding document Srinath Mannam
2019-02-18 17:22 ` Rob Herring [this message]
2019-02-19 3:39 ` Srinath Mannam
2019-02-06 17:32 ` [PATCH v3 2/3] phy: sr-usb: Add Stingray USB PHY driver Srinath Mannam
2019-02-06 17:32 ` [PATCH v3 3/3] arm64: dts: Add USB DT nodes for Stingray SoC Srinath Mannam
2019-02-15 4:30 ` [PATCH v3 0/3] Stingray USB PHY driver support Srinath Mannam
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=20190218172221.GA20334@bogus \
--to=robh@kernel.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=jnair@caviumnetworks.com \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=srinath.mannam@broadcom.com \
--cc=tj@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;
as well as URLs for NNTP newsgroup(s).