From: Andy Shevchenko <andriy.shevchenko@intel.com>
To: berringtoni36@gmail.com
Cc: "Jonathan Cameron" <jic23@kernel.org>,
"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: Mon, 19 Oct 2026 13:13:37 +0300 [thread overview]
Message-ID: <atXtUSkBM0dBG80A@ashevche-desk.local> (raw)
In-Reply-To: <20261018-adxl345-period-cache-v2-resend-1@gmail.com>
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.
...
> /* Inactivity time in s */
> - return regmap_write(st->regmap, ADXL345_REG_TIME_INACT, val);
> + ret = regmap_write(st->regmap, ADXL345_REG_TIME_INACT, val);
> + if (ret)
> + return ret;
> +
> + st->inact_time_ms = MILLI * val;
While at it, replace MILLI with MSEC_PER_SEC (from time.h).
> + return 0;
...
> static int adxl345_set_inactivity_time(struct adxl345_state *st, u32 val_int)
> {
> + int ret;
> +
> + ret = regmap_write(st->regmap, ADXL345_REG_TIME_INACT, val_int);
> + if (ret)
> + return ret;
> +
> st->inact_time_ms = MILLI * val_int;
Ditto.
> - return regmap_write(st->regmap, ADXL345_REG_TIME_INACT, val_int);
> + return 0;
> }
...
> static int adxl345_set_freefall_time(struct adxl345_state *st, u32 val_fract)
> {
> + int ret;
> +
> /*
> * Datasheet max. value is 255 * 5000 us = 1.275000 seconds.
> *
> * Recommended values between 100ms and 350ms (0x14 to 0x46)
> */
> + ret = regmap_write(st->regmap, ADXL345_REG_TIME_FF,
> + DIV_ROUND_CLOSEST(val_fract, 5));
> + if (ret)
> + return ret;
> +
> st->inact_time_ms = DIV_ROUND_UP(val_fract, MILLI);
Hmm... Okay, since it's three instances and only one you actually touched
perhaps a separate patch.
> - return regmap_write(st->regmap, ADXL345_REG_TIME_FF,
> - DIV_ROUND_CLOSEST(val_fract, 5));
> + return 0;
> }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2026-10-19 10:13 UTC|newest]
Thread overview: 4+ 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 [this message]
2026-10-19 10:21 ` Andy Shevchenko
2026-10-19 12:53 ` Iron Berrington
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=atXtUSkBM0dBG80A@ashevche-desk.local \
--to=andriy.shevchenko@intel.com \
--cc=Michael.Hennerich@analog.com \
--cc=andy@kernel.org \
--cc=berringtoni36@gmail.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--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®