From: Brad Boyer <flar@allandria.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: Michael Schmitz <schmitz@biophys.uni-duesseldorf.de>,
flameman mayer <flamemaniii@gmail.com>,
linux-m68k@lists.linux-m68k.org
Subject: Re: mac68k serial
Date: Sat, 17 Jan 2009 00:24:24 -0800 [thread overview]
Message-ID: <20090117082424.GA3651@cynthia.pants.nu> (raw)
In-Reply-To: <Pine.LNX.4.64.0901171736060.19123@loopy.telegraphics.com.au>
On Sat, Jan 17, 2009 at 05:59:51PM +1100, Finn Thain wrote:
> On Sat, 17 Jan 2009, Michael Schmitz wrote:
> > Can't you add an empty SCC dispatch that just returns, or will that
> > cause an interrupt storm?
>
> The VIA would be OK with that. Whether it would work or not would depend
> on the SCC. That is, I don't know.
The SCC IRQ isn't a VIA interrupt as far as I can tell. It looks like
only models with OSS (the IIfx) or PSC (Q660AV + Q840AV) have a way
to block the SCC IRQ. The comments in mac_scc_dispatch specifically
say that the SCC causes interrupt storms if we ignore it.
We really ought to redesign the interrupt handling for macs so it's
obvious how the interrupts wander through all the layers. There is
all that logic in the common m68k interrupt handling to register
different interrupt controllers and the mac code just registers one
giant synthetic interrupt source rather than having each driver
register directly with the core for VIA, OSS, PSC, etc.
> You could also ifdef 0 the relevant code in via.c --
>
> 311 request_irq(IRQ_AUTO_4, mac_scc_dispatch, IRQ_FLG_LOCK,
> 312 "scc", mac_scc_dispatch);
>
> I don't really care enough to send a temporary patch upstream since the
> serial port is presently only useful to those hacking on the kernel
> anyway.
I don't think that will really fix anything, since IRQ_AUTO_* interrupts
aren't really blocked or ignored if you don't register them. They go
directly into the CPU which doesn't have a true IRQ mask.
Brad Boyer
flar@allandria.com
next prev parent reply other threads:[~2009-01-17 8:24 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-13 21:49 mac68k serial flameman mayer
2009-01-14 0:32 ` Brad Boyer
2009-01-14 1:50 ` Finn Thain
2009-01-16 23:31 ` Michael Schmitz
2009-01-17 3:13 ` Falcon IDE breakage Michael Schmitz
2009-01-17 11:58 ` Geert Uytterhoeven
2009-01-18 0:58 ` Michael Schmitz
2009-01-18 1:45 ` Falcon IDE breakage [patch] Michael Schmitz
2009-01-19 12:24 ` Bartlomiej Zolnierkiewicz
2009-01-18 2:10 ` [PATCH 1/3] m68k: section mismatch fixes: EtherNAT Michael Schmitz
2009-01-18 2:17 ` [PATCH 2/3] m68k: section mismatch fixes: DMAsound Michael Schmitz
2009-01-30 18:37 ` Geert Uytterhoeven
2009-01-18 2:22 ` [PATCH 3/3] m68k: section mismatch fixes: Atari SCSI Michael Schmitz
2009-01-30 18:38 ` Geert Uytterhoeven
2009-01-30 18:35 ` [PATCH 1/3] m68k: section mismatch fixes: EtherNAT Geert Uytterhoeven
2009-02-01 0:14 ` Michael Schmitz
2009-02-01 9:50 ` Geert Uytterhoeven
2009-02-01 10:22 ` Geert Uytterhoeven
2009-02-01 13:09 ` David D. Kilzer
2009-02-02 3:36 ` Michael Schmitz
2009-02-02 7:43 ` Geert Uytterhoeven
2009-01-17 6:59 ` mac68k serial Finn Thain
2009-01-17 8:24 ` Brad Boyer [this message]
2009-01-18 0:43 ` Michael Schmitz
2009-01-18 5:18 ` Brad Boyer
2009-01-14 21:26 ` Kolbjørn Barmen
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=20090117082424.GA3651@cynthia.pants.nu \
--to=flar@allandria.com \
--cc=flamemaniii@gmail.com \
--cc=fthain@telegraphics.com.au \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=schmitz@biophys.uni-duesseldorf.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