From: Daniel Mack <daniel@caiaq.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH] ALSA: ASoC: support more sample rates on raumfeld devices
Date: Wed, 13 Jan 2010 16:43:20 +0100 [thread overview]
Message-ID: <20100113154320.GD9007@buzzloop.caiaq.de> (raw)
In-Reply-To: <20100113130208.GD27473@rakim.wolfsonmicro.main>
On Wed, Jan 13, 2010 at 01:02:09PM +0000, Mark Brown wrote:
> On Wed, Jan 13, 2010 at 11:25:38AM +0100, Daniel Mack wrote:
> > Add support for sample rates other than 44100Khz on raumfeld audio
> > devices. Force the codec's supported sample rates as the table of
> > supported rates which is calculated at run-time does not suffice: if we
> > call snd_soc_dai_set_sysclk() at stream startup, half of the possible
> > rates are missing.
>
> I'm not massively enthusiastic about this -
Me neither, and I agree to your objections.
> I'd much rather be able to
> give the CODEC a hook to let it know what MCLK rates it can have and a
> callback to update them. It's a perfect case for the clock API but of
> course we can't use that off-SoC :/
I thought about this too and disliked it as well. It would make the
codec be in charge of dealing with clock changes, which is - in this
case particularily at least - not apropriate as the codec is slave to
all clocks.
For this application, the codec driver would need to be as dumb as
possible: I would just get the information about which MCLK and LRCLK it
runs with and it could reject invalid configurations by return value.
But that would imply major changes to the clocking logic in the cs4270
driver, which is fine as-is when it acts as master.
I'm uncertain and hence I just went the other way which bypasses this
logic for now, also not to break existing platforms.
Daniel
next prev parent reply other threads:[~2010-01-13 15:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 10:25 [PATCH] ALSA: ASoC: support more sample rates on raumfeld devices Daniel Mack
2010-01-13 13:02 ` Mark Brown
2010-01-13 15:35 ` Timur Tabi
2010-01-13 15:43 ` Daniel Mack [this message]
2010-01-13 16:27 ` Mark Brown
2010-01-15 16:36 ` [PATCH 1/2] ALSA: ASoC: cs4270: allow passing freq=0 in set_dai_sysclk() Daniel Mack
2010-01-15 16:36 ` [PATCH 2/2] ALSA: ASoC: support more sample rates on raumfeld devices Daniel Mack
2010-01-15 17:08 ` [PATCH 1/2] ALSA: ASoC: cs4270: allow passing freq=0 in set_dai_sysclk() Timur Tabi
2010-01-15 17:29 ` 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=20100113154320.GD9007@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.