From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Paul Kocialkowski <contact@paulk.fr>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
Mikko Perttunen <cyndis@kapsi.fi>, Peter Rosin <peda@axentia.se>
Subject: Re: [PATCH v2 5/6] ARM: tegra: nyan-big: Proper pinmux for TPM i2c
Date: Wed, 25 Jan 2017 12:16:29 +0100 [thread overview]
Message-ID: <20170125111629.GI9344@ulmo.ba.sec> (raw)
In-Reply-To: <2710b1a1-eab5-0a0d-657f-e6bc9b5cefaa@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1165 bytes --]
On Wed, Jan 25, 2017 at 11:10:56AM +0000, Jon Hunter wrote:
>
> On 25/01/17 11:06, Thierry Reding wrote:
> > * PGP Signed by an unknown key
> >
> > On Sun, Jan 22, 2017 at 04:47:52PM +0100, Paul Kocialkowski wrote:
> >> This corrects the pinmux for accessing the TPM over the i2c line.
> >> Thus, it allows correctly probing the module, that previously failed with i2c
> >> errors.
> >>
> >> Signed-off-by: Paul Kocialkowski <contact@paulk.fr>
> >> ---
> >> arch/arm/boot/dts/tegra124-nyan-big.dts | 20 ++++++++++----------
> >> 1 file changed, 10 insertions(+), 10 deletions(-)
> >
> > I've applied an s/i2c/I2C/ in the commit message and applied this. Can
> > you also make sure that these changes go into the nyan-big configuration
> > of the tegra-pinmux-scripts[0]? I know Stephen wants to keep those in
> > sync with the DTS.
> >
> > Thanks,
> > Thierry
> >
> > [0]: https://github.com/NVIDIA/tegra-pinmux-scripts
>
> Looks like it has already been changed ...
>
> https://github.com/NVIDIA/tegra-pinmux-scripts/commit/5049f75b3099515ffb7f064dcf23568c17aecb01
Excellent, no need for any further action then.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-01-25 11:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 15:47 [PATCH v2 1/6] ARM: tegra: nyan: Use proper IRQ type definitions Paul Kocialkowski
2017-01-22 15:47 ` [PATCH v2 2/6] ARM: tegra: nyan: Use external control for bq24735 charger Paul Kocialkowski
2017-01-25 10:59 ` Thierry Reding
2017-01-25 11:01 ` Paul Kocialkowski
2017-01-22 15:47 ` [PATCH v2 3/6] ARM: tegra: nyan-big: Include compatible revisions for proper detection Paul Kocialkowski
2017-01-25 11:02 ` Thierry Reding
2017-01-25 11:08 ` Paul Kocialkowski
2017-01-25 11:14 ` Thierry Reding
2017-01-25 11:19 ` Paul Kocialkowski
2017-01-22 15:47 ` [PATCH v2 4/6] ARM: tegra: nyan-blaze: " Paul Kocialkowski
2017-01-25 11:04 ` Thierry Reding
2017-01-22 15:47 ` [PATCH v2 5/6] ARM: tegra: nyan-big: Proper pinmux for TPM i2c Paul Kocialkowski
2017-01-25 11:06 ` Thierry Reding
2017-01-25 11:10 ` Jon Hunter
2017-01-25 11:16 ` Thierry Reding [this message]
2017-01-22 15:47 ` [PATCH v2 6/6] ARM: tegra: nyan-blaze: " Paul Kocialkowski
2017-01-25 11:09 ` Thierry Reding
2017-01-25 10:58 ` [PATCH v2 1/6] ARM: tegra: nyan: Use proper IRQ type definitions 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=20170125111629.GI9344@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=contact@paulk.fr \
--cc=cyndis@kapsi.fi \
--cc=devicetree@vger.kernel.org \
--cc=gnurou@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=peda@axentia.se \
--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).