From: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>
To: daniel.lezcano@oss.qualcomm.com, rafael@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org
Subject: [PATCH v1 0/4] powercap: dtpm: Use generic hierarchy helpers and add RK3588 support
Date: Wed, 19 Aug 2026 18:56:01 +0200 [thread overview]
Message-ID: <20260819165605.1398880-1-daniel.lezcano@oss.qualcomm.com> (raw)
This series builds on top of the previously submitted powercap series
introducing the generic powercap hierarchy infrastructure.
DTPM currently implements its own hierarchy creation logic to walk a
platform-provided description, create the corresponding DTPM zones and
tear them down. With the generic powercap hierarchy infrastructure in
place, this logic can be shared at the powercap core level.
Convert DTPM to use the generic powercap hierarchy helpers. The platform
hierarchy is duplicated before use and powercap_hierarchy_create() and
powercap_hierarchy_destroy() take care of its lifetime and traversal.
DTPM provides the callbacks responsible for creating and destroying the
DTPM instance associated with each powercap node. The CPU and devfreq
backends are adjusted accordingly.
As a preparation for this conversion, simplify the existing RK3399
description. The CPU backend creates one DTPM zone per cpufreq policy,
so describing every CPU belonging to the same policy results in
duplicate zones. Keep only one CPU node for each RK3399 cpufreq policy.
The Rockchip virtual node descriptor is then made SoC-independent so it
can be reused by other Rockchip platforms.
Finally, add an RK3588 hierarchy. The RK3588 has three cpufreq policies,
represented by cpu@0, cpu@400 and cpu@600. These three CPU domains are
grouped below a virtual package node:
rk3588
`-- package
|-- cpu0-cpufreq
|-- cpu4-cpufreq
`-- cpu6-cpufreq
This series depends on:
Link: https://lore.kernel.org/all/20260806110159.69690-1-daniel.lezcano@oss.qualcomm.com/
Daniel Lezcano (4):
powercap: dtpm: Remove duplicate RK3399 CPU hierarchy nodes
powercap: dtpm: Use generic powercap hierarchy helpers
powercap: dtpm: Rename Rockchip virtual node descriptor
powercap: dtpm: Add RK3588 hierarchy
--
2.43.0
Daniel Lezcano (4):
powercap: dtpm: Remove duplicate RK3399 CPU hierarchy nodes
powercap: dtpm: Use generic powercap hierarchy helpers
powercap: dtpm: Rename Rockchip virtual node descriptor
powercap: dtpm: Add RK3588 hierarchy
drivers/powercap/dtpm.c | 165 ++++++++++++++------------------
drivers/powercap/dtpm_cpu.c | 22 ++---
drivers/powercap/dtpm_devfreq.c | 22 +++--
drivers/soc/rockchip/dtpm.c | 127 ++++++++++++++++++------
include/linux/dtpm.h | 5 +-
5 files changed, 195 insertions(+), 146 deletions(-)
--
2.43.0
next reply other threads:[~2026-08-19 16:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 16:56 Daniel Lezcano [this message]
2026-08-19 16:56 ` [PATCH v1 1/4] powercap: dtpm: Remove duplicate RK3399 CPU hierarchy nodes Daniel Lezcano
2026-08-19 16:56 ` [PATCH v1 2/4] powercap: dtpm: Use generic powercap hierarchy helpers Daniel Lezcano
2026-08-19 16:56 ` [PATCH v1 3/4] powercap: dtpm: Rename Rockchip virtual node descriptor Daniel Lezcano
2026-08-19 16:56 ` [PATCH v1 4/4] powercap: dtpm: Add RK3588 hierarchy Daniel Lezcano
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=20260819165605.1398880-1-daniel.lezcano@oss.qualcomm.com \
--to=daniel.lezcano@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@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