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>,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/6] OPP: Scope based cleanup helpers and lock guards
Date: Thu, 24 Apr 2025 16:06:43 +0530 [thread overview]
Message-ID: <cover.1745490980.git.viresh.kumar@linaro.org> (raw)
Hello,
This series performs various cleanups / optimizations for the OPP core.
- Introduce and use scope based cleanup headers
- Use mutex locking guards
No intentional functional impact.
--
Viresh
Viresh Kumar (6):
OPP: Remove _get_opp_table_kref()
OPP: Return opp from dev_pm_opp_get()
OPP: Return opp_table from dev_pm_opp_get_opp_table_ref()
OPP: Use scope-based OF cleanup helpers
OPP: Define and use scope-based cleanup helpers
OPP: Use mutex locking guards
drivers/opp/core.c | 426 ++++++++++++++---------------------------
drivers/opp/cpu.c | 30 +--
drivers/opp/of.c | 205 +++++++-------------
drivers/opp/opp.h | 1 -
include/linux/pm_opp.h | 21 +-
5 files changed, 249 insertions(+), 434 deletions(-)
--
2.31.1.272.g89b43f80a514
next reply other threads:[~2025-04-24 10:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-24 10:36 Viresh Kumar [this message]
2025-04-24 10:36 ` [PATCH 1/6] OPP: Remove _get_opp_table_kref() Viresh Kumar
2025-04-24 10:36 ` [PATCH 2/6] OPP: Return opp from dev_pm_opp_get() Viresh Kumar
2025-04-24 10:36 ` [PATCH 3/6] OPP: Return opp_table from dev_pm_opp_get_opp_table_ref() Viresh Kumar
2025-04-24 10:36 ` [PATCH 4/6] OPP: Use scope-based OF cleanup helpers Viresh Kumar
2025-04-24 10:36 ` [PATCH 5/6] OPP: Define and use scope-based " Viresh Kumar
2025-04-24 10:36 ` [PATCH 6/6] OPP: Use mutex locking guards 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.1745490980.git.viresh.kumar@linaro.org \
--to=viresh.kumar@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).