From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Usyskin, Alexander" <alexander.usyskin@intel.com>,
<intel-gfx@lists.freedesktop.org>
Cc: Simon Richter <Simon.Richter@hogyros.de>,
Arnd Bergmann <arnd@arndb.de>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"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: Fri, 30 Jan 2026 16:15:14 -0500 [thread overview]
Message-ID: <aX0fYgU4FHIbsUET@intel.com> (raw)
In-Reply-To: <CY5PR11MB63665464BE137AE70B0D47ADED9EA@CY5PR11MB6366.namprd11.prod.outlook.com>
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
>
>
next prev parent reply other threads:[~2026-01-30 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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=aX0fYgU4FHIbsUET@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=Simon.Richter@hogyros.de \
--cc=alexander.usyskin@intel.com \
--cc=arnd@arndb.de \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.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