linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 13/16] ARM: tegra: Fix Beaver's PCIe lane configuration
Date: Thu, 25 Jul 2013 10:53:27 -0700	[thread overview]
Message-ID: <1374774810-18459-14-git-send-email-thierry.reding@gmail.com> (raw)
In-Reply-To: <1374774810-18459-1-git-send-email-thierry.reding@gmail.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 at 1,0 {
 			status = "okay";
-			nvidia,num-lanes = <4>;
+			nvidia,num-lanes = <2>;
 		};
 
 		pci at 2,0 {
-			status = "okay";
-			nvidia,num-lanes = <1>;
+			nvidia,num-lanes = <2>;
 		};
 
 		pci at 3,0 {
-			nvidia,num-lanes = <1>;
+			status = "okay";
+			nvidia,num-lanes = <2>;
 		};
 	};
 
-- 
1.8.1.5

  parent reply	other threads:[~2013-07-25 17:53 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 17:53 [PATCH v5 00/16] Rewrite Tegra PCIe driver Thierry Reding
2013-07-25 17:53 ` [PATCH v5 01/16] ARM: tegra: Move tegra_pcie_xclk_clamp() to PMC Thierry Reding
2013-07-25 17:53 ` [PATCH v5 02/16] ARM: tegra: Move pmc.h to include/linux/tegra-pmc.h Thierry Reding
2013-07-25 17:53 ` [PATCH v5 03/16] PCI: tegra: Move PCIe driver to drivers/pci/host Thierry Reding
2013-07-25 17:53 ` [PATCH v5 04/16] ARM: tegra: tamonten: Add PCIe support Thierry Reding
2013-07-25 17:53 ` [PATCH v5 05/16] ARM: tegra: tec: " Thierry Reding
2013-07-25 17:53 ` [PATCH v5 06/16] ARM: tegra: harmony: Initialize PCIe from DT Thierry Reding
2013-07-25 17:53 ` [PATCH v5 07/16] ARM: tegra: trimslice: " Thierry Reding
2013-07-25 17:53 ` [PATCH v5 08/16] PCI: tegra: Add Tegra 30 PCIe support Thierry Reding
2013-07-25 18:00   ` Bjorn Helgaas
2013-07-25 17:53 ` [PATCH v5 09/16] PCI: tegra: set up PADS_REFCLK_CFG1 Thierry Reding
2013-07-25 18:01   ` Bjorn Helgaas
2013-07-25 17:53 ` [PATCH v5 10/16] ARM: tegra: Add Tegra30 PCIe support Thierry Reding
2013-07-25 17:53 ` [PATCH v5 11/16] ARM: tegra: Enable PCIe controller on Cardhu Thierry Reding
2013-07-25 17:53 ` [PATCH v5 12/16] ARM: tegra: Enable PCIe controller on Beaver Thierry Reding
2013-07-25 17:53 ` Thierry Reding [this message]
2013-07-25 17:53 ` [PATCH v5 14/16] ARM: tegra: Update default configuration (PCIe) Thierry Reding
2013-07-25 17:53 ` [PATCH v5 15/16] ARM: dts: tegra: Increase prefetchable PCI memory space Thierry Reding
2013-07-25 17:53 ` [PATCH v5 16/16] MAINTAINERS: Add myself as Tegra PCIe maintainer Thierry Reding

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=1374774810-18459-14-git-send-email-thierry.reding@gmail.com \
    --to=thierry.reding@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.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).