On Fri, Jan 27, 2012 at 18:49:42, Nori, Sekhar wrote:
Hi Jon,
On Tue, Jan 17, 2012 at 15:32:23, Nori, Sekhar wrote:
I was able to reproduce this on the EVM using v2.6.38 (works)
and v3.2 + my patch (doesn't work). I just started poking some
registers to see what is happening. Will keep you
Hi Jon,
On Fri, Jan 27, 2012 at 18:49:42, Nori, Sekhar wrote:
Hi Jon,
On Tue, Jan 17, 2012 at 15:32:23, Nori, Sekhar wrote:
I was able to reproduce this on the EVM using v2.6.38 (works)
and v3.2 + my patch (doesn't work). I just started poking some
registers to see what is happening.
Hi Jon,
On Tue, Jan 17, 2012 at 15:32:23, Nori, Sekhar wrote:
I was able to reproduce this on the EVM using v2.6.38 (works)
and v3.2 + my patch (doesn't work). I just started poking some
registers to see what is happening. Will keep you updated
on any progress.
Following patch fixes the
Hi Jon,
On Mon, Jan 16, 2012 at 17:08:30, Jon Povey wrote:
Sorry, last email had some lies, I had testing errors:
Jon Povey wrote:
But I did try reverting the genirq change too, and
the interrupt handler still wasn't called
This was incorrect, interrupt DOES work with genirq reverted
Nori, Sekhar wrote:
On Wed, Jan 11, 2012 at 17:17:34, Jon Povey wrote:
Unbanked GPIO IRQs (I am on DM365) seem to have been broken
by commit aac4dd1dab8acfc244d697473d2a5f4424a5746c, conversion
to generic irq chip, leading to an oops from request_irq().
The root cause indeed seems to be
Sorry, last email had some lies, I had testing errors:
Jon Povey wrote:
But I did try reverting the genirq change too, and
the interrupt handler still wasn't called
This was incorrect, interrupt DOES work with genirq reverted on 3.2.
3.2 vanilla: oops requesting irq
3.2 + your patch: no
Hi Jon,
On Wed, Jan 11, 2012 at 17:17:34, Jon Povey wrote:
Unbanked GPIO IRQs (I am on DM365) seem to have been broken
by commit aac4dd1dab8acfc244d697473d2a5f4424a5746c, conversion
to generic irq chip, leading to an oops from request_irq().
Please note I am on kernel 3.0.0-rc7 not the
