diff options
| author |   Ketil Johnsen <ketil.johnsen@arm.com> | 2025-10-08 12:51:11 +0200 |
|---|---|---|
| committer |   Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2025-10-23 16:24:32 +0200 |
| commit | 8f3254e568b2a337e56737b4e143a5722df09b56 (patch) | |
| tree | 5990cadc348e9995e83f69111387744bd3931c4b /tools/perf/scripts/python/bin/ssh:/git@git.zx2c4.com | |
| parent | net: usb: lan78xx: fix use of improperly initialized dev->chipid in lan78xx_reset (diff) | |
drm/panthor: Ensure MCU is disabled on suspend
[ Upstream commit e07e10ae83bdf429f59c8c149173a8c4f29c481e ]
Currently the Panthor driver needs the GPU to be powered down
between suspend and resume. If this is not done, then the
MCU_CONTROL register will be preserved as AUTO, which again will
cause a premature FW boot on resume. The FW will go directly into
fatal state in this case.
This case needs to be handled as there is no guarantee that the
GPU will be powered down after the suspend callback on all platforms.
The fix is to call panthor_fw_stop() in "pre-reset" path to ensure
the MCU_CONTROL register is cleared (set DISABLE). This matches
well with the already existing call to panthor_fw_start() from the
"post-reset" path.
Signed-off-by: Ketil Johnsen <ketil.johnsen@arm.com>
Acked-by: Boris Brezillon <boris.brezillon@collabora.com>
Reviewed-by: Steven Price <steven.price@arm.com>
Fixes: 2718d91816ee ("drm/panthor: Add the FW logical block")
Signed-off-by: Steven Price <steven.price@arm.com>
Link: https://lore.kernel.org/r/20251008105112.4077015-1-ketil.johnsen@arm.com
Signed-off-by: Sasha Levin <sashal@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/bin/ssh:/git@git.zx2c4.com')
0 files changed, 0 insertions, 0 deletions