From: Thierry Reding <thierry.reding@gmail.com>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, stable@vger.kernel.org
Subject: Re: [PATCH] ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
Date: Mon, 9 Jul 2018 16:01:10 +0200 [thread overview]
Message-ID: <20180709140110.GA18353@ulmo> (raw)
In-Reply-To: <1530608387-9591-1-git-send-email-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1177 bytes --]
On Tue, Jul 03, 2018 at 09:59:47AM +0100, Jon Hunter wrote:
> On all versions of Tegra30 Cardhu, the reset signal to the NXP PCA9546
> I2C mux is connected to the Tegra GPIO BB0. Currently, this pin on the
> Tegra is not configured as a GPIO but as a special-function IO (SFIO)
> that is multiplexing the pin to an I2S controller. On exiting system
> suspend, I2C commands sent to the PCA9546 are failing because there is
> no ACK. Although it is not possible to see exactly what is happening
> to the reset during suspend, by ensuring it is configured as a GPIO
> and driven high, to de-assert the reset, the failures are no longer
> seen.
>
> Please note that this GPIO is also used to drive the reset signal
> going to the camera connector on the board. However, given that there
> is no camera support currently for Cardhu, this should not have any
> impact.
>
> Fixes: 40431d16ff11 ("ARM: tegra: enable PCA9546 on Cardhu")
>
> Cc: stable@vger.kernel.org
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> arch/arm/boot/dts/tegra30-cardhu.dtsi | 1 +
> 1 file changed, 1 insertion(+)
Applied to for-4.19/arm/dt, thanks.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2018-07-09 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 8:59 [PATCH] ARM: tegra: Fix Tegra30 Cardhu PCA954x reset Jon Hunter
2018-07-09 14:01 ` Thierry Reding [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=20180709140110.GA18353@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.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).