[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200111150735.GA16291@qmqm.qmqm.pl>
Date: Sat, 11 Jan 2020 16:07:35 +0100
From: Michał Mirosław <mirq-linux@...e.qmqm.pl>
To: Jonathan Cameron <jic23@...nel.org>
Cc: Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald-Stadler <pmeerw@...erw.net>,
Jean-Baptiste Maneyrol <jmaneyrol@...ensense.com>,
linux-iio@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] iio: imu/mpu6050: support dual-edge IRQ
On Sat, Jan 11, 2020 at 12:10:47PM +0000, Jonathan Cameron wrote:
> On Mon, 06 Jan 2020 12:17:54 +0100
> Michał Mirosław <mirq-linux@...e.qmqm.pl> wrote:
>
> > Make mpu6050 usable on platforms which provide only any-edge interrupts.
> > This also covers shared interrupt case.
>
> So this had me confused for a bit because I assumed we were trying to make
> a level interrupt providing device work with edge interrupts. Seems
> device supports a pulsed mode and the driver supports this.
>
> Why do we want to detect on both edges? Do you have a crazy board
> with this shared and some devices using the rising edge and some the falling one?
>
> For shared case it should return that it did not handle the interrupt
> to allow spurious interrupt detection to work...
Hmm. The shared interrupt is a red herring. I'll remove the sentence
from commitmsg as it looks like the driver needs a few more fixups
to be able to share the interrupt line.
The patch is required on platforms that support only dual-edge
interrupts, like eg. AT91SAM9G45-based one I have.
Best Regards,
Michał Mirosław
Powered by blists - more mailing lists