Support PDM format and DSD format.
Add new dts property to configure dataline. The SAI has multiple
successive FIFO registers, but in some use
case the required dataline/FIFOs are not successive.
Changes in v2:
- refine the commit subject of patch 5/7
Shengjiu Wang (7):
ASoC: fsl_sai: Add PDM daifmt support
ASoC: fsl_sai: Add DSD bit format support
ASoC: fsl_sai: Add support for more sample rates
ASoc: fsl_sai: Add pinctrl operation for PDM and DSD
ASoC: fsl_sai: Make res a member of struct fsl_sai
ASoC: dt-bindings: fsl-sai: Add new property to configure dataline
ASoC: fsl_sai: Configure dataline/FIFO information from dts property
.../devicetree/bindings/sound/fsl-sai.txt | 8 +
sound/soc/fsl/fsl_sai.c | 260 ++++++++++++++++--
sound/soc/fsl/fsl_sai.h | 26 +-
3 files changed, 272 insertions(+), 22 deletions(-)
--
2.17.1
On Fri, 17 Jun 2022 15:44:30 +0800, Shengjiu Wang wrote:
> Support PDM format and DSD format.
> Add new dts property to configure dataline. The SAI has multiple
> successive FIFO registers, but in some use
> case the required dataline/FIFOs are not successive.
>
> Changes in v2:
> - refine the commit subject of patch 5/7
>
> [...]
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next
Thanks!
[1/7] ASoC: fsl_sai: Add PDM daifmt support
commit: c111c2ddb3fdfca06bb5c7a56db7f97d6d9ea640
[2/7] ASoC: fsl_sai: Add DSD bit format support
commit: 4665770407de8af3b24250cec2209eaf58546f8a
[3/7] ASoC: fsl_sai: Add support for more sample rates
commit: 0d11bab8ef3e5540dfba111947dbd8dcfb813150
[4/7] ASoc: fsl_sai: Add pinctrl operation for PDM and DSD
commit: b4ee8a913e617a2d0f19226225bc025c8640bf34
[5/7] ASoC: fsl_sai: Make res a member of struct fsl_sai
commit: cd640ca20095ed3b9306981f0064313a54fd4568
[6/7] ASoC: dt-bindings: fsl-sai: Add new property to configure dataline
commit: 6b878ac2711056dd07c712caf89f58449cf5a592
[7/7] ASoC: fsl_sai: Configure dataline/FIFO information from dts property
commit: e3f4e5b1a3e654d518155b37c7b2084cbce9d1a7
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