[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CY5PR11MB636633FFBB10ECA1033BC114ED9DA@CY5PR11MB6366.namprd11.prod.outlook.com>
Date: Sun, 1 Feb 2026 10:15:30 +0000
From: "Usyskin, Alexander" <alexander.usyskin@...el.com>
To: Simon Richter <Simon.Richter@...yros.de>
CC: Arnd Bergmann <arnd@...db.de>, Geert Uytterhoeven
<geert+renesas@...der.be>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Vivi,
Rodrigo" <rodrigo.vivi@...el.com>, "intel-gfx@...ts.freedesktop.org"
<intel-gfx@...ts.freedesktop.org>
Subject: RE: [PATCH] misc/mei: INTEL_MEI should depend on X86 or DRM_XE
> > >
> > > > 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@...ts.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
Powered by blists - more mailing lists