From: Jonathan Cameron <jic23@kernel.org>
To: "Michał Mirosław" <mirq-linux@rere.qmqm.pl>
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
linux-iio@vger.kernel.org
Subject: Re: [PATCH v2 4/7] iio: accel: kxcjk1013: rename motion direction bits
Date: Sun, 3 Sep 2017 12:57:36 +0100 [thread overview]
Message-ID: <20170903125736.68d4a918@archlinux> (raw)
In-Reply-To: <763b40e19a19f0d35944b2b4bc0dcf7634dd69b8.1503352742.git.mirq-linux@rere.qmqm.pl>
On Tue, 22 Aug 2017 00:03:31 +0200
Michał Mirosław <mirq-linux@rere.qmqm.pl> wrote:
> Rename INT_SRC2 bits - detected motion direction. This will avoid
> duplication when KXTF9's tap direction is implemented.
>
> Signed-off-by: Michał Mirosław <mirq-linux@rere.qmqm.pl>
I would have preferred this being left until the tap direction
stuff is ready to go. It's a premature change at the moment.
It is not that important though so lets leave it here to avoid a
respin if there are no issues in later patches.
If you are respining for some reason I'd like this dropped for now.
Jonathan
> ---
> drivers/iio/accel/kxcjk-1013.c | 24 ++++++++++++------------
> 1 file changed, 12 insertions(+), 12 deletions(-)
>
> diff --git a/drivers/iio/accel/kxcjk-1013.c b/drivers/iio/accel/kxcjk-1013.c
> index 3022bc951dc2..252004640403 100644
> --- a/drivers/iio/accel/kxcjk-1013.c
> +++ b/drivers/iio/accel/kxcjk-1013.c
> @@ -80,12 +80,12 @@
> #define KXCJK1013_REG_INT_SRC1_BIT_WUFS BIT(1)
> #define KXCJK1013_REG_INT_SRC1_BIT_DRDY BIT(4)
>
> -#define KXCJK1013_REG_INT_SRC2_BIT_ZP BIT(0)
> -#define KXCJK1013_REG_INT_SRC2_BIT_ZN BIT(1)
> -#define KXCJK1013_REG_INT_SRC2_BIT_YP BIT(2)
> -#define KXCJK1013_REG_INT_SRC2_BIT_YN BIT(3)
> -#define KXCJK1013_REG_INT_SRC2_BIT_XP BIT(4)
> -#define KXCJK1013_REG_INT_SRC2_BIT_XN BIT(5)
> +#define KXCJK1013_DIRECTION_BIT_ZP BIT(0)
> +#define KXCJK1013_DIRECTION_BIT_ZN BIT(1)
> +#define KXCJK1013_DIRECTION_BIT_YP BIT(2)
> +#define KXCJK1013_DIRECTION_BIT_YN BIT(3)
> +#define KXCJK1013_DIRECTION_BIT_XP BIT(4)
> +#define KXCJK1013_DIRECTION_BIT_XN BIT(5)
>
> #define KXCJK1013_DEFAULT_WAKE_THRES 1
>
> @@ -1043,7 +1043,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> return;
> }
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_XN)
> + if (ret & KXCJK1013_DIRECTION_BIT_XN)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
> @@ -1052,7 +1052,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> IIO_EV_DIR_FALLING),
> data->timestamp);
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_XP)
> + if (ret & KXCJK1013_DIRECTION_BIT_XP)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
> @@ -1061,7 +1061,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> IIO_EV_DIR_RISING),
> data->timestamp);
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_YN)
> + if (ret & KXCJK1013_DIRECTION_BIT_YN)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
> @@ -1070,7 +1070,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> IIO_EV_DIR_FALLING),
> data->timestamp);
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_YP)
> + if (ret & KXCJK1013_DIRECTION_BIT_YP)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
> @@ -1079,7 +1079,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> IIO_EV_DIR_RISING),
> data->timestamp);
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_ZN)
> + if (ret & KXCJK1013_DIRECTION_BIT_ZN)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
> @@ -1088,7 +1088,7 @@ static void kxcjk1013_report_motion_event(struct iio_dev *indio_dev)
> IIO_EV_DIR_FALLING),
> data->timestamp);
>
> - if (ret & KXCJK1013_REG_INT_SRC2_BIT_ZP)
> + if (ret & KXCJK1013_DIRECTION_BIT_ZP)
> iio_push_event(indio_dev,
> IIO_MOD_EVENT_CODE(IIO_ACCEL,
> 0,
next prev parent reply other threads:[~2017-09-03 11:57 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 22:03 [PATCH v2 0/7] iio: accel: kxcjk1003: support Kionix KXTF9 Michał Mirosław
2017-08-21 22:03 ` [PATCH v2 2/7] iio: accel: kxcjk1013: fix INT_CTRL/INT_SRC1 bit names Michał Mirosław
2017-09-03 11:50 ` Jonathan Cameron
2017-08-21 22:03 ` [PATCH v2 1/7] iio: accel: kxcjk1003: refactor ODR setting Michał Mirosław
2017-09-03 11:48 ` Jonathan Cameron
2017-08-21 22:03 ` [PATCH v2 4/7] iio: accel: kxcjk1013: rename motion direction bits Michał Mirosław
2017-09-03 11:57 ` Jonathan Cameron [this message]
2017-08-21 22:03 ` [PATCH v2 3/7] iio: accel: kxcjk1013: extract report_motion_event() from interrupt handler Michał Mirosław
2017-09-03 11:51 ` Jonathan Cameron
2017-08-21 22:03 ` [PATCH v2 6/7] iio: accel: kxcjk1013: make sampling_frequency_avail per-type Michał Mirosław
2017-09-03 11:59 ` Jonathan Cameron
2017-08-21 22:03 ` [PATCH v2 7/7] iio: accel: kxcjk1013: add support for KXTF9 Michał Mirosław
2017-09-03 12:05 ` Jonathan Cameron
2017-08-21 22:03 ` [PATCH v2 5/7] iio: accel: kxcjk1013: make sysfs/sampling_frequency_avail dynamic Michał Mirosław
2017-09-03 11:58 ` Jonathan Cameron
2017-09-03 12:02 ` Jonathan Cameron
2017-08-21 22:05 ` [PATCH v2 0/7] iio: accel: kxcjk1003: support Kionix KXTF9 Michał Mirosław
2017-09-03 11:43 ` Jonathan Cameron
2017-09-04 21:04 ` Michał Mirosław
2017-09-10 13:32 ` Jonathan Cameron
2017-09-06 15:10 ` Srinivas Pandruvada
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=20170903125736.68d4a918@archlinux \
--to=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--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;
as well as URLs for NNTP newsgroup(s).