diff options
| author | Gustavo Sousa <gustavo.sousa@intel.com> | 2025-01-13 17:38:56 -0300 |
|---|---|---|
| committer | Gustavo Sousa <gustavo.sousa@intel.com> | 2025-01-17 08:33:53 -0300 |
| commit | 58b7cd603db38d16350d380df70dbce468e99101 (patch) | |
| tree | d3143018310f725b296407a0c18cf9391e631b36 /tools/lib/python/kdoc | |
| parent | 0d69fc7a023b8a979fc8b2bd9cd0754a24abf99d (diff) | |
| download | linux-58b7cd603db38d16350d380df70dbce468e99101.tar.gz linux-58b7cd603db38d16350d380df70dbce468e99101.zip | |
drm/i915/display: Use display MMIO functions in intel_display_irq.c
Most of MMIO accesses from intel_display_irq.c are currently done via
uncore_*() functions instead of the display-specific ones, namely
intel_de_*(). Because of that, DMC wakelock ends up being ignored and
some invalid MMIO accesses are performed while display is in dynamic DC
states. Thus, update the display IRQ code to use the intel_de_*() MMIO
functions.
After this change, we are left with some IRQ-specific functions that
still use the unwrapped uncore_*() functions (i.e. gen2_irq_init,
gen3_irq_reset and gen2_assert_iir_is_zero). We will deal with them in
an upcoming change.
Reviewed-by: Jouni Högander <jouni.hogander@intel.com>
Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20250113204306.112266-2-gustavo.sousa@intel.com
Diffstat (limited to 'tools/lib/python/kdoc')
0 files changed, 0 insertions, 0 deletions