From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: laurent.pinchart@ideasonboard.com, prabhakar.csengg@gmail.com,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Tomi Valkeinen" <tomi.valkeinen@ideasonboard.com>,
"Paweł Anikiel" <panikiel@google.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: v4l2-subdev: Refactor events
Date: Sun, 20 Oct 2024 10:45:59 +0000 [thread overview]
Message-ID: <ZxTfZ1GOMdOmrmTt@kekkonen.localdomain> (raw)
In-Reply-To: <ZxQtlwVZ9JfIM8tl@tom-HP-ZBook-Fury-15-G7-Mobile-Workstation>
Hi Tommaso,
On Sun, Oct 20, 2024 at 12:07:19AM +0200, Tommaso Merciai wrote:
> Hi Sakari,
>
> On Fri, Oct 18, 2024 at 07:30:30PM +0000, Sakari Ailus wrote:
> > Hi Tommaso,
> >
> > Thanks for working on this.
>
> In real it's a Laurent's suggestion :)
>
> >
> > On Fri, Oct 18, 2024 at 07:11:03PM +0200, Tommaso Merciai wrote:
> > > Controls can be exposed to userspace via a v4l-subdevX device, and
> > > userspace has to be able to subscribe to control events so that it is
> > > notified when the control changes value.
> > > If a control handler is set for the subdev then set the HAS_EVENTS
> > > flag automatically into v4l2_subdev_init_finalize() and use
> > > v4l2_ctrl_subdev_subscribe_event() and v4l2_event_subdev_unsubscribe()
> > > as default if subdev don't have .(un)subscribe control operations.
> > >
> > > Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> > > ---
> > > drivers/media/v4l2-core/v4l2-subdev.c | 22 ++++++++++++++++++++--
> > > 1 file changed, 20 insertions(+), 2 deletions(-)
> > >
> > > diff --git a/drivers/media/v4l2-core/v4l2-subdev.c b/drivers/media/v4l2-core/v4l2-subdev.c
> > > index 3a4ba08810d2..77ca829b9983 100644
> > > --- a/drivers/media/v4l2-core/v4l2-subdev.c
> > > +++ b/drivers/media/v4l2-core/v4l2-subdev.c
> > > @@ -691,10 +691,25 @@ static long subdev_do_ioctl(struct file *file, unsigned int cmd, void *arg,
> > > return v4l2_event_dequeue(vfh, arg, file->f_flags & O_NONBLOCK);
> > >
> > > case VIDIOC_SUBSCRIBE_EVENT:
> > > - return v4l2_subdev_call(sd, core, subscribe_event, vfh, arg);
> > > + if (v4l2_subdev_has_op(sd, core, subscribe_event))
> > > + return v4l2_subdev_call(sd, core, subscribe_event,
> > > + vfh, arg);
> > > +
> > > + if ((sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS) &&
> > > + vfh->ctrl_handler)
> > > + return v4l2_ctrl_subdev_subscribe_event(sd, vfh, arg);
> > > +
> > > + return -ENOIOCTLCMD;
> >
> > While this mostly does the same thing, I prefer the order of tests below.
> > Could you align event subscription with unsubscription?
>
> What about:
>
> case VIDIOC_SUBSCRIBE_EVENT:
> if (!(sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS))
> return -ENOIOCTLCMD;
>
> if (v4l2_subdev_has_op(sd, core, subscribe_event))
> return v4l2_subdev_call(sd, core, subscribe_event,
> vfh, arg);
>
> if (!vfh->ctrl_handler)
> return -ENOTTY;
>
> return v4l2_ctrl_subdev_subscribe_event(sd, vfh, arg);
Oh, right. Actually the earlier unsubscription didn't always produce
correct results. I missed that. This is needlessly complicated at the
moment. So I'd do:
case VIDIOC_SUBSCRIBE_EVENT:
if (v4l2_subdev_has_op(sd, core, subscribe_event))
return v4l2_subdev_call(sd, core, subscribe_event,
vfh, arg);
return (sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS) &&
vfh->ctrl_handler ?
v4l2_ctrl_subdev_subscribe_event(sd, vfh, arg) :
-ENOIOCTLCMD;
case VIDIOC_UNSUBSCRIBE_EVENT:
if (v4l2_subdev_has_op(sd, core, unsubscribe_event))
return v4l2_subdev_call(sd, core, unsubscribe_event,
vfh, arg);
return sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS ?
v4l2_event_subdev_unsubscribe(sd, vfh, arg) :
-ENOIOCTLCMD;
>
> case VIDIOC_UNSUBSCRIBE_EVENT:
> if (!(sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS))
> return -ENOIOCTLCMD;
>
> if (v4l2_subdev_has_op(sd, core, unsubscribe_event))
> return v4l2_subdev_call(sd, core, unsubscribe_event,
> vfh, arg);
>
> return v4l2_event_subdev_unsubscribe(sd, vfh, arg);
>
> ?
>
> Thanks & Regards,
> Tommaso
>
> >
> > >
> > > case VIDIOC_UNSUBSCRIBE_EVENT:
> > > - return v4l2_subdev_call(sd, core, unsubscribe_event, vfh, arg);
> > > + if (!(sd->flags & V4L2_SUBDEV_FL_HAS_EVENTS))
> > > + return -ENOIOCTLCMD;
> > > +
> > > + if (v4l2_subdev_has_op(sd, core, unsubscribe_event))
> > > + return v4l2_subdev_call(sd, core, unsubscribe_event,
> > > + vfh, arg);
> > > +
> > > + return v4l2_event_subdev_unsubscribe(sd, vfh, arg);
> > >
> > > #ifdef CONFIG_VIDEO_ADV_DEBUG
> > > case VIDIOC_DBG_G_REGISTER:
> > > @@ -1641,6 +1656,9 @@ int __v4l2_subdev_init_finalize(struct v4l2_subdev *sd, const char *name,
> > > }
> > > }
> > >
> > > + if (sd->ctrl_handler)
> > > + sd->flags |= V4L2_SUBDEV_FL_HAS_EVENTS;
> > > +
> > > state = __v4l2_subdev_state_alloc(sd, name, key);
> > > if (IS_ERR(state))
> > > return PTR_ERR(state);
> >
> > --
> > Kind regards,
> >
> > Sakari Ailus
--
Sakari Ailus
next prev parent reply other threads:[~2024-10-20 10:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 17:11 Tommaso Merciai
2024-10-18 19:30 ` Sakari Ailus
2024-10-19 22:07 ` Tommaso Merciai
2024-10-20 10:45 ` Sakari Ailus [this message]
2024-10-20 15:46 ` 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=ZxTfZ1GOMdOmrmTt@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=panikiel@google.com \
--cc=prabhakar.csengg@gmail.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tomm.merciai@gmail.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®