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] ARM: mvebu: Fix of_clk_get() call in a non sleeping context
Date: Tue, 8 Mar 2016 20:55:04 +0000	[thread overview]
Message-ID: <20160308205503.GO19428@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20160308175147.7203734e@free-electrons.com>

On Tue, Mar 08, 2016 at 05:51:47PM +0100, Thomas Petazzoni wrote:
> Hello,
> 
> On Tue, 08 Mar 2016 17:38:11 +0100, Gregory CLEMENT wrote:
> 
> > And from clk_enable comment we have:
> > ""
> > clk_enable must not sleep, which differentiates it from clk_prepare.  In a
> > simple case, clk_enable can be used instead of clk_prepare to ungate a clk
> > if the operation will never sleep.
> > ""
> > 
> > Moreoever for me the "must" was to insist to the order of the call no to
> > the fact that both must be called.
> 
> Right make sense, thanks for correcting me on this. If that's OK from a
> clock maintainer point of view, I'm fine.

The comment Gregory quoted is an _implementation_ comment: it's saying
that you can implement the gating/ungating in either clk_prepare() or
clk_enable().

It isn't giving permission for users of the clk API to omit these calls.

-- 
RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.

  reply	other threads:[~2016-03-08 20:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-08 14:18 [PATCH] ARM: mvebu: Fix of_clk_get() call in a non sleeping context Gregory CLEMENT
2016-03-08 15:41 ` Thomas Petazzoni
2016-03-08 16:19   ` Gregory CLEMENT
2016-03-08 16:31     ` Thomas Petazzoni
2016-03-08 16:38       ` Gregory CLEMENT
2016-03-08 16:51         ` Thomas Petazzoni
2016-03-08 20:55           ` Russell King - ARM Linux [this message]
2016-03-08 20:50         ` Russell King - ARM Linux
2016-03-10 12:44           ` Gregory CLEMENT

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=20160308205503.GO19428@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).