[PATCH v5 0/2] Introduces MDSYNC support for CS35L45

Ricardo Rivera-Matos posted 2 patches 4 weeks, 1 day ago
.../devicetree/bindings/sound/cirrus,cs35l45.yaml  | 20 +++++
sound/soc/codecs/cs35l45-tables.c                  |  4 +
sound/soc/codecs/cs35l45.c                         | 89 +++++++++++++++++++++-
sound/soc/codecs/cs35l45.h                         | 23 ++++++
4 files changed, 132 insertions(+), 4 deletions(-)
[PATCH v5 0/2] Introduces MDSYNC support for CS35L45
Posted by Ricardo Rivera-Matos 4 weeks, 1 day ago
The CS35L45 has SYNC pin that can be used as a multi
device synchronization (MDSYNC) bus. This pin can send
various message types between Cirrus devices.

This patch series adds support for long and short DSP
messages between CS35L45 devices.

Each device on the SYNC bus must have a unique transmitter
identifier per message type as the bus arbitrates message
priority via this identifier. These identifiers are set by
the introduced devicetree properties. The priority
assignment is intended to be a static system integration
decision.

The relevant receiver controls are introduced as mixer
controls so they are exposed at runtime to be configured
for the appropriate use cases.

Signed-off-by: Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
---
Changes in v5:
- Flattened sync node in favor sync properties directly under cs35l45
  node
- Using device_property_read_u32() now that sync node has been flattened
- Apply sync config immediately when GPIO1 is configured as SYNC pin
- Normalize SYNC Enable mixer value when comparing and storing
- Link to v4: https://lore.kernel.org/r/20260821-sound-for-next-cs35l45-sync-v4-v4-0-20d3a07c3b8d@opensource.cirrus.com

Changes in v4:
 - return 0 when controls are unchanged
 - adds locking to cs35l45_sync_en_put
 - Enable -> Switch

Changes in v3:
 - snd_soc_kcontrol_component -> snd_kcontrol_chip
 - only register sync controls if GPIO mux selects SYNC
 - return 1 on cs35l45_sync_en_put success
 - drop | in dt property description

Changes in v2:
 - Fixed property parsing namespace issue

---
Ricardo Rivera-Matos (2):
      ASoC: dt-bindings: cs35l45: Adds SYNC properties
      ASoC: cs35l45: Adds support for SYNC bus

 .../devicetree/bindings/sound/cirrus,cs35l45.yaml  | 20 +++++
 sound/soc/codecs/cs35l45-tables.c                  |  4 +
 sound/soc/codecs/cs35l45.c                         | 89 +++++++++++++++++++++-
 sound/soc/codecs/cs35l45.h                         | 23 ++++++
 4 files changed, 132 insertions(+), 4 deletions(-)
---
base-commit: ab07442c27d0f9fa3aee4185fcb3dbf521fac746
change-id: 20260821-sound-for-next-cs35l45-sync-v4-c2664a7bd536

Best regards,
-- 
Ricardo Rivera-Matos <rriveram@opensource.cirrus.com>
Re: [PATCH v5 0/2] Introduces MDSYNC support for CS35L45
Posted by Mark Brown 3 weeks ago
On Fri, 28 Aug 2026 10:46:25 -0500, Ricardo Rivera-Matos wrote:
> Introduces MDSYNC support for CS35L45
> 
> The CS35L45 has SYNC pin that can be used as a multi
> device synchronization (MDSYNC) bus. This pin can send
> various message types between Cirrus devices.
> 
> This patch series adds support for long and short DSP
> messages between CS35L45 devices.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: dt-bindings: cs35l45: Adds SYNC properties
      https://git.kernel.org/broonie/sound/c/8351ccada421
[2/2] ASoC: cs35l45: Adds support for SYNC bus
      https://git.kernel.org/broonie/sound/c/f3c8f89a1502

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