mbox series

[v4,0/2] ASoC: codecs: lpass-wsa: fix VI capture setup.

Message ID 20250403160209.21613-1-srinivas.kandagatla@linaro.org (mailing list archive)
Headers show
Series ASoC: codecs: lpass-wsa: fix VI capture setup. | expand

Message

Srinivas Kandagatla April 3, 2025, 4:02 p.m. UTC
From: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>

This two patches fixes below two issues with the VI setup.

1. Only one channel gets enabled on VI feedback patch instead of two
channels
2. recording rate is hardcoded to 8K instead dyamically setting it up.

Both of these issues are fixed in these patches.

Changes since v3:
	- rearranged the code, and removed some empty lines.
Changes since v2:
	- updated commit logs to reflect the issue.

Changes since v1:
	- add missing break statement.

Srinivas Kandagatla (2):
  ASoC: codecs:lpass-wsa-macro: Fix vi feedback rate
  ASoC: codecs:lpass-wsa-macro: Fix logic of enabling vi channels

 sound/soc/codecs/lpass-wsa-macro.c | 117 +++++++++++++++++++++--------
 1 file changed, 84 insertions(+), 33 deletions(-)

Comments

Mark Brown April 8, 2025, 12:49 p.m. UTC | #1
On Thu, 03 Apr 2025 17:02:07 +0100, srinivas.kandagatla@linaro.org wrote:
> This two patches fixes below two issues with the VI setup.
> 
> 1. Only one channel gets enabled on VI feedback patch instead of two
> channels
> 2. recording rate is hardcoded to 8K instead dyamically setting it up.
> 
> Both of these issues are fixed in these patches.
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/2] ASoC: codecs:lpass-wsa-macro: Fix vi feedback rate
      commit: d7bff1415e85b889dc8908be6aedba8807ae5e37
[2/2] ASoC: codecs:lpass-wsa-macro: Fix logic of enabling vi channels
      commit: 7648beb65600220996ebb2da207610b1ff9b735e

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