diff options
| author | Marek Szyprowski <m.szyprowski@samsung.com> | 2018-05-16 11:42:39 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2018-05-17 07:27:08 +0300 |
| commit | e935dba111621bd6a0c5d48e6511a4d9885103b4 (patch) | |
| tree | f8252697e6b87805e10e2c3dc1ffb55f1f891494 /virt | |
| parent | b6456057038b572382753b5e963f56f10e704804 (diff) | |
| download | linux-e935dba111621bd6a0c5d48e6511a4d9885103b4.tar.xz | |
spi: spi-s3c64xx: Fix system resume support
Since Linux v4.10 release (commit 1d9174fbc55e "PM / Runtime: Defer
resuming of the device in pm_runtime_force_resume()"),
pm_runtime_force_resume() function doesn't runtime resume device if it was
not runtime active before system suspend. Thus, driver should not do any
register access after pm_runtime_force_resume() without checking the
runtime status of the device. To fix this issue, simply move
s3c64xx_spi_hwinit() call to s3c64xx_spi_runtime_resume() to ensure that
hardware is always properly initialized. This fixes Synchronous external
abort issue on system suspend/resume cycle on newer Exynos SoCs.
Signed-off-by: Marek Szyprowski <m.szyprowski@samsung.com>
Reviewed-by: Krzysztof Kozlowski <krzk@kernel.org>
Signed-off-by: Mark Brown <broonie@kernel.org>
Cc: stable@vger.kernel.org
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions