From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: Rob Herring <robh@kernel.org>,
kuninori.morimoto.gx@renesas.com, alsa-devel@alsa-project.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH V2 1/2] ASoC: dt-bindings: audio-graph-port: Add dai-tdm-slot-width-map
Date: Fri, 25 Feb 2022 20:40:00 +0000 [thread overview]
Message-ID: <Yhk+oFJBMAqYNc6r@sirena.org.uk> (raw)
In-Reply-To: <7d11f36e-4b56-8c17-a114-d024f76f3b9e@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 502 bytes --]
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.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-02-25 20:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 13:48 [PATCH V2 0/2] ASoC: audio_graph_card2: Support variable slot widths Richard Fitzgerald
2022-02-17 13:48 ` [PATCH V2 1/2] ASoC: dt-bindings: audio-graph-port: Add dai-tdm-slot-width-map Richard Fitzgerald
2022-02-24 22:10 ` Rob Herring
2022-02-25 12:08 ` Richard Fitzgerald
2022-02-25 20:40 ` Mark Brown [this message]
2022-02-17 13:48 ` [PATCH V2 2/2] ASoC: audio_graph_card2: Add support for variable slot widths Richard Fitzgerald
2022-03-07 20:38 ` [PATCH V2 0/2] ASoC: audio_graph_card2: Support " Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Yhk+oFJBMAqYNc6r@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.cirrus.com \
--cc=rf@opensource.cirrus.com \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox