From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: Greg KH <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
balbi@kernel.org, paul.elder@ideasonboard.com,
kernel@pengutronix.de, nicolas@ndufresne.ca,
kieran.bingham@ideasonboard.com
Subject: Re: [PATCH v2 0/4] usb: gadget: uvc: parse configfs entries and implement v4l2 enum api calls
Date: Tue, 6 Dec 2022 23:30:48 +0200 [thread overview]
Message-ID: <Y4+0iK460LL0dKPE@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20221206170721.GB15222@pengutronix.de>
Hi Michael,
On Tue, Dec 06, 2022 at 06:07:21PM +0100, Michael Grzeschik wrote:
> On Mon, Dec 05, 2022 at 11:17:15PM +0200, Laurent Pinchart wrote:
> >On Sun, Dec 04, 2022 at 09:29:16AM +0100, Greg KH wrote:
> >> On Sat, Dec 03, 2022 at 11:26:14PM +0200, Laurent Pinchart wrote:
> >> > On Sat, Sep 10, 2022 at 12:13:31AM +0200, Michael Grzeschik wrote:
> >> > > This series improves the uvc video gadget by parsing the configfs
> >> > > entries. With the configfs data, the userspace now is able to use simple
> >> > > v4l2 api calls like enum and try_format to check for valid configurations
> >> > > initially set by configfs.
> >> >
> >> > I've realized that this whole series got merged, despite my multiple
> >> > attempts to explain why I think it's not a good idea. The UVC gadget
> >> > requires userspace support, and there's no point in trying to move all
> >> > these things to the kernel side. It only bloats the kernel, makes the
> >> > code more complex, more difficult to maintain, and will make UVC 1.5
> >> > support more difficult.
> >>
> >> I can easily revert them, but I did not see any objections to them
> >> originally and so I merged them as is the normal method :)
> >
> > I don't think a revert is needed. The issue I pointed out regarding the
> > duplication of static const data can be solved on top. The API additions
> > from this series are, in my opinion, not a good idea for the reasons I
> > explained, but they don't hurt so much that we need to go nuclear on
> > this.
> >
> > Michael, will you be addressing the static const data issue ?
>
> Yes. I will also move the uvc_fmts[] array and uvc_format_by_guid to its
> own compile unit.
Thank you.
> I will go with drivers/media/usb/uvc.c
>
> While at it the headerfile will better also be moved from
> include/media/v4l2-uvc.h to linux/usb/uvc.h.
Works for me, especially for the GUIDs. For the structure and function
prototype, I don't mind using include/media/, up to you.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2022-12-06 21:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 22:13 [PATCH v2 0/4] usb: gadget: uvc: parse configfs entries and implement v4l2 enum api calls Michael Grzeschik
2022-09-09 22:13 ` [PATCH v2 1/4] media: v4l: move helper functions for fractions from uvc to v4l2-common Michael Grzeschik
2022-09-09 22:13 ` [PATCH v2 2/4] media: uvcvideo: move uvc_format_desc to common header Michael Grzeschik
2022-12-03 21:19 ` Laurent Pinchart
2022-09-09 22:13 ` [PATCH v2 3/4] usb: gadget: uvc: add v4l2 enumeration api calls Michael Grzeschik
2022-09-09 22:13 ` [PATCH v2 4/4] usb: gadget: uvc: add v4l2 try_format api call Michael Grzeschik
2022-12-03 21:26 ` [PATCH v2 0/4] usb: gadget: uvc: parse configfs entries and implement v4l2 enum api calls Laurent Pinchart
2022-12-03 21:46 ` Michael Grzeschik
2022-12-04 8:29 ` Greg KH
2022-12-05 21:17 ` Laurent Pinchart
2022-12-06 17:07 ` Michael Grzeschik
2022-12-06 18:20 ` Ricardo Ribalda
2022-12-06 21:30 ` Laurent Pinchart [this message]
2025-05-12 10:19 ` Krzysztof Opasiak
2025-05-12 10:38 ` Greg KH
2025-05-12 10:43 ` Krzysztof Opasiak
2025-05-12 21:03 ` Krzysztof Opasiak
2025-05-13 5:04 ` Greg KH
2025-05-13 10:04 ` Nicolas Dufresne
2025-05-13 10:31 ` Krzysztof Opasiak
2025-05-13 12:46 ` Nicolas Dufresne
2025-05-13 12:55 ` Michael Grzeschik
2025-05-13 13:07 ` Krzysztof Opasiak
2025-05-13 13:35 ` Michael Grzeschik
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=Y4+0iK460LL0dKPE@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kernel@pengutronix.de \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgr@pengutronix.de \
--cc=nicolas@ndufresne.ca \
--cc=paul.elder@ideasonboard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.