mirror of
https://git.proxmox.com/git/mirror_ubuntu-kernels.git
synced 2025-11-25 12:44:01 +00:00
da94e9c64c
We recently introduced a new mutex to protect concurrent execution of ALSA and KMS hooks, and the concurrent access to some of vc4_hdmi fields. However, using it in the detect hook was creating a reentrency issue with CEC code. Indeed, calling cec_s_phys_addr_from_edid from detect might call the CEC adap_enable hook with the lock held, eventually resulting in a deadlock. Since we didn't really need to protect anything at the moment in the CEC code, the decision was made to ignore the mutex in those CEC hooks, working around the issue. However, we can have the same thing happening if we end up triggering a mode set from the detect callback, for example using drm_atomic_helper_connector_hdmi_reset_link(). Since we don't really need to protect anything in detect either, let's just drop the lock in detect, and add it again in CEC. Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Maxime Ripard <maxime@cerno.tech> Link: https://lore.kernel.org/r/20220829134731.213478-4-maxime@cerno.tech |
||
|---|---|---|
| .. | ||
| Kconfig | ||
| Makefile | ||
| vc4_bo.c | ||
| vc4_crtc.c | ||
| vc4_debugfs.c | ||
| vc4_dpi.c | ||
| vc4_drv.c | ||
| vc4_drv.h | ||
| vc4_dsi.c | ||
| vc4_fence.c | ||
| vc4_gem.c | ||
| vc4_hdmi_phy.c | ||
| vc4_hdmi_regs.h | ||
| vc4_hdmi.c | ||
| vc4_hdmi.h | ||
| vc4_hvs.c | ||
| vc4_irq.c | ||
| vc4_kms.c | ||
| vc4_packet.h | ||
| vc4_perfmon.c | ||
| vc4_plane.c | ||
| vc4_qpu_defines.h | ||
| vc4_regs.h | ||
| vc4_render_cl.c | ||
| vc4_trace_points.c | ||
| vc4_trace.h | ||
| vc4_txp.c | ||
| vc4_v3d.c | ||
| vc4_validate_shaders.c | ||
| vc4_validate.c | ||
| vc4_vec.c | ||