From: Viresh Kumar <viresh.kumar@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
Rob Herring <robh@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
DTML <devicetree@vger.kernel.org>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Hector Yuan <hector.yuan@mediatek.com>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains
Date: Tue, 19 Oct 2021 12:54:25 +0530 [thread overview]
Message-ID: <20211019072425.dvq3ummjdkjmucgm@vireshk-i7> (raw)
In-Reply-To: <CAPDyKFppiogQ5GLQJCqvYGfDQ80HrLLiv43o4H4WBW0PqyONNg@mail.gmail.com>
On 15-10-21, 11:17, Ulf Hansson wrote:
> As far as I understand, the "performance domains" DT bindings that
> $subject patch introduces, allows us to group devices into domains, to
> let them be "performance controlled" together. Right?
This and it also provides a reg space where we can get/set the
performance state.
> Unless I am missing something, it looks like power domains DT bindings
> already offer this for us. Yes, certainly, the DT doc [1] needs an
> updated description to better explain this, but other than that we
> should be fine, don't you think?
I think yes we can make it work through that as well, but I am not
sure if we will be able to use required-opp n stuff here as the DT
doesn't have the OPP table for the CPUs.
The CPU's freq table is generated at runtime, see
drivers/cpufreq/mediatek-cpufreq-hw.c for example.
--
viresh
next prev parent reply other threads:[~2021-10-19 7:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 15:54 [PATCH v4] dt-bindings: dvfs: Add support for generic performance domains Sudeep Holla
2021-05-17 19:17 ` Rob Herring
2021-05-19 11:23 ` Sudeep Holla
2021-05-20 3:54 ` Viresh Kumar
2021-05-17 20:45 ` Rob Herring
2021-05-19 11:20 ` Sudeep Holla
2021-05-20 19:43 ` Rob Herring
2021-05-21 4:08 ` Viresh Kumar
2021-05-21 15:24 ` Sudeep Holla
2021-05-24 9:17 ` Viresh Kumar
2021-05-24 10:05 ` Sudeep Holla
2021-10-14 10:56 ` Ulf Hansson
2021-10-14 14:55 ` Sudeep Holla
2021-10-15 9:17 ` Ulf Hansson
2021-10-19 7:24 ` Viresh Kumar [this message]
2021-10-19 13:58 ` Ulf Hansson
2021-10-20 6:24 ` Viresh Kumar
2021-10-20 10:25 ` Sudeep Holla
2021-10-21 13:34 ` Ulf Hansson
2021-10-21 15:35 ` Sudeep Holla
2021-10-20 12:11 ` Rob Herring
2021-10-21 13:13 ` Ulf Hansson
2021-10-21 13:33 ` Sudeep Holla
2021-10-21 16:01 ` Ulf Hansson
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=20211019072425.dvq3ummjdkjmucgm@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=hector.yuan@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=robh+dt@kernel.org \
--cc=robh@kernel.org \
--cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).