mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
Cc: "Liao, Bard" <bard.liao@intel.com>,
	Bard Liao <yung-chuan.liao@linux.intel.com>,
	"linux-sound@vger.kernel.org" <linux-sound@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peter.ujfalusi@linux.intel.com" <peter.ujfalusi@linux.intel.com>
Subject: Re: [PATCH] soundwire: debugfs: add root-level peripherals table
Date: Tue, 8 Sep 2026 19:18:55 +0530	[thread overview]
Message-ID: <aqASR5r7Bf8tdAwJ@parshuram> (raw)
In-Reply-To: <9f06bdbc-b25d-4a8f-aeb6-ba11e43e9cdb@linux.dev>

On 04-09-26, 15:47, Pierre-Louis Bossart wrote:
> On 9/4/26 13:36, Liao, Bard wrote:
> > 
> > 
> >> -----Original Message-----
> >> From: Pierre-Louis Bossart <pierre-louis.bossart@linux.dev>
> >> Sent: Friday, September 4, 2026 3:35 PM
> >> To: Bard Liao <yung-chuan.liao@linux.intel.com>; linux-
> >> sound@vger.kernel.org; vkoul@kernel.org
> >> Cc: vinod.koul@linaro.org; linux-kernel@vger.kernel.org;
> >> peter.ujfalusi@linux.intel.com; Liao, Bard <bard.liao@intel.com>
> >> Subject: Re: [PATCH] soundwire: debugfs: add root-level peripherals table
> >>
> >> 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?
> > 
> > It is convenient for the user to get all information on top of the
> > soundwire folder instead of looking for the information one by one
> > in each peripheral folder.
> Right, but as Charles suggested one could use a script to provide the
> information in a more self-explanatory format.
> That script could even be added to 'alsa-info' and make existing reports
> better without needing kernel changes.

Yep, and debugfs maynot be on all platform, sysfs is...


-- 
~Vinod

  parent reply	other threads:[~2026-09-08 13:49 UTC|newest]

Thread overview: 7+ 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-07  1:15       ` Liao, Bard
2026-09-08 13:48       ` Vinod Koul [this message]
2026-09-04 12:11   ` Charles Keepax

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=aqASR5r7Bf8tdAwJ@parshuram \
    --to=vkoul@kernel.org \
    --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=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®