From: Viresh Kumar <viresh.kumar@linaro.org>
To: Nishanth Menon <nm@ti.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Stephen Boyd <sboyd@kernel.org>,
Viresh Kumar <vireshk@kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Dmitry Osipenko <dmitry.osipenko@collabora.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH V2 0/4] OPP: Make ceil/floor/exact helpers share code
Date: Tue, 5 Jul 2022 12:07:36 +0530 [thread overview]
Message-ID: <cover.1657002904.git.viresh.kumar@linaro.org> (raw)
Hello,
All helpers of type ceil/floor/exact do pretty much the same thing. Rewrite them
in order to reduce code redundancy.
Tested the freq based routines on Hikey platform, works as expected.
This is rebased over other recent OPP changes and is pushed here:
git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/pm.git opp/linux-next
V1->V2:
- Don't cast unsigned int * to unsigned long *.
- Rearrange into 4 patches instead of 5.
- Move back to 80 column width.
- New tags.
--
Viresh
Viresh Kumar (4):
OPP: Remove dev_pm_opp_find_freq_ceil_by_volt()
OPP: Add generic key finding helpers and use them for freq APIs
OPP: Use generic key finding helpers for level key
OPP: Use generic key finding helpers for bandwidth key
drivers/opp/core.c | 429 +++++++++++++++--------------------------
include/linux/pm_opp.h | 8 -
2 files changed, 155 insertions(+), 282 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2022-07-05 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 6:37 Viresh Kumar [this message]
2022-07-05 6:37 ` [PATCH V2 1/4] OPP: Remove dev_pm_opp_find_freq_ceil_by_volt() Viresh Kumar
2022-07-05 6:37 ` [PATCH V2 2/4] OPP: Add generic key finding helpers and use them for freq APIs Viresh Kumar
2022-07-05 6:37 ` [PATCH V2 3/4] OPP: Use generic key finding helpers for level key Viresh Kumar
2022-07-05 6:37 ` [PATCH V2 4/4] OPP: Use generic key finding helpers for bandwidth key 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=cover.1657002904.git.viresh.kumar@linaro.org \
--to=viresh.kumar@linaro.org \
--cc=dmitry.osipenko@collabora.com \
--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).