From: Stephen Warren <swarren@wwwdotorg.org>
To: Alexandre Courbot <acourbot@nvidia.com>,
Thierry Reding <thierry.reding@gmail.com>
Cc: linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
gnurou@gmail.com
Subject: Re: [PATCH 0/2] ARM: tegra: roth: pinmux fixes
Date: Fri, 27 Jun 2014 16:08:31 -0600 [thread overview]
Message-ID: <53ADEB5F.5030502@wwwdotorg.org> (raw)
In-Reply-To: <1403508779-25896-1-git-send-email-acourbot@nvidia.com>
On 06/23/2014 01:32 AM, Alexandre Courbot wrote:
> Two small but important fixes to SHIELD's pinmux configuration.
> The use of invalid properties caused the pinmux to not be applied
> at all. Also the setting for sdmmc clock lines resulted in random
> errors or even the impossibility to probe attached devices.
>
> Alexandre Courbot (2):
> ARM: tegra: roth: fix unsupported pinmux properties
> ARM: tegra: roth: enable input on mmc clock pins
The series, applied to Tegra's for-3.17/dt branch.
Sorry for the delay; I'd forgotten that our internal discussion resolved
my questions about patch 2.
Still looking forward to internal bugs files against the Jetson TK1 and
Venice2 board pinmux spreadsheets for the same issue:-)
next prev parent reply other threads:[~2014-06-27 22:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-23 7:32 [PATCH 0/2] ARM: tegra: roth: pinmux fixes Alexandre Courbot
2014-06-23 7:32 ` [PATCH 1/2] ARM: tegra: roth: fix unsupported pinmux properties Alexandre Courbot
2014-06-23 7:32 ` [PATCH 2/2] ARM: tegra: roth: enable input on mmc clock pins Alexandre Courbot
2014-06-23 19:01 ` Stephen Warren
2014-06-24 5:44 ` Alexandre Courbot
2014-06-24 15:53 ` Stephen Warren
2014-06-23 18:46 ` [PATCH 0/2] ARM: tegra: roth: pinmux fixes Stephen Warren
2014-06-24 3:57 ` Alexandre Courbot
2014-06-27 22:08 ` Stephen Warren [this message]
2014-06-29 4:27 ` Alexandre Courbot
2014-06-30 15:46 ` 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=53ADEB5F.5030502@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=acourbot@nvidia.com \
--cc=gnurou@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
/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