From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Banajit Goswami <bgoswami@quicinc.com>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
Cc: neil.armstrong@linaro.org, linux-arm-msm@vger.kernel.org,
krzysztof.kozlowski@linaro.org, linux-sound@vger.kernel.org,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH v4 0/3] ASoC: codecs: lpass: add support for v2.5 rx macro
Date: Sat, 15 Jun 2024 21:16:52 +0100 [thread overview]
Message-ID: <171848261202.320905.12613370824204863532.b4-ty@kernel.org> (raw)
In-Reply-To: <20240612-lpass-codec-v25-v4-0-f63d3676dbc4@linaro.org>
On Thu, 13 Jun 2024 11:49:30 +0100, Srinivas Kandagatla wrote:
> This patchset adds support to reading codec version and also adds
> support for v2.5 codec version in rx macro.
>
> LPASS 2.5 and up versions have changes in some of the rx blocks which
> are required to get headset functional correctly.
>
> Tested this on SM8450, X13s and x1e80100 crd.
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/3] ASoC: codecs: lpass-macro: add helpers to get codec version
commit: 378918d5918116b95300dd7f03913a1d0841f223
[2/3] ASoC: codec: lpass-rx-macro: prepare driver to accomdate new codec versions
commit: dbacef05898d65f586fb9b90ba367e6bf898d68d
[3/3] ASoC: codec: lpass-rx-macro: add support for 2.5 codec version
commit: 432e5074f805d0f976c7430af376a0dd07f1c6d7
All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.
You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.
If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.
Please add any relevant lists and maintainers to the CCs when replying
to this mail.
Thanks,
Mark
prev parent reply other threads:[~2024-06-15 20:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-13 10:49 [PATCH v4 0/3] ASoC: codecs: lpass: add support for v2.5 rx macro Srinivas Kandagatla
2024-06-13 10:49 ` [PATCH v4 1/3] ASoC: codecs: lpass-macro: add helpers to get codec version Srinivas Kandagatla
2024-06-13 10:49 ` [PATCH v4 2/3] ASoC: codec: lpass-rx-macro: prepare driver to accomdate new codec versions Srinivas Kandagatla
2024-06-13 10:49 ` [PATCH v4 3/3] ASoC: codec: lpass-rx-macro: add support for 2.5 codec version Srinivas Kandagatla
2024-06-13 11:00 ` Krzysztof Kozlowski
2024-06-13 11:04 ` Srinivas Kandagatla
2024-06-14 10:39 ` Krzysztof Kozlowski
2024-06-15 20:16 ` Mark Brown [this message]
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=171848261202.320905.12613370824204863532.b4-ty@kernel.org \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bgoswami@quicinc.com \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=perex@perex.cz \
--cc=srinivas.kandagatla@linaro.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