From: Michael Tretter <m.tretter@pengutronix.de>
To: Thomas Haemmerle <thomas.haemmerle@wolfvision.net>,
laurent.pinchart@ideasonboard.com, gregkh@linuxfoundation.org,
balbi@kernel.org, hverkuil@xs4all.nl, linux-usb@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [PATCH v4] usb: gadget: uvc: fix multiple opens
Date: Fri, 15 Jan 2021 13:55:46 +0100 [thread overview]
Message-ID: <20210115125546.GC30739@pengutronix.de> (raw)
In-Reply-To: <20201207085310.GD1553@pengutronix.de>
On Mon, 07 Dec 2020 09:53:10 +0100, Michael Tretter wrote:
> On Tue, 01 Dec 2020 20:27:30 +0100, Thomas Haemmerle wrote:
> > Currently, the UVC function is activated when open on the corresponding
> > v4l2 device is called.
> > On another open the activation of the function fails since the
> > deactivation counter in `usb_function_activate` equals 0. However the
> > error is not returned to userspace since the open of the v4l2 device is
> > successful.
> >
> > On a close the function is deactivated (since deactivation counter still
> > equals 0) and the video is disabled in `uvc_v4l2_release`, although the
> > UVC application potentially is streaming.
> >
> > Move activation of UVC function to subscription on UVC_EVENT_SETUP
> > because there we can guarantee for a userspace application utilizing
> > UVC.
> > Block subscription on UVC_EVENT_SETUP while another application already
> > is subscribed to it, indicated by `bool func_connected` in
> > `struct uvc_device`.
> > Extend the `struct uvc_file_handle` with member `bool is_uvc_app_handle`
> > to tag it as the handle used by the userspace UVC application.
> >
> > With this a process is able to check capabilities of the v4l2 device
> > without deactivating the function for the actual UVC application.
> >
> > Signed-off-by: Thomas Haemmerle <thomas.haemmerle@wolfvision.net>
>
> While I agree that this driver overall could really use some love, this patch
> at least fixes the driver for user space applications that scan for v4l2
> devices.
>
> Reviewed-By: Michael Tretter <m.tretter@pengutronix.de>
Ping.
Is there anything missing for getting this patch merged?
Michael
>
> > ---
> > v4:
> > - remove unnecessary inner parentheses
> > - keep and use the local video variable in `uvc_v4l2_release()`
> >
> > v3:
> > - replace `unsigned int connections` with `bool func_connected`
> > - rename `bool connected` to `bool is_uvc_app_handle`
> >
> > v2:
> > - fix deadlock in `uvc_v4l2_unsubscribe_event()` (mutex is already
> > locked in v4l2-core) introduced in v1
> > - lock mutex in `uvc_v4l2_release()` to suppress ioctls and protect
> > connected
> >
> > drivers/usb/gadget/function/uvc.h | 2 ++
> > drivers/usb/gadget/function/uvc_v4l2.c | 49 ++++++++++++++++++++++----
> > 2 files changed, 44 insertions(+), 7 deletions(-)
> >
> > diff --git a/drivers/usb/gadget/function/uvc.h b/drivers/usb/gadget/function/uvc.h
> > index 23ee25383c1f..893aaa70f81a 100644
> > --- a/drivers/usb/gadget/function/uvc.h
> > +++ b/drivers/usb/gadget/function/uvc.h
> > @@ -117,6 +117,7 @@ struct uvc_device {
> > enum uvc_state state;
> > struct usb_function func;
> > struct uvc_video video;
> > + bool func_connected;
> >
> > /* Descriptors */
> > struct {
> > @@ -147,6 +148,7 @@ static inline struct uvc_device *to_uvc(struct usb_function *f)
> > struct uvc_file_handle {
> > struct v4l2_fh vfh;
> > struct uvc_video *device;
> > + bool is_uvc_app_handle;
> > };
> >
> > #define to_uvc_file_handle(handle) \
> > diff --git a/drivers/usb/gadget/function/uvc_v4l2.c b/drivers/usb/gadget/function/uvc_v4l2.c
> > index 4ca89eab6159..197c26f7aec6 100644
> > --- a/drivers/usb/gadget/function/uvc_v4l2.c
> > +++ b/drivers/usb/gadget/function/uvc_v4l2.c
> > @@ -227,17 +227,55 @@ static int
> > uvc_v4l2_subscribe_event(struct v4l2_fh *fh,
> > const struct v4l2_event_subscription *sub)
> > {
> > + struct uvc_device *uvc = video_get_drvdata(fh->vdev);
> > + struct uvc_file_handle *handle = to_uvc_file_handle(fh);
> > + int ret;
> > +
> > if (sub->type < UVC_EVENT_FIRST || sub->type > UVC_EVENT_LAST)
> > return -EINVAL;
> >
> > - return v4l2_event_subscribe(fh, sub, 2, NULL);
> > + if (sub->type == UVC_EVENT_SETUP && uvc->func_connected)
> > + return -EBUSY;
> > +
> > + ret = v4l2_event_subscribe(fh, sub, 2, NULL);
> > + if (ret < 0)
> > + return ret;
> > +
> > + if (sub->type == UVC_EVENT_SETUP) {
> > + uvc->func_connected = true;
> > + handle->is_uvc_app_handle = true;
> > + uvc_function_connect(uvc);
> > + }
> > +
> > + return 0;
> > +}
> > +
> > +static void uvc_v4l2_disable(struct uvc_device *uvc)
> > +{
> > + uvc->func_connected = false;
> > + uvc_function_disconnect(uvc);
> > + uvcg_video_enable(&uvc->video, 0);
> > + uvcg_free_buffers(&uvc->video.queue);
> > }
> >
> > static int
> > uvc_v4l2_unsubscribe_event(struct v4l2_fh *fh,
> > const struct v4l2_event_subscription *sub)
> > {
> > - return v4l2_event_unsubscribe(fh, sub);
> > + struct uvc_device *uvc = video_get_drvdata(fh->vdev);
> > + struct uvc_file_handle *handle = to_uvc_file_handle(fh);
> > + int ret;
> > +
> > + ret = v4l2_event_unsubscribe(fh, sub);
> > + if (ret < 0)
> > + return ret;
> > +
> > + if (sub->type == UVC_EVENT_SETUP && handle->is_uvc_app_handle) {
> > + uvc_v4l2_disable(uvc);
> > + handle->is_uvc_app_handle = false;
> > + }
> > +
> > + return 0;
> > }
> >
> > static long
> > @@ -292,7 +330,6 @@ uvc_v4l2_open(struct file *file)
> > handle->device = &uvc->video;
> > file->private_data = &handle->vfh;
> >
> > - uvc_function_connect(uvc);
> > return 0;
> > }
> >
> > @@ -304,11 +341,9 @@ uvc_v4l2_release(struct file *file)
> > struct uvc_file_handle *handle = to_uvc_file_handle(file->private_data);
> > struct uvc_video *video = handle->device;
> >
> > - uvc_function_disconnect(uvc);
> > -
> > mutex_lock(&video->mutex);
> > - uvcg_video_enable(video, 0);
> > - uvcg_free_buffers(&video->queue);
> > + if (handle->is_uvc_app_handle)
> > + uvc_v4l2_disable(uvc);
> > mutex_unlock(&video->mutex);
> >
> > file->private_data = NULL;
> > --
> > 2.25.1
> >
> >
>
next prev parent reply other threads:[~2021-01-15 12:56 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 10:31 [PATCH] usb: gadget: uvc: fix multiple opens thomas.haemmerle
2020-11-05 10:37 ` Greg KH
2020-11-09 8:59 ` [PATCH v2] " thomas.haemmerle
2020-11-10 8:25 ` thomas.haemmerle
2020-11-10 8:40 ` Greg KH
2020-11-10 9:56 ` Thomas Hämmerle
2020-11-10 10:06 ` Greg KH
2020-11-10 14:30 ` [PATCH v3] " thomas.haemmerle
2020-11-13 13:36 ` Greg KH
2020-11-16 15:48 ` Laurent Pinchart
2020-11-21 12:50 ` Thomas Hämmerle
2020-12-01 19:27 ` [PATCH v4] " Thomas Haemmerle
2020-12-07 8:53 ` Michael Tretter
2021-01-15 12:55 ` Michael Tretter [this message]
2021-01-15 13:09 ` Felipe Balbi
2021-02-11 15:04 ` Michael Tretter
2021-10-03 20:13 ` [RESEND PATCH " Michael Grzeschik
2021-10-04 23:53 ` Laurent Pinchart
2021-10-05 10:59 ` Greg KH
2021-10-05 11:06 ` Felipe Balbi
2021-10-05 11:37 ` Greg KH
2021-10-04 23:55 ` [PATCH v3] " Laurent Pinchart
2020-11-10 10:31 ` [PATCH v2] " Hans Verkuil
2020-11-10 11:53 ` Thomas Hämmerle
2020-11-10 14:43 ` Hans Verkuil
2020-11-10 15:10 ` Thomas Hämmerle
2020-11-10 15:36 ` Hans Verkuil
2020-11-10 15:50 ` Thomas Hämmerle
2020-11-10 16:01 ` Hans Verkuil
2020-11-16 15:31 ` Laurent Pinchart
2020-11-16 15:48 ` Hans Verkuil
2020-11-16 15:50 ` 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=20210115125546.GC30739@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=thomas.haemmerle@wolfvision.net \
/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).