diff options
author | Dom Cobley <popcornmix@gmail.com> | 2022-06-13 16:47:58 +0200 |
---|---|---|
committer | Maxime Ripard <maxime@cerno.tech> | 2022-06-28 14:56:16 +0200 |
commit | c94cd0620a922156c9ff9af9c3301b174b287677 (patch) | |
tree | 6daeb595d9936f40f36eec3e92149b13a8f75e90 /drivers/parport | |
parent | 0ee5a40152b15f200ed3a0d51e8aa782ea979c6a (diff) | |
download | linux-c94cd0620a922156c9ff9af9c3301b174b287677.tar.bz2 |
drm/vc4: hdmi: Force modeset when bpc or format changes
Whenever the maximum BPC is changed, vc4_hdmi_encoder_compute_config()
might pick up a different BPC or format depending on the display
capabilities.
That change will have a number of side effects, including the clock
rates and whether the scrambling is enabled.
However, only drm_crtc_state.connectors_changed will be set to true,
since that properly only affects the connector.
This means that while drm_atomic_crtc_needs_modeset() will return true,
and thus drm_atomic_helper_commit_modeset_enables() will call our
encoder atomic_enable() hook, mode_changed will be false.
So crtc_set_mode() will not call our encoder .atomic_mode_set() hook. We
use this hook in vc4 to set the vc4_hdmi_connector_state.output_bpc (and
output_format), and will then reuse the value in .atomic_enable() to select
whether or not scrambling should be enabled.
However, since our clock rate is pre-computed during .atomic_check(), we
end up with the clocks properly configured, but the scrambling disabled,
leading to a blank screen.
Let's set mode_changed to true in our HDMI driver to force the update of
output_bpc, and thus prevent the issue entirely.
Fixes: ba8c0faebbb0 ("drm/vc4: hdmi: Enable 10/12 bpc output")
Signed-off-by: Dom Cobley <popcornmix@gmail.com>
Link: https://lore.kernel.org/r/20220613144800.326124-32-maxime@cerno.tech
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
Diffstat (limited to 'drivers/parport')
0 files changed, 0 insertions, 0 deletions