Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Brian Masney <bmasney@redhat.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
	Stephen Boyd <sboyd@kernel.org>,
	linux-tegra@vger.kernel.org, Timo Alho <talho@nvidia.com>,
	Thierry Reding <thierry.reding@kernel.org>,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH V2] clk: tegra: Support unique names for multi-socket platforms
Date: Tue, 7 Jul 2026 16:26:26 +0100	[thread overview]
Message-ID: <a3ee12e9-2173-4386-9426-4752dd84c504@nvidia.com> (raw)
In-Reply-To: <ak0U0HQG-jLlNF5J@redhat.com>

Hi Brian,

On 07/07/2026 16:01, Brian Masney wrote:
> Hi Jon,
> 
> On Tue, Jul 07, 2026 at 07:28:38AM +0100, Jon Hunter wrote:
>> On 02/06/2026 13:01, Thierry Reding wrote:
>>> On Tue, Jun 02, 2026 at 09:43:34AM +0100, Jon Hunter wrote:
>>>> On multi-socket platforms each socket has its own BPMP which exposes the
>>>> same clock names. Fix this by using the NUMA ID as a prefix for the
>>>> clock names on multi-socket platforms.
>>>>
>>>> Use 'sizeof(info->name)' in the strscpy() and snprintf() functions to
>>>> future proof against anyone changing the size of the 'name' array.
>>>>
>>>> Co-developed-by: Timo Alho <talho@nvidia.com>
>>>> Signed-off-by: Timo Alho <talho@nvidia.com>
>>>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>>>> ---
>>>> Changes since V1:
>>>> - Use NUMA ID as a prefix and not a suffix for the clock name.
>>>>
>>>>    drivers/clk/tegra/clk-bpmp.c | 10 +++++++++-
>>>>    1 file changed, 9 insertions(+), 1 deletion(-)
>>>
>>> Reviewed-by: Thierry Reding <treding@nvidia.com>
>>
>>
>> Please let me know if you have any comments on this or if this is OK to be
>> picked up now?
> 
> I made a pull for Stephen last week for various clk patches that were
> missed during the last merge window. I included your patch.
> 
> https://lore.kernel.org/linux-clk/akLzCVzbMbUsgDda@redhat.com/
> 
> I'm going to collect up stuff at rc6 this development cycle and assemble
> another pull then.

OK great! Thanks!

Jon

-- 
nvpublic


  reply	other threads:[~2026-07-07 15:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-02  8:43 [PATCH V2] clk: tegra: Support unique names for multi-socket platforms Jon Hunter
2026-06-02 12:01 ` Thierry Reding
2026-07-07  6:28   ` Jon Hunter
2026-07-07 15:01     ` Brian Masney
2026-07-07 15:26       ` Jon Hunter [this message]
2026-06-15 16:08 ` Brian Masney

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=a3ee12e9-2173-4386-9426-4752dd84c504@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=bmasney@redhat.com \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=sboyd@kernel.org \
    --cc=talho@nvidia.com \
    --cc=thierry.reding@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