From: Viresh Kumar <viresh.kumar@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
"Rafael J. Wysocki" <rafael@kernel.org>
Cc: linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/8] OPP: Allow multiple clocks for a device
Date: Mon, 13 Jun 2022 13:37:06 +0530 [thread overview]
Message-ID: <20220613080706.jqilerx6jc4m2pxh@vireshk-i7> (raw)
In-Reply-To: <8b29fa207024dc295639f9ba52c28e45782e3baa.1654849214.git.viresh.kumar@linaro.org>
On 10-06-22, 13:50, Viresh Kumar wrote:
> @@ -1594,24 +1601,28 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_remove_all_dynamic);
> struct dev_pm_opp *_opp_allocate(struct opp_table *opp_table)
> {
> struct dev_pm_opp *opp;
> - int supply_count, supply_size, icc_size;
> + int supply_count, supply_size, icc_size, clk_size;
>
> /* Allocate space for at least one supply */
> supply_count = opp_table->regulator_count > 0 ?
> opp_table->regulator_count : 1;
> supply_size = sizeof(*opp->supplies) * supply_count;
> + clk_size = sizeof(*opp->rates) * opp_table->clk_count;
> icc_size = sizeof(*opp->bandwidth) * opp_table->path_count;
>
> /* allocate new OPP node and supplies structures */
> opp = kzalloc(sizeof(*opp) + supply_size + icc_size, GFP_KERNEL);
The change for this line was lost in rebase I think. I have fixed my branch with
this Krzysztof, so testing over it should be fine. Thanks.
--
viresh
next prev parent reply other threads:[~2022-06-13 8:07 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 8:20 [PATCH 0/8] OPP: Add support for multiple clocks Viresh Kumar
2022-06-10 8:20 ` [PATCH 1/8] OPP: Use consistent names for OPP table instances Viresh Kumar
2022-06-10 8:20 ` [PATCH 2/8] OPP: Remove rate_not_available parameter to _opp_add() Viresh Kumar
2022-06-10 8:20 ` [PATCH 3/8] OPP: Reuse _opp_compare_key() in _opp_add_static_v2() Viresh Kumar
2022-06-22 13:58 ` Jon Hunter
2022-06-22 14:07 ` Viresh Kumar
2022-06-10 8:20 ` [PATCH 4/8] OPP: Make dev_pm_opp_set_opp() independent of frequency Viresh Kumar
2022-06-10 8:20 ` [PATCH 5/8] OPP: Allow multiple clocks for a device Viresh Kumar
2022-06-13 8:07 ` Viresh Kumar [this message]
2022-06-22 13:47 ` Jon Hunter
2022-06-22 14:15 ` Viresh Kumar
2022-06-22 15:27 ` Jon Hunter
2022-06-29 18:33 ` Dmitry Osipenko
2022-06-30 0:50 ` Viresh Kumar
2022-06-30 9:13 ` Dmitry Osipenko
2022-06-30 9:52 ` Viresh Kumar
2022-06-30 9:57 ` Dmitry Osipenko
2022-06-30 10:15 ` Viresh Kumar
2022-07-04 12:09 ` Viresh Kumar
2022-07-04 13:17 ` Dmitry Osipenko
2022-07-04 15:52 ` Viresh Kumar
2022-07-04 18:04 ` Dmitry Osipenko
2022-07-05 4:08 ` Viresh Kumar
2022-06-30 8:38 ` Krzysztof Kozlowski
2022-06-30 9:39 ` Viresh Kumar
2022-06-30 12:32 ` Krzysztof Kozlowski
2022-06-30 12:39 ` Krzysztof Kozlowski
2022-07-01 6:47 ` Viresh Kumar
2022-07-05 6:59 ` Viresh Kumar
2022-07-05 8:18 ` Krzysztof Kozlowski
2022-07-05 8:40 ` Viresh Kumar
2022-06-10 8:20 ` [PATCH 6/8] OPP: Add key specific assert() method to key finding helpers Viresh Kumar
2022-06-10 8:20 ` [PATCH 7/8] OPP: Assert clk_count == 1 for single clk helpers Viresh Kumar
2022-06-10 8:20 ` [PATCH 8/8] OPP: Provide a simple implementation to configure multiple clocks Viresh Kumar
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=20220613080706.jqilerx6jc4m2pxh@vireshk-i7 \
--to=viresh.kumar@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=vincent.guittot@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).