All of lore.kernel.org
 help / color / mirror / Atom feed
From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: On common struct clk in clock framework.
Date: Thu, 4 Jul 2013 12:58:48 +0200	[thread overview]
Message-ID: <201307041258.49200.heiko@sntech.de> (raw)
In-Reply-To: <2625323.Iy4l3LBv4H@amdc1227>

Hi,

Am Donnerstag, 4. Juli 2013, 12:32:26 schrieb Tomasz Figa:
> On Thursday 04 of July 2013 10:21:27 mind entropy wrote:
> > On Wed, Jul 3, 2013 at 11:37 PM, Tomasz Figa <tomasz.figa@gmail.com>
> 
> wrote:
> > > The examples you pointed are not using Common Clock Framework. See
> > > Documentation/clk.txt and drivers/clk/ for more information about CCF.
> > > 
> > > As for s3c24xx, CCF driver for the whole platform is already merged for
> > > Linux 3.11.
> > > 
> > > Best regards,
> > > Tomasz
> > 
> > Thanks TomasZ. I have gone through the docs and was quite confused. I
> > will have a look at the merge.
> 
> Oops. It seems like s3c24xx clk driver is not merged yet. I don't know why
> I thought it is. Heiko (on CC) has been working on it and I remember seeing
> some patches from him. Sorry for misinformation.

the ccf conversion should be ready, but at the time I submitted them, the pwm 
rework [that got rid of the pwm-internal clocks] was still missing.

At some point in the threads I lost track of its state, did the pwm rework 
make it into 3.11 after all, or is it an early 3.12 change?


Heiko

  reply	other threads:[~2013-07-04 10:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03 13:35 On common struct clk in clock framework mind entropy
2013-07-03 18:07 ` Tomasz Figa
2013-07-04  4:51   ` mind entropy
2013-07-04  5:07     ` Mike Turquette
2013-07-04 10:32     ` Tomasz Figa
2013-07-04 10:58       ` Heiko Stübner [this message]
2013-07-04 11:07         ` Heiko Stübner

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=201307041258.49200.heiko@sntech.de \
    --to=heiko@sntech.de \
    --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 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.