From: Thierry Reding <thierry.reding@gmail.com>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Jason Cooper <jason@lakedaemon.net>,
linux-tegra@vger.kernel.org, linux-pci@vger.kernel.org
Subject: [PATCH v6 11/14] ARM: tegra: Fix Beaver's PCIe lane configuration
Date: Fri, 9 Aug 2013 16:49:29 +0200 [thread overview]
Message-ID: <1376059772-16669-12-git-send-email-treding@nvidia.com> (raw)
In-Reply-To: <1376059772-16669-1-git-send-email-treding@nvidia.com>
From: Stephen Warren <swarren@nvidia.com>
Beaver's PCIe lane configuration most closely matches x2 x2 x2 rather
than x4 x1 x1, since clocks 0 and 2 are used, and lanes 0 and 5 are used,
and the only way those align is with a x2 x2 x2 configuration.
Also, disable root port 1; there's nothing connected to it. Root port 0
is the on-board PCIe Ethernet, and port 2 is the mini-PCIe slot.
Signed-off-by: Stephen Warren <swarren@nvidia.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
---
arch/arm/boot/dts/tegra30-beaver.dts | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/arm/boot/dts/tegra30-beaver.dts b/arch/arm/boot/dts/tegra30-beaver.dts
index 4d9fa31..e1dd644 100644
--- a/arch/arm/boot/dts/tegra30-beaver.dts
+++ b/arch/arm/boot/dts/tegra30-beaver.dts
@@ -18,16 +18,16 @@
pci@1,0 {
status = "okay";
- nvidia,num-lanes = <4>;
+ nvidia,num-lanes = <2>;
};
pci@2,0 {
- status = "okay";
- nvidia,num-lanes = <1>;
+ nvidia,num-lanes = <2>;
};
pci@3,0 {
- nvidia,num-lanes = <1>;
+ status = "okay";
+ nvidia,num-lanes = <2>;
};
};
--
1.8.3.4
next prev parent reply other threads:[~2013-08-09 14:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 14:49 [PATCH v6 00/14] Rewrite Tegra PCIe driver Thierry Reding
2013-08-09 14:49 ` [PATCH v6 01/14] PCI: tegra: Move PCIe driver to drivers/pci/host Thierry Reding
2013-08-09 14:49 ` [PATCH v6 02/14] ARM: tegra: tamonten: Add PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 03/14] ARM: tegra: tec: " Thierry Reding
2013-08-09 14:49 ` [PATCH v6 04/14] ARM: tegra: harmony: Initialize PCIe from DT Thierry Reding
2013-08-09 14:49 ` [PATCH v6 05/14] ARM: tegra: trimslice: " Thierry Reding
2013-08-09 14:49 ` [PATCH v6 06/14] PCI: tegra: Add Tegra 30 PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 07/14] PCI: tegra: set up PADS_REFCLK_CFG1 Thierry Reding
2013-08-09 14:49 ` [PATCH v6 08/14] ARM: tegra: Add Tegra30 PCIe support Thierry Reding
2013-08-09 14:49 ` [PATCH v6 09/14] ARM: tegra: Enable PCIe controller on Cardhu Thierry Reding
2013-08-09 14:49 ` [PATCH v6 10/14] ARM: tegra: Enable PCIe controller on Beaver Thierry Reding
2013-08-09 14:49 ` Thierry Reding [this message]
2013-08-09 14:49 ` [PATCH v6 12/14] ARM: tegra: Update default configuration (PCIe) Thierry Reding
2013-08-09 14:49 ` [PATCH v6 13/14] ARM: dts: tegra: Increase prefetchable PCI memory space Thierry Reding
2013-08-09 14:49 ` [PATCH v6 14/14] MAINTAINERS: Add myself as Tegra PCIe maintainer Thierry Reding
2013-08-09 14:56 ` Bjorn Helgaas
2013-08-09 15:08 ` [PATCH v6 00/14] Rewrite Tegra PCIe driver Jason Cooper
2013-08-12 16:16 ` Thierry Reding
2013-08-12 16:22 ` Jason Cooper
2013-08-12 21:19 ` Stephen Warren
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=1376059772-16669-12-git-send-email-treding@nvidia.com \
--to=thierry.reding@gmail.com \
--cc=bhelgaas@google.com \
--cc=jason@lakedaemon.net \
--cc=linux-pci@vger.kernel.org \
--cc=linux-tegra@vger.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).