From: Bjorn Helgaas <helgaas@kernel.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-pm@vger.kernel.org, "Rafael J. Wysocki" <rafael@kernel.org>,
linux-pci@vger.kernel.org, dri-devel@lists.freedesktop.org,
"Jaroslav Kysela" <perex@perex.cz>,
"Stanislaw Gruszka" <stanislaw.gruszka@linux.intel.com>,
laurent.pinchart@ideasonboard.com,
"David Airlie" <airlied@gmail.com>,
"Paul Elder" <paul.elder@ideasonboard.com>,
linux-media@vger.kernel.org,
"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
intel-gfx@lists.freedesktop.org,
"Lucas De Marchi" <lucas.demarchi@intel.com>,
"Mark Brown" <broonie@kernel.org>,
"Jacek Lawrynowicz" <jacek.lawrynowicz@linux.intel.com>,
"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
"Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
intel-xe@lists.freedesktop.org,
"Tvrtko Ursulin" <tvrtko.ursulin@linux.intel.com>,
"Alex Elder" <elder@kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-sound@vger.kernel.org, "Takashi Iwai" <tiwai@suse.com>,
"Daniel Vetter" <daniel@ffwll.ch>,
netdev@vger.kernel.org
Subject: Re: [PATCH v4 1/3] pm: runtime: Simplify pm_runtime_get_if_active() usage
Date: Tue, 23 Jan 2024 11:24:23 -0600 [thread overview]
Message-ID: <20240123172423.GA317147@bhelgaas> (raw)
In-Reply-To: <20240123095642.97303-2-sakari.ailus@linux.intel.com>
On Tue, Jan 23, 2024 at 11:56:42AM +0200, Sakari Ailus wrote:
> There are two ways to opportunistically increment a device's runtime PM
> usage count, calling either pm_runtime_get_if_active() or
> pm_runtime_get_if_in_use(). The former has an argument to tell whether to
> ignore the usage count or not, and the latter simply calls the former with
> ign_usage_count set to false. The other users that want to ignore the
> usage_count will have to explitly set that argument to true which is a bit
> cumbersome.
>
> To make this function more practical to use, remove the ign_usage_count
> argument from the function. The main implementation is renamed as
> pm_runtime_get_conditional().
>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> Reviewed-by: Alex Elder <elder@linaro.org> # drivers/net/ipa/ipa_smp2p.c
> Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Acked-by: Takashi Iwai <tiwai@suse.de> # sound/
> Reviewed-by: Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com> # drivers/accel/ivpu/
> Acked-by: Rodrigo Vivi <rodrigo.vivi@intel.com> # drivers/gpu/drm/i915/
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Acked-by: Bjorn Helgaas <bhelgaas@google.com> # drivers/pci/
- Previous PM history uses "PM: " in the subject lines (not "pm: ").
- I don't know whether it's feasible, but it would be nice if the
intel_pm_runtime_pm.c rework could be done in one shot instead of
being split between patches 1/3 and 2/3.
Maybe it could be a preliminary patch that uses the existing
if_active/if_in_use interfaces, followed by the trivial if_active
updates in this patch. I think that would make the history easier
to read than having the transitory pm_runtime_get_conditional() in
the middle.
- Similarly, it would be nice if pm_runtime_get_conditional() never
had to be published in pm_runtime.h, instead of being temporarily
added there by this patch and then immediately made private by 2/3.
Maybe that's not practical, I dunno.
Bjorn
next prev parent reply other threads:[~2024-01-23 17:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-23 9:56 [PATCH v4 0/3] Small runtime PM API changes Sakari Ailus
2024-01-23 9:56 ` [PATCH v4 1/3] pm: runtime: Simplify pm_runtime_get_if_active() usage Sakari Ailus
2024-01-23 17:24 ` Bjorn Helgaas [this message]
2024-01-23 20:44 ` Sakari Ailus
2024-01-23 21:48 ` Bjorn Helgaas
2024-01-23 22:40 ` Sakari Ailus
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=20240123172423.GA317147@bhelgaas \
--to=helgaas@kernel.org \
--cc=airlied@gmail.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=broonie@kernel.org \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=netdev@vger.kernel.org \
--cc=paul.elder@ideasonboard.com \
--cc=perex@perex.cz \
--cc=rafael@kernel.org \
--cc=rodrigo.vivi@intel.com \
--cc=sakari.ailus@linux.intel.com \
--cc=stanislaw.gruszka@linux.intel.com \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tiwai@suse.com \
--cc=tvrtko.ursulin@linux.intel.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;
as well as URLs for NNTP newsgroup(s).