On 2017-06-13 07:41, Stephen Boyd wrote:
On 06/06, kgu...@codeaurora.org wrote:
On 2017-05-31 07:27, Stephen Boyd wrote:
>On 05/30, Kiran Gunda wrote:
>>From: Abhijeet Dharmapurikar
>>
>>We see a unmapped irqs trigger right around bootup. This could
>>likely be because the bootloader exited lea
On 06/06, kgu...@codeaurora.org wrote:
> On 2017-05-31 07:27, Stephen Boyd wrote:
> >On 05/30, Kiran Gunda wrote:
> >>From: Abhijeet Dharmapurikar
> >>
> >>We see a unmapped irqs trigger right around bootup. This could
> >>likely be because the bootloader exited leaving the interrupts
> >>in an un
On 2017-05-31 07:27, Stephen Boyd wrote:
On 05/30, Kiran Gunda wrote:
From: Abhijeet Dharmapurikar
We see a unmapped irqs trigger right around bootup. This could
likely be because the bootloader exited leaving the interrupts
in an unknown or unhandled state. Ack and mask the interrupt
if one
On 05/30, Kiran Gunda wrote:
> From: Abhijeet Dharmapurikar
>
> We see a unmapped irqs trigger right around bootup. This could
> likely be because the bootloader exited leaving the interrupts
> in an unknown or unhandled state. Ack and mask the interrupt
> if one is found. A request_irq later wi
From: Abhijeet Dharmapurikar
We see a unmapped irqs trigger right around bootup. This could
likely be because the bootloader exited leaving the interrupts
in an unknown or unhandled state. Ack and mask the interrupt
if one is found. A request_irq later will unmask it and also
setup proper mappin
5 matches
Mail list logo