linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>, linuxppc-embedded@lists.linuxppc.org
Subject: [PATCH and RFC] Remove request_8xxirq
Date: Thu, 20 Jun 2002 13:34:55 -0700	[thread overview]
Message-ID: <20020620203455.GG16052@opus.bloom.county> (raw)

[-- Attachment #1: Type: text/plain, Size: 1675 bytes --]

The following two patches remove request_8xxirq and redesign how we
handle interrupts.  There's patches both against 2.5 (For inclusion
first, mainly for comment tho) and for 2.4 (which has been tested but is
intended for inclusion much later, probably 2.4.21 time-frame).

The new interrupt handling scheme allows all 8xx interrupt handlers to be
installed via the standard request_irq() function.  This required a
"flattened" representation of the interrupt vectors from all interrupt
controllers so that we can uniquely identify any interrupt source with a
single integer.  The interrupt vector numbers used by request_irq() are:

        request_irq vector      interrupt source
        ------------------      ----------------
        0 - 15                  SIU interrupt vectors 0 to 15
        16 - 47                 CPM interrupt vectors 0 to 31
        48 - 63                 8259 interrupt vectors 0 to 15 (MBX only)


In the 2.4 version of this patch, cpm_install_handler and request_8xxirq
still work as expected.   The 2.5 version removes both of bits of
backwards compatibility (since there will no doubt be numerous other
changes for drivers to take into consideration for 2.4.xx vs 2.6.xx).

The first benefit of all of these changes is that it gets PCI working on
MBX (and any other 8xx system with PCI).  The second benefit is that it
lets all of the otherwise properly written PCMCIA drivers just work
(such as orinoco_cs) which would previously panic() on request_irq().

The bulk of this work was done by Andy Lowe and then moved up to current
kernels and expanded slightly by myself.

Comments?

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

[-- Attachment #2: 8xx_8260_irq-2.5.patch.gz --]
[-- Type: application/octet-stream, Size: 10434 bytes --]

[-- Attachment #3: 8xx_8260_irq.patch.gz --]
[-- Type: application/octet-stream, Size: 10103 bytes --]

             reply	other threads:[~2002-06-20 20:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-20 20:34 Tom Rini [this message]
2002-06-20 21:04 ` [PATCH and RFC] Remove request_8xxirq Dan Malek
2002-06-20 21:39   ` Tom Rini
2002-06-20 22:03     ` Dan Malek
2002-06-20 16:58       ` Benjamin Herrenschmidt
2002-06-20 22:34       ` Tom Rini
2002-06-20 21:16 ` Wolfgang Denk
     [not found] <20020620214551.GI16052@opus.bloom.county>
2002-06-20 21:58 ` Wolfgang Denk
     [not found]   ` <20020620221016.GK16052@opus.bloom.county>
     [not found]     ` <3D12F667.30902@bluewin.ch>
2002-06-24 17:00       ` Tom Rini
2002-06-24 17:49         ` Dan Malek
2002-06-24 17:59           ` Tom Rini
     [not found]         ` <3D1793E1.3030509@bluewin.ch>
     [not found]           ` <20020624224100.GL3489@opus.bloom.county>
2002-06-25  0:03             ` Dan Malek
     [not found] <3D124DF4.6060505@embeddededge.com>
2002-06-20 22:02 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2002-06-21  2:32 Andy Lowe
2002-06-21  4:35 ` Dan Malek
2002-06-21  4:54   ` Andy Lowe
     [not found] <15635.16331.965632.877856@argo.ozlabs.ibm.com>
2002-06-23 16:54 ` Stephan Linke

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=20020620203455.GG16052@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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;
as well as URLs for NNTP newsgroup(s).