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>
Subject: Re: [PATCH v3 0/1] iio: bmi323: have the peripheral consume less power
Date: Mon, 26 Aug 2024 23:00:10 +0200 [thread overview]
Message-ID: <1a8adbc3-e8b3-4133-a2dd-449d584d8e8d@gmail.com> (raw)
In-Reply-To: <20240826114129.71f417c5@jic23-huawei>
On 26/08/24 12:41, Jonathan Cameron wrote:
> On Sat, 24 Aug 2024 16:11:21 +0200
> Denis Benato <benato.denis96@gmail.com> wrote:
>
>> 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.
>>
> For future reference, don't send new versions of a patch series
> in reply to previous version. It's a good way to ensure your
> code does not get reviewed as busy maintainers and reviewers
> tend to start with latest threads and this style means
> your patch ends up way off the top of the screen!
>
> I don't know if other subsystems specifically ask for this style
> of reply, but the ones that I interact with all specifically ask
> people to not do what you have here.
>
> Jonathan
>
Hello Jonathan,
Thanks for the heads up! I didn't know and now I do.
Thanks for your time, patience and guidance.
Best regards,
Denis
>> 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(-)
>>
>
prev parent reply other threads:[~2024-08-26 21:00 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 ` [PATCH v3 0/1] iio: bmi323: have the peripheral consume less power Denis Benato
2024-08-24 14:11 ` [PATCH v3 1/1] iio: bmi323: peripheral in lowest power state on suspend 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 [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=1a8adbc3-e8b3-4133-a2dd-449d584d8e8d@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