From: Lukasz Luba <lukasz.luba@arm.com>
To: Daniel Lezcano <daniel.lezcano@linaro.org>
Cc: rafael@kernel.org, linux-kernel@vger.kernel.org,
linux-pm@vger.kernel.org
Subject: Re: [PATCH v3 2/5] powercap/drivers/dtpm: Create a registering system
Date: Thu, 11 Mar 2021 10:23:11 +0000 [thread overview]
Message-ID: <bbafd2d8-ea89-5e96-5742-6d1a924e3649@arm.com> (raw)
In-Reply-To: <20210310110212.26512-2-daniel.lezcano@linaro.org>
On 3/10/21 11:02 AM, Daniel Lezcano wrote:
> A SoC can be differently structured depending on the platform and the
> kernel can not be aware of all the combinations, as well as the
> specific tweaks for a particular board.
>
> The creation of the hierarchy must be delegated to userspace.
>
> These changes provide a registering mechanism where the different
> subsystems will initialize their dtpm backends and register with a
> name the dtpm node in a list.
>
> The next changes will provide an userspace interface to create
> hierachically the different nodes. Those will be created by name and
s/hierachically/hierarchically
> found via the list filled by the different subsystem.
>
> If a specified name is not found in the list, it is assumed to be a
> virtual node which will have children and the default is to allocate
> such node.
>
> When the node register in the list, the function will be dtpm_register
> where the previous semantic was to create the node. Thus, the
> functions are renamed to reflect their purpose.
>
> Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
> ---
>
> V2:
> - Fixed error code path by dropping lock
> ---
> drivers/powercap/dtpm.c | 161 ++++++++++++++++++++++++++++++++++--
> drivers/powercap/dtpm_cpu.c | 4 +-
> include/linux/dtpm.h | 12 ++-
> 3 files changed, 164 insertions(+), 13 deletions(-)
>
apart from the above, LGTM
Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
next prev parent reply other threads:[~2021-03-11 10:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 11:02 [PATCH v3 1/5] powercap/drivers/dtpm: Encapsulate even more the code Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 2/5] powercap/drivers/dtpm: Create a registering system Daniel Lezcano
2021-03-11 10:23 ` Lukasz Luba [this message]
2021-03-10 11:02 ` [PATCH v3 3/5] powercap/drivers/dtpm: Simplify the dtpm table Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 4/5] powercap/drivers/dtpm: Use container_of instead of a private data field Daniel Lezcano
2021-03-10 11:02 ` [PATCH v3 5/5] powercap/drivers/dtpm: Scale the power with the load Daniel Lezcano
2021-03-10 11:22 ` Lukasz Luba
2021-03-11 10:15 ` [PATCH v3 1/5] powercap/drivers/dtpm: Encapsulate even more the code Lukasz Luba
2021-03-11 10:57 ` Daniel Lezcano
2021-03-12 10:11 ` Lukasz Luba
2021-03-12 10:22 ` Lukasz Luba
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=bbafd2d8-ea89-5e96-5742-6d1a924e3649@arm.com \
--to=lukasz.luba@arm.com \
--cc=daniel.lezcano@linaro.org \
--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
all inboxes | Powered by JetHome®