diff options
author | Lyude Paul <lyude@redhat.com> | 2020-08-26 14:24:54 -0400 |
---|---|---|
committer | Lyude Paul <lyude@redhat.com> | 2020-08-31 19:10:09 -0400 |
commit | f28e32d3906eac2e1cb3291b448f0d528ec93996 (patch) | |
tree | abaef9a58157a3312e09b46557a5e84e1a43e624 /drivers/gpu/drm/drm_dp_helper.c | |
parent | a4efad354cf1b9d5275adc85f67fcaaa1c2912d8 (diff) | |
download | linux-f28e32d3906eac2e1cb3291b448f0d528ec93996.tar.bz2 |
drm/nouveau/kms: Don't change EDID when it hasn't actually changed
Currently in nouveau_connector_ddc_detect() and
nouveau_connector_detect_lvds(), we start the connector probing process
by releasing the previous EDID and informing DRM of the change. However,
since commit 5186421cbfe2 ("drm: Introduce epoch counter to
drm_connector") drm_connector_update_edid_property() actually checks
whether the new EDID we've specified is different from the previous one,
and updates the connector's epoch accordingly if it is. But, because we
always set the EDID to NULL first in nouveau_connector_ddc_detect() and
nouveau_connector_detect_lvds() we end up making DRM think that the EDID
changes every single time we do a connector probe - which isn't needed.
So, let's fix this by not clearing the EDID at the start of the
connector probing process, and instead simply changing or removing it
once near the end of the probing process. This will help prevent us from
sending unneeded hotplug events to userspace when nothing has actually
changed.
Signed-off-by: Lyude Paul <lyude@redhat.com>
Reviewed-by: Ben Skeggs <bskeggs@redhat.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20200826182456.322681-19-lyude@redhat.com
Diffstat (limited to 'drivers/gpu/drm/drm_dp_helper.c')
0 files changed, 0 insertions, 0 deletions