From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] opp: Provide a function for just setting bandwidth
Date: Fri, 26 May 2023 12:59:17 +0200 [thread overview]
Message-ID: <f8731d93-b335-6d9a-183c-34a652f45455@linaro.org> (raw)
In-Reply-To: <20230526105320.pfnu3oxl2cm37ot7@vireshk-i7>
On 26.05.2023 12:53, Viresh Kumar wrote:
> On 26-05-23, 11:17, Konrad Dybcio wrote:
>> Currently it's not possible to set just the bandwidth if the OPP
>> describes other properties (required-opps, opp-hz etc.).
>>
>> Introduce dev_pm_opp_set_bw() to solve this problem.
>
> The OPP core (intentionally) doesn't provide any such interface for
> freq, volt, bw, level, etc.
>
> Setting just one of the properties for a device is potentially harmful and the
> OPP must be set as a whole and so this isn't allowed. There is
> dev_pm_opp_set_freq(), but it uses freq to just find the OPP and sets entire OPP
> only.
>
> Why should be break this for bw ?
>
There are some users which have tight power sequencing requirements,
like the Qualcomm Adreno GPU.
Dropping the entire OPP kills clocks, bw and required-opps at once,
but on certain Adrenos we need something like:
disable memory clock (clk)
disable all other clocks, including the opp-managed core clock (clk_bulk)
kill one, fully manually controlled genpd (manual runtime pm)
remove bus vote (func proposed in this patch)
kill another genpd (manual runtime pm)
kill the opp-managed genpd (automatic pm calls)
Changing the order kills the chip until you reboot the whole board and
setting freq=0 using dev_pm_opp_set_rate doesn't drop the bw vote.
Konrad
next prev parent reply other threads:[~2023-05-26 10:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 9:17 [PATCH] opp: Provide a function for just setting bandwidth Konrad Dybcio
2023-05-26 10:53 ` Viresh Kumar
2023-05-26 10:59 ` Konrad Dybcio [this message]
2023-05-29 4:58 ` Viresh Kumar
2023-05-29 9:35 ` Konrad Dybcio
2023-05-29 9:40 ` Viresh Kumar
2023-05-29 11:38 ` Konrad Dybcio
2023-05-29 11:44 ` Viresh Kumar
2023-05-29 10:38 ` Georgi Djakov
2023-05-29 11:40 ` Konrad Dybcio
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=f8731d93-b335-6d9a-183c-34a652f45455@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=viresh.kumar@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