From: Daniel Ritz <daniel.ritz@alcatel.ch>
To: Russell King <rmk+lkml@arm.linux.org.uk>, daniel.ritz@gmx.ch
Cc: Pavel Roskin <proski@gnu.org>,
linux-pcmcia <linux-pcmcia@lists.infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] yenta: irq-routing for TI bridges
Date: Tue, 24 Feb 2004 16:23:11 +0100 [thread overview]
Message-ID: <200402241623.11569.daniel.ritz@alcatel.ch> (raw)
In-Reply-To: <20040224124011.A30975@flint.arm.linux.org.uk>
[removing akpm from cc as it is pcmcia centric]
On Tuesday 24 February 2004 13:40, Russell King wrote:
> On Tue, Feb 24, 2004 at 12:59:50PM +0100, Daniel Ritz wrote:
> > there's another bug btw. one that is probably never hit and harmless too:
> > rmk's notbook has parellel isa interrupts, INTA is _not_ routed.
>
> Not true. It has parallel ISA interrupts _and_ parallel PCI interrupts.
> It's a TI 1250. Unfortunately, the 1250 data sheet isn't available,
> however there seems to be some consistency in the device codes to
> features offered.
ok, i see the 1250, 1450 are different. the 1410/1520 doc says nothing about it.
did i miss something about the 1410/1520/etc ?
>
> The 1450 and 1251A (both of which seem similar to 1250) has separate pins
> for PCI parallel interrupts which are outside the control of the "IRQMUX"
> register. When these pins are not used for parallel PCI interrupts,
> they function as "GPIO3" and "IRQSER" (for PCI serial interrupts)
> respectively. The function of these pins is controlled by the device
> control register.
>
> Please note that "IRQMUX" is a misleading definition of the register in
> question. The register programs various multifunction pins on the device
> which _may_ be IRQ outputs, LED outputs, ZV switching outputs, audio, or
> even GPIO.
TI calls it Multifunction Routing Register for a reason :)
so i think the safe way would be:
- move routing code to 12xx_override()
- first test interrupts, do nothing if working correct
- try to reflect the settings in device control register, test again
- fall back to pci if nothing works
- handle the 125x/1450 by not touching MFUNC0
- don't do INTB routing, set INTRTIE instead (on 2 slot chips)
(- remove the bad code from 2.4 and do the same)
next prev parent reply other threads:[~2004-02-24 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 23:33 [PATCH] yenta: irq-routing for TI bridges Daniel Ritz
2004-02-24 0:00 ` Russell King
2004-02-24 0:32 ` Daniel Ritz
2004-02-24 1:06 ` Pavel Roskin
2004-02-24 11:59 ` Daniel Ritz
2004-02-24 12:40 ` Russell King
2004-02-24 15:23 ` Daniel Ritz [this message]
2004-02-24 23:26 ` [PATCH] yenta: irq-routing for TI bridges - take 2 Daniel Ritz
2004-02-25 6:55 ` Pavel Roskin
2004-02-25 20:03 ` Daniel Ritz
2004-02-25 21:20 ` Pavel Roskin
2004-02-25 23:01 ` Daniel Ritz
2004-02-24 16:38 ` [PATCH] yenta: irq-routing for TI bridges David Hinds
2004-02-24 0:46 ` Pavel Roskin
2004-02-24 12:44 ` Russell King
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=200402241623.11569.daniel.ritz@alcatel.ch \
--to=daniel.ritz@alcatel.ch \
--cc=daniel.ritz@gmx.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pcmcia@lists.infradead.org \
--cc=proski@gnu.org \
--cc=rmk+lkml@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.