From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: SAMSUNG: Bug fix spin_lock recursion in clk_enable() and clk_disable()
Date: Tue, 19 Oct 2010 19:57:51 +0100 [thread overview]
Message-ID: <20101019185751.GB10325@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4CBCD3A5.5070701@fluff.org>
On Tue, Oct 19, 2010 at 12:09:25AM +0100, Ben Dooks wrote:
> I'm not sure, but I don't belive that the clk_ api has
> ever been callable from non-sleepable contexts such as
> interrupt handlers.
>
> I would welcome RMK's response (or any other response)
> about this issue?
We have traditionally allowed it from non-sleepable contexts, mainly
because the platforms I've been using it with have had such simple
clock implementations that it's not worth artifically restricting it,
or the implementation only requires a few us delay after enabling a
clock.
next prev parent reply other threads:[~2010-10-19 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-12 0:39 [PATCH] ARM: SAMSUNG: Bug fix spin_lock recursion in clk_enable() and clk_disable() Jaecheol Lee
2010-10-18 23:09 ` Ben Dooks
2010-10-19 1:12 ` Jassi Brar
2010-10-19 2:55 ` mhban
2010-10-19 18:57 ` Russell King - ARM Linux [this message]
2010-10-21 22:39 ` Ben Dooks
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=20101019185751.GB10325@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).