From: Michael Tretter <m.tretter@pengutronix.de>
To: Felipe Balbi <balbi@kernel.org>
Cc: Thomas Haemmerle <thomas.haemmerle@wolfvision.net>,
laurent.pinchart@ideasonboard.com, gregkh@linuxfoundation.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: Thu, 11 Feb 2021 16:04:45 +0100 [thread overview]
Message-ID: <20210211150445.GM30300@pengutronix.de> (raw)
In-Reply-To: <87pn261h4c.fsf@kernel.org>
On Fri, 15 Jan 2021 15:09:39 +0200, Felipe Balbi wrote:
> Thomas Haemmerle <thomas.haemmerle@wolfvision.net> writes:
> > 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>
>
> Laurent, do you agree with the change?
Gentle ping.
Michael
next prev parent reply other threads:[~2021-02-11 15:19 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
2021-01-15 13:09 ` Felipe Balbi
2021-02-11 15:04 ` Michael Tretter [this message]
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=20210211150445.GM30300@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).