linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: santosh nayak <santoshprasadnayak@gmail.com>
To: linux@arm.linux.org.uk
Cc: FlorianSchandinat@gmx.de, linux-fbdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
	Santosh Nayak <santoshprasadnayak@gmail.com>
Subject: [PATCH] Video : Amba: Use in_interrupt() in clcdfb_sleep().
Date: Sun, 11 Mar 2012 13:26:25 +0000	[thread overview]
Message-ID: <1331471665-22226-1-git-send-email-santoshprasadnayak@gmail.com> (raw)
In-Reply-To: <CAFLxGvygW=DeSQbRq8Wbcdy5E3e4vYcN666_9oWgnuwzT1WKqw@mail.gmail.com>

From: Santosh Nayak <santoshprasadnayak@gmail.com>

Instead of "in_atomic()", we can use in_interrupt() to check whether
its an interrupt context.

Signed-off-by: Santosh Nayak <santoshprasadnayak@gmail.com>
---
 drivers/video/amba-clcd.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/video/amba-clcd.c b/drivers/video/amba-clcd.c
index 0a2cce7..63c25da 100644
--- a/drivers/video/amba-clcd.c
+++ b/drivers/video/amba-clcd.c
@@ -39,7 +39,7 @@ static const char *clcd_name = "CLCD FB";
  */
 static inline void clcdfb_sleep(unsigned int ms)
 {
-	if (in_atomic()) {
+	if (in_interrupt()) {
 		mdelay(ms);
 	} else {
 		msleep(ms);
-- 
1.7.4.4


       reply	other threads:[~2012-03-11 13:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-11 13:26 santosh nayak [this message]
2012-03-11 13:22 ` [PATCH] Video : Amba: Use in_interrupt() in clcdfb_sleep() richard -rw- weinberger
2012-03-11 13:27 ` Russell King - ARM Linux
2012-03-11 14:29   ` santosh prasad nayak
2012-03-11 14:36     ` Russell King - ARM Linux
2012-03-11 14:49       ` santosh prasad nayak
2012-03-11 15:03         ` Russell King - ARM Linux
2012-03-11 15:31           ` santosh prasad nayak
2012-03-11 15:48             ` Russell King - ARM Linux
2012-03-11 16:49               ` santosh prasad nayak
2012-03-11 16:42                 ` Russell King - ARM Linux
2012-03-11 16:58                   ` santosh prasad nayak
2012-03-11 17:05                     ` Russell King - ARM Linux
2012-03-11 18:24               ` Alan Cox

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=1331471665-22226-1-git-send-email-santoshprasadnayak@gmail.com \
    --to=santoshprasadnayak@gmail.com \
    --cc=FlorianSchandinat@gmx.de \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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).