From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
"cristian.marussi@arm.com" <cristian.marussi@arm.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>
Subject: Re: Question regarding scmi_perf_domain.c
Date: Tue, 10 Oct 2023 11:55:03 +0100 [thread overview]
Message-ID: <20231010105503.jwrmjahuvcjgwtk5@bogus> (raw)
In-Reply-To: <DU0PR04MB9417DE145496DC03579F50E488CDA@DU0PR04MB9417.eurprd04.prod.outlook.com>
On Tue, Oct 10, 2023 at 10:30:17AM +0000, Peng Fan wrote:
> Hi Ulf,
>
> I just see you wrote scmi_perf_domain.c, just wonder this driver is only
> for devices, not support arm cores, right?
>
> For ARM cores, we still need scmi_cpufreq.c for performance settings,
> right?
Sorry if I wasn't clear. The reason I mentioned it in private is that
we now support the power domain bindings in the scmi-cpufreq.c as you
were little bit nervous to use the clock bindings(though they work just
fine, I understand the possible confusion with the clock protocol).
There is also separate SCMI performance genpd driver that works for
non-CPU devices. As Ulf mentioned, scmi-cpufreq is not dependent on
those genpd performance driver ATM and we still need to check if it
has to be yet. Hope that clarifies.
--
Regards,
Sudeep
next prev parent reply other threads:[~2023-10-10 10:55 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-10 10:30 Question regarding scmi_perf_domain.c Peng Fan
2023-10-10 10:38 ` Ulf Hansson
2023-10-10 10:55 ` Sudeep Holla [this message]
2023-10-10 11:02 ` Ulf Hansson
2023-10-10 12:01 ` Peng Fan
2023-10-10 13:00 ` Sudeep Holla
2023-10-10 13:15 ` Peng Fan
2023-10-10 13:30 ` Sudeep Holla
2023-10-10 13:43 ` Peng Fan
2023-10-10 14:51 ` Sudeep Holla
2023-10-10 15:23 ` Ulf Hansson
2023-10-10 16:23 ` Sudeep Holla
2023-10-10 21:14 ` Ulf Hansson
2023-10-11 0:30 ` Peng Fan
2023-10-11 9:16 ` Sudeep Holla
2023-10-11 9:26 ` Ulf Hansson
2023-10-11 11:52 ` Peng Fan
2023-10-11 14:15 ` Sudeep Holla
2023-10-12 11:53 ` Ulf Hansson
2023-10-16 15:08 ` Ulf Hansson
2023-10-17 9:04 ` Sudeep Holla
2023-10-17 10:46 ` Ulf Hansson
2023-10-17 13:49 ` Sudeep Holla
2023-10-17 13:18 ` Peng Fan
2023-10-17 13:55 ` Sudeep Holla
2023-10-17 14:35 ` Peng Fan
2023-10-17 16:24 ` Sudeep Holla
2023-10-10 12:48 ` Sudeep Holla
2023-10-10 12:53 ` Peng Fan
2023-10-10 13:02 ` 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=20231010105503.jwrmjahuvcjgwtk5@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=linux-pm@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=ulf.hansson@linaro.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