From: Cristian Marussi <cristian.marussi@arm.com>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
Cc: Cristian Marussi <cristian.marussi@arm.com>,
arm-scmi@vger.kernel.org, guomin_chen@sina.com,
linux-arm-kernel@lists.infradead.org, peng.fan@nxp.com,
quic_xinqzhan@quicinc.com, sudeep.holla@arm.com
Subject: Re: [RFC PATCH 2/2] firmware: arm_scmi: Add bus support for autoloading
Date: Mon, 8 Jun 2026 21:53:00 +0100 [thread overview]
Message-ID: <aicrrJHflSTu5g0v@pluto> (raw)
In-Reply-To: <256c182e-a093-4bf5-a353-ca5c06eff489@oss.qualcomm.com>
On Mon, Jun 08, 2026 at 07:06:42PM +0200, Daniel Lezcano wrote:
>
> Hi Cristian,
>
> thanks for your answer
>
> On 6/8/26 18:51, Cristian Marussi wrote:
> > On Mon, Jun 08, 2026 at 04:51:03PM +0200, Daniel Lezcano wrote:
> > > On Mon, Feb 03, 2025 at 10:01:54AM +0000, Cristian Marussi wrote:
> > > > Emit proper MODALIAS uevents when SCMI devices are created and make sure
> > > > all the standard protocol devices are requested when the bus is
> > > > initialized.
> > > >
> > > > Signed-off-by: Cristian Marussi <cristian.marussi@arm.com>
> > > > ---
> > >
> > > Hi Cristian,
Hi,
> > >
> >
> > Hi Daniel,
> >
> > nice to hear from you in the SCMI land :P
> >
> > > what is the status of this patch ?
> >
> > ....I'd say forgotten/abandoned...I worked on that a bit when I realized
> > only part of the stack was autoloaded...then it did NOT received much
> > love and then I forgot it....buried by other prios....
> >
> > Indeed I have still the local branch...but after a quick check I think
> > is the same as the RFC posted.
> >
> > bbd14b0f7733 firmware: arm_scmi: Add bus support for autoloading
> > 8d982393b505 firmware: arm_scmi: Generate aliases for SCMI modules
> > 383c127faa97 (scmi_vendors_autoload_V2) firmware: arm_scmi: Add aliases to transport modules
> > 00caa894bce2 firmware: arm_scmi: Add module aliases to i.MX vendor protocols
> > d900620c46bb firmware: arm_scmi: Support vendor protocol modules autoloading
> > 4fe57bbeb6dc firmware: arm_scmi: Allow transport properties for multiple instances
> > ad236e5a7f01 Linux 6.13-rc1
> >
> > ...where scmi_vendors_autoload_V2 is merged already...
>
> Actually, I'm puzzled.
>
> On our platform, until 7.1-rc1 we had to add a modprobe.d script to load the
> scmi_cpufreq driver because autoload was not suppported.
>
> Now (7.1-rc1) it seems to be automatically loaded.
>
mmm...I am not sure....but I have a memory to have seen this behaviour
with cpufreq...on some more full-fledged distro (not the usual bare
minimum deboostrapped thing...)...never fully investigated though...
> I imagined the autoload module has been added between 7.0 and 7.1, but the
> series you are mentioning is from 6.13.
Not sure when effectively merged BUT definitely NOT 7.0/7.1...
>
> What I am missing ?
Any chance that on a more complete kernel/distro some symbol dependencies
in modules.dep kicks in, unknowingly, that triggers the load of
scmi-coufreq ?
Not sure if it make any sense...since I miss anyway where the
SCMI-cpufreq <---> cpufreq-driver association is baked in with the current
module device tables...
Not so much of an help here...sorry.
Anyway, I may respin this in the future if there is some interest...unless
someone precedes me :D
Thanks
Cristian
next prev parent reply other threads:[~2026-06-08 20:53 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 14:18 [PATCH 1/3] firmware: arm_scmi: Relax duplicate name constraint across protocol ids Sudeep Holla
2025-01-31 14:18 ` [PATCH 2/3] firmware: arm_scmi: Add name and protocol id attributes Sudeep Holla
2025-02-03 6:25 ` Dhruva Gole
2025-01-31 14:18 ` [PATCH 3/3] firmware: arm_scmi: Emit modalias for SCMI devices Sudeep Holla
2025-02-03 9:33 ` Cristian Marussi
2025-02-03 10:01 ` [RFC PATCH 1/2] firmware: arm_scmi: Generate aliases for SCMI modules Cristian Marussi
2025-02-03 10:01 ` [RFC PATCH 2/2] firmware: arm_scmi: Add bus support for autoloading Cristian Marussi
2026-06-08 14:51 ` Daniel Lezcano
2026-06-08 16:51 ` Cristian Marussi
2026-06-08 17:06 ` Daniel Lezcano
2026-06-08 20:53 ` Cristian Marussi [this message]
2025-02-02 11:08 ` [PATCH 1/3] firmware: arm_scmi: Relax duplicate name constraint across protocol ids Peng Fan
2025-02-03 6:21 ` Dhruva Gole
2025-02-21 11:36 ` 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=aicrrJHflSTu5g0v@pluto \
--to=cristian.marussi@arm.com \
--cc=arm-scmi@vger.kernel.org \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=guomin_chen@sina.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=quic_xinqzhan@quicinc.com \
--cc=sudeep.holla@arm.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