From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
Alex Raimondi <raimondi@miromico.ch>
Subject: Re: [PATCH] Change comment in include linux/clk.h
Date: Sun, 5 Oct 2008 20:40:35 +0100 [thread overview]
Message-ID: <20081005194035.GA23047@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1223234438-28004-1-git-send-email-haavard.skinnemoen@atmel.com>
On Sun, Oct 05, 2008 at 09:20:38PM +0200, Haavard Skinnemoen wrote:
> From: Alex Raimondi <raimondi@miromico.ch>
>
> clk_get and clk_put may not be used from within interrupt
> context. Change comment to this function.
>
> Signed-off-by: Alex Raimondi <raimondi@miromico.ch>
> Signed-off-by: Haavard Skinnemoen <haavard.skinnemoen@atmel.com>
> ---
> I see several ARM implementation using mutexes for locking in these
> functions. So I assume we never want to call them from interrupt
> context, right?
Correct. I'm not sure why anyone would even consider doing so.
Acked-by: Russell King <rmk+kernel@arm.linux.org.uk>
>
> include/linux/clk.h | 4 ++++
> 1 files changed, 4 insertions(+), 0 deletions(-)
>
> diff --git a/include/linux/clk.h b/include/linux/clk.h
> index 5ca8c6f..7787773 100644
> --- a/include/linux/clk.h
> +++ b/include/linux/clk.h
> @@ -35,6 +35,8 @@ struct clk;
> * clk_get may return different clock producers depending on @dev.)
> *
> * Drivers must assume that the clock source is not enabled.
> + *
> + * clk_get should not be called from within interrupt context.
> */
> struct clk *clk_get(struct device *dev, const char *id);
>
> @@ -76,6 +78,8 @@ unsigned long clk_get_rate(struct clk *clk);
> * Note: drivers must ensure that all clk_enable calls made on this
> * clock source are balanced by clk_disable calls prior to calling
> * this function.
> + *
> + * clk_put should not be called from within interrupt context.
> */
> void clk_put(struct clk *clk);
>
> --
> 1.5.6.5
>
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2008-10-05 19:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-05 19:20 Haavard Skinnemoen
2008-10-05 19:40 ` Russell King [this message]
2008-10-05 19:55 ` Haavard Skinnemoen
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=20081005194035.GA23047@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=haavard.skinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=raimondi@miromico.ch \
/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
all inboxes | Powered by JetHome®