public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: Mike Tipton <quic_mdtipton@quicinc.com>,
	Cristian Marussi <cristian.marussi@arm.com>,
	"Rafael J . Wysocki" <rafael@kernel.org>,
	Viresh Kumar <viresh.kumar@linaro.org>,
	arm-scmi@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cpufreq: scmi: Skip SCMI devices that aren't used by the CPUs
Date: Mon, 14 Apr 2025 18:28:14 +0800	[thread overview]
Message-ID: <20250414102813.GB19563@nxa18884-linux> (raw)
In-Reply-To: <20250414-splendid-clam-of-democracy-dacf96@sudeepholla>

Hi Sudeep,
On Mon, Apr 14, 2025 at 09:23:24AM +0100, Sudeep Holla wrote:
>Hi Peng,
>
>On Mon, Apr 14, 2025 at 04:38:32PM +0800, Peng Fan wrote:
>> Hi Mike,
>> On Fri, Apr 11, 2025 at 02:29:41PM -0700, Mike Tipton wrote:
>> >Currently, all SCMI devices with performance domains attempt to register
>> >a cpufreq driver,
>> 
>> The scmi cpufreq device is created based on entry
>> { SCMI_PROTOCOL_PERF, "cpufreq" },
>> 
>> So the scmi-cpufreq driver could only probe the upper single device.
>> 
>> How could the driver work with all SCMI devices with performance domains?
>> 
>
>IIUC, this is on a system with multiple SCMI servers/providers some of
>which don't deal with CPU performance domains at all.

Yeah. This sounds valid case.
CPU perf only needs to be managed by one server, the other server
also has performance domains that only for peripherals.

Thanks,
Peng

>
>-- 
>Regards,
>Sudeep


  reply	other threads:[~2025-04-14  9:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-11 21:29 [PATCH] cpufreq: scmi: Skip SCMI devices that aren't used by the CPUs Mike Tipton
2025-04-14  8:38 ` Peng Fan
2025-04-14  8:23   ` Sudeep Holla
2025-04-14 10:28     ` Peng Fan [this message]
2025-04-14 15:34       ` Mike Tipton
2025-04-15  9:06 ` Peng Fan
2025-04-15 16:44   ` Mike Tipton

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=20250414102813.GB19563@nxa18884-linux \
    --to=peng.fan@oss.nxp.com \
    --cc=arm-scmi@vger.kernel.org \
    --cc=cristian.marussi@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=quic_mdtipton@quicinc.com \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@arm.com \
    --cc=viresh.kumar@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