[PATCH v2 00/10] ASoC: rockchip: spdif: Cleanups and port features from Rockchip's BSP kernel

[Mark Brown]

On Tue, 03 Feb 2026 17:46:22 +0100, Sebastian Reichel wrote:
> I'm currently working on DisplayPort audio support for the Rockchip
> RK3588/RK3576 SoCs, which preferrably use S/PDIF as DAI source.
> 
> Apparently the upstream Rockchip S/PDIF driver is lacking a couple of
> features right now, which are necessary to get things going (i.e.
> setting the sysclk from the machine driver). I found the missing bits
> in Rockchip's 6.1 BSP kernel and ported them over. This series effectly
> brings the mainline kernel on-par with the BSP driver, but also contains
> a couple of cleanup patches of my own to bring the driver to the modern
> age.
> 
> [...]

Applied to

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

Thanks!

[01/10] ASoC: rockchip: spdif: Use device_get_match_data()
        commit: 27b5096ef0f3a78441128b993f0353a77f2f5f53
[02/10] ASoC: rockchip: spdif: Move DT compatible table
        commit: 45df1f66b99340e1d6e90501f1e938400a3e9768
[03/10] ASoC: rockchip: spdif: Fully convert to device managed resources
        commit: 7e2de68e4dbaee65864b0c5972e1b03037243632
[04/10] ASoC: rockchip: spdif: Use dev_err_probe
        commit: 730b0af2748a74528e0ad25f2bcd3272e96db10a
[05/10] ASoC: rockchip: spdif: Improve sample rate support
        commit: 72bcc223032cb71e640e466eb644537e369959a5
[06/10] ASoC: rockchip: spdif: Swap PCM and DAI component registration order
        commit: 7bdde9a2fd6577e18cd99e4f0e71e466ba626e77
[07/10] ASoC: rockchip: spdif: Add support for set mclk rate
        commit: 298082783a0d6d07109f8ce09ab410a1de12876d
[08/10] ASoC: rockchip: spdif: Add support for format S32_LE
        commit: c43ec509019842c0b836e858dc486c216b51b087
[09/10] ASoC: rockchip: spdif: Fill IEC958 CS info per params
        commit: 07a791020be9b190d4a57b5ee823ede1e98df493
[10/10] ASoC: rockchip: spdif: Convert to FIELD_PREP
        commit: d94ea902462ac39846d878aa67b78408727e0674

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