From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: DelaySystem@tubot.lat
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
mchehab@kernel.org
Subject: Re: [PATCH v2] media: ipu6: declare firmware files with MODULE_FIRMWARE
Date: Mon, 9 Nov 2026 11:23:54 +0200 [thread overview]
Message-ID: <avGRKmGuMCfR4WeI@kekkonen.localdomain> (raw)
In-Reply-To: <20261107-batch1-s1-ipu6-fw-v2-1-0e8567a1aefa@tubot.lat>
Hi,
On Sat, Nov 07, 2026 at 09:04:40PM -0800, DelaySystem via B4 Relay wrote:
> From: DelaySystem <DelaySystem@tubot.lat>
>
> The driver requests one of eight firmware blobs at runtime depending on
> the detected SoC (IPU6, IPU6SE, IPU6EP, IPU6EPADLN, IPU6EPMTL, IPU7,
> IPU7P5 or IPU8), selected through isp->cpd_fw_name, but never declares
> them. As a result modinfo shows no firmware: lines and initramfs
> generators cannot pick up the dependency automatically.
>
> Add MODULE_FIRMWARE() for every blob the driver can request.
>
> Suggested-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Link: https://lore.kernel.org/all/apqB28RBDZV4BlDZ@kekkonen.localdomain/
> Signed-off-by: DelaySystem <DelaySystem@tubot.lat>
Could we have a real name here? Same for From:.
> ---
> Changes in v2:
> - Resend with corrected Cc list (v1 accidentally reached only Sakari and linux-kernel: repeated --cc flags do not accumulate in b4); no code change.
> - Adds linux-media@vger.kernel.org and Mauro Carvalho Chehab to Cc.
> - Link to v1: https://patch.msgid.link/20261107-batch1-s1-ipu6-fw-v1-1-1d5323aff7b2@tubot.lat
> ---
> drivers/media/pci/intel/ipu6/ipu6.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/media/pci/intel/ipu6/ipu6.c b/drivers/media/pci/intel/ipu6/ipu6.c
> index cdf812c02960..ec2a9c2bf587 100644
> --- a/drivers/media/pci/intel/ipu6/ipu6.c
> +++ b/drivers/media/pci/intel/ipu6/ipu6.c
> @@ -1028,3 +1028,11 @@ MODULE_AUTHOR("Yunliang Ding <yunliang.ding@intel.com>");
> MODULE_AUTHOR("Hongju Wang");
> MODULE_LICENSE("GPL");
> MODULE_DESCRIPTION("Intel IPU6 PCI driver");
> +MODULE_FIRMWARE(IPU6SE_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU6EP_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU6_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU6EPMTL_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU6EPADLN_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU7_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU7P5_FIRMWARE_NAME);
> +MODULE_FIRMWARE(IPU8_FIRMWARE_NAME);
>
--
Regards,
Sakari Ailus
prev parent reply other threads:[~2026-11-09 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-08 5:04 DelaySystem via B4 Relay
2026-11-09 9:23 ` Sakari Ailus [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=avGRKmGuMCfR4WeI@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=DelaySystem@tubot.lat \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®