From: domen@coderock.org
To: rmk@arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, domen@coderock.org, nacc@us.ibm.com
Subject: [patch 4/4] arm/cpu-sa1110: replace schedule_timeout() with msleep()
Date: Sat, 05 Mar 2005 23:41:24 +0100 [thread overview]
Message-ID: <20050305224124.C5CC41EE1E@trashy.coderock.org> (raw)
Use msleep() instead of schedule_timeout() to guarantee the task
delays as expected. Neither signals nor wait-queue events are important at this
point in the code, I believe.
Signed-off-by: Nishanth Aravamudan <nacc@us.ibm.com>
Signed-off-by: Domen Puncer <domen@coderock.org>
---
kj-domen/arch/arm/mach-sa1100/cpu-sa1110.c | 3 +--
1 files changed, 1 insertion(+), 2 deletions(-)
diff -puN arch/arm/mach-sa1100/cpu-sa1110.c~msleep-arch_arm_mach-sa1100_cpu-sa1110 arch/arm/mach-sa1100/cpu-sa1110.c
--- kj/arch/arm/mach-sa1100/cpu-sa1110.c~msleep-arch_arm_mach-sa1100_cpu-sa1110 2005-03-05 16:10:43.000000000 +0100
+++ kj-domen/arch/arm/mach-sa1100/cpu-sa1110.c 2005-03-05 16:10:43.000000000 +0100
@@ -271,8 +271,7 @@ static int sa1110_target(struct cpufreq_
*/
sdram_set_refresh(2);
if (!irqs_disabled()) {
- set_current_state(TASK_UNINTERRUPTIBLE);
- schedule_timeout(20 * HZ / 1000);
+ msleep(20);
} else {
mdelay(20);
}
_
next reply other threads:[~2005-03-05 22:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-05 22:41 domen [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-20 21:49 [patch 4/4] arm/cpu-sa1110: replace schedule_timeout() with msleep() domen
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=20050305224124.C5CC41EE1E@trashy.coderock.org \
--to=domen@coderock.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nacc@us.ibm.com \
--cc=rmk@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