linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: Common clock API for i.MX
Date: Wed, 25 Jan 2012 14:53:33 +0000	[thread overview]
Message-ID: <20120125145333.GO3687@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAKGA1bm_rLyMB-Xr-XZQHQRVDySu9JuCoVZL=FFv9sa1y6eD1A@mail.gmail.com>

On Wed, Jan 25, 2012 at 07:45:15AM -0600, Matt Sealey wrote:
> On Wed, Jan 25, 2012 at 2:45 AM, Russell King - ARM Linux

> > My conclusion, therefore, is that there's very little actual interest
> > amongst the ARM community to move towards a common clk API.

> Maybe it's a chicken-egg thing; nobody wants to work on it until someone else
> has done some legwork? :)

I do think that this is a big part of the issue, the patches have been
floating around for ages and it's not clear when they'll manage to make
it in (and hence when it'll be worth moving to use them).

> > As a result of the lack of motivation by others over this, I've lost
> > interest in it. ?Sorry.

> Can I drum up some interest here? Guys, what's going on? Who was
> ultimately responsible for the code/concept?

Mike Turquette has been driving this for the past while.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120125/01b3dd62/attachment.sig>

  parent reply	other threads:[~2012-01-25 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25  1:54 Common clock API for i.MX Matt Sealey
2012-01-25  8:45 ` Russell King - ARM Linux
2012-01-25 13:45   ` Matt Sealey
2012-01-25 14:44     ` Russell King - ARM Linux
2012-01-25 20:33       ` Sylwester Nawrocki
2012-01-25 14:53     ` Mark Brown [this message]
2012-01-25 15:42       ` Nicolas Pitre
2012-01-25 15:52         ` Mark Brown
2012-01-26  6:20   ` Shawn Guo
2012-01-26 19:02     ` Sascha Hauer
2012-02-07  0:20   ` Saravana Kannan
2012-01-26  6:10 ` Shawn Guo

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=20120125145333.GO3687@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).