linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: Gwendal Grignou <gwendal@chromium.org>,
	andy.shevchenko@gmail.com, campello@chromium.org,
	lars@metafoo.de, linux-iio@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH] iio: sx9310: Fix write_.._debounce()
Date: Thu, 1 Apr 2021 14:21:45 +0100	[thread overview]
Message-ID: <20210401142145.5f92fac6@jic23-huawei> (raw)
In-Reply-To: <161722015839.2260335.4267819779077188735@swboyd.mtv.corp.google.com>

On Wed, 31 Mar 2021 12:49:18 -0700
Stephen Boyd <swboyd@chromium.org> wrote:

> Quoting Gwendal Grignou (2021-03-31 11:22:22)
> > Check input to be sure it matches Semtech sx9310 specification and
> > can fit into debounce register.
> > Compare argument writen to thresh_.._period with read from same
> > sysfs attribute:
> > 
> > Before:                   Afer:
> > write   |  read           write   |  read
> > -1      |     8           -1 fails: -EINVAL
> > 0       |     8           0       |     0
> > 1       |     0           1       |     0
> > 2..15   |  2^log2(N)      2..15   |  2^log2(N)
> > 16      |     0           >= 16 fails: -EINVAL
> > 
> > Fixes: 1b6872015f0b ("iio: sx9310: Support setting debounce values")
> > Signed-off-by: Gwendal Grignou <gwendal@chromium.org>
> > Cc: stable@vger.kernel.org
> > ---  
> 
> Reviewed-by: Stephen Boyd <swboyd@chromium.org>

Applied to the fixes-togreg branch of iio.git.

Thanks,

Jonathan



      reply	other threads:[~2021-04-01 18:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-31 18:22 [PATCH] iio: sx9310: Fix write_.._debounce() Gwendal Grignou
2021-03-31 19:49 ` Stephen Boyd
2021-04-01 13:21   ` 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=20210401142145.5f92fac6@jic23-huawei \
    --to=jic23@kernel.org \
    --cc=andy.shevchenko@gmail.com \
    --cc=campello@chromium.org \
    --cc=gwendal@chromium.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=stable@vger.kernel.org \
    --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).