From: Arnd Bergmann <arnd@arndb.de>
To: Rasmus Villemoes <linux@rasmusvillemoes.dk>
Cc: Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org, linux-kernel@vger.kernel.org,
Richard Henderson <rth@twiddle.net>,
Geert Uytterhoeven <geert@linux-m68k.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>
Subject: Re: no-op delay loops
Date: Mon, 30 Nov 2015 22:44:56 +0100 [thread overview]
Message-ID: <4521348.97HWjoEYIi@wuerfel> (raw)
In-Reply-To: <874mg3b2h5.fsf@rasmusvillemoes.dk>
On Monday 30 November 2015 22:29:26 Rasmus Villemoes wrote:
>
> OK, thanks. That's a very very long time ago.
>
> FWIW, the remaining instances that my trivial coccinelle script found
> are
>
> ./arch/alpha/boot/main.c:187:1-4: no-op delay loop
> ./arch/m68k/68000/m68VZ328.c:86:10-13: no-op delay loop
> ./arch/m68k/bvme6000/config.c:338:2-5: no-op delay loop
> ./arch/m68k/coldfire/m53xx.c:533:1-4: no-op delay loop
> ./drivers/cpufreq/cris-artpec3-cpufreq.c:85:3-6: no-op delay loop
> ./drivers/cpufreq/cris-etraxfs-cpufreq.c:85:3-6: no-op delay loop
> ./drivers/tty/hvc/hvc_opal.c:313:3-6: no-op delay loop
> ./drivers/tty/hvc/hvc_vio.c:289:3-6: no-op delay loop
>
> (cc += a few people). The tty ones use volatile, so they probably work,
> though one might still want to use the *delay API.
>
>
I suspect the tty users do it like this to get console output
before calibrate_delay_loop() is called.
Ard
next prev parent reply other threads:[~2015-11-30 21:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-27 8:53 no-op delay loops Rasmus Villemoes
2015-11-27 9:04 ` yalin wang
2015-11-27 9:25 ` Andy Shevchenko
2015-11-27 11:17 ` Arnd Bergmann
2015-11-30 21:29 ` Rasmus Villemoes
2015-11-30 21:44 ` Arnd Bergmann [this message]
2015-12-01 1:25 ` Ralf Baechle
2015-12-01 15:31 ` Richard Henderson
2015-11-27 11:20 ` Ralf Baechle
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=4521348.97HWjoEYIi@wuerfel \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=linux@rasmusvillemoes.dk \
--cc=ralf@linux-mips.org \
--cc=rjw@rjwysocki.net \
--cc=rth@twiddle.net \
/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