From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-sunxi@lists.linux.dev,
Eugen Hristev <eugen.hristev@collabora.com>,
Maxime Ripard <mripard@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Kieran Bingham <kieran.bingham@ideasonboard.com>,
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Subject: Re: [PATCH 4/8] media: v4l2-subdev: Refactor warnings in v4l2_subdev_link_validate()
Date: Tue, 25 Jun 2024 17:02:47 +0300 [thread overview]
Message-ID: <20240625140247.GC30459@pendragon.ideasonboard.com> (raw)
In-Reply-To: <ZncAJRoydaWoxGRj@valkosipuli.retiisi.eu>
On Sat, Jun 22, 2024 at 04:47:33PM +0000, Sakari Ailus wrote:
> Hi Laurent,
>
> Thanks for the patch.
>
> On Wed, Jun 19, 2024 at 04:23:52AM +0300, Laurent Pinchart wrote:
> > The v4l2_subdev_link_validate() function prints a one-time warning if it
> > gets called on a link whose source or sink is not a subdev. As links get
> > validated in the context of their sink, a call to the helper when the
> > link's sink is not a subdev indicates that the driver has set its
> > .link_validate() handler to v4l2_subdev_link_validate() on a non-subdev
> > entity, which is a clear driver bug. On the other hand, the link's
> > source not being a subdev indicates that the helper is used for a subdev
> > connected to a video output device, which is a lesser issue, if only
> > because this is currently common practice.
> >
> > There are no drivers left in the kernel that use
> > v4l2_subdev_link_validate() in a context where it may get called on a
> > non-subdev sink. Replace the pr_warn_once() with a WARN_ON() in this
> > case to make sure that new offenders won't be introduced.
> >
> > Signed-off-by: Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
> > ---
> > drivers/media/v4l2-core/v4l2-subdev.c | 14 +++++++++-----
> > 1 file changed, 9 insertions(+), 5 deletions(-)
> >
> > diff --git a/drivers/media/v4l2-core/v4l2-subdev.c b/drivers/media/v4l2-core/v4l2-subdev.c
> > index 4f71199bf592..2d5e39c79620 100644
> > --- a/drivers/media/v4l2-core/v4l2-subdev.c
> > +++ b/drivers/media/v4l2-core/v4l2-subdev.c
> > @@ -1451,11 +1451,15 @@ int v4l2_subdev_link_validate(struct media_link *link)
> > bool states_locked;
> > int ret;
> >
> > - if (!is_media_entity_v4l2_subdev(link->sink->entity) ||
> > - !is_media_entity_v4l2_subdev(link->source->entity)) {
> > - pr_warn_once("%s of link '%s':%u->'%s':%u is not a V4L2 sub-device, driver bug!\n",
> > - !is_media_entity_v4l2_subdev(link->sink->entity) ?
> > - "sink" : "source",
> > + /*
> > + * Links are validated in the context of the sink entity. Usage of this
> > + * helper on a sink that is not a subdev is a clear driver bug.
> > + */
> > + if (WARN_ON(!is_media_entity_v4l2_subdev(link->sink->entity)))
> > + return -EINVAL;
>
> WARN*() is nowadays deprecated.
Why so ? I've followed a recent discussion where some people pointed out
they disliked WARN*() due to panic-on-warn, but I didn't see any
conclusion there that deprecated WARN*().
> Could you continue to use pr_warn_once()
> for this (or dev_warn_one())?
I think a WARN_ON() is the right option here. A failure indicates a
clear driver bug, we should be as loud as possible to make sure it gets
noticed during development.
> > +
> > + if (!is_media_entity_v4l2_subdev(link->source->entity)) {
> > + pr_warn_once("source of link '%s':%u->'%s':%u is not a V4L2 sub-device, driver bug!\n",
> > link->source->entity->name, link->source->index,
> > link->sink->entity->name, link->sink->index);
> > return 0;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2024-06-25 14:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-19 1:23 [PATCH 0/8] media: v4l2: Improve media link validation Laurent Pinchart
2024-06-19 1:23 ` [PATCH 1/8] media: microchip-isc: Drop v4l2_subdev_link_validate() for video devices Laurent Pinchart
2024-06-19 1:23 ` [PATCH 2/8] media: sun4i_csi: Implement link validate for sun4i_csi subdev Laurent Pinchart
2024-06-22 15:03 ` Chen-Yu Tsai
2024-06-22 16:44 ` Sakari Ailus
2024-06-25 21:09 ` Laurent Pinchart
2024-06-25 21:49 ` Sakari Ailus
2024-06-26 5:50 ` Laurent Pinchart
2024-06-19 1:23 ` [PATCH 3/8] media: sun4i_csi: Don't use v4l2_subdev_link_validate() for video device Laurent Pinchart
2024-06-22 15:04 ` Chen-Yu Tsai
2024-06-19 1:23 ` [PATCH 4/8] media: v4l2-subdev: Refactor warnings in v4l2_subdev_link_validate() Laurent Pinchart
2024-06-22 16:47 ` Sakari Ailus
2024-06-25 14:02 ` Laurent Pinchart [this message]
2024-06-25 15:46 ` Sakari Ailus
2024-06-25 15:54 ` Laurent Pinchart
2024-06-19 1:23 ` [PATCH 5/8] media: v4l2-subdev: Support hybrid links " Laurent Pinchart
2024-06-19 1:23 ` [PATCH 6/8] media: renesas: vsp1: Print debug message to diagnose validation failure Laurent Pinchart
2024-06-19 1:23 ` [PATCH 7/8] media: renesas: vsp1: Implement .link_validate() for video devices Laurent Pinchart
2024-06-19 1:23 ` [PATCH 8/8] [DNI] media: renesas: vsp1: Validate all links through .link_validate() Laurent Pinchart
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=20240625140247.GC30459@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=eugen.hristev@collabora.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mripard@kernel.org \
--cc=sakari.ailus@iki.fi \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wens@csie.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