From mboxrd@z Thu Jan 1 00:00:00 1970 From: mperttunen@nvidia.com (Mikko Perttunen) Date: Mon, 25 Aug 2014 15:10:19 +0300 Subject: [PATCH] ARM: tegra: add PCIe-related pins to the Jetson TK1 pinmux tables In-Reply-To: <53FB160F.6000700@nvidia.com> References: <1408742308-18004-1-git-send-email-swarren@wwwdotorg.org> <53FB10B8.3010408@suse.de> <53FB160F.6000700@nvidia.com> Message-ID: <53FB27AB.8010608@nvidia.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org .. and apparently the device tree patches are in staging/tegra. On 25/08/14 13:55, Mikko Perttunen wrote: > On 25/08/14 13:32, Andreas F?rber wrote: >> Hi Stephen, >> >> Am 22.08.2014 23:18, schrieb Stephen Warren: >>> From: Stephen Warren >>> >>> This pinmux tables currently omit any configuration for PCIe clk_req, >>> wake, and rst pins, which in turn causes intermittent failures in >>> U-Boot's PCIe support. Import an updated version of the pinmux tables >>> which rectifies this. >>> >>> (While I'm still hoping to remove the pinmux tables from DTs for >>> Tegra124+ devices, while they're still here, they may as well be >>> complete and correct). >>> >>> Signed-off-by: Stephen Warren >>> --- >>> arch/arm/boot/dts/tegra124-jetson-tk1.dts | 35 >>> +++++++++++++++++++++++++++++++ >>> 1 file changed, 35 insertions(+) >> >> I've tested this patch on both -rc1 and yesterday's torvalds/linux.git >> with tegra_defconfig: Both with or without this patch I get empty lspci >> output. >> >> There doesn't seem to be a tegra/linux.git for-next branch based on -rc1 >> yet - are patches from other subsystem trees needed to get the on-board >> Ethernet detected or maybe some config option? > > git://gitorious.org/thierryreding/linux.git staging/pci > >> >> Or did you test PCIe via the on-board slot? >> >> I used U-Boot v2014.07, in case it matters. >> >> Thanks, >> Andreas >> > > Cheers, > Mikko > -- > To unsubscribe from this list: send the line "unsubscribe linux-tegra" in > the body of a message to majordomo at vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html