The debugfs summary currently shows the power sequencing device's name.
This is not really helpful since the device name is always "pwrseq.N".

Also print the parent device's name. This would likely be the device
node name from the device tree, something like "nvme-connector". This
would make it much easier for the developer to associate the summary
with a certain device.

Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
---
 drivers/power/sequencing/core.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/power/sequencing/core.c b/drivers/power/sequencing/core.c
index 4dff71be11b6..14335c4f813e 100644
--- a/drivers/power/sequencing/core.c
+++ b/drivers/power/sequencing/core.c
@@ -1043,7 +1043,7 @@ static int pwrseq_debugfs_seq_show(struct seq_file *seq, void *data)
 	struct pwrseq_target *target;
 	struct pwrseq_unit *unit;
 
-	seq_printf(seq, "%s:\n", dev_name(dev));
+	seq_printf(seq, "%s (%s):\n", dev_name(dev), dev_name(dev->parent));
 
 	seq_puts(seq, "  targets:\n");
 	list_for_each_entry(target, &pwrseq->targets, list)
-- 
2.54.0.545.g6539524ca2-goog

On Thu, 07 May 2026 13:29:41 +0800, Chen-Yu Tsai wrote:
> The debugfs summary currently shows the power sequencing device's name.
> This is not really helpful since the device name is always "pwrseq.N".
> 
> Also print the parent device's name. This would likely be the device
> node name from the device tree, something like "nvme-connector". This
> would make it much easier for the developer to associate the summary
> with a certain device.
> 
> [...]

Applied, thanks!

[1/1] power: sequencing: print power sequencing device parent in debugfs
      https://git.kernel.org/brgl/c/513f49c33e91e58975ada7967b44512179f0e703

Best regards,
-- 
Bartosz Golaszewski <bartosz.golaszewski@oss.qualcomm.com>