mirror of
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git
synced 2024-10-11 19:19:42 +00:00
5f9e93fed4
Calling request_irq() followed by disable_irq() is usually a bad idea, specially if the interrupt can be pending, and you're not yet in a position to handle it. This is exactly what happens on my kevin system when rebooting in a second kernel using kexec: Some interrupt is left pending from the previous kernel, and we take it too early, before disable_irq() could do anything. Let's clear the pending interrupts as we initialize the HW, and move the interrupt request after that point. This ensures that we're in a sane state when the interrupt is requested. Cc: stable@vger.kernel.org Signed-off-by: Marc Zyngier <marc.zyngier@arm.com> [adapted to recent rockchip-drm changes] Signed-off-by: Heiko Stuebner <heiko@sntech.de> Link: https://patchwork.freedesktop.org/patch/msgid/20180220130120.5254-2-marc.zyngier@arm.com |
||
|---|---|---|
| .. | ||
| analogix_dp-rockchip.c | ||
| cdn-dp-core.c | ||
| cdn-dp-core.h | ||
| cdn-dp-reg.c | ||
| cdn-dp-reg.h | ||
| dw-mipi-dsi.c | ||
| dw_hdmi-rockchip.c | ||
| inno_hdmi.c | ||
| inno_hdmi.h | ||
| Kconfig | ||
| Makefile | ||
| rockchip_drm_drv.c | ||
| rockchip_drm_drv.h | ||
| rockchip_drm_fb.c | ||
| rockchip_drm_fb.h | ||
| rockchip_drm_fbdev.c | ||
| rockchip_drm_fbdev.h | ||
| rockchip_drm_gem.c | ||
| rockchip_drm_gem.h | ||
| rockchip_drm_psr.c | ||
| rockchip_drm_psr.h | ||
| rockchip_drm_vop.c | ||
| rockchip_drm_vop.h | ||
| rockchip_lvds.c | ||
| rockchip_lvds.h | ||
| rockchip_vop_reg.c | ||
| rockchip_vop_reg.h | ||