From: Jonathan Cameron <jic23@kernel.org>
To: Gwendal Grignou <gwendal@chromium.org>
Cc: lars@metafoo.de, andy.shevchenko@gmail.com,
linux-iio@vger.kernel.org,
Jongpil Jung <jongpil19.jung@samsung.com>
Subject: Re: [PATCH v2] iio: sx9360: fix iio event generation
Date: Sun, 30 Jan 2022 12:41:05 +0000 [thread overview]
Message-ID: <20220130124105.23ed6bdb@jic23-huawei> (raw)
In-Reply-To: <20220122213444.745152-1-gwendal@chromium.org>
On Sat, 22 Jan 2022 13:34:44 -0800
Gwendal Grignou <gwendal@chromium.org> wrote:
> From: Jongpil Jung <jongpil19.jung@samsung.com>
>
> To convert SX9360 status register ["REG_STAT"], into a channel
> index, we need to right shift by |stat_offset|, not left shift.
> Also the PROXSTAT bit (3) is for channel 1 (PHM, Phase Measured), not (PHR,
> Phase Reference, channel 0), so the offset is 2 instead of 3.
>
> Fixes: f75095753 ("iio:proximity:sx9360: Add sx9360 support")
Should be 12 chars of the hash.
Also, tree rebased at rc1 so it's wrong anyway :)
Fixed it up and applied to the togreg branch of iio.git and pushed
out as testing for 0-day to see if it can find anything else.
Thanks,
Jonathan
> Signed-off-by: Jongpil Jung <jongpil19.jung@samsung.com>
> Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
> ---
> Changes since v1:
> - Change title to highlight the patch is a fix.
> - Put "Fixes:" tag in the commit message footer
>
> drivers/iio/proximity/sx9360.c | 2 +-
> drivers/iio/proximity/sx_common.c | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/iio/proximity/sx9360.c b/drivers/iio/proximity/sx9360.c
> index 6fd6561bb6f5b8..3ebb30c8a4f61d 100644
> --- a/drivers/iio/proximity/sx9360.c
> +++ b/drivers/iio/proximity/sx9360.c
> @@ -775,7 +775,7 @@ static const struct sx_common_chip_info sx9360_chip_info = {
> .reg_reset = SX9360_REG_RESET,
>
> .mask_enable_chan = SX9360_REG_GNRL_CTRL0_PHEN_MASK,
> - .stat_offset = 3,
> + .stat_offset = 2,
> .num_channels = SX9360_NUM_CHANNELS,
> .num_default_regs = ARRAY_SIZE(sx9360_default_regs),
>
> diff --git a/drivers/iio/proximity/sx_common.c b/drivers/iio/proximity/sx_common.c
> index ac8fd5920481cb..a7c07316a0a91e 100644
> --- a/drivers/iio/proximity/sx_common.c
> +++ b/drivers/iio/proximity/sx_common.c
> @@ -87,7 +87,7 @@ static void sx_common_push_events(struct iio_dev *indio_dev)
> return;
> }
>
> - val <<= data->chip_info->stat_offset;
> + val >>= data->chip_info->stat_offset;
>
> /*
> * Only iterate over channels with changes on proximity status that have
prev parent reply other threads:[~2022-01-30 12:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 21:34 [PATCH v2] iio: sx9360: fix iio event generation Gwendal Grignou
2022-01-30 12:41 ` Jonathan Cameron [this message]
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=20220130124105.23ed6bdb@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy.shevchenko@gmail.com \
--cc=gwendal@chromium.org \
--cc=jongpil19.jung@samsung.com \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
/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