diff options
| author | Gustavo Sousa <[email protected]> | 2025-02-27 21:09:12 +0000 |
|---|---|---|
| committer | Gustavo Sousa <[email protected]> | 2025-02-28 16:30:57 +0000 |
| commit | 322ec93e9081d717fbc02c14fe80f754709e8b9c (patch) | |
| tree | 7eef9fca31f08939595ac101b65b548c2ab3ecef /drivers/gpu/drm/i915/display/intel_dp_mst.c | |
| parent | drm/i915/audio: Extend Wa_14020863754 to Xe3_LPD (diff) | |
| download | kernel-322ec93e9081d717fbc02c14fe80f754709e8b9c.tar.gz kernel-322ec93e9081d717fbc02c14fe80f754709e8b9c.zip | |
drm/i915/display: Use explicit base values in POWER_DOMAIN_*() macros
Although we have comments in intel_display_limits.h saying that the
code expects PIPE_A and TRANSCODER_A to be zero, it doesn't hurt to add
them as explicit base values for calculating the power domain offset in
POWER_DOMAIN_*() macros.
On the plus side, we have that this:
* Fixes a warning reported by kernel test robot <[email protected]>
about doing arithmetic with two different enum types.
* Makes the code arguably more robust (in the unlikely event of those
bases becoming non-zero).
v2:
- Prefer using explicit base values instead of simply casting the
macro argument to int. (Ville)
- Update commit message to match the new approach (for reference, the
old message subject was "drm/i915/display: Use explicit cast in
POWER_DOMAIN_*() macros").
Reported-by: kernel test robot <[email protected]>
Closes: https://lore.kernel.org/oe-kbuild-all/[email protected]/
Reviewed-by: Ville Syrjälä <[email protected]>
Link: https://patchwork.freedesktop.org/patch/msgid/20250227-improve-type-safey-power-domain-macros-v3-1-b6eaa00f9c33@intel.com
Signed-off-by: Gustavo Sousa <[email protected]>
Diffstat (limited to 'drivers/gpu/drm/i915/display/intel_dp_mst.c')
0 files changed, 0 insertions, 0 deletions
