mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Iron Berrington <berringtoni36@gmail.com>
Cc: "Andy Shevchenko" <andriy.shevchenko@intel.com>,
	"Nuno Sá" <nuno.sa@analog.com>,
	"Michael Hennerich" <Michael.Hennerich@analog.com>,
	"David Lechner" <dlechner@baylibre.com>,
	"Andy Shevchenko" <andy@kernel.org>,
	linux@analog.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 RESEND] iio: accel: adxl345: update period cache after successful write
Date: Sat, 24 Oct 2026 03:43:51 +0100	[thread overview]
Message-ID: <20261024034351.5d1be9c6@jic23-hlaptop> (raw)
In-Reply-To: <CAF2O-sPB3ggqwEA1LXsrA=tCpZGJMdx8KAXLXrW7RcaEk9y1iA@mail.gmail.com>

On Mon, 19 Oct 2026 07:53:28 -0500
Iron Berrington <berringtoni36@gmail.com> wrote:

> Hi Andy,
> 
> Thanks for the review and the Reviewed-by tag. I'll address the
> time-unit constants in a separate cleanup patch, keeping this fix
> focused on updating the cache after successful writes.
> 
Applied.
> Best regards,
> Wenqiang
> 
> 
> On Mon, 19 Oct 2026 13:21:44 +0300, Andy Shevchenko
> <andriy.shevchenko@intel.com> wrote:
> > On Sun, Oct 18, 2026 at 09:42:00PM +0800, Wenqiang Zhao via B4 Relay wrote:
> >  
> > > The ADXL345 event-period read path returns st->inact_time_ms. The setters
> > > for inactivity, free-fall and the ODR-derived default currently update
> > > this cache before writing TIME_INACT or TIME_FF. If the regmap write
> > > fails, the sysfs write reports an error but a subsequent read returns
> > > the requested period even though it was not programmed.
> > >
> > > Update the cached period only after the corresponding regmap write
> > > succeeds.  
> >
> > Reviewed-by: Andy Shevchenko <andriy.shevchenko@intel.com>
> > Assuming that my comments may lead to a separate cleanup patch later on.
> >
> > --
> > With Best Regards,
> > Andy Shevchenko  


      reply	other threads:[~2026-10-24  2:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 13:42 Wenqiang Zhao via B4 Relay
2026-10-19 10:13 ` Andy Shevchenko
2026-10-19 10:21 ` Andy Shevchenko
2026-10-19 12:53   ` Iron Berrington
2026-10-24  2:43     ` 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=20261024034351.5d1be9c6@jic23-hlaptop \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=andriy.shevchenko@intel.com \
    --cc=andy@kernel.org \
    --cc=berringtoni36@gmail.com \
    --cc=dlechner@baylibre.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@analog.com \
    --cc=nuno.sa@analog.com \
    /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®