Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: alsa-devel@alsa-project.org, tiwai@suse.de, broonie@kernel.org
Subject: Re: [PATCH] ALSA: core: sysfs: show components string
Date: Tue, 24 Mar 2020 00:12:15 -0500	[thread overview]
Message-ID: <a74e4b68-d6f6-c12d-d600-d8cb7321cc00@linux.intel.com> (raw)
In-Reply-To: <20200324043336.GA8342@workstation>




>>> On the other hand, the node of sysfs is quite common in Linux because
>>> it's tightly coupled to kernel objects. Let you see files under
>>> 'Documentation/ABI/'. We can find efforts to maintain sysfs node so
>>> safe and stable. Due to this reason, it's better to take more care when
>>> adding new node.
>>>
>>> Would I request you the reason to add this node and the reason that
>>> current ALSA control interface doesn't satisfy your requirement?
>>
>> simplicity for user support. Anyone can peak at a sysfs file, not everyone
>> is familiar with the alsa control interface.
>>
>> We get lots of bug reports from people who are asking for configuration
>> help, and the simpler the command is the better.
> 
> For my information, would I request you to disclose the part of such reports?
> 
> I need supplemental information about the reason to add the alternative
> path to expose it, especially the reason that no developers work to
> improve existent tool relevant to UCM and are going to wish to add the
> alternative without utilizing ALSA control character device.

I don't understand your question, sorry. UCM already uses the control 
interface, it's not a matter of adding a new interface but making it 
easier to visualize the contents reported by the machine driver.

See for example 
https://github.com/alsa-project/alsa-ucm-conf/blob/4722f5b3859903521ba0f92a64d86af31083ca50/ucm2/sof-hda-dsp/HiFi.conf#L145

when people report that their microphone is not reported by 
PulseAudio/UCM, it's very helpful to know what UCM was supposed to use 
in the first place. We don't have a debugger or step-by-step mechanisms 
to figure out what the configurations are.

There is zero intent to advertise this sysfs node as a basis for 
applications to bypass the control interface, if that was what you 
thought I was promoting.

  reply	other threads:[~2020-03-24  5:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 19:36 [PATCH] ALSA: core: sysfs: show components string Pierre-Louis Bossart
2020-03-23 19:41 ` Mark Brown
2020-03-23 20:21   ` Pierre-Louis Bossart
2020-03-23 20:23   ` Takashi Iwai
2020-03-24  1:53 ` Takashi Sakamoto
2020-03-24  3:34   ` Pierre-Louis Bossart
2020-03-24  4:33     ` Takashi Sakamoto
2020-03-24  5:12       ` Pierre-Louis Bossart [this message]
2020-03-24  9:01         ` Takashi Sakamoto
2020-03-24 13:15           ` Pierre-Louis Bossart
2020-03-24 13:45             ` Jaroslav Kysela
2020-03-24 14:56             ` Takashi Iwai
2020-03-24 14:59               ` Pierre-Louis Bossart
2020-03-24 11:54     ` Mark Brown

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=a74e4b68-d6f6-c12d-d600-d8cb7321cc00@linux.intel.com \
    --to=pierre-louis.bossart@linux.intel.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=tiwai@suse.de \
    /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