From: Jaroslav Kysela <perex@perex.cz>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
ALSA development <alsa-devel@alsa-project.org>
Cc: Takashi Iwai <tiwai@suse.de>, Mark Brown <broonie@kernel.org>
Subject: Re: [alsa-devel] [PATCH 2/2] ASoC: Intel - use control components to describe card config
Date: Tue, 19 Nov 2019 20:22:56 +0100 [thread overview]
Message-ID: <f2de9597-c9c2-7696-622b-a2bbc2c32bb7@perex.cz> (raw)
In-Reply-To: <72dfc285-70e8-706d-3018-535bda1e8630@linux.intel.com>
Dne 19. 11. 19 v 20:12 Pierre-Louis Bossart napsal(a):
>
>
> On 11/19/19 11:49 AM, Jaroslav Kysela wrote:
>> Use the control interface (field 'components' in the info structure)
>> to pass the I/O configuration details. The long card name might
>> be used in GUI. This information should be hidden.
>>
>> Signed-off-by: Jaroslav Kysela <perex@perex.cz>
>> Cc: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
>> Cc: Mark Brown <broonie@kernel.org>
>> ---
>> sound/soc/intel/Kconfig | 9 +++++++++
>> sound/soc/intel/boards/bytcht_es8316.c | 16 ++++++++++++----
>> sound/soc/intel/boards/bytcr_rt5640.c | 14 +++++++++++---
>> sound/soc/intel/boards/bytcr_rt5651.c | 26 ++++++++++++++++----------
>> 4 files changed, 48 insertions(+), 17 deletions(-)
>>
>> diff --git a/sound/soc/intel/Kconfig b/sound/soc/intel/Kconfig
>> index c8de0bb5bed9..3421957adedb 100644
>> --- a/sound/soc/intel/Kconfig
>> +++ b/sound/soc/intel/Kconfig
>> @@ -47,6 +47,15 @@ config SND_SOC_INTEL_SST_FIRMWARE
>> # Haswell/Broadwell/Baytrail legacy and will be set
>> # when these platforms are enabled
>>
>> +config SND_SOC_INTEL_USE_CTL_COMPONENTS
>> + bool "Use CTL components for I/O configuration"
>> + help
>> + Some drivers might pass the I/O configuration through the
>> + soundcard's driver name in the control user space API.
>> + The new scheme is to put this information to the components
>> + field in the ALSA's card info structure. Say Y, if you
>> + have ALSA user space version 1.2.2+.
>> +
>
> If this is at the board level, then maybe move this to
> sound/soc/intel/boards/Kconfig
>
> I am not sure about the alsa-lib dependency, it's a bit odd, isn't it?
> shouldn't this be handled via protocol versions? or a configuration
> provided by alsa-lib somehow?
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.
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 19:23 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 [this message]
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
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=f2de9597-c9c2-7696-622b-a2bbc2c32bb7@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).