linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/7] clk: Add a generic clock infrastructure
Date: Sun, 16 Oct 2011 19:55:21 +0200	[thread overview]
Message-ID: <20111016175521.GA13565@pengutronix.de> (raw)
In-Reply-To: <20111014103233.GB9485@b20223-02.ap.freescale.net>

On Fri, Oct 14, 2011 at 06:32:33PM +0800, Richard Zhao wrote:
> On Fri, Oct 14, 2011 at 11:05:04AM +0100, Mark Brown wrote:
> > On Fri, Oct 14, 2011 at 04:10:26PM +0800, Richard Zhao wrote:
> > > On Thu, Sep 22, 2011 at 03:26:56PM -0700, Mike Turquette wrote:
> > 
> > snip essentially Mike's entire mail - *please* delete irrelevant quotes
> > from your replies, it makes it very much easier to find the new text in
> > your mail and is much more friendly to people reading mail on mobile
> > devices.
> I snip not enough? sorry for that. I'll be carefull.
> > 
> > > > +static int __clk_enable(struct clk *clk)
> > > > +{
> > 
> > > Could you expose __clk_enable/__clk_disable? I find it hard to implement
> > > clk group. clk group means, when a major clk enable/disable, it want a set
> > > of other clks enable/disable accordingly.
> > 
> > Shouldn't this be something the core is implementing?  I'd strongly
> > expect that the clock drivers are relatively dumb and delegate all the
> > decision making to the core API.  Otherwise it's going to be hard for
> > the core to implement any logic that involves working with more than one
> > clock like rate change notification, or guarantee that driver requests
> > made through the API are satisfied, as the state of the clocks will be
> > changing underneath it.
> From my point of view, the first step of generic clk can be, easy to adopt
> features of clocks in current mainline git.
> Back to the clk group, I have a patch based on Sascha's work. 
> http://git.linaro.org/gitweb?p=people/riczhao/linux-2.6.git;a=shortlog;h=refs/heads/imx-clk

I thought further about this and a clock group is not something we want
to have at all. Clocks are supposed to be arranged in a tree and
grouping clocks together violates this which leads to problems.
This grouping should be done at driver level, so when a driver needs
more than one clock it should request them all, maybe with a clk_get_all
helper function.

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2011-10-16 17:55 UTC|newest]

Thread overview: 72+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-22 22:26 [PATCH v2 0/7] Add a generic struct clk Mike Turquette
2011-09-22 22:26 ` [PATCH v2 1/7] clk: Add a generic clock infrastructure Mike Turquette
2011-09-25  3:55   ` Grant Likely
2011-09-25  5:26     ` Turquette, Mike
2011-10-03 14:17   ` Rob Herring
2011-10-03 14:25     ` Mark Brown
2011-10-03 15:24       ` Rob Herring
2011-10-03 16:31         ` Mark Brown
2011-10-03 16:43           ` Russell King - ARM Linux
2011-10-03 17:05             ` Mark Brown
2011-10-04 18:09     ` Grant Likely
2011-10-27 11:54     ` Domenico Andreoli
2011-10-03 22:02   ` Rob Herring
2011-10-03 22:15     ` Turquette, Mike
2011-10-06  1:17   ` Saravana Kannan
2011-10-06 16:11     ` Turquette, Mike
2011-10-11 11:25   ` Richard Zhao
2011-10-13 14:44   ` Russell King - ARM Linux
2011-10-13 17:16     ` Turquette, Mike
2011-10-14  8:10   ` Richard Zhao
2011-10-14 10:05     ` Mark Brown
2011-10-14 10:32       ` Richard Zhao
2011-10-16 17:55         ` Sascha Hauer [this message]
2011-10-17  8:48           ` Richard Zhao
2011-10-17  9:20             ` Mark Brown
2011-10-17 10:53               ` Richard Zhao
2011-10-17 11:05                 ` Sascha Hauer
2011-10-17 11:30                   ` Russell King - ARM Linux
2011-10-14 18:14   ` Turquette, Mike
2011-10-15  2:24     ` Richard Zhao
2011-10-15  2:34       ` Richard Zhao
2011-10-16 21:17       ` Turquette, Mike
2011-10-17 11:31         ` Richard Zhao
2011-10-21  9:00   ` Richard Zhao
2011-10-23 12:55   ` Shawn Guo
2011-10-23 16:49     ` Turquette, Mike
2011-09-22 22:26 ` [PATCH v2 2/7] clk: Implement clk_set_rate Mike Turquette
2011-10-11 11:49   ` Richard Zhao
2011-10-23 14:24   ` Shawn Guo
2011-10-23 16:50     ` Turquette, Mike
2011-09-22 22:26 ` [PATCH v2 3/7] clk: Add fixed-rate clock Mike Turquette
2011-10-23 14:30   ` Shawn Guo
2011-10-23 16:51     ` Turquette, Mike
2011-09-22 22:26 ` [PATCH v2 4/7] clk: Add simple gated clock Mike Turquette
2011-09-25  4:02   ` Grant Likely
2011-09-25  5:27     ` Turquette, Mike
2011-09-26 18:33   ` Rob Herring
2011-09-26 18:40     ` Jamie Iles
2011-09-26 19:10       ` Rob Herring
2011-09-26 19:37         ` Jamie Iles
2011-09-26 22:37           ` Turquette, Mike
2011-09-26 23:30             ` Rob Herring
2011-10-05  1:41               ` Saravana Kannan
2011-10-12  6:46   ` Richard Zhao
2011-10-12 14:59     ` Turquette, Mike
2011-10-16 18:26       ` Sascha Hauer
2011-10-17  6:42         ` Richard Zhao
2011-10-17 17:46           ` Turquette, Mike
2011-10-13 14:45   ` Russell King - ARM Linux
2011-10-13 17:18     ` Turquette, Mike
2011-09-22 22:27 ` [PATCH v2 5/7] clk: Add Kconfig option to build all generic clk drivers Mike Turquette
2011-09-22 22:27 ` [PATCH v2 6/7] clk: Add initial WM831x clock driver Mike Turquette
2011-09-25  4:08   ` Grant Likely
2011-09-25  5:29     ` Turquette, Mike
2011-09-26  9:38     ` Mark Brown
2011-10-04 18:18       ` Grant Likely
2011-10-04 20:50         ` Mark Brown
2011-10-04 23:22           ` Grant Likely
2011-09-22 22:27 ` [PATCH v2 7/7] x86: Enable generic clk API on x86 Mike Turquette
2011-09-22 23:17 ` [PATCH v2 0/7] Add a generic struct clk Turquette, Mike
2011-09-25  4:10 ` Grant Likely
2011-09-29 18:54 ` 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=20111016175521.GA13565@pengutronix.de \
    --to=s.hauer@pengutronix.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 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).