From: "Arnd Bergmann" <arnd@arndb.de>
To: "Alexander Usyskin" <alexander.usyskin@intel.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
"Simon Richter" <Simon.Richter@hogyros.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
Date: Wed, 28 Jan 2026 08:24:08 +0100 [thread overview]
Message-ID: <96fb5e3f-7855-4fe6-b263-60bc132716d3@app.fastmail.com> (raw)
In-Reply-To: <CY5PR11MB636685688893B7873C3BE85AED91A@CY5PR11MB6366.namprd11.prod.outlook.com>
On Wed, Jan 28, 2026, at 07:57, Usyskin, Alexander wrote:
>> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>> As far as I can tell, i915 and xe will attempt (and fail) to
>> use MEI if that is enabled, so there is no point in enabling
>> INTEL_MEI outside of compile-testing even if XE is built.
>>
>
> There are different usages of mei:
> - for discrete graphics xe/i915 will load mei via auxiliary device also
> on non x86.
Right, I see.
> - for integrated xe/i915 communicate with mei for on-chip CSME - this
> scenario is x86 only.
>
> IMO this should cover all:
> depends on X86 || DRM_XE!=n || DRM_I915!=n || COMPILE_TEST
Ok
Arnd
next prev parent reply other threads:[~2026-01-28 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-27 19:11 Geert Uytterhoeven
2026-01-28 6:41 ` Usyskin, Alexander
2026-01-28 6:50 ` Arnd Bergmann
2026-01-28 6:57 ` Usyskin, Alexander
2026-01-28 7:24 ` Arnd Bergmann [this message]
2026-01-29 4:45 ` Simon Richter
2026-01-29 5:53 ` Usyskin, Alexander
2026-01-30 21:15 ` Rodrigo Vivi
2026-02-01 10:15 ` Usyskin, Alexander
2026-02-02 9:33 ` Geert Uytterhoeven
2026-02-02 11:43 ` Usyskin, Alexander
2026-01-29 8:17 ` Geert Uytterhoeven
2026-01-29 8:53 ` Arnd Bergmann
2026-01-29 9:01 ` 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=96fb5e3f-7855-4fe6-b263-60bc132716d3@app.fastmail.com \
--to=arnd@arndb.de \
--cc=Simon.Richter@hogyros.de \
--cc=alexander.usyskin@intel.com \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®