From: Hans de Goede <johannes.goede@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Cristian Marussi <cristian.marussi@arm.com>,
Sudeep Holla <sudeep.holla@kernel.org>
Cc: Hans de Goede <johannes.goede@oss.qualcomm.com>,
Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>,
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: [PATCH v3 2/3] firmware: arm_scmi: Pre-register protocol, name tupples for standard protocols
Date: Thu, 20 Aug 2026 21:48:49 +0200 [thread overview]
Message-ID: <20260820194850.459739-3-johannes.goede@oss.qualcomm.com> (raw)
In-Reply-To: <20260820194850.459739-1-johannes.goede@oss.qualcomm.com>
From: Cristian Marussi <cristian.marussi@arm.com>
Driver module auto-loading requires the devices to already be created for
udev to get the necessary uevents based on which udev auto-loads modules.
But SCMI devices are only created after their { protocol, name } tupples
have been registered which is done from scmi_driver_register().
This creates a circular dependency where device creation is waiting for
the driver to register and loading the module with the driver is waiting
for the device to be created.
Pre-register the tupples for standard protocols to break this circular
dependency.
Tested-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
Signed-off-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
---
Changes in v3:
- Drop adding of a bus uevent function this is already done
- Update comments and commit message with a better explanation of why
- Link to v1/RFC: https://patch.msgid.link/20250203100154.140877-2-cristian.marussi@arm.com
---
drivers/firmware/arm_scmi/bus.c | 47 ++++++++++++++++++++++++++++-----
1 file changed, 40 insertions(+), 7 deletions(-)
diff --git a/drivers/firmware/arm_scmi/bus.c b/drivers/firmware/arm_scmi/bus.c
index d12d5de15a1a..111727904a89 100644
--- a/drivers/firmware/arm_scmi/bus.c
+++ b/drivers/firmware/arm_scmi/bus.c
@@ -77,12 +77,13 @@ static int scmi_protocol_device_request(const struct scmi_device_id *id_table)
if (phead) {
head = phead;
list_for_each_entry(rdev, head, node) {
+ /* pr_debug() because dups are expected for std protocols */
if (!strcmp(rdev->id_table->name, id_table->name)) {
- pr_err("Ignoring duplicate request [%d] %s\n",
- rdev->id_table->protocol_id,
- rdev->id_table->name);
- ret = -EINVAL;
- goto out;
+ pr_debug("Device already requested [%d] %s\n",
+ rdev->id_table->protocol_id,
+ rdev->id_table->name);
+ mutex_unlock(&scmi_requested_devices_mtx);
+ return 0;
}
}
}
@@ -579,17 +580,49 @@ static void scmi_devices_unregister(void)
bus_for_each_dev(&scmi_bus_type, NULL, NULL, __scmi_devices_unregister);
}
+/* Standard protocols table */
+static const struct scmi_device_id scmi_std_id_table[] = {
+ { SCMI_PROTOCOL_POWER, "genpd" },
+ { SCMI_PROTOCOL_SYSTEM, "syspower" },
+ { SCMI_PROTOCOL_PERF, "perf" },
+ { SCMI_PROTOCOL_PERF, "cpufreq" },
+ { SCMI_PROTOCOL_CLOCK, "clocks" },
+ { SCMI_PROTOCOL_SENSOR, "hwmon" },
+ { SCMI_PROTOCOL_SENSOR, "iiodev" },
+ { SCMI_PROTOCOL_RESET, "reset" },
+ { SCMI_PROTOCOL_VOLTAGE, "regulator" },
+ { SCMI_PROTOCOL_POWERCAP, "powercap" },
+ { SCMI_PROTOCOL_PINCTRL, "pinctrl" },
+ { SCMI_PROTOCOL_PINCTRL, "pinctrl-imx" },
+ { },
+};
+
static int __init scmi_bus_init(void)
{
int retval;
retval = bus_register(&scmi_bus_type);
- if (retval)
+ if (retval) {
pr_err("SCMI protocol bus register failed (%d)\n", retval);
+ return retval;
+ }
+
+ /*
+ * Driver module auto-loading requires the devices to already be created
+ * for udev to get the necessary uevents. But the devices are only
+ * created after their { protocol, name } tupples have been registered
+ * which is done from scmi_driver_register(). Pre-register the tupples
+ * for known (in tree) drivers to break this circular dependency.
+ */
+ retval = scmi_protocol_table_register(scmi_std_id_table);
+ if (retval) {
+ bus_unregister(&scmi_bus_type);
+ return retval;
+ }
pr_info("SCMI protocol bus registered\n");
- return retval;
+ return 0;
}
subsys_initcall(scmi_bus_init);
--
2.55.0
next prev parent reply other threads:[~2026-08-20 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 19:48 [PATCH v3 0/3] firmware: arm_scmi: fix module auto-loading Hans de Goede
2026-08-20 19:48 ` [PATCH v3 1/3] module: add SCMI device table alias support Hans de Goede
2026-08-24 12:22 ` Uwe Kleine-König
2026-08-24 14:58 ` Hans de Goede
2026-08-25 8:32 ` Uwe Kleine-König
2026-08-20 19:48 ` Hans de Goede [this message]
2026-08-20 19:48 ` [PATCH v3 3/3] firmware: arm_scmi: Pre-register protocol, name tupples for IMX 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=20260820194850.459739-3-johannes.goede@oss.qualcomm.com \
--to=johannes.goede@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=arm-scmi@vger.kernel.org \
--cc=cristian.marussi@arm.com \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=imx@lists.linux.dev \
--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