summaryrefslogtreecommitdiffstats
path: root/drivers
diff options
context:
space:
mode:
authorDmitry Osipenko <digetx@gmail.com>2019-04-12 01:12:50 +0300
committerThierry Reding <treding@nvidia.com>2019-04-18 11:36:24 +0200
commita359de1b4055b2e9c0e8d650b099fcb5ceca25fe (patch)
tree363246f1f3716ca9f9d0c5bdcd946406feb7d50c /drivers
parent48791f972234301a72e4c40745d0abafa0985d2d (diff)
downloadlinux-stable-a359de1b4055b2e9c0e8d650b099fcb5ceca25fe.tar.gz
linux-stable-a359de1b4055b2e9c0e8d650b099fcb5ceca25fe.tar.bz2
linux-stable-a359de1b4055b2e9c0e8d650b099fcb5ceca25fe.zip
Revert "ARM: tegra: Restore memory arbitration on resume from LP1 on Tegra30+"
Turned out that the actual bug was in the Memory Controller driver that programmed shadowed registers without latching the new values and then there was a bug on EMEM arbitration configuration calculation that results in a wrong value being latched on resume from suspend. The Memory Controller has been fixed properly now, hence the workaround patch could be reverted safely. Signed-off-by: Dmitry Osipenko <digetx@gmail.com> Signed-off-by: Thierry Reding <treding@nvidia.com>
Diffstat (limited to 'drivers')
0 files changed, 0 insertions, 0 deletions