From: Simon Richter <Simon.Richter@hogyros•de>
To: linux-kernel@vger•kernel.org, linux-next@vger•kernel.org
Cc: Simon Richter <Simon.Richter@hogyros•de>,
Alexander Usyskin <alexander.usyskin@intel•com>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>
Subject: [PATCH v2 0/4] Intel MEI Kconfig cleanups
Date: Thu, 8 Jan 2026 03:26:01 +0900 [thread overview]
Message-ID: <20260107182615.488194-1-Simon.Richter@hogyros.de> (raw)
In-Reply-To: <20260107174646.GA1230850@psionic12.psi5.com>
Hi,
this enables GPU firmware updates on Intel dGPUs plugged into non-x86
machines. The most important patches are the first and last.
The second patch switches the ME interfaces for GPUs to use !=n tests, so
it is possible for them to be builtins when the GPU drivers themselves are
modules (as is likely). MEI is built-in by default on x86_64 (and Atom).
This might need some discussion what is desirable here:
- this is a strong dependency from an "early" directory (misc/mei) to a
later one (gpu/drm), causing backtracking
- does it make sense for MEI to be built-in by default, or should it
default to being a module?
- is the strong dependency desired because if the code is compiled as
built-in, it will not be used until the module is loaded?
There is no strong functional dependency here, no symbol references, as
these devices are enumerated over an auxiliary bus.
Also, enable building without the GPU drivers for compile testing.
No stable backport.
Simon
Simon Richter (4):
misc/mei: Allow building Intel ME interface on non-x86
misc/mei: Decouple ME interfaces from GPU drivers
misc/mei: Allow building standalone for compile testing
misc/mei: gsc_proxy: add dependency on Xe driver
drivers/misc/mei/Kconfig | 6 +++---
drivers/misc/mei/gsc_proxy/Kconfig | 2 +-
drivers/misc/mei/hdcp/Kconfig | 2 +-
drivers/misc/mei/pxp/Kconfig | 2 +-
4 files changed, 6 insertions(+), 6 deletions(-)
base-commit: f8f9c1f4d0c7a64600e2ca312dec824a0bc2f1da
--
2.47.3
next parent reply other threads:[~2026-01-07 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260107174646.GA1230850@psionic12.psi5.com>
2026-01-07 18:26 ` Simon Richter [this message]
2026-01-07 18:26 ` [PATCH v2 1/4] misc/mei: Allow building Intel ME interface on non-x86 Simon Richter
2026-01-07 18:26 ` [PATCH v2 2/4] misc/mei: Decouple ME interfaces from GPU drivers Simon Richter
2026-01-07 18:26 ` [PATCH v2 3/4] misc/mei: Allow building standalone for compile testing Simon Richter
2026-01-07 18:26 ` [PATCH v2 4/4] misc/mei: gsc_proxy: add dependency on Xe driver Simon Richter
2026-01-13 7:09 ` [PATCH v2 0/4] Intel MEI Kconfig cleanups Usyskin, Alexander
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=20260107182615.488194-1-Simon.Richter@hogyros.de \
--to=simon.richter@hogyros$(echo .)de \
--cc=alexander.usyskin@intel$(echo .)com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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