From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>,
Srinivas Kandagatla <srini@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>,
Takashi Iwai <tiwai@suse.com>
Cc: linux-sound@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, kernel@oss.qualcomm.com,
prasad.kumpatla@oss.qualcomm.com
Subject: Re: [PATCH v2] ASoC: codecs: lpass-macro: Add support for channel map mixer control
Date: Tue, 2 Sep 2025 14:58:11 +0200 [thread overview]
Message-ID: <708dc6e4-1566-4c72-9f3a-a34f935ac247@oss.qualcomm.com> (raw)
In-Reply-To: <20250902062300.212021-1-mohammad.rafi.shaik@oss.qualcomm.com>
On 9/2/25 8:23 AM, Mohammad Rafi Shaik wrote:
> Introduce the channel map mixer control support for LPASS macro
> codec Digital Audio Interfaces (DAIs). The channel map mixer controls
> are required by APPS to configure usecase-specific audio routing and
> channel mapping.
>
> Signed-off-by: Mohammad Rafi Shaik <mohammad.rafi.shaik@oss.qualcomm.com>
> ---
[...]
> +int lpass_macro_add_chmap_ctls(struct snd_soc_pcm_runtime *rtd,
> + struct snd_soc_dai *dai, int dir)
> +{
> + struct snd_pcm_chmap *info;
> + int ret;
> +
> + info = kzalloc(sizeof(*info), GFP_KERNEL);
> + if (!info)
> + return -ENOMEM;
> +
> + ret = snd_pcm_add_chmap_ctls(rtd->pcm, dir, NULL,
double space after '='
Konrad
next prev parent reply other threads:[~2025-09-02 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 6:23 [PATCH v2] ASoC: codecs: lpass-macro: Add support for channel map mixer control Mohammad Rafi Shaik
2025-09-02 12:58 ` Konrad Dybcio [this message]
2025-09-29 5:52 ` Mohammad Rafi Shaik
2025-10-01 14:06 ` Alexey Klimov
2025-10-03 7:00 ` Mohammad Rafi Shaik
2025-10-04 13:10 ` Srinivas Kandagatla
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=708dc6e4-1566-4c72-9f3a-a34f935ac247@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=kernel@oss.qualcomm.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mohammad.rafi.shaik@oss.qualcomm.com \
--cc=perex@perex.cz \
--cc=prasad.kumpatla@oss.qualcomm.com \
--cc=srini@kernel.org \
--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