From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Ulf Hansson <ulf.hansson@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Nikunj Kela <nkela@quicinc.com>,
Prasad Sodagudi <psodagud@quicinc.com>,
Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] OPP/pmdomain: Assign required_devs for required OPPs through genpd
Date: Sat, 22 Jun 2024 14:18:05 +0200 [thread overview]
Message-ID: <12b17db6-2649-4b7e-a35e-797ba2d9f2aa@linaro.org> (raw)
In-Reply-To: <20240619140849.368580-1-ulf.hansson@linaro.org>
On 19.06.2024 4:08 PM, Ulf Hansson wrote:
> Through dev_pm_opp_set_config() the _opp_attach_genpd() allows consumer
> drivers to hook up a device to its PM domains. This works for both a single
> and multiple PM domains. Their corresponding virtual devices that are
> created by genpd during attach, are later being assigned as the
> required_devs for the corresponding required OPPs.
>
> In principle this works fine, but there are some problems. Especially as
> the index for a "required-opps" may not necessarily need to match the index
> for the "power-domain" in DT, in which case things gets screwed up.
So, is this series essentially tackling a problem like this:
pdp_A: power-domain-provider@aaaaaa {
[...]
opp-table {
pdp_A_opp0: opp-0 {
opp-level = <0>;
};
};
};
pdp_B: power-domain-provider@bbbbbbb {
[...]
opp-table {
pdp_B_opp0: opp-0 {
opp-level = <0>;
};
};
};
nice-device@ccccccc {
[...]
power-domains = <&pdp_A>,
<&pdp_B>;
// order doesn't match /\
required-opps = <&pdp_B_opp0>,
<&pdp_A_opp0>;
};
?
Konrad
next prev parent reply other threads:[~2024-06-22 12:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 14:08 [PATCH 0/7] OPP/pmdomain: Assign required_devs for required OPPs through genpd Ulf Hansson
2024-06-19 14:08 ` [PATCH 1/7] OPP: Fix support for required OPPs for multiple PM domains Ulf Hansson
2024-06-19 14:08 ` [PATCH 2/7] OPP: Drop a redundant in-parameter to _set_opp_level() Ulf Hansson
2024-06-26 5:47 ` Viresh Kumar
2024-06-19 14:08 ` [PATCH 3/7] OPP: Rework _set_required_devs() to manage a single device per call Ulf Hansson
2024-06-26 6:33 ` Viresh Kumar
2024-07-11 10:19 ` Ulf Hansson
2024-07-11 13:03 ` Viresh Kumar
2024-06-19 14:08 ` [PATCH 4/7] OPP: Introduce an OF helper function to inform if required-opps is used Ulf Hansson
2024-06-26 5:49 ` Viresh Kumar
2024-06-19 14:08 ` [PATCH 5/7] pmdomain: core: Manage the default required OPP from a separate function Ulf Hansson
2024-06-19 14:08 ` [PATCH 6/7] OPP/pmdomain: Set the required_dev for a required OPP during genpd attach Ulf Hansson
2024-06-26 6:37 ` Viresh Kumar
2024-07-11 10:24 ` Ulf Hansson
2024-06-19 14:08 ` [PATCH 7/7] pmdomain: core: Drop the redundant dev_to_genpd_dev() Ulf Hansson
2024-06-22 12:18 ` Konrad Dybcio [this message]
2024-06-24 15:02 ` [PATCH 0/7] OPP/pmdomain: Assign required_devs for required OPPs through genpd 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=12b17db6-2649-4b7e-a35e-797ba2d9f2aa@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=andersson@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nkela@quicinc.com \
--cc=nm@ti.com \
--cc=psodagud@quicinc.com \
--cc=sboyd@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=ulf.hansson@linaro.org \
--cc=vireshk@kernel.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).