[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yhk+oFJBMAqYNc6r@sirena.org.uk>
Date: Fri, 25 Feb 2022 20:40:00 +0000
From: Mark Brown <broonie@...nel.org>
To: Richard Fitzgerald <rf@...nsource.cirrus.com>
Cc: Rob Herring <robh@...nel.org>, kuninori.morimoto.gx@...esas.com,
alsa-devel@...a-project.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, patches@...nsource.cirrus.com
Subject: Re: [PATCH V2 1/2] ASoC: dt-bindings: audio-graph-port: Add
dai-tdm-slot-width-map
On Fri, Feb 25, 2022 at 12:08:00PM +0000, Richard Fitzgerald wrote:
> On 24/02/2022 22:10, Rob Herring wrote:
> > Is there a need for specifying where in the slot the data is?
> I don't believe so, all the protocols I know of have the data bits
> transmitted first followed by padding. There's no harm adding a
> reserved field to allow for this info if it is ever needed, but it would
> be unused at present as there's no kernel API to do this.
It's part of the general format for the bus I'd say.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists