From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Paul Mackerras <paulus@samba.org>,
Alexandre.Bounine@tundra.com,
Yang Xin-Xin-r48390 <Xin-Xin.Yang@freescale.com>
Subject: Re: [PATCH] powerpc: update mpc7448hpc2 board irq supportusingdevice tree
Date: 24 Aug 2006 16:36:06 +0800 [thread overview]
Message-ID: <1156408565.6591.2.camel@localhost.localdomain> (raw)
In-Reply-To: <1156398659.8433.193.camel@localhost.localdomain>
On Thu, 2006-08-24 at 13:50, Benjamin Herrenschmidt wrote:
> > -struct hw_interrupt_type tsi108_pci_irq = {
> > +static struct irq_chip tsi108_pci_irq = {
> > .typename = "tsi108_PCI_int",
> > - .enable = tsi108_pci_irq_enable,
> > - .disable = tsi108_pci_irq_disable,
> > + .mask = tsi108_pci_irq_disable,
> > .ack = tsi108_pci_irq_ack,
> > .end = tsi108_pci_irq_end,
> > + .unmask = tsi108_pci_irq_enable,
> > };
> >
> > /*
>
> While the patch as-is looks ok, it also looks like you could take
> advantage of the new genirq code to clean up your TSI irq handling a
> bit. You probably don't need a end() handler anymore provided that you
> properly set your main handler to be either level, edge or fasteoi (in
> which case, you need an eoi handler).
I need the end() handler. The main handler can not proper process the
case.
Roy
next prev parent reply other threads:[~2006-08-24 8:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 2:19 [PATCH] powerpc: update mpc7448hpc2 board irq support using device tree Zang Roy-r61911
2006-08-23 3:38 ` Benjamin Herrenschmidt
2006-08-23 11:45 ` [PATCH] powerpc: update mpc7448hpc2 board irq support usingdevice tree Zang Roy-r61911
2006-08-24 5:29 ` Zang Roy-r61911
2006-08-24 5:50 ` Benjamin Herrenschmidt
2006-08-24 8:36 ` Zang Roy-r61911 [this message]
2006-08-24 8:53 ` [PATCH] powerpc: update mpc7448hpc2 board irq supportusingdevice tree Benjamin Herrenschmidt
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=1156408565.6591.2.camel@localhost.localdomain \
--to=tie-fei.zang@freescale.com \
--cc=Alexandre.Bounine@tundra.com \
--cc=Xin-Xin.Yang@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.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).