public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Sudeep Holla <sudeep.holla@kernel.org>,
	Jassi Brar <jassisinghbrar@gmail.com>
Subject: Re: [PATCH v3] mailbox: add list of used channels to debugfs
Date: Tue, 14 Apr 2026 17:28:46 +0200	[thread overview]
Message-ID: <ad5dLuPq15ic_69f@shikoro> (raw)
In-Reply-To: <CAMuHMdXr2cM0KZhvOqueMZ+wQ6FqEeoPGvdOLG4g+AzWirpcGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1043 bytes --]

Hi Geert,

> > Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> 
> Thanks for your patch, which looks useful!

Glad you like it!

> Can you please put it in a subdir, like all other summaries:

Sadly not, because of the paragraph from above:

> > Note that mailbox controllers currently can be instantiated at any
> > initcall stage. So, per-controller debugfs handling was discarded
> > because it is not clear when to create the root "mailbox"-debugfs entry.
> > A central file was chosen, similar to the GPIO subsystem, which is
> > independent of the initcall stage because it will be accessed only when
> > userspace is available anyhow.

I would need to use core_initcall for the mailbox-subsys. debugfs itself
also uses core_initcall. Then, some drivers (e.g. hi3660-mailbox) use
core_initcall. I don't think the subdir is worth all the potential race
conditions and fragile solutions which usually come with it. Or do you
know a solid solution to this problem?

Happy hacking,

   Wolfram


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2026-04-14 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-13 12:00 [PATCH v3] mailbox: add list of used channels to debugfs Wolfram Sang
2026-04-14 13:12 ` Geert Uytterhoeven
2026-04-14 15:28   ` Wolfram Sang [this message]
2026-04-14 16:03     ` Geert Uytterhoeven

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=ad5dLuPq15ic_69f@shikoro \
    --to=wsa+renesas@sang-engineering.com \
    --cc=geert@linux-m68k.org \
    --cc=jassisinghbrar@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=sudeep.holla@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