From: Jonathan Cameron <jic23@kernel.org>
To: Arnav Kapoor <kapoorarnav43@gmail.com>
Cc: "David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Stephen Boyd" <swboyd@chromium.org>,
linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] iio: proximity: sx9310: report a hysteresis of 0 when it is disabled
Date: Mon, 2 Nov 2026 00:47:07 +0000 [thread overview]
Message-ID: <20261102004707.596faffd@jic23-hlaptop> (raw)
In-Reply-To: <20261026112054.59895-1-kapoorarnav43@gmail.com>
On Mon, 26 Oct 2026 16:50:49 +0530
Arnav Kapoor <kapoorarnav43@gmail.com> wrote:
> sx9310_read_hysteresis() turns a PROXHYST value of 0 (no hysteresis)
> into a shift of 0 and reports the full threshold, which writing back
> then usually fails with -EINVAL. Report 0, as sx9324 and sx9360 do.
>
> Fixes: 08f0411c48f2 ("iio: sx9310: Support setting hysteresis values")
> Signed-off-by: Arnav Kapoor <kapoorarnav43@gmail.com>
Seems correct to me, but not massively urgent. So with that in mind
I've queued this one on the testing branch of iio.git.
I've just rebased that on the newly available 7.4-rc1, so will give
it a few days exposure to the bots before pushing out for linux-next.
Thanks,
Jonathan
> ---
> Changes in v2:
> - Invert the conditional (Andy)
>
> v1: https://lore.kernel.org/all/20261026100041.16018-1-kapoorarnav43@gmail.com/
>
> Compile-tested only (W=1); I don't have SX9310 hardware.
>
> drivers/iio/proximity/sx9310.c | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
>
> diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
> index 79ba46d8a0aa..dc1b1c3f4776 100644
> --- a/drivers/iio/proximity/sx9310.c
> +++ b/drivers/iio/proximity/sx9310.c
> @@ -446,11 +446,10 @@ static int sx9310_read_hysteresis(struct sx_common_data *data,
> return ret;
>
> regval = FIELD_GET(SX9310_REG_PROX_CTRL10_HYST_MASK, regval);
> - if (!regval)
> - regval = 5;
> -
> - /* regval is at most 5 */
> - *val = pthresh >> (5 - regval);
> + if (regval)
> + *val = pthresh >> (5 - regval);
> + else
> + *val = 0;
>
> return IIO_VAL_INT;
> }
>
> base-commit: 2ef6f5c4ee56e90c237c5f7687f09e635f7d30a9
prev parent reply other threads:[~2026-11-02 0:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-26 11:20 Arnav Kapoor
2026-11-02 0:47 ` 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=20261102004707.596faffd@jic23-hlaptop \
--to=jic23@kernel.org \
--cc=andriy.shevchenko@intel.com \
--cc=andy@kernel.org \
--cc=dlechner@baylibre.com \
--cc=kapoorarnav43@gmail.com \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=swboyd@chromium.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
all inboxes | Powered by JetHome®