From: Austin Schuh <austin.linux@gmail.com>
To: Thierry Reding <thierry.reding@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>
Cc: Austin Schuh <austin.linux@gmail.com>,
Mikko Perttunen <mperttunen@nvidia.com>,
Aniruddha Rao <anrao@nvidia.com>,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2] firmware: tegra: bpmp: populate debugfs in the background
Date: Fri, 23 Oct 2026 22:50:54 -0700 [thread overview]
Message-ID: <20261024055055.602558-1-austin.linux@gmail.com> (raw)
In-Reply-To: <n59f1S6wQICe5ZxgcNxb3w@nvidia.com>
Populating the BPMP debugfs mirror takes a series of synchronous BPMP
requests, several per directory. On an Orin Nano (Tegra234) the tree has
about 10,800 entries, and the BPMP probe doesn't return for between two
and six seconds, depending on the L4T release. Every device that gets its
clocks, resets or power domains from the BPMP waits for it, which on
Tegra234 is nearly all of them, so PCIe, NVMe and the root filesystem all
come up that much later.
Commit c7fc690da6f1 ("firmware: tegra: bpmp: Allow BPMP debugfs population
to be skipped") lets a system that doesn't need the mirror turn it off with
tegra_bpmp.debugfs=0. A system that does use it, for instance to set
clocks from userspace at boot, still pays the full cost.
Nothing in the kernel uses the mirror, and the probe already only logs an
error from it, so populate it from a workqueue instead. It isn't an
async_schedule() job, since kernel_init() waits for all of those before it
starts init. The workqueue is freezable, so a system suspend waits for the
mirror instead of failing its requests, and the mirrors of a system with
several BPMPs are populated one at a time, as their probes did, so that one
failing can't remove the shared root while another is filling it in.
The mirror is filled in as .debug-populating and renamed to debug once it
is complete, so userspace never sees part of it. Userspace that needs it
right after boot can wait for debug to appear: the rename sends inotify an
IN_MOVED_TO event on the directory above it. With systemd, a path unit can
start the service that uses the mirror once it is there:
# bpmp-debugfs.path
[Path]
PathExists=/sys/kernel/debug/bpmp/debug
Unit=bpmp-clocks.service
[Install]
WantedBy=paths.target
A Type=oneshot bpmp-clocks.service needs RemainAfterExit=yes, or the path
unit starts it again each time it exits.
Measured with initcall_debug on an Orin Nano running 6.18.39 with
NVIDIA's patches: with an earlier L4T release, the probe returns after
1.2 seconds instead of 6.36. With the BPMP firmware from L4T 39.2.1 it
returns after 0.51 seconds, and the mirror is complete and renamed 2.2
seconds later, about 1.3 seconds after init has started.
Assisted-by: LLM
Signed-off-by: Austin Schuh <austin.linux@gmail.com>
---
Notes:
Changes in v2 (thanks, Mikko):
- Embed the work_struct in struct tegra_bpmp instead of allocating it,
and cancel it with cancel_work_sync() from a devm action.
- Fill the mirror in as .debug-populating and rename it to debug once
it is complete, so userspace never sees part of it, and can wait for
it by waiting for debug to appear.
- Queue the work on system_freezable_wq, so a system suspend waits for
it instead of failing its BPMP requests with -EAGAIN and tearing the
mirror down.
- Hold bpmp_debugfs_root_lock across the whole population, so two BPMPs
are populated one at a time, as their probes did, and one failing
can't remove the shared root while the other is creating its
directory in it.
- Move the work into bpmp-debugfs.c; tegra_bpmp_probe() is unchanged.
Based on tegra/for-7.4/firmware (1bbcf4a19f14). Built for arm64, W=1,
no new warnings. Booted on an Orin Nano with the same change on 6.18.39
with NVIDIA's patches: the mirror appears complete, with all 10,831
entries, and reads correctly. With a 20 second delay added before the
rename, the path unit from the commit message started its service 3 ms
after the rename, and the service saw all 10,831 entries.
v1: https://lore.kernel.org/r/20261017065012.3063980-1-austin.linux@gmail.com
drivers/firmware/tegra/bpmp-debugfs.c | 67 ++++++++++++++++++++++++---
include/soc/tegra/bpmp.h | 2 +
2 files changed, 62 insertions(+), 7 deletions(-)
diff --git a/drivers/firmware/tegra/bpmp-debugfs.c b/drivers/firmware/tegra/bpmp-debugfs.c
index 2efc48b522ac..bfc13e990eb2 100644
--- a/drivers/firmware/tegra/bpmp-debugfs.c
+++ b/drivers/firmware/tegra/bpmp-debugfs.c
@@ -782,27 +782,30 @@ MODULE_PARM_DESC(debugfs,
static struct dentry *bpmp_debugfs_get_root(void)
{
- guard(mutex)(&bpmp_debugfs_root_lock);
+ lockdep_assert_held(&bpmp_debugfs_root_lock);
if (!bpmp_debugfs_root)
bpmp_debugfs_root = debugfs_create_dir("bpmp", NULL);
return bpmp_debugfs_root;
}
-int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
+static int tegra_bpmp_populate_debugfs(struct tegra_bpmp *bpmp)
{
struct dentry *root, *d;
char name[32];
bool inband;
int err;
- if (!bpmp_debugfs_enabled)
- return 0;
-
inband = tegra_bpmp_mrq_is_supported(bpmp, MRQ_DEBUG);
if (!inband && !tegra_bpmp_mrq_is_supported(bpmp, MRQ_DEBUGFS))
return 0;
+ /*
+ * Populate one BPMP at a time, so that one failing can't remove the
+ * shared root while another is creating its directory in it.
+ */
+ guard(mutex)(&bpmp_debugfs_root_lock);
+
root = bpmp_debugfs_get_root();
if (IS_ERR(root))
return PTR_ERR(root);
@@ -818,7 +821,11 @@ int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
}
}
- bpmp->debugfs_mirror = debugfs_create_dir("debug", d);
+ /*
+ * Fill the mirror in under another name and rename it to "debug"
+ * once it is complete, so that userspace never sees part of it.
+ */
+ bpmp->debugfs_mirror = debugfs_create_dir(".debug-populating", d);
if (IS_ERR(bpmp->debugfs_mirror)) {
err = PTR_ERR(bpmp->debugfs_mirror);
goto out;
@@ -830,12 +837,14 @@ int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
else
err = bpmp_populate_debugfs_shmem(bpmp);
+ if (!err)
+ err = debugfs_change_name(bpmp->debugfs_mirror, "debug");
+
out:
if (err < 0) {
if (!IS_ERR(d))
debugfs_remove_recursive(d);
- guard(mutex)(&bpmp_debugfs_root_lock);
if (root == d) {
bpmp_debugfs_root = NULL;
} else if (simple_empty(root)) {
@@ -846,3 +855,47 @@ int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
return err;
}
+
+static void tegra_bpmp_debugfs_work(struct work_struct *work)
+{
+ struct tegra_bpmp *bpmp =
+ container_of(work, struct tegra_bpmp, debugfs_work);
+ int err;
+
+ err = tegra_bpmp_populate_debugfs(bpmp);
+ if (err < 0)
+ dev_err(bpmp->dev, "debugfs initialization failed: %d\n", err);
+}
+
+static void tegra_bpmp_cancel_debugfs(void *data)
+{
+ struct tegra_bpmp *bpmp = data;
+
+ cancel_work_sync(&bpmp->debugfs_work);
+}
+
+int tegra_bpmp_init_debugfs(struct tegra_bpmp *bpmp)
+{
+ int err;
+
+ if (!bpmp_debugfs_enabled)
+ return 0;
+
+ INIT_WORK(&bpmp->debugfs_work, tegra_bpmp_debugfs_work);
+
+ err = devm_add_action_or_reset(bpmp->dev, tegra_bpmp_cancel_debugfs,
+ bpmp);
+ if (err < 0)
+ return err;
+
+ /*
+ * Mirroring the BPMP's debugfs tree takes several requests per
+ * directory, which on Tegra234 adds up to seconds. Nothing else
+ * waits for it, so do it in the background rather than hold up every
+ * device that depends on the BPMP. The workqueue is freezable so
+ * that system suspend waits for it instead of failing its requests.
+ */
+ queue_work(system_freezable_wq, &bpmp->debugfs_work);
+
+ return 0;
+}
diff --git a/include/soc/tegra/bpmp.h b/include/soc/tegra/bpmp.h
index f55db918ccb1..f961c265326c 100644
--- a/include/soc/tegra/bpmp.h
+++ b/include/soc/tegra/bpmp.h
@@ -12,6 +12,7 @@
#include <linux/reset-controller.h>
#include <linux/semaphore.h>
#include <linux/types.h>
+#include <linux/workqueue.h>
#include <soc/tegra/bpmp-abi.h>
@@ -103,6 +104,7 @@ struct tegra_bpmp {
#ifdef CONFIG_DEBUG_FS
struct dentry *debugfs_mirror;
+ struct work_struct debugfs_work;
#endif
bool suspended;
base-commit: 1bbcf4a19f1495f769b69e9569d8c1e81df074f5
--
2.47.3
next prev parent reply other threads:[~2026-10-24 5:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-17 6:50 [PATCH] " Austin Schuh
2026-10-23 8:16 ` Mikko Perttunen
2026-10-24 5:50 ` Austin Schuh [this message]
2026-10-24 8:28 ` Austin Schuh
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=20261024055055.602558-1-austin.linux@gmail.com \
--to=austin.linux@gmail.com \
--cc=anrao@nvidia.com \
--cc=jonathanh@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mperttunen@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
all inboxes | Powered by JetHome®