From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@oss.qualcomm.com>, rafael@kernel.org
Cc: linux-pm@vger.kernel.org, shuah@kernel.org,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org,
manaf.pallikunhi@oss.qualcomm.com
Subject: Re: [PATCH 0/2] powercap: Introduce generic hierarchy helpers and selftests
Date: Mon, 7 Sep 2026 11:46:14 +0100 [thread overview]
Message-ID: <350caba2-4a95-4945-91dd-0be89b2d3e22@arm.com> (raw)
In-Reply-To: <ef124b64-e7d2-4c9c-9890-00685e34f314@oss.qualcomm.com>
Hi Daniel,
On 9/7/26 11:03, Daniel Lezcano wrote:
>
> Hi Rafael,
>
> On 8/6/26 13:01, Daniel Lezcano wrote:
>> Powercap controllers frequently expose a hierarchy of power zones (for
>> example package, clusters and CPUs). Until now, each driver had to
>> implement its own hierarchy traversal, parent lookup, error handling and
>> teardown logic.
>>
>> This series introduces a generic hierarchy description and helper
>> functions allowing a controller to instantiate and destroy an entire
>> powercap hierarchy from a static description. The framework takes care of
>> duplicating the hierarchy description, rebasing parent pointers,
>> creating zones in dependency order and performing the appropriate
>> rollback and cleanup on errors.
>>
>> The series also adds a kselftest exercising the new API by creating a
>> synthetic hierarchy, validating the exported sysfs hierarchy and
>> attributes, and ensuring that all resources are correctly released when
>> the hierarchy is destroyed.
>>
>> The patches are organized as follows:
>>
>> 1. powercap: Add generic zone hierarchy creation helpers
>> 2. selftests/powercap: Add powercap hierarchy creation API tests
>>
>> The API was primarily motivated by the recently posted SPEL series and
>> also provides a migration path for DTPM to use the same generic
>> infrastructure instead of maintaining its own hierarchy handling.
>>
>> Link: SPEL cover letter <https://lore.kernel.org/lkml/20260702-
>> qcom_spel_driver_upstream-v3-0-434d50f0c5b0@oss.qualcomm.com/>
>>
>> Daniel Lezcano (2):
>> powercap: Add generic zone hierarchy creation helpers
>> selftests/powercap: Add powercap hierarchy creation API tests
>>
>> --
> It was easy to migrate DTPM to this API and AFAICT Manaf was able to
> migrate also its series to this new API.
>
> Is it possible to consider it for merging ?
I will do a review for this patch set today...
I can see some potential improvements there.
Regards,
Lukasz
next prev parent reply other threads:[~2026-09-07 10:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 11:01 [PATCH 0/2] powercap: Introduce generic hierarchy helpers and selftests Daniel Lezcano
2026-08-06 11:01 ` [PATCH 1/2] powercap: Add generic zone hierarchy creation helpers Daniel Lezcano
2026-08-06 11:01 ` [PATCH 2/2] selftests/powercap: Add powercap hierarchy creation API tests Daniel Lezcano
2026-09-07 10:03 ` [PATCH 0/2] powercap: Introduce generic hierarchy helpers and selftests Daniel Lezcano
2026-09-07 10:46 ` Lukasz Luba [this message]
2026-09-11 15:44 ` Manaf Meethalavalappu Pallikunhi
2026-09-11 15:48 ` 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=350caba2-4a95-4945-91dd-0be89b2d3e22@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@oss.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=manaf.pallikunhi@oss.qualcomm.com \
--cc=rafael@kernel.org \
--cc=shuah@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