From: Thierry Reding <thierry.reding@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-pci@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: [PATCH 1/2] dt-bindings: pci: tegra: Update for per-lane PHYs
Date: Tue, 8 Mar 2016 16:48:13 +0100 [thread overview]
Message-ID: <1457452094-5409-1-git-send-email-thierry.reding@gmail.com> (raw)
From: Thierry Reding <treding@nvidia.com>
Changes to the pad controller device tree binding have required that
each lane be associated with a separate PHY. Update the PCI host bridge
device tree binding to allow each root port to define the list of PHYs
required to drive the lanes associated with it.
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
.../devicetree/bindings/pci/nvidia,tegra20-pcie.txt | 18 +++++++++++++++++-
1 file changed, 17 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
index 75321ae23c08..033fe4b5afac 100644
--- a/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
+++ b/Documentation/devicetree/bindings/pci/nvidia,tegra20-pcie.txt
@@ -60,11 +60,14 @@ Required properties:
- afi
- pcie_x
-Required properties on Tegra124 and later:
+Required properties on Tegra124 and later (deprecated):
- phys: Must contain an entry for each entry in phy-names.
- phy-names: Must include the following entries:
- pcie
+These properties are deprecated in favour of per-lane PHYs define in each of
+the root ports (see below).
+
Power supplies for Tegra20:
- avdd-pex-supply: Power supply for analog PCIe logic. Must supply 1.05 V.
- vdd-pex-supply: Power supply for digital PCIe I/O. Must supply 1.05 V.
@@ -122,6 +125,13 @@ Required properties:
- Root port 0 uses 4 lanes, root port 1 is unused.
- Both root ports use 2 lanes.
+Required properties for Tegra124 and later:
+- phys: Must contain an phandle to a PHY for each entry in phy-names.
+- phy-names: Must include an entry for each active lane. Note that the number
+ of entries does not have to (though usually will) be equal to the specified
+ number of lanes in the nvidia,num-lanes property. Entries are of the form
+ "pcie-N": where N ranges from 0 to the value specified in nvidia,num-lanes.
+
Example:
SoC DTSI:
@@ -169,6 +179,9 @@ SoC DTSI:
ranges;
nvidia,num-lanes = <2>;
+
+ phys = <&{/padctl@0,7009f000/pads/pcie/pcie-4}>;
+ phy-names = "pcie-0";
};
pci@2,0 {
@@ -183,6 +196,9 @@ SoC DTSI:
ranges;
nvidia,num-lanes = <2>;
+
+ phys = <&{/padctl@0,7009f000/pads/pcie/pcie-2}>;
+ phy-names = "pcie-0";
};
};
--
2.7.1
next reply other threads:[~2016-03-08 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 15:48 Thierry Reding [this message]
[not found] ` <1457452094-5409-1-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-08 15:48 ` [PATCH v3 2/2] PCI: tegra: Support per-lane PHYs Thierry Reding
2016-03-11 23:54 ` Bjorn Helgaas
[not found] ` <1457452094-5409-2-git-send-email-thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2016-03-16 17:01 ` Stephen Warren
[not found] ` <56E9915F.9040608-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2016-04-13 16:01 ` Thierry Reding
2016-04-13 17:01 ` Stephen Warren
2016-04-14 15:26 ` Thierry Reding
2016-04-05 17:07 ` Bjorn Helgaas
2016-03-16 16:51 ` [PATCH 1/2] dt-bindings: pci: tegra: Update for " Stephen Warren
2016-04-13 16:22 ` Thierry Reding
2016-04-13 17:04 ` Stephen Warren
2016-04-14 15:29 ` Thierry Reding
[not found] ` <20160414152905.GB3366-EkSeR96xj6Pcmrwk2tT4+A@public.gmane.org>
2016-04-18 14:48 ` Thierry Reding
2016-03-17 16:26 ` Rob Herring
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=1457452094-5409-1-git-send-email-thierry.reding@gmail.com \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=gnurou@gmail.com \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=swarren@wwwdotorg.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).