From: Thierry Reding <thierry.reding@kernel.org>
To: Jon Hunter <jonathanh@nvidia.com>
Cc: Ulf Hansson <ulfh@kernel.org>,
linux-pm@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH V2] pmdomain: tegra: Add support for multi-socket platforms
Date: Tue, 2 Jun 2026 13:59:59 +0200 [thread overview]
Message-ID: <ah6_-WJrMOiPkMVS@orome> (raw)
In-Reply-To: <20260602083959.350689-1-jonathanh@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1951 bytes --]
On Tue, Jun 02, 2026 at 09:39:59AM +0100, Jon Hunter wrote:
> On multi-socket platforms each socket has its own BPMP that is
> registered with the kernel. For such platforms prefix the NUMA ID for
> each socket to the BPMP powergate name to ensure there is a unique name
> for each power-domain. Note that we only add the NUMA ID for powergates
> that return a valid name because an invalid name indicates that the
> powergate ID is not supported.
>
> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
> ---
> Changes since V1:
> - Use NUMA ID as a prefix and not a suffix for the powergate name.
>
> drivers/pmdomain/tegra/powergate-bpmp.c | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/drivers/pmdomain/tegra/powergate-bpmp.c b/drivers/pmdomain/tegra/powergate-bpmp.c
> index 8cde4f384846..5e869b0eb96e 100644
> --- a/drivers/pmdomain/tegra/powergate-bpmp.c
> +++ b/drivers/pmdomain/tegra/powergate-bpmp.c
> @@ -137,6 +137,11 @@ static char *tegra_bpmp_powergate_get_name(struct tegra_bpmp *bpmp,
> if (err < 0 || msg.rx.ret < 0)
> return NULL;
>
> + if (response.get_name.name[0] != '\0' &&
> + dev_to_node(bpmp->dev) != NUMA_NO_NODE)
> + return kasprintf(GFP_KERNEL, "%d-%s", dev_to_node(bpmp->dev),
> + response.get_name.name);
> +
> return kstrdup(response.get_name.name, GFP_KERNEL);
Why are we not checking response.get_name.name for the empty string in
the single socket case? Or the other way around: why is this important
for multi-socket if it isn't for single socket?
Looking at the caller of this function, it will check for this case
itself, so I'm thinking we should rework that as part of this patch and
simply return NULL early for both cases when name[0] == '\0'. That way
the caller is simplified and we get a bit more consistency in this
function. It is going to make for a slightly bigger diff, but I think
overall it'd be an improvement.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-06-02 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 8:39 [PATCH V2] pmdomain: tegra: Add support for multi-socket platforms Jon Hunter
2026-06-02 11:59 ` Thierry Reding [this message]
2026-06-02 13:39 ` Jon Hunter
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=ah6_-WJrMOiPkMVS@orome \
--to=thierry.reding@kernel.org \
--cc=jonathanh@nvidia.com \
--cc=linux-pm@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=ulfh@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