From: Jyri Sarha <jsarha@ti.com>
To: Lars-Peter Clausen <lars@metafoo.de>,
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:09:14 +0200 [thread overview]
Message-ID: <54F5884A.1090702@ti.com> (raw)
In-Reply-To: <54F4C0F2.8000201@metafoo.de>
On 03/02/2015 09:58 PM, Lars-Peter Clausen wrote:
> On 03/02/2015 03:14 PM, Jyri Sarha wrote:
>> Add DT properties to dailink for setting samplerate and samplewidth
>> constraints. The DT binding document has been updated.
>
> Can you include a description why this is needed and how and when it is
> supposed to be used?
Would this addition do:
------------------------------------------------------------
These constraints help to disable the sample-format and sample-rate
combinations that do not properly work on a specific HW.
------------------------------------------------------------
The reason why we need these is coming from limitations in McASP clock
generation. With a simple divider one can only produce certain
bit-clocks. With those bit-clocks we can only play/capture some
sample-rate and sample-width combinations accurately.
The McASP driver could try to set the constraints automatically.
However, since the constraint code can not select sample-width and
sample-rate combinations there is a compromise to be made between them.
Making such compromises automatically does not usually work that well.
In our case these properties could of course be added to McASP driver,
but then again I would expect that there is a wider need for this kind
of functionality. And it may not always be clear if either end of the
link alone is responsible for less than perfect operation.
Best regards,
Jyri
next prev parent reply other threads:[~2015-03-03 10:09 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
2015-03-02 19:58 ` [alsa-devel] " Lars-Peter Clausen
2015-03-03 10:09 ` Jyri Sarha [this message]
[not found] ` <54F5884A.1090702-l0cyMroinI0@public.gmane.org>
2015-03-03 11:30 ` 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=54F5884A.1090702@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=lars@metafoo.de \
--cc=liam.r.girdwood@linux.intel.com \
--cc=moinejf@free.fr \
--cc=peter.ujfalusi@ti.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).