From: Mark Brown <broonie@kernel.org>
To: Raghu Bankapur <quic_rbankapu@quicinc.com>
Cc: Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Krishna Jha <quic_kkishorj@quicinc.com>
Subject: Re: [PATCH V0 1/1] asoc: msm: use hashtable to check kcontrol
Date: Mon, 30 May 2022 16:13:27 +0200 [thread overview]
Message-ID: <YpTRB6rwGGUnUmvK@sirena.org.uk> (raw)
In-Reply-To: <ad55bbd41cc253acb9af6ac068c15dd1545ecd81.1653813866.git.quic_rbankapu@quicinc.com>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-30 15:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 8:50 [PATCH V0 0/1] asoc: msm: use hashtable to check kcontrol Raghu Bankapur
2022-05-29 8:50 ` [PATCH V0 1/1] " Raghu Bankapur
2022-05-29 9:35 ` Takashi Iwai
[not found] ` <f3a25238-fcc6-2381-e329-0bd80a3632a5@quicinc.com>
2022-06-10 6:01 ` Takashi Iwai
2022-06-13 9:19 ` Raghu Ballappa Bankapur
2022-06-13 10:02 ` Takashi Iwai
2022-05-29 10:40 ` kernel test robot
2022-05-30 14:13 ` Mark Brown [this message]
2022-05-31 4:46 ` kernel test robot
2022-05-30 14:08 ` [PATCH V0 0/1] " Mark Brown
[not found] <cover.1654252861.git.quic_rbankapu@quicinc.com>
2022-06-03 10:42 ` [PATCH V0 1/1] " Raghu Bankapur
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=YpTRB6rwGGUnUmvK@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=quic_kkishorj@quicinc.com \
--cc=quic_rbankapu@quicinc.com \
--cc=tiwai@suse.com \
/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