On Thursday 10 December 2015 08:46 PM, Sekhar Nori wrote:
> Hi Felipe,
>
> On Tuesday 08 December 2015 07:15 PM, Felipe Balbi wrote:
>> Sekhar Nori writes:
>
>>> + /*
>>> +* A spurious IRQ can result if interrupt that triggered the
>>> +* sorting is no longer active during the sorting
Hi Felipe,
On Tuesday 08 December 2015 07:15 PM, Felipe Balbi wrote:
> Sekhar Nori writes:
>> +/*
>> + * A spurious IRQ can result if interrupt that triggered the
>> + * sorting is no longer active during the sorting (10 INTC
>> + * functional clock cycles after interrupt asserti
Hi,
Sekhar Nori writes:
> Under some conditions, irq sorting procedure used
> by INTC can go wrong resulting in a spurious irq
> getting reported.
>
> If this condition is not handled, it results in
> endless stream of:
>
> unexpected IRQ trap at vector 00
>
> messages from ack_bad_irq()
>
>
Under some conditions, irq sorting procedure used
by INTC can go wrong resulting in a spurious irq
getting reported.
If this condition is not handled, it results in
endless stream of:
unexpected IRQ trap at vector 00
messages from ack_bad_irq()
Handle the spurious interrupt condition in oma
4 matches
Mail list logo
