From: Jassi Brar <jassisinghbrar@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Seungwhan Youn <sw.youn@samsung.com>,
alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>,
Seungwhan Youn <claude.youn@gmail.com>
Subject: Re: [PATCH 4/7] ASoC: Automatically calculate clock ratio for WM8580
Date: Tue, 17 Aug 2010 08:14:43 +0900 [thread overview]
Message-ID: <AANLkTindYfm3vh_OgF-0tt_MS+Uxii2s7Dw=Kk487RTd@mail.gmail.com> (raw)
In-Reply-To: <20100816151958.GE3276@rakim.wolfsonmicro.main>
On Tue, Aug 17, 2010 at 12:19 AM, Mark Brown
<broonie@opensource.wolfsonmicro.com> wrote:
> On Mon, Aug 16, 2010 at 09:51:35PM +0900, Jassi Brar wrote:
>
>> When CPU MASTER was default, people asked for SLAVE. But nobody asked
>> for MASTER since we selected SLAVE by default. Both work equally well, it just
>> saves our efforts.
>
> What were people actually complaining about? I suspect it was the root
> clock for the audio tree that they were concerned about rather than the
> I2S bus clock.
No complaints. I just get the task to do.
I guess most quality conscious products can afford to attach a dedicated
OSC to a good CODEC. A CODEC already specifies the clocks it support
and usually comes with 'preferred' input clocks. So, just having a specified
rating accurate enough OSC can take care of quality. On the other hand
the clock sources on CPU side are not particularly accurate for audio-clock
generation. Or so have I seen so far.
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2010-08-16 23:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-13 19:33 [PATCH 0/7] WM8580 updates Mark Brown
2010-08-13 19:35 ` [PATCH 1/7] ASoC: Add a bit of resource unwinding in the S3C IISv4 driver Mark Brown
2010-08-13 19:35 ` [PATCH 2/7] ASoC: Convert WM8580 hw_params to use snd_soc_update_bits() Mark Brown
2010-08-13 19:35 ` [PATCH 3/7] ASoC: Remove unused rate selection bitmasks from WM8580 Mark Brown
2010-08-13 19:35 ` [PATCH 4/7] ASoC: Automatically calculate clock ratio for WM8580 Mark Brown
2010-08-15 9:00 ` Seungwhan Youn
2010-08-15 11:09 ` Mark Brown
2010-08-16 4:36 ` Jassi Brar
2010-08-16 10:20 ` Mark Brown
2010-08-16 12:51 ` Jassi Brar
2010-08-16 15:19 ` Mark Brown
2010-08-16 23:14 ` Jassi Brar [this message]
2010-08-17 9:46 ` Mark Brown
2010-08-31 6:46 ` Jassi Brar
2010-08-31 10:42 ` Mark Brown
2010-08-16 4:16 ` Seungwhan Youn
2010-08-16 12:21 ` Mark Brown
2010-08-16 12:47 ` Jassi Brar
2010-08-13 19:35 ` [PATCH 5/7] ASoC: Implement BCLK rate selection " Mark Brown
2010-08-13 19:35 ` [PATCH 6/7] ASoC: Fix inverted WM8580 capture mute control Mark Brown
2010-08-15 4:50 ` Seungwhan Youn
2010-08-15 6:20 ` Seungwhan Youn
2010-08-13 19:35 ` [PATCH 7/7] ASoC: Automatically manage WM8580 DAC OSR Mark Brown
2010-08-14 4:09 ` [PATCH 0/7] WM8580 updates Jassi Brar
2010-08-15 9:21 ` Seungwhan Youn
2010-08-15 11:10 ` Mark Brown
2010-08-16 9:44 ` Seungwhan Youn
2010-08-16 14:49 ` Mark Brown
2010-08-19 11:37 ` Seungwhan Youn
2010-08-14 10:45 ` Liam Girdwood
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='AANLkTindYfm3vh_OgF-0tt_MS+Uxii2s7Dw=Kk487RTd@mail.gmail.com' \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=claude.youn@gmail.com \
--cc=lrg@slimlogic.co.uk \
--cc=sw.youn@samsung.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).