summaryrefslogtreecommitdiff
path: root/drivers/mmc/Makefile
diff options
context:
space:
mode:
authorImre Deak <imre.deak@intel.com>2024-10-25 19:02:55 +0300
committerImre Deak <imre.deak@intel.com>2024-10-31 18:10:11 +0200
commitc8081b2a8ac5aba91d75bc0ed0a442cbe568b36c (patch)
treed7f6040469f963c0ac5fbadcabfef2f55d8d3b7d /drivers/mmc/Makefile
parent5861258c4e6a829a10200b41ba3fb4d7d1a4054f (diff)
drm/i915/dp: Track source OUI validity explicitly
While updating the source OUI on the sink the driver should avoid writing the OUI if it's already up-to-date to prevent the sink from resetting itself in response to the update. On eDP - the only output type where the OUI was updated so far - the driver ensured this by comparing the current source OUI DPCD register values with the expected Intel OUI value, skipping the update in case of a match. On some non-eDP sinks - at least on Synaptics branch devices - this method doesn't work, since the source OUI DPCD registers read back as all 0, even after updating the registers. Handle the above kind of sinks by tracking when the OUI was updated and so should be valid, regardless of what the DPCD registers contain. eDP sinks reset the written source OUI value when the panel power is disabled, invalidate the OUI state accordingly. This is required by a follow-up patch updating the source OUI for non-eDP sink types as well. v2: Fix setting intel_dp::oui_valid=true, if the DPCD register contains already the expected value. Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Signed-off-by: Imre Deak <imre.deak@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20241025160259.3088727-5-imre.deak@intel.com
Diffstat (limited to 'drivers/mmc/Makefile')
0 files changed, 0 insertions, 0 deletions