From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@kernel.org>
Cc: <linux-tegra@vger.kernel.org>, Jon Hunter <jonathanh@nvidia.com>
Subject: [PATCH] firmware: tegra: bpmp: Add support for multi-socket platforms
Date: Fri, 22 May 2026 11:16:14 +0100 [thread overview]
Message-ID: <20260522101614.24028-1-jonathanh@nvidia.com> (raw)
On multi-socket platforms each socket has its own BPMP that is
registered with the kernel. For such platforms append the NUMA ID for
each socket to the BPMP debugfs directory name to ensure there is a
unique name for each BPMP. Note that a 32 byte array is more than large
enough for storing the name.
Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
---
drivers/firmware/tegra/bpmp-debugfs.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/firmware/tegra/bpmp-debugfs.c b/drivers/firmware/tegra/bpmp-debugfs.c
index 4221fed70ad4..4f15aae5f124 100644
--- a/drivers/firmware/tegra/bpmp-debugfs.c
+++ b/drivers/firmware/tegra/bpmp-debugfs.c
@@ -772,6 +772,7 @@ static int bpmp_populate_debugfs_shmem(struct tegra_bpmp *bpmp)
int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
{
struct dentry *root;
+ char name[32] = "bpmp";
bool inband;
int err;
@@ -780,7 +781,10 @@ int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
if (!inband && !tegra_bpmp_mrq_is_supported(bpmp, MRQ_DEBUGFS))
return 0;
- root = debugfs_create_dir("bpmp", NULL);
+ if (dev_to_node(bpmp->dev) != NUMA_NO_NODE)
+ snprintf(name, sizeof(name), "bpmp.%d", dev_to_node(bpmp->dev));
+
+ root = debugfs_create_dir(name, NULL);
if (IS_ERR(root))
return -ENOMEM;
--
2.43.0
next reply other threads:[~2026-05-22 10:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-22 10:16 Jon Hunter [this message]
2026-05-29 15:10 ` [PATCH] firmware: tegra: bpmp: Add support for multi-socket platforms 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=20260522101614.24028-1-jonathanh@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-tegra@vger.kernel.org \
--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