From: Martin Fuzzey <mfuzzey@parkeon.com>
To: Jonathan Cameron <jic23@kernel.org>,
Martin Kepplinger <martink@posteo.de>,
knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
roberta.dobrescu@gmail.com,
christoph.muellner@theobroma-systems.com
Cc: linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org,
Martin Kepplinger <martin.kepplinger@theobroma-systems.com>
Subject: Re: [PATCH 7/9] iio: mma8452: change iio event type to IIO_EV_TYPE_MAG
Date: Mon, 06 Jul 2015 10:39:12 +0200 [thread overview]
Message-ID: <559A3EB0.2060200@parkeon.com> (raw)
In-Reply-To: <559919F5.8070107@kernel.org>
On 05/07/15 13:50, Jonathan Cameron wrote:
> On 04/07/15 14:55, Martin Kepplinger wrote:
>> IIO_EV_TYPE_THRESH in rising direction describes an event where the
>> threshold is crossed in rising direction, positive or negative values
>> being possible. This is not the case here.
>>
>> Since the threshold is no signed value and only the magnitude is compared,
>> IIO_EV_TYPE_MAG is what describes the behaviour of these devices, see the
>> sysfs-bus-iio ABI Documentation.
Fwiw there was some discussion of this before the initial submission:
http://www.spinics.net/lists/linux-iio/msg14039.html
Initially I used a magnitude too but Jonathan convinced me it should be
a threshold.
"
The moment you know the sign of the magnitude it stops being a magnitude
and becomes a generic threshold. Report it as such and control it as such.
"
Thing is that the hardware indeed only compares the absolute value for
the threshold *but* indicates with the event the sign.
However it is true that the driver doesn't currently do anything with
the sign information.
>> Signed-off-by: Martin Kepplinger <martin.kepplinger@theobroma-systems.com>
>> Signed-off-by: Christoph Muellner <christoph.muellner@theobroma-systems.com>
> This is a fix and so should have been the first patch in the series. It will
> want to go via a different tree (iio-fixes) and probably be marked for stable.
>
> I would however like Peter's ack on this as well before taking it.
>> ---
>> drivers/iio/accel/mma8452.c | 10 +++++-----
>> 1 file changed, 5 insertions(+), 5 deletions(-)
>>
>> diff --git a/drivers/iio/accel/mma8452.c b/drivers/iio/accel/mma8452.c
>> index 7f6e3b4..e23ebd0 100644
>> --- a/drivers/iio/accel/mma8452.c
>> +++ b/drivers/iio/accel/mma8452.c
>> @@ -598,21 +598,21 @@ static void mma8452_transient_interrupt(struct iio_dev *indio_dev)
>> if (src & data->chip_info->ev_src_xe)
>> iio_push_event(indio_dev,
>> IIO_MOD_EVENT_CODE(IIO_ACCEL, 0, IIO_MOD_X,
>> - IIO_EV_TYPE_THRESH,
>> + IIO_EV_TYPE_MAG,
>> IIO_EV_DIR_RISING),
>> ts);
>>
>> if (src & data->chip_info->ev_src_ye)
>> iio_push_event(indio_dev,
>> IIO_MOD_EVENT_CODE(IIO_ACCEL, 0, IIO_MOD_Y,
>> - IIO_EV_TYPE_THRESH,
>> + IIO_EV_TYPE_MAG,
>> IIO_EV_DIR_RISING),
>> ts);
>>
>> if (src & data->chip_info->ev_src_ze)
>> iio_push_event(indio_dev,
>> IIO_MOD_EVENT_CODE(IIO_ACCEL, 0, IIO_MOD_Z,
>> - IIO_EV_TYPE_THRESH,
>> + IIO_EV_TYPE_MAG,
>> IIO_EV_DIR_RISING),
>> ts);
>> }
>> @@ -689,7 +689,7 @@ static int mma8452_reg_access_dbg(struct iio_dev *indio_dev,
>>
>> static const struct iio_event_spec mma8452_transient_event[] = {
>> {
>> - .type = IIO_EV_TYPE_THRESH,
>> + .type = IIO_EV_TYPE_MAG,
>> .dir = IIO_EV_DIR_RISING,
>> .mask_separate = BIT(IIO_EV_INFO_ENABLE),
>> .mask_shared_by_type = BIT(IIO_EV_INFO_VALUE) |
>> @@ -700,7 +700,7 @@ static const struct iio_event_spec mma8452_transient_event[] = {
>>
>> static const struct iio_event_spec mma8452_motion_event[] = {
>> {
>> - .type = IIO_EV_TYPE_THRESH,
>> + .type = IIO_EV_TYPE_MAG,
>> .dir = IIO_EV_DIR_RISING,
>> .mask_separate = BIT(IIO_EV_INFO_ENABLE),
>> .mask_shared_by_type = BIT(IIO_EV_INFO_VALUE) |
>>
next prev parent reply other threads:[~2015-07-06 8:39 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 13:55 [PATCH v3 0/9] iio: mma8452: improve driver and support more chips Martin Kepplinger
2015-07-04 13:55 ` [PATCH 1/9] iio: mma8452: refactor for seperating chip specific data Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:37 ` Jonathan Cameron
2015-07-05 11:37 ` Jonathan Cameron
2015-07-04 13:55 ` [PATCH 2/9] iio: mma8452: add support for MMA8453Q accelerometer chip Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:41 ` Jonathan Cameron
2015-07-05 11:41 ` Jonathan Cameron
2015-07-04 13:55 ` [PATCH 3/9] iio: mma8452: add freefall / motion interrupt source Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:44 ` Jonathan Cameron
2015-07-05 11:44 ` Jonathan Cameron
2015-07-05 11:44 ` Jonathan Cameron
2015-07-05 11:44 ` Jonathan Cameron
2015-07-04 13:55 ` [PATCH 4/9] iio: mma8452: add support for MMA8652FC and MMA8653FC accelerometers Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:47 ` Jonathan Cameron
2015-07-05 11:47 ` Jonathan Cameron
2015-07-04 13:55 ` [PATCH 5/9] iio: mma8452: add devicetree documentation Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:48 ` Jonathan Cameron
2015-07-05 11:48 ` Jonathan Cameron
2015-07-05 11:50 ` Martin Kepplinger
2015-07-05 11:50 ` Martin Kepplinger
2015-07-05 12:12 ` Jonathan Cameron
2015-07-05 12:12 ` Jonathan Cameron
2015-07-06 8:06 ` Martin Fuzzey
2015-07-06 8:13 ` Martin Kepplinger
2015-07-06 8:13 ` Martin Kepplinger
2015-07-04 13:55 ` [PATCH 6/9] iio: mma8452: add copyright notice comment Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-04 13:55 ` [PATCH 7/9] iio: mma8452: change iio event type to IIO_EV_TYPE_MAG Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:50 ` Jonathan Cameron
2015-07-05 11:50 ` Jonathan Cameron
2015-07-06 8:39 ` Martin Fuzzey [this message]
2015-07-07 7:05 ` Jonathan Cameron
2015-07-07 7:05 ` Jonathan Cameron
2015-07-07 7:05 ` Jonathan Cameron
2015-07-07 7:32 ` Martin Kepplinger
2015-07-07 7:32 ` Martin Kepplinger
2015-07-04 13:55 ` [PATCH 8/9] iio: mma8452: leave sysfs namings to the iio core Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-04 13:55 ` [PATCH 9/9] iio: mma8452: add devicetree property to allow all pin wirings Martin Kepplinger
2015-07-04 13:55 ` Martin Kepplinger
2015-07-05 11:51 ` Jonathan Cameron
2015-07-05 11:51 ` Jonathan Cameron
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=559A3EB0.2060200@parkeon.com \
--to=mfuzzey@parkeon.com \
--cc=christoph.muellner@theobroma-systems.com \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.kepplinger@theobroma-systems.com \
--cc=martink@posteo.de \
--cc=pmeerw@pmeerw.net \
--cc=roberta.dobrescu@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.