[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <ZNkSFvZkQgtudM5Z@finisterre.sirena.org.uk>
Date: Sun, 13 Aug 2023 18:25:42 +0100
From: Mark Brown <broonie@...nel.org>
To: Rob Herring <robh@...nel.org>
Cc: Daniel Baluta <daniel.baluta@....nxp.com>,
alsa-devel@...a-project.org, kuninori.morimoto.gx@...esas.com,
spujar@...dia.com, tiwai@...e.com, perex@...ex.cz,
linux-kernel@...r.kernel.org, linux-imx@....com,
devicetree@...r.kernel.org, daniel.baluta@...il.com
Subject: Re: [PATCH 2/2] ASoC: dt-bindings: simple-card: Document new DAI
flags playback-only/capture-only
On Fri, Aug 11, 2023 at 01:12:36PM -0600, Rob Herring wrote:
> On Tue, Aug 01, 2023 at 11:24:33AM +0300, Daniel Baluta wrote:
> > + playback-only:
> > + description: dai-link is used only for playback
> > + $ref: /schemas/types.yaml#/definitions/flag
> > + capture-only:
> > + description: dai-link is used only for capture
> > + $ref: /schemas/types.yaml#/definitions/flag
> Wouldn't this be implicit based on limitations in the either the cpu or
> codec DAI?
You can see cases where people just don't connect some of the signals
for whatever reason so even if the two devices could do bidrectional
audio the board can't, and there are also cases like the at91sam9g20ek
where the DAI is connected for bidrectional audio but there's not
actually any audio inputs you can connect (even loopbacks) for one of
the directions so it's best to just mask things out from the user.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists