Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 16:00:35 +0200 Martin Kepplinger wrote: > Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron > : > >On Mon, 4 Sep 2017 23:06:37 -0400 > >harinath Nampally wrote: > > > >> > I agree with your

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Sun, 10 Sep 2017 16:00:35 +0200 Martin Kepplinger wrote: > Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron > : > >On Mon, 4 Sep 2017 23:06:37 -0400 > >harinath Nampally wrote: > > > >> > I agree with your understanding. It's a rising threshold, just > >that the input >

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron : >On Mon, 4 Sep 2017 23:06:37 -0400 >harinath Nampally wrote: > >> > I agree with your understanding. It's a rising threshold, just >that the input >> > will only reflect high frequency

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 10. September 2017 15:44:24 MESZ schrieb Jonathan Cameron : >On Mon, 4 Sep 2017 23:06:37 -0400 >harinath Nampally wrote: > >> > I agree with your understanding. It's a rising threshold, just >that the input >> > will only reflect high frequency changes in the signal. >> Thank you for the

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Mon, 4 Sep 2017 23:06:37 -0400 harinath Nampally wrote: > > I agree with your understanding. It's a rising threshold, just that the > > input > > will only reflect high frequency changes in the signal. > Thank you for the clarification. I am hoping this gets merged

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Mon, 4 Sep 2017 23:06:37 -0400 harinath Nampally wrote: > > I agree with your understanding. It's a rising threshold, just that the > > input > > will only reflect high frequency changes in the signal. > Thank you for the clarification. I am hoping this gets merged in the > next window if

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> I agree with your understanding. It's a rising threshold, just that the input > will only reflect high frequency changes in the signal. Thank you for the clarification. I am hoping this gets merged in the next window if no other issues. Thanks, Hari On Sun, Sep 3, 2017 at 12:24 PM, Jonathan

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> I agree with your understanding. It's a rising threshold, just that the input > will only reflect high frequency changes in the signal. Thank you for the clarification. I am hoping this gets merged in the next window if no other issues. Thanks, Hari On Sun, Sep 3, 2017 at 12:24 PM, Jonathan

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Tue, 29 Aug 2017 23:01:16 -0400 harinath Nampally wrote: > > We should never say "transient is for rising > > direction" or "ff_mt is for falling direction". any combination is fine. > > Ok I agree that there is no hard and fast rule that "transient is for rising >

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

On Tue, 29 Aug 2017 23:01:16 -0400 harinath Nampally wrote: > > We should never say "transient is for rising > > direction" or "ff_mt is for falling direction". any combination is fine. > > Ok I agree that there is no hard and fast rule that "transient is for rising > direction" or "ff_mt is

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> We should never say "transient is for rising > direction" or "ff_mt is for falling direction". any combination is fine. Ok I agree that there is no hard and fast rule that "transient is for rising direction" or "ff_mt is for falling direction". But in our case, datasheet for these chips define

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

> We should never say "transient is for rising > direction" or "ff_mt is for falling direction". any combination is fine. Ok I agree that there is no hard and fast rule that "transient is for rising direction" or "ff_mt is for falling direction". But in our case, datasheet for these chips define

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 28.08.2017 02:23 schrieb Harinath Nampally: This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver design hardcodes the event specific information, so only one event can be

Re: [PATCH v5] iio: accel: mma8452: improvements to handle multiple events

Am 28.08.2017 02:23 schrieb Harinath Nampally: This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver design hardcodes the event specific information, so only one event can be

[PATCH v5] iio: accel: mma8452: improvements to handle multiple events

This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver design hardcodes the event specific information, so only one event can be supported by this driver at any given

[PATCH v5] iio: accel: mma8452: improvements to handle multiple events

This driver supports multiple devices like mma8653, mma8652, mma8452, mma8453 and fxls8471. Almost all these devices have more than one event. Current driver design hardcodes the event specific information, so only one event can be supported by this driver at any given