* [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
@ 2026-01-27 19:11 Geert Uytterhoeven
2026-01-28 6:41 ` Usyskin, Alexander
0 siblings, 1 reply; 14+ messages in thread
From: Geert Uytterhoeven @ 2026-01-27 19:11 UTC (permalink / raw)
To: Alexander Usyskin, Arnd Bergmann, Greg Kroah-Hartman,
Simon Richter
Cc: linux-kernel, Geert Uytterhoeven
The Intel Management Engine Interface is only present on x86 platforms
and Intel Xe graphics cards. Hence add a dependency on X86 or DRM_XE,
to prevent asking the user about this driver when configuring a kernel
for a non-x86 architecture and without Xe graphics support.
Fixes: 25f9b0d351552f63 ("misc/mei: Allow building Intel ME interface on non-x86")
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
---
drivers/misc/mei/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
index 5902dd1ee44baf16..094fb1dde0fe80c5 100644
--- a/drivers/misc/mei/Kconfig
+++ b/drivers/misc/mei/Kconfig
@@ -3,6 +3,7 @@
config INTEL_MEI
tristate "Intel Management Engine Interface"
depends on PCI
+ depends on X86 || DRM_XE!=n || COMPILE_TEST
default X86_64 || MATOM
help
The Intel Management Engine (Intel ME) provides Manageability,
--
2.43.0
^ permalink raw reply related [flat|nested] 14+ messages in thread* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-27 19:11 [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE Geert Uytterhoeven
@ 2026-01-28 6:41 ` Usyskin, Alexander
2026-01-28 6:50 ` Arnd Bergmann
0 siblings, 1 reply; 14+ messages in thread
From: Usyskin, Alexander @ 2026-01-28 6:41 UTC (permalink / raw)
To: Geert Uytterhoeven, Arnd Bergmann, Greg Kroah-Hartman,
Simon Richter
Cc: linux-kernel@vger.kernel.org
> Subject: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>
> The Intel Management Engine Interface is only present on x86 platforms
> and Intel Xe graphics cards. Hence add a dependency on X86 or DRM_XE,
> to prevent asking the user about this driver when configuring a kernel
> for a non-x86 architecture and without Xe graphics support.
>
> Fixes: 25f9b0d351552f63 ("misc/mei: Allow building Intel ME interface on
> non-x86")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> drivers/misc/mei/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
> index 5902dd1ee44baf16..094fb1dde0fe80c5 100644
> --- a/drivers/misc/mei/Kconfig
> +++ b/drivers/misc/mei/Kconfig
> @@ -3,6 +3,7 @@
> config INTEL_MEI
> tristate "Intel Management Engine Interface"
> depends on PCI
> + depends on X86 || DRM_XE!=n || COMPILE_TEST
Add DRM_I915 here too, MEI may depend on it.
- -
Thanks,
Sasha
> default X86_64 || MATOM
> help
> The Intel Management Engine (Intel ME) provides Manageability,
> --
> 2.43.0
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-28 6:41 ` Usyskin, Alexander
@ 2026-01-28 6:50 ` Arnd Bergmann
2026-01-28 6:57 ` Usyskin, Alexander
0 siblings, 1 reply; 14+ messages in thread
From: Arnd Bergmann @ 2026-01-28 6:50 UTC (permalink / raw)
To: Alexander Usyskin, Geert Uytterhoeven, Greg Kroah-Hartman,
Simon Richter
Cc: linux-kernel@vger.kernel.org
On Wed, Jan 28, 2026, at 07:41, Usyskin, Alexander wrote:
>> Subject: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>>
>> The Intel Management Engine Interface is only present on x86 platforms
>> and Intel Xe graphics cards. Hence add a dependency on X86 or DRM_XE,
>> to prevent asking the user about this driver when configuring a kernel
>> for a non-x86 architecture and without Xe graphics support.
>>
>> Fixes: 25f9b0d351552f63 ("misc/mei: Allow building Intel ME interface on
>> non-x86")
>> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
>> ---
>> drivers/misc/mei/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
>> index 5902dd1ee44baf16..094fb1dde0fe80c5 100644
>> --- a/drivers/misc/mei/Kconfig
>> +++ b/drivers/misc/mei/Kconfig
>> @@ -3,6 +3,7 @@
>> config INTEL_MEI
>> tristate "Intel Management Engine Interface"
>> depends on PCI
>> + depends on X86 || DRM_XE!=n || COMPILE_TEST
>
> Add DRM_I915 here too, MEI may depend on it.
Based on the patch description, shouldn't the dependency allow
compile-testing only if both XE and I915 are turned off, as in
depends on X86 || (DRM_XE=n && DRM_I915=n && COMPILE_TEST)
?
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.
Arnd
^ permalink raw reply [flat|nested] 14+ messages in thread* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-28 6:50 ` Arnd Bergmann
@ 2026-01-28 6:57 ` Usyskin, Alexander
2026-01-28 7:24 ` Arnd Bergmann
2026-01-29 4:45 ` Simon Richter
0 siblings, 2 replies; 14+ messages in thread
From: Usyskin, Alexander @ 2026-01-28 6:57 UTC (permalink / raw)
To: Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman,
Simon Richter
Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>
> On Wed, Jan 28, 2026, at 07:41, Usyskin, Alexander wrote:
> >> Subject: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
> >>
> >> The Intel Management Engine Interface is only present on x86 platforms
> >> and Intel Xe graphics cards. Hence add a dependency on X86 or DRM_XE,
> >> to prevent asking the user about this driver when configuring a kernel
> >> for a non-x86 architecture and without Xe graphics support.
> >>
> >> Fixes: 25f9b0d351552f63 ("misc/mei: Allow building Intel ME interface on
> >> non-x86")
> >> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> >> ---
> >> drivers/misc/mei/Kconfig | 1 +
> >> 1 file changed, 1 insertion(+)
> >>
> >> diff --git a/drivers/misc/mei/Kconfig b/drivers/misc/mei/Kconfig
> >> index 5902dd1ee44baf16..094fb1dde0fe80c5 100644
> >> --- a/drivers/misc/mei/Kconfig
> >> +++ b/drivers/misc/mei/Kconfig
> >> @@ -3,6 +3,7 @@
> >> config INTEL_MEI
> >> tristate "Intel Management Engine Interface"
> >> depends on PCI
> >> + depends on X86 || DRM_XE!=n || COMPILE_TEST
> >
> > Add DRM_I915 here too, MEI may depend on it.
>
> Based on the patch description, shouldn't the dependency allow
> compile-testing only if both XE and I915 are turned off, as in
>
> depends on X86 || (DRM_XE=n && DRM_I915=n && COMPILE_TEST)
>
> ?
>
> 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.
- 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
- -
Thanks,
Sasha
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-28 6:57 ` Usyskin, Alexander
@ 2026-01-28 7:24 ` Arnd Bergmann
2026-01-29 4:45 ` Simon Richter
1 sibling, 0 replies; 14+ messages in thread
From: Arnd Bergmann @ 2026-01-28 7:24 UTC (permalink / raw)
To: Alexander Usyskin, Geert Uytterhoeven, Greg Kroah-Hartman,
Simon Richter
Cc: linux-kernel@vger.kernel.org
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
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-28 6:57 ` Usyskin, Alexander
2026-01-28 7:24 ` Arnd Bergmann
@ 2026-01-29 4:45 ` Simon Richter
2026-01-29 5:53 ` Usyskin, Alexander
2026-01-29 8:17 ` Geert Uytterhoeven
1 sibling, 2 replies; 14+ messages in thread
From: Simon Richter @ 2026-01-29 4:45 UTC (permalink / raw)
To: Usyskin, Alexander, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman
Cc: linux-kernel@vger.kernel.org
Hi,
On 1/28/26 3:57 PM, Usyskin, Alexander wrote:
> There are different usages of mei:
> - for discrete graphics xe/i915 will load mei via auxiliary device also on non x86.
> - 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
Is there discrete i915?
DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which
is why I didn't add it in my version of the patch. If DRM_I915 is useful
on non-x86 we might want to change that as well.
Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
becomes available only after selecting DRM_XE, which is in a directory
included much later, so the question is not shown initially, is that a
problem?
Simon
^ permalink raw reply [flat|nested] 14+ messages in thread* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-29 4:45 ` Simon Richter
@ 2026-01-29 5:53 ` Usyskin, Alexander
2026-01-30 21:15 ` Rodrigo Vivi
2026-01-29 8:17 ` Geert Uytterhoeven
1 sibling, 1 reply; 14+ messages in thread
From: Usyskin, Alexander @ 2026-01-29 5:53 UTC (permalink / raw)
To: Simon Richter, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman, Vivi, Rodrigo
Cc: linux-kernel@vger.kernel.org
> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>
> Hi,
>
> On 1/28/26 3:57 PM, Usyskin, Alexander wrote:
>
> > There are different usages of mei:
> > - for discrete graphics xe/i915 will load mei via auxiliary device also on non
> x86.
> > - 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
>
> Is there discrete i915?
>
DG1, Alchemist and some server cards are supported by i915
> DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant,
> which
> is why I didn't add it in my version of the patch. If DRM_I915 is useful
> on non-x86 we might want to change that as well.
>
Let ask gfx people.
Rodrigo, is DRM_I915 useful on non-x86?
> Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
> becomes available only after selecting DRM_XE, which is in a directory
> included much later, so the question is not shown initially, is that a
> problem?
>
By not enabling INTEL_MEI the biggest thing that you loose are the firmware update.
I'm not sure how to sort this out and if it is worth the effort.
- -
Thanks,
Sasha
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-29 5:53 ` Usyskin, Alexander
@ 2026-01-30 21:15 ` Rodrigo Vivi
2026-02-01 10:15 ` Usyskin, Alexander
0 siblings, 1 reply; 14+ messages in thread
From: Rodrigo Vivi @ 2026-01-30 21:15 UTC (permalink / raw)
To: Usyskin, Alexander, intel-gfx
Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman, linux-kernel@vger.kernel.org
On Thu, Jan 29, 2026 at 12:53:12AM -0500, Usyskin, Alexander wrote:
> > Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
> >
> > Hi,
> >
> > On 1/28/26 3:57 PM, Usyskin, Alexander wrote:
> >
> > > There are different usages of mei:
> > > - for discrete graphics xe/i915 will load mei via auxiliary device also on non
> > x86.
> > > - 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
> >
> > Is there discrete i915?
> >
>
> DG1, Alchemist and some server cards are supported by i915
>
> > DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant,
> > which
> > is why I didn't add it in my version of the patch. If DRM_I915 is useful
> > on non-x86 we might want to change that as well.
> >
>
> Let ask gfx people.
Cc: intel-gfx@lists.freedesktop.org
> Rodrigo, is DRM_I915 useful on non-x86?
No, I really don't believe it would work out.
>
> > Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
> > becomes available only after selecting DRM_XE, which is in a directory
> > included much later, so the question is not shown initially, is that a
> > problem?
> >
>
> By not enabling INTEL_MEI the biggest thing that you loose are the firmware update.
> I'm not sure how to sort this out and if it is worth the effort.
>
> - -
> Thanks,
> Sasha
>
>
^ permalink raw reply [flat|nested] 14+ messages in thread
* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-30 21:15 ` Rodrigo Vivi
@ 2026-02-01 10:15 ` Usyskin, Alexander
2026-02-02 9:33 ` Geert Uytterhoeven
0 siblings, 1 reply; 14+ messages in thread
From: Usyskin, Alexander @ 2026-02-01 10:15 UTC (permalink / raw)
To: Simon Richter
Cc: Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman,
linux-kernel@vger.kernel.org, Vivi, Rodrigo,
intel-gfx@lists.freedesktop.org
> > >
> > > > There are different usages of mei:
> > > > - for discrete graphics xe/i915 will load mei via auxiliary device also on non
> > > x86.
> > > > - 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
> > >
> > > Is there discrete i915?
> > >
> >
> > DG1, Alchemist and some server cards are supported by i915
> >
> > > DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant,
> > > which
> > > is why I didn't add it in my version of the patch. If DRM_I915 is useful
> > > on non-x86 we might want to change that as well.
> > >
> >
> > Let ask gfx people.
>
> Cc: intel-gfx@lists.freedesktop.org
>
> > Rodrigo, is DRM_I915 useful on non-x86?
>
> No, I really don't believe it would work out.
>
In this case the below should be good, I suppose:
depends on X86 || DRM_XE!=n || COMPILE_TEST
- -
Thanks,
Sasha
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-02-01 10:15 ` Usyskin, Alexander
@ 2026-02-02 9:33 ` Geert Uytterhoeven
2026-02-02 11:43 ` Usyskin, Alexander
0 siblings, 1 reply; 14+ messages in thread
From: Geert Uytterhoeven @ 2026-02-02 9:33 UTC (permalink / raw)
To: Usyskin, Alexander
Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman, linux-kernel@vger.kernel.org, Vivi, Rodrigo,
intel-gfx@lists.freedesktop.org
Hi Sasha
On Sun, 1 Feb 2026 at 11:15, Usyskin, Alexander
<alexander.usyskin@intel.com> wrote:
> > > > > There are different usages of mei:
> > > > > - for discrete graphics xe/i915 will load mei via auxiliary device also on non
> > > > x86.
> > > > > - 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
> > > >
> > > > Is there discrete i915?
> > >
> > > DG1, Alchemist and some server cards are supported by i915
> > >
> > > > DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant,
> > > > which
> > > > is why I didn't add it in my version of the patch. If DRM_I915 is useful
> > > > on non-x86 we might want to change that as well.
> > >
> > > Let ask gfx people.
> >
> > Cc: intel-gfx@lists.freedesktop.org
> >
> > > Rodrigo, is DRM_I915 useful on non-x86?
> >
> > No, I really don't believe it would work out.
>
> In this case the below should be good, I suppose:
>
> depends on X86 || DRM_XE!=n || COMPILE_TEST
... which is exactly what I added in my patch. So life's good?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 14+ messages in thread* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-02-02 9:33 ` Geert Uytterhoeven
@ 2026-02-02 11:43 ` Usyskin, Alexander
0 siblings, 0 replies; 14+ messages in thread
From: Usyskin, Alexander @ 2026-02-02 11:43 UTC (permalink / raw)
To: Geert Uytterhoeven
Cc: Simon Richter, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman, linux-kernel@vger.kernel.org, Vivi, Rodrigo,
intel-gfx@lists.freedesktop.org
> Subject: Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
>
> Hi Sasha
>
> On Sun, 1 Feb 2026 at 11:15, Usyskin, Alexander
> <alexander.usyskin@intel.com> wrote:
> > > > > > There are different usages of mei:
> > > > > > - for discrete graphics xe/i915 will load mei via auxiliary device also on
> non
> > > > > x86.
> > > > > > - 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
> > > > >
> > > > > Is there discrete i915?
> > > >
> > > > DG1, Alchemist and some server cards are supported by i915
> > > >
> > > > > DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is
> redundant,
> > > > > which
> > > > > is why I didn't add it in my version of the patch. If DRM_I915 is useful
> > > > > on non-x86 we might want to change that as well.
> > > >
> > > > Let ask gfx people.
> > >
> > > Cc: intel-gfx@lists.freedesktop.org
> > >
> > > > Rodrigo, is DRM_I915 useful on non-x86?
> > >
> > > No, I really don't believe it would work out.
> >
> > In this case the below should be good, I suppose:
> >
> > depends on X86 || DRM_XE!=n || COMPILE_TEST
>
> ... which is exactly what I added in my patch. So life's good?
>
From my point of view now - yes, it is reasonable.
- -
Thanks,
Sasha
^ permalink raw reply [flat|nested] 14+ messages in thread
* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-29 4:45 ` Simon Richter
2026-01-29 5:53 ` Usyskin, Alexander
@ 2026-01-29 8:17 ` Geert Uytterhoeven
2026-01-29 8:53 ` Arnd Bergmann
2026-01-29 9:01 ` Usyskin, Alexander
1 sibling, 2 replies; 14+ messages in thread
From: Geert Uytterhoeven @ 2026-01-29 8:17 UTC (permalink / raw)
To: Simon Richter
Cc: Usyskin, Alexander, Arnd Bergmann, Geert Uytterhoeven,
Greg Kroah-Hartman, linux-kernel@vger.kernel.org
Hi Simon,
On Thu, 29 Jan 2026 at 05:45, Simon Richter <Simon.Richter@hogyros.de> wrote:
> On 1/28/26 3:57 PM, Usyskin, Alexander wrote:
> > There are different usages of mei:
> > - for discrete graphics xe/i915 will load mei via auxiliary device also on non x86.
> > - 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
>
> Is there discrete i915?
>
> DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which
> is why I didn't add it in my version of the patch. If DRM_I915 is useful
> on non-x86 we might want to change that as well.
Then the dependency of DRM_I915 on X86 should be dropped first...
> Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
> becomes available only after selecting DRM_XE, which is in a directory
> included much later, so the question is not shown initially, is that a
> problem?
Let's give it a try on arm64.
Remove "# CONFIG_DRM_XE is not set" from .config.
$ make oldconfig
[...]
Intel Xe2 Graphics (DRM_XE) [N/y/?] (NEW) y
[...]
Intel Management Engine Interface (INTEL_MEI) [N/y/?] (NEW) y
ME Enabled Intel Chipsets (INTEL_MEI_ME) [Y/n/?] (NEW)
[...]
So the ordering is not an issue.
I only wonder about some of the other INTEL_MEI_* options.
I think e.g. INTEL_MEI_ME now needs a dependency on X86, as I doubt
any of these Intel Chipsets are used on non-x86?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
^ permalink raw reply [flat|nested] 14+ messages in thread* Re: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-29 8:17 ` Geert Uytterhoeven
@ 2026-01-29 8:53 ` Arnd Bergmann
2026-01-29 9:01 ` Usyskin, Alexander
1 sibling, 0 replies; 14+ messages in thread
From: Arnd Bergmann @ 2026-01-29 8:53 UTC (permalink / raw)
To: Geert Uytterhoeven, Simon Richter
Cc: Alexander Usyskin, Geert Uytterhoeven, Greg Kroah-Hartman,
linux-kernel@vger.kernel.org
On Thu, Jan 29, 2026, at 09:17, Geert Uytterhoeven wrote:
> On Thu, 29 Jan 2026 at 05:45, Simon Richter <Simon.Richter@hogyros.de> wrote:
>>
>> DRM_I915 depends on PCI && X86 (so "X86 || DRM_I915" is redundant, which
>> is why I didn't add it in my version of the patch. If DRM_I915 is useful
>> on non-x86 we might want to change that as well.
>
> Then the dependency of DRM_I915 on X86 should be dropped first...
This is not easily done, with the amount of 'select' statements
from the I915 drive, including X86_PLATFORM_DEVICES and ACPI_WMI.
At the minimum, changing this should involve turning a lot of
these into 'depends on' to avoid dependency loops, plus
build testing random configurations.
Arnd
^ permalink raw reply [flat|nested] 14+ messages in thread* RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
2026-01-29 8:17 ` Geert Uytterhoeven
2026-01-29 8:53 ` Arnd Bergmann
@ 2026-01-29 9:01 ` Usyskin, Alexander
1 sibling, 0 replies; 14+ messages in thread
From: Usyskin, Alexander @ 2026-01-29 9:01 UTC (permalink / raw)
To: Geert Uytterhoeven, Simon Richter
Cc: Arnd Bergmann, Geert Uytterhoeven, Greg Kroah-Hartman,
linux-kernel@vger.kernel.org
>
> > Also, is there any policy on dependency ordering? On non-X86, INTEL_MEI
> > becomes available only after selecting DRM_XE, which is in a directory
> > included much later, so the question is not shown initially, is that a
> > problem?
>
> Let's give it a try on arm64.
> Remove "# CONFIG_DRM_XE is not set" from .config.
>
> $ make oldconfig
> [...]
> Intel Xe2 Graphics (DRM_XE) [N/y/?] (NEW) y
> [...]
> Intel Management Engine Interface (INTEL_MEI) [N/y/?] (NEW) y
> ME Enabled Intel Chipsets (INTEL_MEI_ME) [Y/n/?] (NEW)
> [...]
>
> So the ordering is not an issue.
>
> I only wonder about some of the other INTEL_MEI_* options.
> I think e.g. INTEL_MEI_ME now needs a dependency on X86, as I doubt
> any of these Intel Chipsets are used on non-x86?
>
INTEL_MEI_ME is re-used by INTEL_MEI_GSC (the HW access code, not PCI one),
so it should not be bound to x86.
- -
Thanks,
Sasha
^ permalink raw reply [flat|nested] 14+ messages in thread
end of thread, other threads:[~2026-02-02 11:44 UTC | newest]
Thread overview: 14+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-01-27 19:11 [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE 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
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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox