From: Timur Tabi <timur@freescale.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH][ASoC v2] Update Freescale MPC8610HPCD fabric driver to support multiple codecs
Date: Fri, 13 Jun 2008 10:13:05 -0500 [thread overview]
Message-ID: <48528E81.2050901@freescale.com> (raw)
In-Reply-To: <9e4733910806130810y24e6a04bh12eed5a26d0a79c4@mail.gmail.com>
Jon Smirl wrote:
> My system works like you describe. We have an external clock
> generator. It needs to be set up in the fabric code.
But can the clock frequency change during runtime? The current ASoC interface
can handle that.
> Isn't the parameter needed for codecs like AC97 where they supply the
> 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.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2008-06-13 15:13 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 [this message]
2008-06-13 15:26 ` Jon Smirl
2008-06-13 15:57 ` Mark Brown
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=48528E81.2050901@freescale.com \
--to=timur@freescale.com \
--cc=alsa-devel@alsa-project.org \
--cc=jonsmirl@gmail.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.