Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>,
	"Jani Nikula" <jani.nikula@intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>
Subject: [Intel-xe] [PATCH v2 0/4] Xe runtime pm refactoring
Date: Thu, 21 Sep 2023 14:14:30 +0300	[thread overview]
Message-ID: <20230921111434.3051325-1-jouni.hogander@intel.com> (raw)

These patches are dropping some ifdefs added to build Xe runtime pm
code.

v2:
  - Remove xe_runtime_pm completely from DRM driver patch
  - Add xe_runtime_pm struct pointer to xe_device in display fixup
  - Add define (xe_runtime_pm -> intel_runtime_pm) instead of rename

Cc: Jani Nikula <jani.nikula@intel.com>
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Vinod Govindapillai <vinod.govindapillai@intel.com>

Jouni Högander (4):
  Revert "FIXME: drm/i915: runtime pm changes"
  drm/i915: Remove runtime suspended boolean from intel_runtime_pm
    struct
  fixup! drm/xe: Introduce a new DRM driver for Intel GPUs
  fixup! drm/xe/display: Implement display support

 .../drm/i915/display/intel_display_power.c    | 25 ++++++++++---------
 drivers/gpu/drm/i915/i915_driver.c            |  3 ---
 drivers/gpu/drm/i915/i915_gpu_error.c         |  2 +-
 drivers/gpu/drm/i915/intel_runtime_pm.c       |  1 -
 drivers/gpu/drm/i915/intel_runtime_pm.h       |  4 +--
 .../xe/compat-i915-headers/intel_runtime_pm.h |  2 ++
 6 files changed, 18 insertions(+), 19 deletions(-)

-- 
2.34.1


             reply	other threads:[~2023-09-21 11:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21 11:14 Jouni Högander [this message]
2023-09-21 11:14 ` [Intel-xe] [PATCH v2 1/4] Revert "FIXME: drm/i915: runtime pm changes" Jouni Högander
2023-09-21 11:14 ` [Intel-xe] [PATCH v2 2/4] drm/i915: Remove runtime suspended boolean from intel_runtime_pm struct Jouni Högander
2023-09-21 11:14 ` [Intel-xe] [PATCH v2 3/4] fixup! drm/xe: Introduce a new DRM driver for Intel GPUs Jouni Högander
2023-09-21 16:28   ` Rodrigo Vivi
2023-09-21 11:14 ` [Intel-xe] [PATCH v2 4/4] fixup! drm/xe/display: Implement display support Jouni Högander
2023-09-21 11:17 ` [Intel-xe] ✓ CI.Patch_applied: success for Xe runtime pm refactoring (rev2) Patchwork
2023-09-21 11:17 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-21 11:18 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-21 11:25 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-21 11:26 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-21 11:27 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-21 12:02 ` [Intel-xe] ✗ CI.BAT: failure " Patchwork
2023-09-21 16:28 ` [Intel-xe] [PATCH v2 0/4] Xe runtime pm refactoring Rodrigo Vivi
2023-09-25  5:38   ` Hogander, Jouni
2023-09-22  5:50 ` [Intel-xe] ✓ CI.Patch_applied: success for Xe runtime pm refactoring (rev3) Patchwork
2023-09-22  5:51 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-09-22  5:52 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-09-22  5:59 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-09-22  5:59 ` [Intel-xe] ✓ CI.Hooks: " Patchwork
2023-09-22  6:01 ` [Intel-xe] ✗ CI.checksparse: warning " Patchwork
2023-09-22  6:35 ` [Intel-xe] ✓ CI.BAT: success " 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=20230921111434.3051325-1-jouni.hogander@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=rodrigo.vivi@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