linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linuxppc-dev@ozlabs.org, jgarzik@pobox.com
Subject: Re: [PATCH] Fix Maple PATA IRQ assignment.
Date: Mon, 01 Jan 2007 21:43:45 +0000	[thread overview]
Message-ID: <1167687826.18169.9.camel@shinybook.infradead.org> (raw)
In-Reply-To: <20070101213444.2794563b@localhost.localdomain>

On Mon, 2007-01-01 at 21:34 +0000, Alan wrote:
> > Er, that would be pci_get_legacy_ide_irq(), which is what I _have_ used.
> 
> Ok un-NAK that, I didn't realise there was a wrapper to those methods too.
> 
> > As I said, the Maple board is the _only_ user, across all architectures
> > and all PowerPC platforms, of pci_get_legacy_ide_irq(). And the AMD74xx
> 
> The Motorola's also used to use funny IRQ numbers for IDE legacy - or are
> they no longer supported

Well, there's no other implementation of pci_get_legacy_ide_irq() (other
than the default {15,14}) except for Maple, throughout all of arch/ppc
and arch/powerpc.

> > driver is the only driver which calls it -- for Maple. Hence the
> > suggestion that perhaps there's a better way to do it.
> 
> IRQ routing is platform not driver. Let's keep it that way.

Well, yes -- that's what my patch does. I was just thinking that since
this is the _only_ platform which currently uses it, it might be worth
fixing it differently -- by changing the platform setup code to either
route the interrupts to match what the generic code expects, or switch
the controller to native mode.

I'm happy enough with the patch I sent too though.

-- 
dwmw2

  reply	other threads:[~2007-01-01 21:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 19:31 [PATCH] Fix Maple PATA IRQ assignment David Woodhouse
2007-01-01 20:10 ` Benjamin Herrenschmidt
2007-01-01 20:26   ` David Woodhouse
2007-01-01 21:23     ` Benjamin Herrenschmidt
2007-01-01 20:44   ` Segher Boessenkool
2007-01-01 21:33     ` Benjamin Herrenschmidt
2007-01-01 22:17       ` Segher Boessenkool
2007-01-01 20:42 ` Segher Boessenkool
2007-01-01 20:56   ` David Woodhouse
2007-01-01 21:22 ` Alan
2007-01-01 21:15   ` David Woodhouse
2007-01-01 21:34     ` Alan
2007-01-01 21:43       ` David Woodhouse [this message]
2007-01-02  0:17         ` Benjamin Herrenschmidt
2007-01-02  0:18 ` Benjamin Herrenschmidt
2007-01-26 22:28 ` Jeff Garzik

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=1167687826.18169.9.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=jgarzik@pobox.com \
    --cc=linuxppc-dev@ozlabs.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).