From: Claudiu Beznea <claudiu.beznea@tuxon.dev>
To: Jonathan Cameron <jic23@kernel.org>
Cc: prabhakar.mahadev-lad.rj@bp.renesas.com, dlechner@baylibre.com,
nuno.sa@analog.com, andy@kernel.org, linux-iio@vger.kernel.org,
linux-renesas-soc@vger.kernel.org, linux-kernel@vger.kernel.org,
Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>,
Ulf Hansson <ulf.hansson@linaro.org>
Subject: Re: [PATCH v5 1/2] iio: adc: rzg2l: Cleanup suspend/resume path
Date: Mon, 18 Aug 2025 08:54:17 +0300 [thread overview]
Message-ID: <b064e3cf-466b-49b9-a66d-399441e1913d@tuxon.dev> (raw)
In-Reply-To: <20250816145334.7a538a19@jic23-huawei>
On 16.08.2025 16:53, Jonathan Cameron wrote:
>> From: Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
>>
>> There is no need to manually track the runtime PM status in the driver.
>> The pm_runtime_force_suspend() and pm_runtime_force_resume() functions
>> already call pm_runtime_status_suspended() to check the runtime PM state.
>>
>> Additionally, avoid calling pm_runtime_put_autosuspend() during the
>> suspend/resume path, as this would decrease the usage counter of a
>> potential user that had the ADC open before the suspend/resume cycle.
>>
>> Fixes: cb164d7c1526 ("iio: adc: rzg2l_adc: Add suspend/resume support")
> That SHA isn't upstream. I think it should be.
> 563cf94f9329
You're right! Thank you for handling it.
next prev parent reply other threads:[~2025-08-18 5:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-10 12:33 [PATCH v5 0/2] iio: rzg2l_adc: Cleanups for rzg2l_adc driver Claudiu
2025-08-10 12:33 ` [PATCH v5 1/2] iio: adc: rzg2l: Cleanup suspend/resume path Claudiu
2025-08-16 13:53 ` Jonathan Cameron
2025-08-18 5:54 ` Claudiu Beznea [this message]
2025-08-10 12:33 ` [PATCH v5 2/2] iio: adc: rzg2l_adc: Set driver data before enabling runtime PM Claudiu
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=b064e3cf-466b-49b9-a66d-399441e1913d@tuxon.dev \
--to=claudiu.beznea@tuxon.dev \
--cc=andy@kernel.org \
--cc=claudiu.beznea.uj@bp.renesas.com \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=ulf.hansson@linaro.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
all inboxes | Powered by JetHome®