devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jyri Sarha <jsarha@ti.com>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	alsa-devel@alsa-project.org, devicetree@vger.kernel.org
Cc: moinejf@free.fr, kuninori.morimoto.gx@renesas.com,
	Li.Xiubo@freescale.com, peter.ujfalusi@ti.com,
	liam.r.girdwood@linux.intel.com, broonie@kernel.org,
	bcousson@baylibre.com
Subject: Re: [PATCH 2/2] ASoC: simple-card: Add support for samplerate and samplewidth constraints
Date: Tue, 3 Mar 2015 12:01:20 +0200	[thread overview]
Message-ID: <54F58670.4070500@ti.com> (raw)
In-Reply-To: <54F4BB68.4030501@linux.intel.com>

On 03/02/2015 09:35 PM, Pierre-Louis Bossart wrote:
> Hi Jyri,
>
> On 3/2/15 8:14 AM, Jyri Sarha wrote:
>>
>>   Optional dai-link subnode properties:
>>
>> +- samplewidth-constraints        : List of integers describing supported
>> +                      sample widths in number of bits.
>
> There are quite a few platforms where the number of bits for valid audio
> bits differs from the number of bits per slot, e.g. 24 bits with 25 bit
> slots, or 24 bits in 32 bit slots. How would this be represented? This
> concept is present for the TDM case but not the simple one.
> -Pierre

As these are dai-link level properties the idea is to set constraints to 
sample-width on the digital audio link, usually i2s. That is why the 
constraint is set based on sample-width and not physical width.

The number if significant bits in the sample-word should in a normal 
case be a property of the codec, if such a property is needed. On the 
other hand the limits for the physical layout in the system memory are 
usually set by the platform driver (= DMA HW), so such a property should 
- in a normal case - go to cpu-dai node. Since these cases can usually 
be associated to either end of the link, there should be no need for 
such properties in the machine driver.

I am not sure what you have in mind with the TDM case. In some cases a 
similar constraint property for number of channels could help.

Best regards,
Jyri

>
>> +- rate-constraints            : List of integers describing supported
>> +                      sample samplerates in Hz.
>>   - format                : CPU/CODEC common audio format.
>>                         "i2s", "right_j", "left_j" , "dsp_a"
>

  reply	other threads:[~2015-03-03 10:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-02 14:14 [PATCH 0/2] simple-card: Add samplerate and samplewidth constraints Jyri Sarha
     [not found] ` <cover.1425303942.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-03-02 14:14   ` [PATCH 1/2] ASoC: simple-card: Remove trailing whitespace Jyri Sarha
     [not found]     ` <c7817be105a96bcbf71202c5497982f59a45a8eb.1425303942.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-03-03 15:34       ` Mark Brown
2015-03-02 14:14   ` [PATCH 2/2] ASoC: simple-card: Add support for samplerate and samplewidth constraints Jyri Sarha
     [not found]     ` <9d01aa0d0bf48d8b41d5086a7e6c9ec08c2b9c48.1425303942.git.jsarha-l0cyMroinI0@public.gmane.org>
2015-03-02 19:35       ` [alsa-devel] " Pierre-Louis Bossart
2015-03-03 10:01         ` Jyri Sarha [this message]
2015-03-02 19:58       ` Lars-Peter Clausen
2015-03-03 10:09         ` Jyri Sarha
     [not found]           ` <54F5884A.1090702-l0cyMroinI0@public.gmane.org>
2015-03-03 11:30             ` [alsa-devel] " Mark Brown
     [not found]               ` <20150303113041.GM21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-03-03 12:00                 ` Jyri Sarha
2015-03-03 15:31                   ` Lars-Peter Clausen
2015-03-04  7:48                     ` Jyri Sarha
2015-03-10 15:25                       ` Jyri Sarha
2015-03-03 15:34                   ` Mark Brown
2015-03-04  7:56                     ` Jyri Sarha
2015-03-04 18:42                       ` 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=54F58670.4070500@ti.com \
    --to=jsarha@ti.com \
    --cc=Li.Xiubo@freescale.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bcousson@baylibre.com \
    --cc=broonie@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=moinejf@free.fr \
    --cc=peter.ujfalusi@ti.com \
    --cc=pierre-louis.bossart@linux.intel.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;
as well as URLs for NNTP newsgroup(s).