lkml.org 
[lkml]   [2017]   [Aug]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v4] iio: accel: mma8452: improvements to handle multiple events
Am 23.08.2017 02:29 schrieb Harinath Nampally:
>>
>> If rising: use transient OR ff_mt device-dependent like before. But
>> now save it in a simple flag,
>> whether transient registers are available.
> Ok, is it good idea to add the flag to struct mma_chip_info like below?
>
> * @mma_scales: scale factors for converting
> register values
> * to m/s^2; 3 modes: 2g, 4g, 8g; 2
> integers
> * per mode: m/s^2 and micro m/s^2
> + * @transient_supported: flag indicating whether chip support
> transient
> + * event, as not all chips support
> transient event
> */
> struct mma_chip_info {
> u8 chip_id;
> const struct iio_chan_spec *channels;
> int num_channels;
> const int mma_scales[3][2];
> + bool transient_supported;
> };
>

I'd avoid boolean and use int and define EVENT_TYPE_TRANSIENT BIT(1) and
EVENT_TYPE_FF_MT BIT(0) for example. So something like
"supported_event_types"
can have all types supported.

But this has quite some implications on your implementation, so your
complete
solution would be more interesting to see. Keep it simple and focus on
only this one
issue of enabling freefall (FF_MT registers) for the devices that
currently use
transient registers.

thanks

>>
>> If falling: switch to ff_mt in any case. (fixing freefall for the
>> transient-devices)
> ok sure.
>
> Thanks,
>
> Hari
>
> On 08/21/2017 04:47 AM, Martin Kepplinger wrote:
>>
>> If rising: use transient OR ff_mt device-dependent like before. But
>> now save it in a simple flag,
>> whether transient registers are available.
>>
>> If falling: switch to ff_mt in any case. (fixing freefall for the
>> transient-devices)

\
 
 \ /
  Last update: 2017-08-23 06:53    [W:0.853 / U:0.128 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site