From: Linus Torvalds <torvalds@linux-foundation.org>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Jay Estabrook <jay.estabrook@hp.com>,
Ivan Kokshaysky <ink@jurassic.park.msu.ru>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH] Use i8253.c lock for PC speaker on MIPS, too.
Date: Fri, 2 Nov 2007 19:46:22 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0711021940010.3342@woody.linux-foundation.org> (raw)
In-Reply-To: <20071102172606.GA29513@linux-mips.org>
On Fri, 2 Nov 2007, Ralf Baechle wrote:
>
> The Jazz machines have to use the PIT timer for dyntick and highresolution
> kernels. This may break because currently just like i386 used to do MIPS
> uses two separate spinlocks in the actual PIT code and the PC speaker
> code. So switch to do it the same that x86 currently does PIT locking.
Hmm. That leaves apparently just alpha/ppc/powerpc as supporting pcspkr,
and *not* doing this. Maybe they should be forced to do the i8253 lock in
arch code too, and expose it through <asm/i8253.h>, instead of having that
butt-ugly #ifdef remain in the sources?
Paul, Jay, Ivan: right now drivers/input/pcspkr.c does this:
#if defined(CONFIG_MIPS) || defined(CONFIG_X86)
/* Use the global PIT lock ! */
#include <asm/i8253.h>
#else
#include <asm/8253pit.h>
static DEFINE_SPINLOCK(i8253_lock);
#endif
and wouldn't it be nice if we just changed it to
#include <asm/i8253.h>
and got rid of one totally unnecessary stupid arch difference?
Linus
next prev parent reply other threads:[~2007-11-03 2:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20071102161650.GA28459@linux-mips.org>
2007-11-02 17:26 ` Ralf Baechle
2007-11-03 2:46 ` Linus Torvalds [this message]
2007-11-03 3:39 ` Paul Mackerras
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=alpine.LFD.0.999.0711021940010.3342@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=ink@jurassic.park.msu.ru \
--cc=jay.estabrook@hp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=tsbogend@alpha.franken.de \
/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®