On Tue, Feb 27, 2018 at 8:05 AM, Tim Harvey wrote:
> When acking irqs we need to take into account the ack-invert case. Without
> this chips that require 0's to ACK interrupts will never clear the interrupt.
>
> I am working on an mfd driver that will use ack-invert and discovered
> this issue. Th
* Tim Harvey [180228 21:18]:
> On Tue, Feb 27, 2018 at 10:39 AM, Tony Lindgren wrote:
> > * Tim Harvey [180227 16:07]:
> >> When acking irqs we need to take into account the ack-invert case. Without
> >> this chips that require 0's to ACK interrupts will never clear the
> >> interrupt.
> >>
> >
On Tue, Feb 27, 2018 at 10:39 AM, Tony Lindgren wrote:
> * Tim Harvey [180227 16:07]:
>> When acking irqs we need to take into account the ack-invert case. Without
>> this chips that require 0's to ACK interrupts will never clear the interrupt.
>>
>> I am working on an mfd driver that will use ac
* Tim Harvey [180227 16:07]:
> When acking irqs we need to take into account the ack-invert case. Without
> this chips that require 0's to ACK interrupts will never clear the interrupt.
>
> I am working on an mfd driver that will use ack-invert and discovered
> this issue. The only user of ack_in
When acking irqs we need to take into account the ack-invert case. Without
this chips that require 0's to ACK interrupts will never clear the interrupt.
I am working on an mfd driver that will use ack-invert and discovered
this issue. The only user of ack_invert currently appears to be the
motorol
5 matches
Mail list logo