From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
Cc: linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: [PATCH] ARM: tegra: add PCIe-related pins to the Jetson TK1 pinmux tables
Date: Mon, 25 Aug 2014 11:24:49 -0600 [thread overview]
Message-ID: <53FB7161.7040502@wwwdotorg.org> (raw)
In-Reply-To: <1408742308-18004-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
On 08/22/2014 03:18 PM, Stephen Warren wrote:
> From: Stephen Warren <swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
>
> 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).
I've applied this to Tegra's for-3.18/dt branch.
prev parent reply other threads:[~2014-08-25 17:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-22 21:18 [PATCH] ARM: tegra: add PCIe-related pins to the Jetson TK1 pinmux tables Stephen Warren
[not found] ` <1408742308-18004-1-git-send-email-swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2014-08-25 10:32 ` Andreas Färber
[not found] ` <53FB10B8.3010408-l3A5Bk7waGM@public.gmane.org>
2014-08-25 10:55 ` Mikko Perttunen
[not found] ` <53FB160F.6000700-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-08-25 12:10 ` Mikko Perttunen
[not found] ` <53FB27AB.8010608-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2014-08-26 22:26 ` Andreas Färber
[not found] ` <53FD0980.2010803-l3A5Bk7waGM@public.gmane.org>
2014-08-27 5:52 ` Thierry Reding
2014-08-27 13:29 ` Andreas Färber
2014-08-25 17:24 ` Stephen Warren [this message]
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=53FB7161.7040502@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=swarren-DDmLM1+adcrQT0dZR+AlfA@public.gmane.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