From: Ryan Mallon <ryan@bluewatersys.com>
To: Alexander Sverdlin <subaparts@yandex.ru>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH] ASoC: Improve EP93xx I2S clocks management.
Date: Mon, 07 Mar 2011 11:02:56 +1300 [thread overview]
Message-ID: <4D740490.8060200@bluewatersys.com> (raw)
In-Reply-To: <1299286635.27359.106.camel@r60e>
On 03/05/2011 01:57 PM, Alexander Sverdlin wrote:
> From: Alexander Sverdlin <subaparts@yandex.ru>
>
> Improve EP93xx I2S clocks management.
> Some freqs values are set not exact as they requested for MCLK and
> original code was not able to find divisors for SCLK and LRCLK.
> This code just picks up nearest value from 3 possible variants.
> This patch makes 44100 and 192000 rates working and fixes
> capture function.
>
> Signed-off-by: Alexander Sverdlin <subaparts@yandex.ru>
> ---
> sound/soc/ep93xx/ep93xx-i2s.c | 19 +++++++++----------
> 1 files changed, 9 insertions(+), 10 deletions(-)
>
> diff --git a/sound/soc/ep93xx/ep93xx-i2s.c b/sound/soc/ep93xx/ep93xx-i2s.c
> index 0458dd4..3d4c086 100644
> --- a/sound/soc/ep93xx/ep93xx-i2s.c
> +++ b/sound/soc/ep93xx/ep93xx-i2s.c
> @@ -242,7 +242,7 @@ static int ep93xx_i2s_hw_params(struct snd_pcm_substream *substream,
> {
> struct ep93xx_i2s_info *info = snd_soc_dai_get_drvdata(dai);
> unsigned word_len, div, sdiv, lrdiv;
> - int found = 0, err;
> + int err;
>
> switch (params_format(params)) {
> case SNDRV_PCM_FORMAT_S16_LE:
> @@ -275,15 +275,14 @@ static int ep93xx_i2s_hw_params(struct snd_pcm_substream *substream,
> * the codec uses.
> */
> div = clk_get_rate(info->mclk) / params_rate(params);
> - for (sdiv = 2; sdiv <= 4; sdiv += 2)
> - for (lrdiv = 64; lrdiv <= 128; lrdiv <<= 1)
> - if (sdiv * lrdiv == div) {
> - found = 1;
> - goto out;
> - }
> -out:
> - if (!found)
> - return -EINVAL;
> + sdiv = 4;
> + if (div > (256 + 512) / 2) {
> + lrdiv = 128;
> + } else {
> + lrdiv = 64;
> + if (div < (128 + 256) / 2)
> + sdiv = 2;
> + }
I don't understand where the magic numbers above come from? Does it work
correctly for all rates? I think a comment is needed to explain how this
works.
An alternative would be to keep the existing loop form, but try and find
the closest match rather than an exact match. Something like this
(untested):
unsigned long diff, lowest_diff = ULONG_MAX;
/* Find the closest match for sdiv/lrdiv */
best_sdiv = 2;
best_lrdiv = 64;
for (sdiv = 2; sdiv <= 4; sdiv += 2) {
for (lrdiv = 64; lrdiv <= 128; lrdiv <<= 1) {
diff = abs(div - (sdiv * lrdiv));
if (diff < lowest_diff) {
lowest_diff = diff;
best_sdiv = sdiv;
best_lrdiv = lrdiv;
}
}
}
sdiv = best_sdiv;
lrdiv = best_lrdiv;
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2011-03-06 22:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 0:57 [PATCH] ASoC: Improve EP93xx I2S clocks management Alexander Sverdlin
2011-03-06 22:02 ` Ryan Mallon [this message]
2011-03-07 5:39 ` Alexander Sverdlin
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=4D740490.8060200@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=alsa-devel@alsa-project.org \
--cc=subaparts@yandex.ru \
/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).