Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Jani Nikula" <jani.nikula@intel.com>
Subject: [PATCH v3 0/3] Improve type-safety on POWER_DOMAIN_*() macros
Date: Mon, 17 Feb 2025 17:34:25 -0300	[thread overview]
Message-ID: <20250217203722.87152-1-gustavo.sousa@intel.com> (raw)

Fix one issue[1] reported by the kernel test robot and also take this
opportunity to improve POWER_DOMAIN_*() macros by making them explicitly
return the expected enum type with patch #2 and then turning them into function
with #3.

Patch #3 could be squashed into #2, but I'll defer that to reviewers to provide
their input.

[1] https://lore.kernel.org/oe-kbuild-all/202502120809.XfmcqkBD-lkp@intel.com/

Gustavo Sousa (3):
  drm/i915/display: Use explicit base values in POWER_DOMAIN_*() macros
  drm/i915/display: Make POWER_DOMAIN_*() always result in enum
    intel_display_power_domain
  drm/i915/display: Convert POWER_DOMAIN_*() to functions

 drivers/gpu/drm/i915/display/i9xx_plane.c     |  2 +-
 drivers/gpu/drm/i915/display/intel_cmtg.c     |  2 +-
 drivers/gpu/drm/i915/display/intel_cursor.c   |  4 +-
 drivers/gpu/drm/i915/display/intel_ddi.c      | 10 ++---
 drivers/gpu/drm/i915/display/intel_display.c  | 39 ++++++++++++-------
 .../gpu/drm/i915/display/intel_display_irq.c  | 18 +++++----
 .../drm/i915/display/intel_display_power.c    | 21 ++++++++++
 .../drm/i915/display/intel_display_power.h    | 15 +++----
 drivers/gpu/drm/i915/display/intel_pipe_crc.c |  2 +-
 drivers/gpu/drm/i915/display/intel_sprite.c   |  6 +--
 drivers/gpu/drm/i915/display/intel_vdsc.c     |  3 +-
 .../drm/i915/display/skl_universal_plane.c    |  2 +-
 drivers/gpu/drm/i915/display/skl_watermark.c  |  2 +-
 13 files changed, 82 insertions(+), 44 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-02-17 20:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 20:34 Gustavo Sousa [this message]
2025-02-17 20:34 ` [PATCH v3 1/3] drm/i915/display: Use explicit base values in POWER_DOMAIN_*() macros Gustavo Sousa
2025-02-17 21:01   ` Ville Syrjälä
2025-02-17 20:34 ` [PATCH v3 2/3] drm/i915/display: Make POWER_DOMAIN_*() always result in enum intel_display_power_domain Gustavo Sousa
2025-02-17 21:01   ` Ville Syrjälä
2025-02-17 20:34 ` [PATCH v3 3/3] drm/i915/display: Convert POWER_DOMAIN_*() to functions Gustavo Sousa
2025-02-17 20:46   ` Ville Syrjälä
2025-02-17 21:25     ` Gustavo Sousa
2025-02-17 20:53 ` ✓ CI.Patch_applied: success for Improve type-safety on POWER_DOMAIN_*() macros (rev3) Patchwork
2025-02-17 20:53 ` ✓ CI.checkpatch: " Patchwork
2025-02-17 20:54 ` ✓ CI.KUnit: " Patchwork
2025-02-17 21:10 ` ✓ CI.Build: " Patchwork
2025-02-17 21:13 ` ✓ CI.Hooks: " Patchwork
2025-02-17 21:14 ` ✓ CI.checksparse: " Patchwork
2025-02-17 21:34 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-18 14:45 ` ✗ Xe.CI.Full: failure " Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20250217203722.87152-1-gustavo.sousa@intel.com \
    --to=gustavo.sousa@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=ville.syrjala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox