mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: Bard Liao <yung-chuan.liao@linux.intel.com>,
	linux-sound@vger.kernel.org, vkoul@kernel.org,
	vinod.koul@linaro.org, linux-kernel@vger.kernel.org,
	peter.ujfalusi@linux.intel.com, bard.liao@intel.com
Subject: Re: [PATCH] soundwire: debugfs: add root-level peripherals table
Date: Fri, 4 Sep 2026 13:11:52 +0100	[thread overview]
Message-ID: <apq1iNvPvf4+RgGW@opensource.cirrus.com> (raw)
In-Reply-To: <6aa4b17e-042e-4319-a3a2-41f7346f3755@linux.dev>

On Fri, Sep 04, 2026 at 09:35:15AM +0200, Pierre-Louis Bossart wrote:
> On 9/2/26 10:18, Bard Liao wrote:
> > The table will let user know what peripherals are listed and get the
> > detected status by the dev_num.
> 
> This sounds useful indeed, but does this need to be in debugfs?
> 
> We already have a sysfs entry for every peripheral listed in ACPI. Each
> peripheral will have a set of properties extracted from DisCo tables,
> could we piggy-back on all this and just expose the dev_num?
> 

The dev_num is already exposed through sysfs, so I think this is
more of a see everything in one place kinda deal. Although I
guess one could just make a script that pulled all the sysfs
stuff together?

Thanks,
Charles

      parent reply	other threads:[~2026-09-04 12:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-02  8:18 Bard Liao
2026-09-04  7:35 ` Pierre-Louis Bossart
2026-09-04 11:36   ` Liao, Bard
2026-09-04 13:47     ` Pierre-Louis Bossart
2026-09-04 12:11   ` Charles Keepax [this message]

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=apq1iNvPvf4+RgGW@opensource.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=bard.liao@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=vinod.koul@linaro.org \
    --cc=vkoul@kernel.org \
    --cc=yung-chuan.liao@linux.intel.com \
    /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®