diff options
| author | Jon Hunter <jonathanh@nvidia.com> | 2018-07-03 09:59:47 +0100 |
|---|---|---|
| committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2018-09-09 20:01:23 +0200 |
| commit | ba99ff79ac84a768cc9163897ec6b616bd14858f (patch) | |
| tree | e4f099707e2d0517a35de75a20a061572b2ff2a1 /certs | |
| parent | b5bc39d4ffb53b0fb335d96d3abf1a4585019c0a (diff) | |
| download | linux-stable-ba99ff79ac84a768cc9163897ec6b616bd14858f.tar.gz linux-stable-ba99ff79ac84a768cc9163897ec6b616bd14858f.tar.bz2 linux-stable-ba99ff79ac84a768cc9163897ec6b616bd14858f.zip | |
ARM: tegra: Fix Tegra30 Cardhu PCA954x reset
commit 6e1811900b6fe6f2b4665dba6bd6ed32c6b98575 upstream.
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>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions