public inbox for linux-iio@vger.kernel.org
 help / color / mirror / Atom feed
From: Denis Benato <benato.denis96@gmail.com>
To: Jonathan Cameron <jic23@kernel.org>
Cc: Jagath Jog J <jagathjog1996@gmail.com>,
	Lars-Peter Clausen <lars@metafoo.de>,
	linux-iio@vger.kernel.org, linux-kernel@vger.kernel.org,
	"Luke D . Jones" <luke@ljones.dev>,
	Jonathan LoBue <jlobue10@gmail.com>,
	Denis Benato <benato.denis96@gmail.com>
Subject: [PATCH v3 0/1] iio: bmi323: have the peripheral consume less power
Date: Sat, 24 Aug 2024 16:11:21 +0200	[thread overview]
Message-ID: <20240824141122.334620-1-benato.denis96@gmail.com> (raw)
In-Reply-To: <20240823192921.7df291f8@jic23-huawei>

The bmi323 chip is part of handhelds PCs that are run on battery.

One of said PC is well-known for its short battery life, even in s2idle:
help mitigate that by putting the device in its lowest-consumption
state while the peripheral is unused.

Have runtime-pm suspend callback save used configuration registers
and runtime-pm resume callback restore saved registers to restore
the previous state.

Changelog:
- V2: patch 1:
	+ change patch commit message
	+ drop removal callbacks and use devm_add_action_or_reset
	+ split bmi323_init in two functions
	+ separate regs to save and relative value
	+ drop unhelpful consts ptr modifiers
	+ add a comment to explain why BMI323_FIFO_CTRL_REG is
	  being used in runtime resume
- V3: patch 1:
  + drop a struct array and replace with an array of
    unsigned int: u8 was too small and it would have resulted
    in overflow of register addresses
  + use single-line comments where possible
  + drop useless comments
  + remove intermediate variables
  + remove blank lines

Previous patches obsoleted:
https://lore.kernel.org/all/20240811161202.19818-1-benato.denis96@gmail.com
https://lore.kernel.org/all/20240818150923.20387-1-benato.denis96@gmail.com

Signed-off-by: Denis Benato <benato.denis96@gmail.com>

Denis Benato (1):
  iio: bmi323: peripheral in lowest power state on suspend

 drivers/iio/imu/bmi323/bmi323_core.c | 155 ++++++++++++++++++++++++++-
 1 file changed, 153 insertions(+), 2 deletions(-)

-- 
2.46.0


  reply	other threads:[~2024-08-24 14:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-11 16:12 [PATCH 0/1] iio: bmi323: have the peripheral consume less power Denis Benato
2024-08-11 16:12 ` [PATCH 1/1] iio: bmi323: peripheral in lowest power state on suspend Denis Benato
2024-08-17 12:49   ` Jonathan Cameron
2024-08-18 15:09     ` [PATCH v2 0/1] iio: bmi323: have the peripheral consume less power Denis Benato
2024-08-18 15:09       ` [PATCH v2] iio: bmi323: peripheral in lowest power state on suspend Denis Benato
2024-08-23 18:29         ` Jonathan Cameron
2024-08-24 14:11           ` Denis Benato [this message]
2024-08-24 14:11             ` [PATCH v3 1/1] " Denis Benato
2024-08-26 10:23               ` Jonathan Cameron
2024-08-26 10:41             ` [PATCH v3 0/1] iio: bmi323: have the peripheral consume less power Jonathan Cameron
2024-08-26 21:00               ` Denis Benato

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=20240824141122.334620-1-benato.denis96@gmail.com \
    --to=benato.denis96@gmail.com \
    --cc=jagathjog1996@gmail.com \
    --cc=jic23@kernel.org \
    --cc=jlobue10@gmail.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luke@ljones.dev \
    /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