From: Rob Herring <robh@kernel.org>
To: Sergio Paracuellos <sergio.paracuellos@gmail.com>
Cc: kishon@ti.com, linux-kernel@vger.kernel.org,
driverdev-devel@linuxdriverproject.org,
devicetree@vger.kernel.org, john@phrozen.org,
linux-mips@vger.kernel.org, neil@brown.name
Subject: Re: [PATCH 2/2] dt-bindings: phy: Add binding for Mediatek MT7621 PCIe PHY
Date: Thu, 28 Mar 2019 10:42:38 -0500 [thread overview]
Message-ID: <20190328154238.GA20934@bogus> (raw)
In-Reply-To: <20190314132210.654-3-sergio.paracuellos@gmail.com>
On Thu, Mar 14, 2019 at 02:22:10PM +0100, Sergio Paracuellos wrote:
> Add bindings to describe Mediatek MT7621 PCIe PHY.
Binding should come before the driver.
>
> Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> ---
> .../bindings/phy/mediatek,mt7621-pci-phy.txt | 54 +++++++++++++++++++
> 1 file changed, 54 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.txt b/Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.txt
> new file mode 100644
> index 000000000000..8addedbe815e
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/mediatek,mt7621-pci-phy.txt
> @@ -0,0 +1,54 @@
> +Mediatek Mt7621 PCIe PHY
> +
> +Required properties:
> +- compatible: must be "mediatek,mt7621-pci-phy"
> +- reg: base address and length of the PCIe PHY block
> +- #address-cells: must be 1
> +- #size-cells: must be 0
> +
> +Each PCIe PHY should be represented by a child node
> +
> +Required properties For the child node:
> +- reg: the PHY ID
> +0 - PCIe RC 0
> +1 - PCIe RC 1
> +- #phy-cells: must be 0
> +
> +Example:
> + pcie0_phy: pcie-phy@1e149000 {
> + compatible = "mediatek,mt7621-pci-phy";
> + reg = <0x1e149000 0x0700>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pcie0_port: pcie-phy@0 {
> + reg = <0>;
> + #phy-cells = <0>;
> + };
> +
> + pcie1_port: pcie-phy@1 {
> + reg = <1>;
> + #phy-cells = <0>;
> + };
If each phy port doesn't have its own resources, then you don't need
child nodes. Just set #phy-cells to 1.
> + };
> +
> + pcie1_phy: pcie-phy@1e14a000 {
> + compatible = "mediatek,mt7621-pci-phy";
> + reg = <0x1e14a000 0x0700>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + pcie2_port: pcie-phy@0 {
> + reg = <0>;
> + #phy-cells = <0>;
> + };
> + };
> +
> + /* users of the PCIe phy */
> +
> + pcie: pcie@1e140000 {
> + ...
> + ...
> + phys = <&pcie0_port>, <&pcie1_port>, <&pcie2_port>;
> + phy-names = "pcie-phy0", "pcie-phy1", "pcie-phy2";
> + };
> --
> 2.19.1
>
next prev parent reply other threads:[~2019-03-28 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 13:22 MT7621 PCIe PHY Sergio Paracuellos
2019-03-14 13:22 ` [PATCH 1/2] phy: ralink: Add PHY driver for " Sergio Paracuellos
2019-03-14 13:22 ` [PATCH 2/2] dt-bindings: phy: Add binding for Mediatek " Sergio Paracuellos
2019-03-28 15:42 ` Rob Herring [this message]
2019-03-28 16:06 ` Sergio Paracuellos
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=20190328154238.GA20934@bogus \
--to=robh@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=john@phrozen.org \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=neil@brown.name \
--cc=sergio.paracuellos@gmail.com \
/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).