From: Jaroslav Kysela <perex@perex.cz>
To: Mark Brown <broonie@kernel.org>, Takashi Iwai <tiwai@suse.de>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: Re: [alsa-devel] [PATCH 2/2] ASoC: Intel - use control components to describe card config
Date: Tue, 19 Nov 2019 21:47:42 +0100 [thread overview]
Message-ID: <95b3dda0-527c-214e-f108-3bdff8010828@perex.cz> (raw)
In-Reply-To: <20191119204138.GI3634@sirena.org.uk>
Dne 19. 11. 19 v 21:41 Mark Brown napsal(a):
> On Tue, Nov 19, 2019 at 09:37:15PM +0100, Takashi Iwai wrote:
>> Jaroslav Kysela wrote:
>
>>> It's not about the protocol. It's about to move this type of
>>> information to another place. I can remove the ALSA version sentence
>>> from the help, because it's just a hint. I would like to create ucm2
>>> configurations based on this rather than the misused long card names.
>
>> But why these are exclusive? The current longname workaround makes
>> the device appearing a bit messy, but does it conflict with the
>> additional component string?
>
> Yeah, it's not clear to me why it's a config option to enable this. I
> can see a config option to turn off the old display name if it's
> particularly irritating to people but I can't see any reason not to
> just provide the new stuff.
Yes, it is really better way to do this. I'll rewrite my patch. Thanks for the
idea.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Sound Maintainer; ALSA Project; Red Hat, Inc.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-19 20:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-19 17:49 [alsa-devel] [PATCH 1/2] ASoC: add control components management Jaroslav Kysela
2019-11-19 17:49 ` [alsa-devel] [PATCH 2/2] ASoC: Intel - use control components to describe card config Jaroslav Kysela
2019-11-19 19:12 ` Pierre-Louis Bossart
2019-11-19 19:22 ` Jaroslav Kysela
2019-11-19 19:39 ` Pierre-Louis Bossart
2019-11-19 20:27 ` Jaroslav Kysela
2019-11-20 0:24 ` Pierre-Louis Bossart
2019-11-19 20:37 ` Takashi Iwai
2019-11-19 20:41 ` Mark Brown
2019-11-19 20:47 ` Jaroslav Kysela [this message]
2019-11-20 17:18 ` [alsa-devel] Applied "ASoC: add control components management" to the asoc tree 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=95b3dda0-527c-214e-f108-3bdff8010828@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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;
as well as URLs for NNTP newsgroup(s).