From: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@intel.com>,
Badal Nilawar <badal.nilawar@intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<anshuman.gupta@intel.com>, <alexander.usyskin@intel.com>,
<gregkh@linuxfoundation.org>
Subject: Re: [PATCH v5 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI
Date: Thu, 3 Jul 2025 10:06:41 -0700 [thread overview]
Message-ID: <737a4487-d474-4adc-b369-2a88792c81c4@intel.com> (raw)
In-Reply-To: <aGWpHRrPR39LWKQ1@intel.com>
On 7/2/2025 2:48 PM, Rodrigo Vivi wrote:
> On Wed, Jul 02, 2025 at 10:22:16PM +0530, Badal Nilawar wrote:
>> Do not review
> Why?
>
> Why don't we add this dependency here?
For INTEL_MEI_LATE_BIND to work we also need INTEL_MEI_GSC, which is
the config for the mei child device and depends on the config for our
driver, so a "depends on" tag would go circular.
INTEL_MEI_GSC also has further dependencies, so if we wanted to "select"
it (instead of marking it with a "depends on") we'd have to select those
dependencies as well, which doesn't scale well.
This patch only works as-is because our CI config does enable
INTEL_MEI_GSC with all its dependencies.
For other mei components (e.g. PXP, HDCP) what we did was notify the
distros that they had to enable the option in their kernel builds if
they wanted the feature to be enabled, so the idea was to do the same here.
Unless there is a kconfig trick we're missing that would make this work?
Daniele
>
>> Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
>> ---
>> drivers/gpu/drm/xe/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/gpu/drm/xe/Kconfig b/drivers/gpu/drm/xe/Kconfig
>> index f66e6d39e319..ef3f4807b0b3 100644
>> --- a/drivers/gpu/drm/xe/Kconfig
>> +++ b/drivers/gpu/drm/xe/Kconfig
>> @@ -45,6 +45,7 @@ config DRM_XE
>> select WANT_DEV_COREDUMP
>> select AUXILIARY_BUS
>> select HMM_MIRROR
>> + select INTEL_MEI_LATE_BIND
>> help
>> Driver for Intel Xe2 series GPUs and later. Experimental support
>> for Xe series is also available.
>> --
>> 2.34.1
>>
prev parent reply other threads:[~2025-07-03 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 16:52 [PATCH v5 00/10] Introducing firmware late binding Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 01/10] mei: bus: add mei_cldev_mtu interface Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 02/10] mei: late_bind: add late binding component driver Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 03/10] drm/xe/xe_late_bind_fw: Introducing xe_late_bind_fw Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 04/10] drm/xe/xe_late_bind_fw: Initialize late binding firmware Badal Nilawar
2025-07-02 23:55 ` Daniele Ceraolo Spurio
2025-07-02 16:52 ` [PATCH v5 05/10] drm/xe/xe_late_bind_fw: Load " Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 06/10] drm/xe/xe_late_bind_fw: Reload late binding fw in rpm resume Badal Nilawar
2025-07-02 21:46 ` Rodrigo Vivi
2025-07-02 16:52 ` [PATCH v5 07/10] drm/xe/xe_late_bind_fw: Reload late binding fw during system resume Badal Nilawar
2025-07-02 21:46 ` Rodrigo Vivi
2025-07-02 16:52 ` [PATCH v5 08/10] drm/xe/xe_late_bind_fw: Introduce debug fs node to disable late binding Badal Nilawar
2025-07-03 0:12 ` Daniele Ceraolo Spurio
2025-07-02 16:52 ` [PATCH v5 09/10] drm/xe/xe_late_bind_fw: Extract and print version info Badal Nilawar
2025-07-02 16:52 ` [PATCH v5 10/10] drm/xe/xe_late_bind_fw: Select INTEL_MEI_LATE_BIND for CI Badal Nilawar
2025-07-02 21:48 ` Rodrigo Vivi
2025-07-03 17:06 ` Daniele Ceraolo Spurio [this message]
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=737a4487-d474-4adc-b369-2a88792c81c4@intel.com \
--to=daniele.ceraolospurio@intel.com \
--cc=alexander.usyskin@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rodrigo.vivi@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
all inboxes | Powered by JetHome®