ASoC: SDCA: Allow sample width wild cards in set_usage()
Subsystems (3)
PATCH 1/1 ASoC: SDCA: Allow sample width wild cards in set_usage()
The SDCA spec allows the sample rate and width to be wild cards, but the current implementation of set_usage() only checked for a wild card of the sample rate.
--- sound/soc/sdca/sdca_asoc.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/soc/sdca/sdca_asoc.c +1 -1
@@ -1478,7 +1478,7 @@ static int set_usage(struct device *dev, struct regmap *regmap,unsigned int rate =sdca_range (range,SDCA_USAGE_SAMPLE_RATE , i);unsigned int width =sdca_range (range,SDCA_USAGE_SAMPLE_WIDTH , i); -if ((!rate || rate == target_rate) && width == target_width) { +if ((!rate || rate == target_rate) && (!width || width == target_width)) {unsigned int usage =sdca_range (range,SDCA_USAGE_NUMBER , i);unsigned int reg =SDW_SDCA_CTL (function->desc->adr, entity->id, sel,0 );
Signature · 1 line
2.43.0
Quoted 7 lines · Simon Trimmer
The SDCA spec allows the sample rate and width to be wild cards, but the current implementation of
set_usage()only checked for a wild card of the sample rate.Fixes 4ed357f72a0e ("ASoC: SDCA: Add hw_params() helper function")Signed-off-by Simon Trimmer <[email protected]>---
Thanks,
Charles
Mark Brown
maintainerQuoted 5 lines · Simon Trimmer
The SDCA spec allows the sample rate and width to be wild cards, but the current implementation of
set_usage()only checked for a wild card of the sample rate.
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/1] ASoC: SDCA: Allow sample width wild cards in set_usage()
commit: 87783532d34050e2bff6749a4fe9860e624a0540
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