Re: [PATCH-next] mfd: ab8500: fix dt irq mapping

2014-06-05 Thread Lee Jones
On Thu, 05 Jun 2014, Kevin Hilman wrote: > On Tue, Jun 3, 2014 at 4:21 AM, Linus Walleij > wrote: > > On Mon, Jun 2, 2014 at 6:27 PM, Grygorii Strashko > > wrote: > > > >> The AD8500 defines itself as interrupt-controller in DT, > >> but it doesn't assign DT node to IRQ domain when creates it. >

Re: [PATCH-next] mfd: ab8500: fix dt irq mapping

2014-06-05 Thread Kevin Hilman
On Tue, Jun 3, 2014 at 4:21 AM, Linus Walleij wrote: > On Mon, Jun 2, 2014 at 6:27 PM, Grygorii Strashko > wrote: > >> The AD8500 defines itself as interrupt-controller in DT, >> but it doesn't assign DT node to IRQ domain when creates it. >> As result, of_irq_xx() helpers don't work because they

Re: [PATCH-next] mfd: ab8500: fix dt irq mapping

2014-06-03 Thread Linus Walleij
On Mon, Jun 2, 2014 at 6:27 PM, Grygorii Strashko wrote: > The AD8500 defines itself as interrupt-controller in DT, > but it doesn't assign DT node to IRQ domain when creates it. > As result, of_irq_xx() helpers don't work because they can't > find necessary IRQ domain. > > Hence, fix it by assig

[PATCH-next] mfd: ab8500: fix dt irq mapping

2014-06-02 Thread Grygorii Strashko
The AD8500 defines itself as interrupt-controller in DT, but it doesn't assign DT node to IRQ domain when creates it. As result, of_irq_xx() helpers don't work because they can't find necessary IRQ domain. Hence, fix it by assigning AD8500 core device DT node to IRQ domain when it's created. This