From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org
Subject: Re: [PATCH] ALSA: core: sysfs: show components string
Date: Tue, 24 Mar 2020 11:54:42 +0000 [thread overview]
Message-ID: <20200324115442.GA7039@sirena.org.uk> (raw)
In-Reply-To: <d31659cc-d528-345f-1e56-b0cfae36be5c@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 590 bytes --]
On Mon, Mar 23, 2020 at 10:34:23PM -0500, Pierre-Louis Bossart wrote:
> In case you missed it, the components are used by machine drivers to report
> e.g. number of speakers, mics, etc, so that UCM can find the right
> configuration. For a given family of products, the syntax will be fixed,
> e.g. hs stands for headset codec, etc.
If that's what you're looking for it sounds like a richer sysfs ABI
which has these things in it more directly would be a more idiomatic fit
(or like Sakamoto-san says adding controls, though that is a barrier to
things like udev and so on like you say).
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2020-03-24 11:55 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
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 [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=20200324115442.GA7039@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=pierre-louis.bossart@linux.intel.com \
--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