From: Peng Fan <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Danilo Krummrich <dakr@kernel.org>,
Saravana Kannan <saravanak@kernel.org>,
Hans de Goede <johannes.goede@oss.qualcomm.com>,
driver-core@lists.linux.dev, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, Peng Fan <peng.fan@nxp.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] driver core: hand off fwnode ownership when shared fwnode owner is rejected
Date: Wed, 30 Sep 2026 15:06:11 +0800 [thread overview]
Message-ID: <ary048HBAkJB4WR9@shlinux89> (raw)
In-Reply-To: <20260929-dazzling-gray-sawfly-cfd671@sudeepholla>
Hi Sudeep,
On Tue, Sep 29, 2026 at 04:56:24PM +0100, Sudeep Holla wrote:
>On Tue, Sep 29, 2026 at 09:35:21AM +0100, Sudeep Holla wrote:
...
>> Yes, but this particular device is i.MX specific issue as it should
>> have never been there. So I will discard that in any future discussion.
>> Use the SCMI pinmux driver and get rid of SCMI pinctrl-imx.
>>
>
>Anyways, I cooked up a patch that may prevent the issue with pinmux.
>See if something like below on top -next helps.
>
>Regards,
>Sudeep
>
>-->8
>diff --git a/drivers/firmware/arm_scmi/bus.c b/drivers/firmware/arm_scmi/bus.c
>index 25197197db8e..cee7cc777724 100644
>--- a/drivers/firmware/arm_scmi/bus.c
>+++ b/drivers/firmware/arm_scmi/bus.c
>@@ -60,13 +60,6 @@ static int scmi_protocol_device_request(const struct scmi_device_id *id_table)
> pr_debug("Requesting SCMI device (%s) for protocol %x\n",
> id_table->name, id_table->protocol_id);
>
>- if (IS_ENABLED(CONFIG_ARM_SCMI_RAW_MODE_SUPPORT) &&
>- !IS_ENABLED(CONFIG_ARM_SCMI_RAW_MODE_SUPPORT_COEX)) {
>- pr_warn("SCMI Raw mode active. Rejecting '%s'/0x%02X\n",
>- id_table->name, id_table->protocol_id);
>- return -EINVAL;
>- }
>-
> /*
> * Find the matching protocol rdev list and then search of any
> * existent equally named device...fails if any duplicate found.
>@@ -181,12 +174,35 @@ static void scmi_protocol_device_unrequest(const struct scmi_device_id *id_table
> }
> }
>
Move static const struct scmi_device_id scmi_std_id_table[] here to avoid
build failure.
>+static bool scmi_device_id_in_std_id_table(const struct scmi_device_id *id)
>+{
>+ for (int i = 0; scmi_std_id_table[i].name[0]; i++) {
>+ if (scmi_std_id_table[i].protocol_id == id->protocol_id &&
>+ !strcmp(scmi_std_id_table[i].name, id->name))
>+ return true;
>+ }
>+
>+ return false;
>+}
>+
Tested your patch it works well, the pinmux issue gone. A very clean fix.
If you post a formal patch, feel free to add my
Tested-by: Peng Fan <peng.fan@nxp.com>
Thanks a lot.
Thanks,
Peng
next prev parent reply other threads:[~2026-09-30 7:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 11:49 Peng Fan (OSS)
2026-09-28 12:09 ` Sudeep Holla
2026-09-29 1:47 ` Peng Fan
2026-09-29 8:35 ` Sudeep Holla
2026-09-29 15:56 ` Sudeep Holla
2026-09-30 7:06 ` Peng Fan [this message]
2026-09-30 8:24 ` Sudeep Holla
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=ary048HBAkJB4WR9@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=cristian.marussi@arm.com \
--cc=dakr@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=imx@lists.linux.dev \
--cc=johannes.goede@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=rafael@kernel.org \
--cc=saravanak@kernel.org \
--cc=stable@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®