alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Mack <zonque@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>, Liam Girdwood <lrg@ti.com>
Subject: Re: Clock generators in ASoC setups
Date: Thu, 02 Aug 2012 22:50:13 +0200	[thread overview]
Message-ID: <501AE805.1060309@gmail.com> (raw)
In-Reply-To: <20120725105258.GH3099@opensource.wolfsonmicro.com>

On 25.07.2012 12:52, Mark Brown wrote:
> On Wed, Jul 25, 2012 at 10:18:24AM +0200, Daniel Mack wrote:
> 
>> some board I'm working on feature chips (connected via I2C) that are in
>> charge of generating clocks for both the CPU DAI and the codecs.
>> Previously, I configured them manually in platform specific code, but I
>> wonder if there's a better, more generic way to get the job done,
>> especially with regards to DT driven boards?
> 
> The problem here is that we don't have a usable clock API to work with.
> 

Hmm, could you elaborate a bit about the background here? So the idea is
to have the clock framework that handles all system clocks also take
care for clocks related to audio?

What would such a framework need to accomplish, and what missing in -
for example - the common clock framework in that regard?

If there's a discussion thread about that topic, a pointer to that would
suffice.


Thanks,
Daniel

  reply	other threads:[~2012-08-02 20:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-25  8:18 Clock generators in ASoC setups Daniel Mack
2012-07-25 10:52 ` Mark Brown
2012-08-02 20:50   ` Daniel Mack [this message]
2012-08-03 21:55     ` 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=501AE805.1060309@gmail.com \
    --to=zonque@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@ti.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).