From: Harinath Nampally <harinath922@gmail.com>
To: Martin Kepplinger <martink@posteo.de>
Cc: jic23@kernel.org, knaack.h@gmx.de, lars@metafoo.de,
pmeerw@pmeerw.net, gregkh@linuxfoundation.org,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
amsfield22@gmail.com, linux-iio-owner@vger.kernel.org
Subject: Re: [PATCH v4] iio: accel: mma8452: improvements to handle multiple events
Date: Tue, 22 Aug 2017 20:29:52 -0400 [thread overview]
Message-ID: <99ef70c3-64f0-66eb-5c1a-45a034ead5d5@gmail.com> (raw)
In-Reply-To: <b5ba8c62743486649f99625d7a43e42b@posteo.de>
>
> 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;
};
>
> 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)
next prev parent reply other threads:[~2017-08-23 0:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-20 16:06 [PATCH v4] iio: accel: mma8452: improvements to handle multiple events Harinath Nampally
2017-08-21 8:47 ` Martin Kepplinger
2017-08-23 0:29 ` Harinath Nampally [this message]
2017-08-23 4:52 ` Martin Kepplinger
2017-08-24 2:38 ` harinath Nampally
2017-08-24 2:42 ` harinath Nampally
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=99ef70c3-64f0-66eb-5c1a-45a034ead5d5@gmail.com \
--to=harinath922@gmail.com \
--cc=amsfield22@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio-owner@vger.kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martink@posteo.de \
--cc=pmeerw@pmeerw.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox