Thread (30 messages) 30 messages, 6 authors, 2012-01-29

Re: [RFCv2 00/14]

From: Rob Herring <hidden>
Date: 2012-01-25 18:51:14
Also in: linux-devicetree, lkml

On 01/25/2012 08:13 AM, Cousson, Benoit wrote:
On 1/23/2012 10:53 PM, Rob Herring wrote:
quoted
On 01/23/2012 03:07 PM, Grant Likely wrote:
quoted
Hey everyone,

Here's the second RFC for the irq_domain patches.  I could use some
help testing now.  I still expect there will be a few bugs.  The
series is based on v3.3-rc1, and I've pushed it out to my git server:

git://git.secretlab.ca/git/linux-2.6.git irqdomain/next
Can you post to linux-arm-kernel too so people are aware of this work
and stop posting dead-end irqdomain patches.
Good point, I have two pending series that are using the
irq_domain_add() so far, so it will be good to have that branch pulled
in arm-soc.
quoted
I tested what you had as of this morning and it works fine for me. Looks
like the only diff is the VExpress code. I'm working on rebasing my
domain support for generic irqchip now.
In fact your generic irqchip should even avoid us to use
irq_domain_add_legacy() since both GPIO and OMAP3 intc are already using
the irqchip.

I guess you are not going to change the interface so the patches I did
on your previous branch to try them should be good already, isn't it?
I've got it rebased on top of Grant's tree. I will send it out soon.

One problem that still remains is it breaks x86 and any platform using
generic irq chip, but not selecting IRQ_DOMAIN. Grant, do you plan to
enable IRQ_DOMAIN for x86 in your series? MIPS may also need fixing.

Rob
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help