On Tue, Mar 29, 2016 at 05:13:05PM +0100, Marc Zyngier wrote:
> - What if my timer is not connected to a controller that implements this
> API? Something that is not a GIC, for example?
As you know irq_set_irqchip_state() does nothing in that case, and the erratum
is thus presumably not worked aro
On Tue, Mar 29, 2016 at 04:21:03PM +0200, Daniel Lezcano wrote:
> On 03/29/2016 10:08 AM, Rabin Vincent wrote:
> > -0 [001] d.h2 99.850527: irq_handler_entry: irq=16 name=gt
> > -0 [001] d.h2 99.850538: irq_handler_exit: irq=16 ret=handled
> > -0 [001] d.H2 99.850540: irq_handler_entry: irq=16 n
Hi Rabin,
On 29/03/16 09:08, Rabin Vincent wrote:
> From: Rabin Vincent
>
> According to the errata document for the Cortex A9 MPCore, the correct
> code sequence in the interrupt handler to workaround erratum 740657
> "Global Timer can send two interrupts for the same event" is:
>
> (1) Read
On 03/29/2016 10:08 AM, Rabin Vincent wrote:
From: Rabin Vincent
According to the errata document for the Cortex A9 MPCore, the correct
code sequence in the interrupt handler to workaround erratum 740657
"Global Timer can send two interrupts for the same event" is:
(1) Read the ICCIAR (Inter
From: Rabin Vincent
According to the errata document for the Cortex A9 MPCore, the correct
code sequence in the interrupt handler to workaround erratum 740657
"Global Timer can send two interrupts for the same event" is:
(1) Read the ICCIAR (Interrupt Acknowledge) register
(2) Modify the compa
5 matches
Mail list logo