public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Adam Borowski <kilobyte@angband.pl>
To: "Winkler, Tomas" <tomas.winkler@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Usyskin, Alexander" <alexander.usyskin@intel.com>
Subject: Re: [PATCH] mei: make hdcp and pxp depend on X86 && PCI
Date: Tue, 25 Apr 2023 13:52:10 +0200	[thread overview]
Message-ID: <20230425115210.GA4151911@angband.pl> (raw)
In-Reply-To: <MN2PR11MB409305D13E46C371321AC2F0E5649@MN2PR11MB4093.namprd11.prod.outlook.com>

On Tue, Apr 25, 2023 at 04:39:23AM +0000, Winkler, Tomas wrote:
> What is the exact issue you are experiencing, can you add the error message this fixes? 

The problem doesn't trigger in mainline, as DRM_I915 can't be enabled on
!X86; https://github.com/kilobyte/linux branch i915 has a WIP port.  Some
unrelated piece (I suspect ACPI changes, didn't bother to investigate) has
in the meantime grown enough bits to enable prerequsites that trigger:

WARNING: unmet direct dependencies detected for INTEL_MEI_ME
  Depends on [n]: X86 && PCI [=y]
  Selected by [y]:
  - INTEL_MEI_HDCP [=y] && DRM_I915 [=y]
  - INTEL_MEI_PXP [=y] && DRM_I915 [=y]

This doesn't cause an actual build failure, as drivers/misc/Makefile has
> obj-$(CONFIG_INTEL_MEI)         += mei/
which won't try to build mei/hdcp nor mei/pxp despite them being enabled
in the config.

Of all the settings in drivers/misc/mei/Kconfig, only these two (that
reside in their own subdirectories) lack this stanza.  You'd want to
deduplicate the selects one day -- but alas, "select" relations are not as
straightforward as "depends", thus I only did the same as for all other
settings in drivers/misc/mei/Kconfig.

Should I quote this warning in full in the commit message?  I thought that
"make ... depend on ..." already explains enough.

Also, as this lack of dependency is an obvious and self-contained change,
I decided to submit it directly via mei, rather than ask for an ACK then
spam you with every iteration of the patchset.  Should it go via drm/i915
instead?

(I'd also like to apologize for sitting on this patchset so long, my
brain's firmware is faulty :/ ).

> > From: Adam Borowski <kilobyte@angband.pl>
> > 
> > All other MEI configs do so already.  This fixes a Kconfig gripe if I915 gets
> > ported to other archs (such as RISC-V in Intel Horse Creek...).
> > 
> > Signed-off-by: Adam Borowski <kilobyte@angband.pl>
> > ---
> >  drivers/misc/mei/hdcp/Kconfig | 1 +
> >  drivers/misc/mei/pxp/Kconfig  | 1 +
> >  2 files changed, 2 insertions(+)
> > 
> > diff --git a/drivers/misc/mei/hdcp/Kconfig b/drivers/misc/mei/hdcp/Kconfig
> > index 54e1c9526909..83e67771ac6b 100644
> > --- a/drivers/misc/mei/hdcp/Kconfig
> > +++ b/drivers/misc/mei/hdcp/Kconfig
> > @@ -4,6 +4,7 @@
> >  config INTEL_MEI_HDCP
> >  	tristate "Intel HDCP2.2 services of ME Interface"
> >  	select INTEL_MEI_ME
> > +	depends on X86 && PCI
> >  	depends on DRM_I915
> >  	help
> >  	  MEI Support for HDCP2.2 Services on Intel platforms.
> > diff --git a/drivers/misc/mei/pxp/Kconfig b/drivers/misc/mei/pxp/Kconfig
> > index 4029b96afc04..95f2c2470d28 100644
> > --- a/drivers/misc/mei/pxp/Kconfig
> > +++ b/drivers/misc/mei/pxp/Kconfig
> > @@ -5,6 +5,7 @@
> >  config INTEL_MEI_PXP
> >  	tristate "Intel PXP services of ME Interface"
> >  	select INTEL_MEI_ME
> > +	depends on X86 && PCI
> >  	depends on DRM_I915
> >  	help
> >  	  MEI Support for PXP Services on Intel platforms.
> > --
> > 2.40.0

Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Q: Is it ok to combine wired, wifi, and/or bluetooth connections
⢿⡄⠘⠷⠚⠋⠀    in wearable computing?
⠈⠳⣄⠀⠀⠀⠀ A: No, that would be mixed fabric, which Lev19:19 forbids.

  reply	other threads:[~2023-04-25 12:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23 13:51 [PATCH] mei: make hdcp and pxp depend on X86 && PCI kilobyte
2023-04-25  4:39 ` Winkler, Tomas
2023-04-25 11:52   ` Adam Borowski [this message]
2023-04-25 13:40     ` Greg Kroah-Hartman
2023-04-25 15:27       ` Adam Borowski
2023-04-25 15:43         ` [PATCH v2] mei: deduplicate X86 && PCI dependencies, make them apply to all subentries kilobyte
2023-04-25 16:16           ` Greg Kroah-Hartman
2023-04-25 21:51         ` [PATCH] mei: make hdcp and pxp depend on X86 && PCI Arnd Bergmann
2023-04-26 18:11           ` Winkler, Tomas
2023-04-28  5:50             ` Arnd Bergmann
2023-04-30  6:38               ` Winkler, Tomas

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=20230425115210.GA4151911@angband.pl \
    --to=kilobyte@angband.pl \
    --cc=alexander.usyskin@intel.com \
    --cc=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tomas.winkler@intel.com \
    /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