From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
linux-media@vger.kernel.org, hans@jjverkuil.nl
Subject: Re: [PATCH 1/1] checkpatch: Deprecate V4L2 pipeline power management code
Date: Tue, 14 Jul 2026 11:15:15 +0300 [thread overview]
Message-ID: <20260714081515.GM1127719@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260713161327.3682-1-sakari.ailus@linux.intel.com>
Hi Sakari,
Thank you for the patch.
On Mon, Jul 13, 2026 at 07:13:27PM +0300, Sakari Ailus wrote:
> The V4L2 pipeline power management code, in particular
> v4l2_pipeline_link_notify(), v4l2_pipeline_pm_get() and
> v4l2_pipeline_pm_put() are deprecated and shall not be used in new code.
>
> The drivers need to use the Runtime PM instead.
I'll be happy to see this API go, so we certainly need to make sure no
new drivers use it.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
> ---
> scripts/checkpatch.pl | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl
> index 2b7a42bbdd94..a8a7374dc9c4 100755
> --- a/scripts/checkpatch.pl
> +++ b/scripts/checkpatch.pl
> @@ -879,6 +879,9 @@ our %deprecated_apis = (
> "DEFINE_IDR" => "DEFINE_XARRAY",
> "idr_init" => "xa_init",
> "idr_init_base" => "xa_init_flags",
> + "v4l2_pipeline_link_notify" => "",
> + "v4l2_pipeline_pm_get" => "",
> + "v4l2_pipeline_pm_put" => "",
> );
>
> #Create a search pattern for all these strings to speed up a loop below
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2026-07-14 8:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-13 16:13 Sakari Ailus
2026-07-14 8:15 ` Laurent Pinchart [this message]
2026-07-14 10:28 ` Joe Perches
2026-07-14 11:14 ` Sakari Ailus
2026-07-14 12:11 ` Joe Perches
2026-07-14 12:31 ` 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=20260714081515.GM1127719@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=apw@canonical.com \
--cc=hans@jjverkuil.nl \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@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
all inboxes | Powered by JetHome®