public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: broonie@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: Thu, 24 Feb 2022 16:10:52 -0600	[thread overview]
Message-ID: <YhgCbKzfPXEVauwW@robh.at.kernel.org> (raw)
In-Reply-To: <20220217134835.282389-2-rf@opensource.cirrus.com>

On Thu, Feb 17, 2022 at 01:48:34PM +0000, Richard Fitzgerald wrote:
> Some audio hardware cannot support a fixed slot width or a slot width
> equal to the sample width in all cases. This is usually due either to
> limitations of the audio serial port or system clocking restrictions.
> 
> This property allows setting a mapping of sample widths and the
> corresponding tdm slot widths.
> 
> Signed-off-by: Richard Fitzgerald <rf@opensource.cirrus.com>
> ---
>  .../devicetree/bindings/sound/audio-graph-port.yaml        | 7 +++++++
>  1 file changed, 7 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> index 476dcb49ece6..420adad49382 100644
> --- a/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> +++ b/Documentation/devicetree/bindings/sound/audio-graph-port.yaml
> @@ -71,4 +71,11 @@ patternProperties:
>          description: CPU to Codec rate channels.
>          $ref: /schemas/types.yaml#/definitions/uint32
>  
> +      dai-tdm-slot-width-map:
> +        description: Mapping of sample widths to slot widths. For hardware that
> +          cannot support a fixed slot width or a slot width equal to sample

A variable slot width sounds like a feature, not a limitation.

> +          width. An array containing one or more pairs of values. Each pair
> +          of values is a sample_width and the corresponding slot_width.

That sounds like a matrix, not an array. N entries of 2 cells each. 

> +        $ref: /schemas/types.yaml#/definitions/uint32-array
> +

I'd think there are some constraints on the values? Slots should be at 
least 8 bits, right? A max of 2x32 bits or is there more 
than stereo within a slot? In any case, it's for sure no where near 2^32 
max.

Is there a need for specifying where in the slot the data is?

Rob

  reply	other threads:[~2022-02-24 22:10 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 [this message]
2022-02-25 12:08     ` Richard Fitzgerald
2022-02-25 20:40       ` Mark Brown
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=YhgCbKzfPXEVauwW@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.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 \
    /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