[PATCH 0/4] ASoC: Add Cadence I2S-SC and I2S-MC controller support

Joakim Zhang (张强庆) joakim.zhang at cixtech.com
Sun Sep 27 22:35:47 PDT 2026


Hello,

> -----Original Message-----
> From: joakim.zhang at cixtech.com <joakim.zhang at cixtech.com>
> Sent: Tuesday, September 22, 2026 7:22 PM
> To: lgirdwood at gmail.com; broonie at kernel.org; robh at kernel.org;
> krzk+dt at kernel.org; conor+dt at kernel.org; perex at perex.cz; tiwai at suse.com;
> p.zabel at pengutronix.de
> Cc: cix-kernel-upstream <cix-kernel-upstream at cixtech.com>; linux-
> sound at vger.kernel.org; devicetree at vger.kernel.org; linux-kernel at vger.kernel.org;
> linux-arm-kernel at lists.infradead.org; Joakim Zhang (张强庆)
> <joakim.zhang at cixtech.com>
> Subject: [PATCH 0/4] ASoC: Add Cadence I2S-SC and I2S-MC controller support
> 
> From: Joakim Zhang <joakim.zhang at cixtech.com>
> 
> This series adds DT bindings and ASoC CPU DAI drivers for the two Cadence I2S
> controllers integrated in the CIX SKY1 audio subsystem.
> 
> I2S-SC is a full-duplex stereo controller supporting standard I2S, left/right-justified
> and DSP formats, mono operation mapped onto the left audio channel, and TDM
> operation with up to 16 slots per frame.
> 
> I2S-MC is a multi-channel controller which moves up to 16 channels through a
> configurable set of its 8 data pins, each pin carrying two slots, and exposes a
> transmit DAI and a receive DAI which can act as clock provider or consumer
> independently.
> 
> Both drivers register the dmaengine PCM helper, select the audio reference clock
> parent for the 8 kHz or 11.025 kHz sample rate family, keep the minimum
> functional-clock to bit-clock ratio required for safe clock domain crossing, and
> support runtime and system suspend/resume with regcache restore.
> 
> Joakim Zhang (4):
>   ASoC: dt-bindings: Add Cadence I2S-SC controller
>   ASoC: cdns: Add Cadence I2S-SC controller driver
>   ASoC: dt-bindings: Add Cadence I2S-MC controller
>   ASoC: cdns: Add Cadence I2S-MC controller driver
> 

I have collected and resolved some issues. The remaining unanswered questions will be discussed further in v2. Especially regarding some issues related to the naming of "compatible" and "property".

Thanks,
Joakim


More information about the linux-arm-kernel mailing list