Re: [PATCH v4] irqchip/mmp: only touch the PJ4 & FIQ bits on enable/disable

2019-01-16 Thread Lubomir Rintel
On Tue, 2019-01-15 at 11:22 +0100, Thomas Gleixner wrote: > On Thu, 20 Dec 2018, Lubomir Rintel wrote: > > > On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71 > > and 72 interrupts. Don't reset the "route to SP" bit (4). > > > > I'm just assuming the bit 4 is the "route to

Re: [PATCH v4] irqchip/mmp: only touch the PJ4 & FIQ bits on enable/disable

2019-01-15 Thread Thomas Gleixner
On Thu, 20 Dec 2018, Lubomir Rintel wrote: > On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71 > and 72 interrupts. Don't reset the "route to SP" bit (4). > > I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the > SP-based keyboard for me and defines > ICU_

Re: [PATCH v4] irqchip/mmp: only touch the PJ4 & FIQ bits on enable/disable

2019-01-10 Thread Lubomir Rintel
On Thu, 2018-12-20 at 22:55 +0100, Lubomir Rintel wrote: > On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71 > and 72 interrupts. Don't reset the "route to SP" bit (4). > > I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the > SP-based keyboard for me and d

[PATCH v4] irqchip/mmp: only touch the PJ4 & FIQ bits on enable/disable

2018-12-20 Thread Lubomir Rintel
On an OLPC XO 1.75 machine, the "security processor" handles the GPIO 71 and 72 interrupts. Don't reset the "route to SP" bit (4). I'm just assuming the bit 4 is the "route to SP" bit -- it fixes the SP-based keyboard for me and defines ICU_INT_ROUTE_SP_IRQ to be 1 << 4. When asked for a data she