From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel@alsa-project.org, Timur Tabi <timur@freescale.com>
Subject: Re: [PATCH][ASoC v2] Update Freescale MPC8610HPCD fabric driver to support multiple codecs
Date: Fri, 13 Jun 2008 16:57:13 +0100 [thread overview]
Message-ID: <20080613155712.GA9955@rakim.wolfsonmicro.main> (raw)
In-Reply-To: <9e4733910806130826l55342b78mae243e7715c61e83@mail.gmail.com>
On Fri, Jun 13, 2008 at 11:26:57AM -0400, Jon Smirl wrote:
[Dynamic clocking.]
> Intel HDA has a much better scheme for handling that via a fixed clock
> and skipping slots. I suspect I'll have to do some work on alsa to
> make this work.
As well adjusting things to support the widest range of sample rates you
also see this used in order to reduce power consumption.
> On 6/13/08, Timur Tabi <timur@freescale.com> wrote:
> > > clock back to the CPU? Timur's device tree is the one with a codec
> > > clock rate. Are there other parameters the system might need to set
> > > into a codec?
> > The direction of the clock. That's why I have "i2s-slave" in the SSI nodes.
Not just one clock, either - some devices support independent control of
the directions of frame and bit clocks, for example. Other things that
can be configured include clock sharing, timeslot configuration for
buses with more than two devices, parameters for the PLLs and dividers
in the internal clocking tree of the codec, clock outputs not associated
with an audio interface and jack detection.
For added fun, consider codecs with multiple I2S interfaces.
> There should be a way for the ssi driver to extract the parameters
> from the device tree and then feed them into the codec in an arch
> independent manner. The codecs need to stay arch independent. I
> haven't tried doing this yet in the code since I haven't needed setup
> parameters.
Could you explain in more detail why you want to do this in the SSI
driver in particular? Trying to have a generic machine driver that
takes configuration from the device tree seems like a worthwhile goal
but I'm not clear what the gain from integrating this into the
controller driver is.
next prev parent reply other threads:[~2008-06-13 15:57 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-13 0:01 [PATCH][ASoC v2] Update Freescale MPC8610HPCD fabric driver to support multiple codecs Timur Tabi
2008-06-13 2:22 ` Jon Smirl
2008-06-13 12:08 ` Timur Tabi
2008-06-13 2:57 ` Jon Smirl
2008-06-13 3:16 ` Jon Smirl
2008-06-13 3:36 ` Jon Smirl
2008-06-13 12:17 ` Timur Tabi
2008-06-13 15:04 ` Mark Brown
2008-06-13 15:10 ` Jon Smirl
2008-06-13 15:13 ` Timur Tabi
2008-06-13 15:26 ` Jon Smirl
2008-06-13 15:57 ` Mark Brown [this message]
2008-06-13 16:59 ` Jon Smirl
2008-06-13 18:40 ` Timur Tabi
2008-06-13 18:59 ` Mark Brown
2008-06-13 19:25 ` Jon Smirl
2008-06-13 20:04 ` Liam Girdwood
2008-06-13 22:42 ` Mark Brown
2008-06-13 12:11 ` Timur Tabi
2008-06-13 13:42 ` Mark Brown
2008-06-13 14:10 ` Jon Smirl
2008-06-13 14:26 ` Timur Tabi
2008-06-13 14:29 ` Jon Smirl
2008-06-13 14:32 ` Timur Tabi
2008-06-13 14:36 ` Jon Smirl
2008-06-13 14:39 ` Timur Tabi
2008-06-13 9:53 ` 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=20080613155712.GA9955@rakim.wolfsonmicro.main \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonsmirl@gmail.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.