From: Pranjal Shrivastava <praan@google.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Will Deacon <will@kernel.org>,
Robin Murphy <robin.murphy@arm.com>,
Joerg Roedel <joro@8bytes.org>, Jason Gunthorpe <jgg@ziepe.ca>,
Rob Clark <robdclark@chromium.org>,
Georgi Djakov <quic_c_gdjako@quicinc.com>,
linux-arm-kernel@lists.infradead.org, iommu@lists.linux.dev
Subject: Re: [PATCH 22/51] iommu/arm-smmu: Switch to __pm_runtime_put_autosuspend()
Date: Thu, 10 Oct 2024 15:33:11 +0000 [thread overview]
Message-ID: <ZwfztwoGAcvyvlWL@google.com> (raw)
In-Reply-To: <20241004094123.113725-1-sakari.ailus@linux.intel.com>
On Fri, Oct 04, 2024 at 12:41:23PM +0300, Sakari Ailus wrote:
> pm_runtime_put_autosuspend() will soon be changed to include a call to
> pm_runtime_mark_last_busy(). This patch switches the current users to
> __pm_runtime_put_autosuspend() which will continue to have the
> functionality of old pm_runtime_put_autosuspend().
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> drivers/iommu/arm/arm-smmu/arm-smmu.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iommu/arm/arm-smmu/arm-smmu.c b/drivers/iommu/arm/arm-smmu/arm-smmu.c
> index 8321962b3714..cad02d5dc6d2 100644
> --- a/drivers/iommu/arm/arm-smmu/arm-smmu.c
> +++ b/drivers/iommu/arm/arm-smmu/arm-smmu.c
> @@ -79,7 +79,7 @@ static inline int arm_smmu_rpm_get(struct arm_smmu_device *smmu)
> static inline void arm_smmu_rpm_put(struct arm_smmu_device *smmu)
> {
> if (pm_runtime_enabled(smmu->dev))
> - pm_runtime_put_autosuspend(smmu->dev);
> + __pm_runtime_put_autosuspend(smmu->dev);
> }
Seems like a straightforward change as a result of [1].
Although, I had a few things to discuss:
1. The `rpm_resume` in drivers/base/power/runtime.c seems to call
`pm_runtime_mark_last_busy` in case the ->runtime_resume callback
returned successfully. In such a case, why would we want to move
`pm_runtime_mark_last_busy` within `pm_runtime_put_autosuspend` ?
2. In the arm-smmu driver, we seem to rely on the rpm_resume to call
`pm_runtime_mark_last_busy` as a part of the ->runtime_resume callback.
The only other case, where we might wanna `*mark_last_busy` is if we
want the autosuspend timer to be re-started in case of a failed suspend.
However, the `arm_smmu_runtime_suspend` doesn't return errno in any case
hence, I don't see any other case where we'd benefit from using
`mark_last_busy` in the arm-smmu driver.
On the other hand, I don't see a problem with using it either :)
Any thoughts Will/Rob/Robin?
>
> static void arm_smmu_rpm_use_autosuspend(struct arm_smmu_device *smmu)
> --
> 2.39.5
>
Apart from the above discussion, for this patch alone:
Reviewed-by: Pranjal Shrivastava <praan@google.com>
Thanks,
Pranjal
[1]
https://lore.kernel.org/all/20240109133639.111210-1-sakari.ailus@linux.intel.com/
next prev parent reply other threads:[~2024-10-10 15:33 UTC|newest]
Thread overview: 122+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 9:41 [PATCH 00/51] treewide: Switch to __pm_runtime_put_autosuspend() Sakari Ailus
2024-10-04 9:41 ` Sakari Ailus
2024-10-04 9:41 ` Sakari Ailus
2024-10-04 9:41 ` Sakari Ailus
2024-10-04 9:41 ` [PATCH 05/51] clk: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 02/51] bluetooth: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 01/51] accel/ivpu: " Sakari Ailus
2024-10-04 9:51 ` Jacek Lawrynowicz
2024-10-04 9:41 ` [PATCH 03/51] bus: sunxi-rsb: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 04/51] hwrng: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 08/51] gpio: " Sakari Ailus
2024-10-04 9:55 ` Bartosz Golaszewski
2024-10-04 10:08 ` Sakari Ailus
2024-10-04 9:41 ` [PATCH 07/51] dmaengine: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 06/51] crypto: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 09/51] drm/amd: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 12/51] drm/panfrost: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 11/51] drm/radeon: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 10/51] drm/nouveau: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 13/51] drivers: drm: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 15/51] stm class: " Sakari Ailus
2024-10-24 10:59 ` Alexander Shishkin
2024-10-04 9:41 ` [PATCH 16/51] i2c: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 18/51] i3c: dw: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 17/51] i3c: master: svc: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 14/51] HSI: omap_ssi_port: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 23/51] irqchip/imx-irqsteer: " Sakari Ailus
2024-10-06 19:52 ` Thomas Gleixner
2024-10-04 9:41 ` [PATCH 22/51] iommu/arm-smmu: " Sakari Ailus
2024-10-10 15:33 ` Pranjal Shrivastava [this message]
2024-10-23 16:48 ` Will Deacon
2024-10-24 15:26 ` Pranjal Shrivastava
2024-10-04 9:41 ` [PATCH 20/51] Input: omap4-keypad: " Sakari Ailus
2024-10-04 9:55 ` Andreas Kemnade
2024-10-04 10:26 ` Sakari Ailus
2024-10-04 10:54 ` Andreas Kemnade
2024-10-04 11:08 ` Dmitry Torokhov
2024-10-04 9:41 ` [PATCH 24/51] mailbox: mtk-cmdq-mailbox: " Sakari Ailus
2024-10-07 14:27 ` Matthias Brugger
2024-10-04 9:41 ` [PATCH 19/51] iio: " Sakari Ailus
2024-10-04 13:45 ` Jonathan Cameron
2024-10-04 9:41 ` [PATCH 25/51] media: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 21/51] Input: cs40l50: " Sakari Ailus
2024-10-04 11:09 ` Dmitry Torokhov
2024-10-04 9:41 ` [PATCH 30/51] net: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 26/51] mfd: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 28/51] mmc: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 27/51] mei: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 29/51] mtd: rawnand: gpmi: " Sakari Ailus
2024-10-04 11:12 ` Miquel Raynal
2024-10-04 9:41 ` [PATCH 31/51] nfc: trf7970a: " Sakari Ailus
2024-10-04 14:05 ` Krzysztof Kozlowski
2024-10-04 9:41 ` [PATCH 32/51] PCI/portdrv: " Sakari Ailus
2024-10-04 9:45 ` Ilpo Järvinen
2024-10-04 9:41 ` [PATCH 33/51] phy: motorola: phy-mapphone-mdm6600: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 35/51] power: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 34/51] phy: ti: phy-twl4030-usb: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 36/51] pwm: img: " Sakari Ailus
2024-10-04 12:38 ` Uwe Kleine-König
2024-10-04 9:41 ` [PATCH 37/51] regulator: stm32-vrefbuf: " Sakari Ailus
2024-10-04 11:34 ` Mark Brown
2024-10-04 9:41 ` [PATCH 39/51] slimbus: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 42/51] staging: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 41/51] spi: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 38/51] remoteproc: omap: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 40/51] soundwire: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 45/51] usb: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 43/51] thunderbolt: " Sakari Ailus
2024-10-04 10:07 ` Mika Westerberg
2024-10-04 9:41 ` [PATCH 49/51] ASoC: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 48/51] ALSA: hda: " Sakari Ailus
2024-10-04 10:56 ` Takashi Iwai
2024-10-04 23:57 ` Mark Brown
2024-10-04 9:41 ` [PATCH 46/51] w1: omap-hdq: " Sakari Ailus
2024-10-04 14:05 ` Krzysztof Kozlowski
2024-10-04 9:41 ` [PATCH 44/51] serial: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 51/51] soc: apple: mailbox: " Sakari Ailus
2024-10-04 9:41 ` [PATCH 50/51] ALSA: intel_hdmi: " Sakari Ailus
2024-10-04 14:38 ` [PATCH 00/51] treewide: " Ulf Hansson
2024-10-04 14:38 ` Ulf Hansson
2024-10-04 14:38 ` Ulf Hansson
2024-10-04 14:38 ` Ulf Hansson
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 18:49 ` Laurent Pinchart
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:08 ` Ulf Hansson
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:25 ` Laurent Pinchart
2024-10-07 22:34 ` Ulf Hansson
2024-10-07 22:34 ` Ulf Hansson
2024-10-07 22:34 ` Ulf Hansson
2024-10-07 22:34 ` Ulf Hansson
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-08 18:24 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:20 ` Rafael J. Wysocki
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 10:27 ` Ulf Hansson
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 12:48 ` Richard Fitzgerald
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-09 13:34 ` Rafael J. Wysocki
2024-10-08 20:38 ` Uwe Kleine-König
2024-10-08 20:38 ` Uwe Kleine-König
2024-10-08 20:38 ` Uwe Kleine-König
2024-10-08 20:38 ` Uwe Kleine-König
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=ZwfztwoGAcvyvlWL@google.com \
--to=praan@google.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=quic_c_gdjako@quicinc.com \
--cc=robdclark@chromium.org \
--cc=robin.murphy@arm.com \
--cc=sakari.ailus@linux.intel.com \
--cc=will@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.