Re: [PATCH] ASoC: core: Support INPUT and OUTPUT DAPM widgets in DT

Mark Brown <[email protected]> Wed, 5 Aug 2026 18:23:32 +0100

Newsgroups	org.kernel.vger.linux-sound,org.kernel.vger.linux-kernel
Message-ID	<[email protected]>

On Wed, Aug 05, 2026 at 08:16:10PM +0300, Ivaylo Dimitrov wrote:

> I have an out-of-tree audio-graph-card2 based machine description for
> Motorola OMAP4 devices using the CPCAP codec together with an external modem
> codec. Without modelling the remote endpoint as a DAPM INPUT/OUTPUT widget,
> the DAPM graph is incomplete and one side of the codec-to-codec link does
> not become active as expected, so runtime PM does not resume one of the
> devices in the link during a call.

Why is it appropriate that the remote endpoint be a raw widget of this
non-specific type?

> I used INPUT/OUTPUT because they appear to be the generic DAPM endpoint
> widgets for this type of digital connection. If there is a more appropriate
> existing widget type for modelling such a remote DAI endpoint, I'd be happy
> to use that instead.

If it's a DAI to DAI link you need a custom machine driver, we don't
have anything like the infrastructure to put DAI<->DAI links in DT.
These should be using AIF widgets.

signature.asc (application/pgp-signature, 488 B)