[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YpTRB6rwGGUnUmvK@sirena.org.uk>
Date: Mon, 30 May 2022 16:13:27 +0200
From: Mark Brown <broonie@...nel.org>
To: Raghu Bankapur <quic_rbankapu@...cinc.com>
Cc: Jaroslav Kysela <perex@...ex.cz>, Takashi Iwai <tiwai@...e.com>,
Liam Girdwood <lgirdwood@...il.com>,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Krishna Jha <quic_kkishorj@...cinc.com>
Subject: Re: [PATCH V0 1/1] asoc: msm: use hashtable to check kcontrol
On Sun, May 29, 2022 at 02:20:09PM +0530, Raghu Bankapur wrote:
> index 5dcf77af07af..0eb18f8ee6fd 100644
> --- a/sound/soc/Kconfig
> +++ b/sound/soc/Kconfig
> @@ -58,6 +58,15 @@ config SND_SOC_TOPOLOGY_KUNIT_TEST
> config SND_SOC_ACPI
> tristate
>
> +config SND_CTL_HASHTABLE
> + bool "Add SND CTL hashtable"
> + help
> + This enables hash table in sound card for kcontrols. The traditional way is
Since the rest of the change is to the ALSA core this should be
in the core ALSA Kconfig, though I'm also wondering if there's
any reason to make it configurable at all - is there any big
downside to just using the hastable all the time? This sort of
tuning control tends to be a bit unclear for users.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists