From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: Hans de Goede <johannes.goede@oss.qualcomm.com>,
Bjorn Andersson <andersson@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
Frank.Li@kernel.org, arm-scmi@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-arm-msm@vger.kernel.org, imx@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 1/2] module: add SCMI device table alias support
Date: Fri, 18 Sep 2026 11:53:42 +0200 [thread overview]
Message-ID: <2104f437-e960-4e55-b0e1-2b37126e8c2f@oss.qualcomm.com> (raw)
In-Reply-To: <20260918092951.5656-2-johannes.goede@oss.qualcomm.com>
Hi Hans,
thanks for taking care of that
On 9/18/26 11:29, Hans de Goede wrote:
> From: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
>
> SCMI client drivers already describe their bus match data with
> MODULE_DEVICE_TABLE(scmi, ...), but modpost does not know how to consume
> SCMI device tables. As a result, SCMI modules do not get generated module
> aliases from their id tables.
>
> Move struct scmi_device_id to mod_devicetable.h so it has a fixed layout
> visible to modpost, add the corresponding generated offsets and teach
> file2alias to emit scmi:<protocol>:<name> aliases.
>
> Use the same stable alias format for SCMI device uevents and sysfs
> modaliases. The previous string included the instance-specific device
> name, which is not useful for matching modules.
>
> Assisted-by: Codex:GPT-5.5
> Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> Tested-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> Signed-off-by: Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>
> Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
> ---
[ ... ]
>
> -#define SCMI_UEVENT_MODALIAS_FMT "%s:%02x:%s"
> +#define SCMI_UEVENT_MODALIAS_FMT SCMI_MODULE_PREFIX "%02x:%s"
>
> BLOCKING_NOTIFIER_HEAD(scmi_requested_devices_nh);
> EXPORT_SYMBOL_GPL(scmi_requested_devices_nh);
> @@ -185,7 +186,7 @@ static int scmi_protocol_table_register(const struct scmi_device_id *id_table)
> const struct scmi_device_id *entry;
> int ret;
>
> - for (entry = id_table; entry->name; entry++) {
> + for (entry = id_table; entry->name[0]; entry++) {
Is it possible to rely on a NULL sentinel?
Here if the id_table is NULL, entry->name | entry->name[0] dereference
the NULL pointer
for (entry = id_table; entry != NULL; entry++)
> ret = scmi_protocol_device_request(entry);
[ ... ]
> #include <linux/bitfield.h>
> +#include <linux/device-id/scmi.h>
> #include <linux/device.h>
> #include <linux/notifier.h>
> #include <linux/types.h>
> @@ -951,11 +952,6 @@ struct scmi_device {
>
> #define to_scmi_dev(d) container_of_const(d, struct scmi_device, dev)
>
> -struct scmi_device_id {
> - u8 protocol_id;
> - const char *name;
> -};
> -
What is the reason of converting the char * to a fixed array? That
limits the name and may result in truncation and potentially name
collision, no ?
[ ... ]
next prev parent reply other threads:[~2026-09-18 9:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-18 9:29 [PATCH v7 0/2] firmware: arm_scmi: fix module auto-loading Hans de Goede
2026-09-18 9:29 ` [PATCH v7 1/2] module: add SCMI device table alias support Hans de Goede
2026-09-18 9:53 ` Daniel Lezcano [this message]
2026-09-18 10:02 ` Hans de Goede
2026-09-18 10:13 ` Daniel Lezcano
2026-09-18 13:38 ` Sudeep Holla
2026-09-18 14:43 ` Rob Clark
2026-09-18 14:48 ` Daniel Lezcano
2026-09-18 20:15 ` Daniel Lezcano
2026-09-18 13:32 ` Sudeep Holla
2026-09-18 14:09 ` Hans de Goede
2026-09-18 20:39 ` Uwe Kleine-König
2026-09-18 9:29 ` [PATCH v7 2/2] firmware: arm_scmi: Always create devices for standard protocols Hans de Goede
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=2104f437-e960-4e55-b0e1-2b37126e8c2f@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=Frank.Li@kernel.org \
--cc=andersson@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=bjorn.andersson@oss.qualcomm.com \
--cc=cristian.marussi@arm.com \
--cc=imx@lists.linux.dev \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sudeep.holla@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®