drm/etnaviv: keep MMU context across runtime suspend/resume
stable inclusion from stable-5.10.68 commit 6b1c223d8a53a9b08f06c65d932eeb3278022ee8 bugzilla: 182671 https://gitee.com/openeuler/kernel/issues/I4EWUH Reference: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=6b1c223d8a53a9b08f06c65d932eeb3278022ee8 -------------------------------- commit 8f3eea9d upstream. The MMU state may be kept across a runtime suspend/resume cycle, as we avoid a full hardware reset to keep the latency of the runtime PM small. Don't pretend that the MMU state is lost in driver state. The MMU context is pushed out when new HW jobs with a different context are coming in. The only exception to this is when the GPU is unbound, in which case we need to make sure to also free the last active context. Cc: stable@vger.kernel.org # 5.4 Reported-by: NMichael Walle <michael@walle.cc> Signed-off-by: NLucas Stach <l.stach@pengutronix.de> Tested-by: NMichael Walle <michael@walle.cc> Tested-by: NMarek Vasut <marex@denx.de> Reviewed-by: NChristian Gmeiner <christian.gmeiner@gmail.com> Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org> Signed-off-by: NChen Jun <chenjun102@huawei.com> Acked-by: NWeilong Chen <chenweilong@huawei.com> Signed-off-by: NChen Jun <chenjun102@huawei.com> Signed-off-by: NZheng Zengkai <zhengzengkai@huawei.com>
Showing
想要评论请 注册 或 登录