public inbox for linux-pm@vger.kernel.org
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"cristian.marussi@arm.com" <cristian.marussi@arm.com>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	Ranjani Vaidyanathan <ranjani.vaidyanathan@nxp.com>,
	Glen G Wienecke <glen.wienecke@nxp.com>
Subject: Re: Question regarding scmi_perf_domain.c
Date: Tue, 10 Oct 2023 14:30:59 +0100	[thread overview]
Message-ID: <20231010133059.57rs52qedrc5mxfr@bogus> (raw)
In-Reply-To: <DU0PR04MB94177FFEAA62AC27839D826F88CDA@DU0PR04MB9417.eurprd04.prod.outlook.com>

On Tue, Oct 10, 2023 at 01:15:26PM +0000, Peng Fan wrote:
> 
> Thanks for the detailed explanation, so power-domains property could be
> used both for power domain or performance domain. But if one
> device has both power domain and performance domain. Only power-domain
> property is not enough. I may understand wrong, let me look into the code.
> 

I haven't tried this but something I could come up quick wit Juno DTS
as reference:

We can change something like this:

      scmi_dvfs: protocol@13 {
              reg = <0x13>;
-             #clock-cells = <1>;
+             #power-domain-cells = <1>;
              mbox-names = "tx", "rx";
              mboxes = <&mailbox 1 0 &mailbox 1 1>;
              shmem = <&cpu_scp_hpri0 &cpu_scp_hpri1>;
      };

And then in the consumer node(taking GPU as it has both perf and power
domains). The CPUs are simpler as don't have explicit power domains, some
Qcom platforms do use that. Anyways I would change GPU node like this.
Hope this clarifies things for you.

 &gpu {
-       clocks = <&scmi_dvfs 2>;
-       power-domains = <&scmi_devpd 9>;
+       power-domains = <&scmi_dvfs 2 &scmi_devpd 9>;
+       power-domain-names = "perf", "power";
        status = "disabled";
 };

-- 
Regards,
Sudeep

  reply	other threads:[~2023-10-10 13:31 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
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 [this message]
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=20231010133059.57rs52qedrc5mxfr@bogus \
    --to=sudeep.holla@arm.com \
    --cc=cristian.marussi@arm.com \
    --cc=glen.wienecke@nxp.com \
    --cc=linux-pm@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=ranjani.vaidyanathan@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