Re: [PATCH v2 3/3] irqchip: orion: reverse irq handling priority

2014-05-04 Thread Jason Cooper
On Mon, Apr 28, 2014 at 11:12:08PM +0200, Sebastian Hesselbarth wrote: > Non-DT irq handlers were working through irq causes from most-significant > to least-significant bit, while DT irqchip driver does it the other way > round. This revealed some more HW issues on Kirkwood peripheral IP, where >

Re: [PATCH v2 3/3] irqchip: orion: reverse irq handling priority

2014-05-04 Thread Jason Cooper
On Mon, Apr 28, 2014 at 11:12:08PM +0200, Sebastian Hesselbarth wrote: Non-DT irq handlers were working through irq causes from most-significant to least-significant bit, while DT irqchip driver does it the other way round. This revealed some more HW issues on Kirkwood peripheral IP, where

[PATCH v2 3/3] irqchip: orion: reverse irq handling priority

2014-04-28 Thread Sebastian Hesselbarth
Non-DT irq handlers were working through irq causes from most-significant to least-significant bit, while DT irqchip driver does it the other way round. This revealed some more HW issues on Kirkwood peripheral IP, where spurious sdio irqs can happen although irqs are masked. Also, the generated

[PATCH v2 3/3] irqchip: orion: reverse irq handling priority

2014-04-28 Thread Sebastian Hesselbarth
Non-DT irq handlers were working through irq causes from most-significant to least-significant bit, while DT irqchip driver does it the other way round. This revealed some more HW issues on Kirkwood peripheral IP, where spurious sdio irqs can happen although irqs are masked. Also, the generated