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

On Thu, Aug 02, 2012 at 10:50:13PM +0200, Daniel Mack wrote:
> On 25.07.2012 12:52, Mark Brown wrote:
> > On Wed, Jul 25, 2012 at 10:18:24AM +0200, Daniel Mack wrote:

> > 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?

Yes, since many of them are the same clocks - we certainly have massive
overlap here and clocks can go in both directions.

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

Well, for a start it'd need to be deployed on a useful set of platforms.
Right now we've not got any clock API at all on most platforms and only
a vanishingly small set are using the generic API.  I'm hopefully going
to persuade Arnd to unblock the one issue preventing me fixing the first
problem and obviously there's some progress on the second.

As things stand there just isn't a non-specific clock API that anything
that generates clocks can realistically use.

      reply	other threads:[~2012-08-04 10:04 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
2012-08-03 21:55     ` Mark Brown [this message]

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=20120803215545.GA4515@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=zonque@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 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).