From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jani.nikula@intel.com
Subject: [PATCH 0/3] drm/i915/pch: small cleanups, refactors
Date: Fri, 7 Feb 2025 12:17:35 +0200 [thread overview]
Message-ID: <cover.1738923308.git.jani.nikula@intel.com> (raw)
The PCH detection code is a bit problematic in terms of making it
independent of i915 core code. I don't have a solution yet, but while
looking I came up with these small improvements.
BR,
Jani.
Jani Nikula (3):
drm/i915/pch: Make LPT LP a dedicated PCH type
drm/i915/pch: Hide PCH device IDs
drm/i915/pch: Remove unused i915->pch_id
.../gpu/drm/i915/display/intel_backlight.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 1 -
drivers/gpu/drm/i915/soc/intel_pch.c | 42 +++++++++++++----
drivers/gpu/drm/i915/soc/intel_pch.h | 45 +++----------------
drivers/gpu/drm/xe/xe_device_types.h | 1 -
5 files changed, 41 insertions(+), 50 deletions(-)
--
2.39.5
next reply other threads:[~2025-02-07 10:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 10:17 Jani Nikula [this message]
2025-02-07 10:17 ` [PATCH 1/3] drm/i915/pch: Make LPT LP a dedicated PCH type Jani Nikula
2025-02-11 18:12 ` Garg, Nemesa
2025-02-12 11:18 ` Jani Nikula
2025-02-07 10:17 ` [PATCH 2/3] drm/i915/pch: Hide PCH device IDs Jani Nikula
2025-02-11 18:03 ` Garg, Nemesa
2025-02-07 10:17 ` [PATCH 3/3] drm/i915/pch: Remove unused i915->pch_id Jani Nikula
2025-02-11 17:59 ` Garg, Nemesa
2025-02-07 11:36 ` ✓ CI.Patch_applied: success for drm/i915/pch: small cleanups, refactors Patchwork
2025-02-07 11:37 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-07 11:38 ` ✓ CI.KUnit: success " Patchwork
2025-02-07 11:54 ` ✓ CI.Build: " Patchwork
2025-02-07 11:56 ` ✓ CI.Hooks: " Patchwork
2025-02-07 11:58 ` ✓ CI.checksparse: " Patchwork
2025-02-07 12:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-07 16:18 ` ✗ 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=cover.1738923308.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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