From: Jonathan Cameron <jic23@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: linux-kernel@vger.kernel.org, linux-iio@vger.kernel.org,
Daniel Campello <campello@chromium.org>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
Douglas Anderson <dianders@chromium.org>,
Gwendal Grignou <gwendal@chromium.org>,
Evan Green <evgreen@chromium.org>
Subject: Re: [PATCH v2] iio: sx9310: Fix semtech,avg-pos-strength setting when > 16
Date: Sat, 21 Nov 2020 15:02:45 +0000 [thread overview]
Message-ID: <20201121150245.4da5c4cf@archlinux> (raw)
In-Reply-To: <20201121145849.32e14ab9@archlinux>
On Sat, 21 Nov 2020 14:58:49 +0000
Jonathan Cameron <jic23@kernel.org> wrote:
> On Fri, 20 Nov 2020 10:29:44 -0800
> Stephen Boyd <swboyd@chromium.org> wrote:
>
> > This DT property can be 0, 16, and then 64, but not 32. The math here
> > doesn't recognize this slight bump in the power of 2 numbers and
> > translates a DT property of 64 into the register value '3' when it
> > really should be '2'. Fix it by subtracting one more if the number being
> > translated is larger than 16.
> >
> > Cc: Daniel Campello <campello@chromium.org>
> > Cc: Lars-Peter Clausen <lars@metafoo.de>
> > Cc: Peter Meerwald-Stadler <pmeerw@pmeerw.net>
> > Cc: Douglas Anderson <dianders@chromium.org>
> > Cc: Gwendal Grignou <gwendal@chromium.org>
> > Cc: Evan Green <evgreen@chromium.org>
> > Signed-off-by: Stephen Boyd <swboyd@chromium.org>
> > ---
> >
> > Changes from v1 (https://lore.kernel.org/r/20201120073842.3232458-1-swboyd@chromium.org):
> > * Changed ternary to consider 17 to 31 as the same as 16
> >
> > drivers/iio/proximity/sx9310.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/iio/proximity/sx9310.c b/drivers/iio/proximity/sx9310.c
> > index a2f820997afc..ee1b4ff05a37 100644
> > --- a/drivers/iio/proximity/sx9310.c
> > +++ b/drivers/iio/proximity/sx9310.c
> > @@ -1305,7 +1305,7 @@ sx9310_get_default_reg(struct sx9310_data *data, int i,
> > if (ret)
> > break;
> >
> > - pos = min(max(ilog2(pos), 3), 10) - 3;
> > + pos = min(max(ilog2(pos), 3), 11) - (pos >= 32 ? 4 : 3);
>
> Given this is now rather tricky to read, I'd just do an explicit lookup of
> the allowed values. Probably just a switch statement.
As an alternative, a comment would help saying that it's powers of 2 except
for a gap at 64.
Thanks,
J
>
> Thanks,
>
> Jonathan
>
> > reg_def->def &= ~SX9310_REG_PROX_CTRL7_AVGPOSFILT_MASK;
> > reg_def->def |= FIELD_PREP(SX9310_REG_PROX_CTRL7_AVGPOSFILT_MASK,
> > pos);
> >
> > base-commit: 5b19ca2c78a0838976064c0347e46a2c859b541d
>
next prev parent reply other threads:[~2020-11-21 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 18:29 [PATCH v2] iio: sx9310: Fix semtech,avg-pos-strength setting when > 16 Stephen Boyd
2020-11-20 18:31 ` Doug Anderson
2020-11-21 14:58 ` Jonathan Cameron
2020-11-21 15:02 ` Jonathan Cameron [this message]
2020-12-02 19:32 ` Stephen Boyd
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=20201121150245.4da5c4cf@archlinux \
--to=jic23@kernel.org \
--cc=campello@chromium.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=gwendal@chromium.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pmeerw@pmeerw.net \
--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;
as well as URLs for NNTP newsgroup(s).