From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 1/3] Adapt ipic driver to new host_ops interface, add set_irq_type to set IRQ sense
Date: Thu, 24 Aug 2006 13:45:25 +1000 [thread overview]
Message-ID: <1156391125.8433.166.camel@localhost.localdomain> (raw)
In-Reply-To: <FBC2DEDA-6D07-4FD6-93FD-E1D37145AB7F@kernel.crashing.org>
On Wed, 2006-08-23 at 20:58 -0500, Kumar Gala wrote:
> On Aug 23, 2006, at 8:39 PM, Kim Phillips wrote:
>
> > This converts ipic code to Benh's IRQ mods. For the IPIC, IRQ
> > sense values in the device tree equal those in include/linux/irq.h;
> > that's 8 for low assertion (most internal IRQs on mpc83xx), and 2
> > for high-to-low change.
> >
> > Signed-off-by: Kim Phillips <kim.phillips@freescale.com>
> > Signed-off-by: Li Yang <leoli@freescale.com>
>
> This breaks the arch/ppc build of 83xx, can we clone ipic as it
> stands move that over to arch/ppc and apply your changes on top of that.
Yup, we should do that, like I did for i8259, at least until
arch/powerpc 83xx is in good enough shape that the arch/ppc one can be
dropped completely.
Ben.
next prev parent reply other threads:[~2006-08-24 3:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 1:39 [PATCH 1/3] Adapt ipic driver to new host_ops interface, add set_irq_type to set IRQ sense Kim Phillips
2006-08-24 1:58 ` Kumar Gala
2006-08-24 3:45 ` Benjamin Herrenschmidt [this message]
2006-08-24 3:44 ` Benjamin Herrenschmidt
2006-08-24 5:44 ` [PATCH 1/3] Adapt ipic driver to new host_ops interface, addset_irq_type " Li Yang-r58472
2006-08-24 5:56 ` Benjamin Herrenschmidt
2006-08-24 7:39 ` Li Yang-r58472
2006-08-24 7:58 ` [PATCH 1/3] Adapt ipic driver to new host_ops interface,addset_irq_type " 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=1156391125.8433.166.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=galak@kernel.crashing.org \
--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).