All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: Vinod Koul <vinod.koul@linux.intel.com>,
	M R Swami Reddy <MR.Swami.Reddy@ti.com>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: FW: [PATCH v3] ASoC: Add support for TI LM49453 Audio codec
Date: Wed, 8 Feb 2012 11:12:53 +0000	[thread overview]
Message-ID: <20120208111252.GA3120@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1328694877.3955.9.camel@odin>


[-- Attachment #1.1: Type: text/plain, Size: 863 bytes --]

On Wed, Feb 08, 2012 at 09:54:37AM +0000, Liam Girdwood wrote:

> However, I think one of the intentions of the clk framework rework is to
> allow non CPU clocks like CODEC PLLs to register as clocks and have
> their dependencies worked out. I've no idea of the status of this atm,
> but maybe Mark knows or you could ask on lkml.

It's going nowhere slowly.  Seems unlikely for 3.4 at this point,
there's been no activity for a month or two except for rmk getting
annoyed at the lack of activity.  The current block is that very few
people are converting the new clk_prepare() APIs, though there's other
problems we seem unable to get any traction on beyond that.

I rather suspect that the general lack of any end in sight is not
helpful for motivation of random maintainers and none of the folks
working on the core API are doing any of that legwork for them.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      parent reply	other threads:[~2012-02-08 11:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <290463D19D2E064191F1F96ECA480A89434AC4A96E@EXMAIL02.scwf.nsc.com>
2012-02-08  9:10 ` FW: [PATCH v3] ASoC: Add support for TI LM49453 Audio codec M R Swami Reddy
2012-02-08  9:18   ` Liam Girdwood
2012-02-08  9:37     ` Vinod Koul
2012-02-08  9:54       ` Liam Girdwood
2012-02-08 10:36         ` Vinod Koul
2012-02-08 10:57           ` Liam Girdwood
2012-02-08 11:17             ` Vinod Koul
2012-02-08 11:21               ` Mark Brown
2012-02-08 14:31                 ` Vinod Koul
2012-02-08 11:20             ` Mark Brown
2012-02-08 13:27               ` Liam Girdwood
2012-02-08 13:54                 ` Mark Brown
2012-02-08 14:33                 ` Vinod Koul
2012-02-08 11:12         ` 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=20120208111252.GA3120@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=MR.Swami.Reddy@ti.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=vinod.koul@linux.intel.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.