linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 01/14] clk: add helper functions clk_prepare_enable and clk_disable_unprepare
Date: Fri, 11 Nov 2011 10:27:27 +0000	[thread overview]
Message-ID: <20111111102727.GC12913@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20111111091556.GI16886@pengutronix.de>

On Fri, Nov 11, 2011 at 10:15:56AM +0100, Sascha Hauer wrote:
> On Fri, Nov 11, 2011 at 05:05:47PM +0800, Richard Zhao wrote:
> > {
> > 	int ret;
> > 
> > 	ret = clk_prepare(clk);
> > 	if (ret)
> > 		return ret;
> > 	ret = clk_enable(clk);
> > 	if (ret)
> > 		clk_unprepare(clk);
> > 	return ret;
> 
> Yes, looks good.

While this looks like a nice easy solution for converting existing
drivers, I'd suggest thinking about this a little more...

I would suggest some thought is given to the placement of clk_enable()
and clk_disable() when adding clk_prepare(), especially if your existing
clk_enable() function can only be called from non-atomic contexts.

Obviously, the transition path needs to be along these lines:

1. add clk_prepare() to drivers
2. implement clk_prepare() and make clk_enable() callable from non-atomic
   contexts
3. move clk_enable() in drivers to places it can be called from non-atomic
   contexts to achieve greater power savings (maybe via the runtime pm)

and where a driver is shared between different sub-architectures which
have non-atomic clk_enable()s, (3) can only happen when all those sub-
architectures have been updated to step (2).

  reply	other threads:[~2011-11-11 10:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11  1:10 [PATCH V2 00/14] add clk_prepare/clk_unprepare to imx drivers Richard Zhao
2011-11-11  1:10 ` [PATCH V2 01/14] clk: add helper functions clk_prepare_enable and clk_disable_unprepare Richard Zhao
2011-11-11  8:49   ` Sascha Hauer
2011-11-11  9:05     ` Richard Zhao
2011-11-11  9:15       ` Sascha Hauer
2011-11-11 10:27         ` Russell King - ARM Linux [this message]
2011-11-11 11:56           ` Sascha Hauer
2011-11-11 14:20             ` Richard Zhao
2011-11-11  1:10 ` [PATCH V2 02/14] ARM: mxc: time: add clk_prepare/clk_unprepare Richard Zhao
2011-11-11  1:10 ` [PATCH V2 03/14] ARM: mxc: ahci: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 04/14] ARM: mxc: pwm: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 05/14] ARM: mxc: epit: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 06/14] ARM: mxc: arch_reset: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 07/14] ARM: mxc: audmux-v2: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 08/14] ARM: pm-imx5: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 09/14] ARM: mx31moboard: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 10/14] ARM: mxs: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 11/14] serial: imx: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 12/14] net: fec: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 13/14] i2c: imx: " Richard Zhao
2011-11-11  1:10 ` [PATCH V2 14/14] mmc: sdhci-esdhc-imx: " Richard Zhao

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=20111111102727.GC12913@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --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).