From: Greg KH <gregkh@linuxfoundation.org>
To: Dan Scally <dan.scally@ideasonboard.com>
Cc: linux-usb@vger.kernel.org, laurent.pinchart@ideasonboard.com,
w36195@motorola.com, m.grzeschik@pengutronix.de,
kieran.bingham@ideasonboard.com, torleiv@huddly.com
Subject: Re: [PATCH v3 0/7] UVC Gadget: Extend color matching support
Date: Thu, 2 Feb 2023 11:29:44 +0100 [thread overview]
Message-ID: <Y9uQmDmuG5a3CCIJ@kroah.com> (raw)
In-Reply-To: <f1d817b8-ab8d-e69d-8a06-d860aabf07fc@ideasonboard.com>
On Thu, Feb 02, 2023 at 10:20:20AM +0000, Dan Scally wrote:
> Morning Greg
>
> On 02/02/2023 10:18, Greg KH wrote:
> > On Mon, Jan 30, 2023 at 02:26:32PM +0000, Daniel Scally wrote:
> > > The current UVC gadget implementation hardcodes a single color matching
> > > descriptor and includes it in the payload of USB descriptors a single time
> > > following all the format and frame descriptors. This is inflexible, and
> > > additionally applies only to the _last_ format in the array of descriptors.
> > >
> > > This series extends the support such that the default descriptor can be amended
> > > and is included once-per-format instead of once-only, it then adds the ability
> > > to create new color matching descriptors and associate them with particular formats.
> > > The default color matching descriptor is retained and used where the user does not
> > > link a new color matching descriptor to the format, so the default interaction
> > > with userspace is unchanged from the current implementation.
> > >
> > > Daniel Scally (7):
> > > usb: gadget: usb: Remove "default" from color matching attributes
> > > usb: uvc: Enumerate valid values for color matching
> > > usb: gadget: uvc: Add struct for color matching in configs
> > > usb: gadget: uvc: Copy color matching descriptor for each frame
> > > usb: gadget: uvc: Remove the hardcoded default color matching
> > > usb: gadget: uvc: Make color matching attributes read/write
> > > usb: gadget: uvc: Allow creating new color matching descriptors
> > >
> > > .../ABI/testing/configfs-usb-gadget-uvc | 19 +-
> > > drivers/usb/gadget/function/f_uvc.c | 9 -
> > > drivers/usb/gadget/function/u_uvc.h | 1 -
> > > drivers/usb/gadget/function/uvc_configfs.c | 282 ++++++++++++++++--
> > > drivers/usb/gadget/function/uvc_configfs.h | 22 +-
> > > include/uapi/linux/usb/video.h | 30 ++
> > > 6 files changed, 315 insertions(+), 48 deletions(-)
> > >
> > > --
> > > 2.34.1
> > >
> > This series does not apply against my tree at all, what was it made
> > against?
>
>
> I thought I had rebased it against usb-linus, was that the wrong branch to
> use? If not then I probably messed it up somehow, I can rebase and resend.
usb-linus is not the right branch for new features, please use usb-next.
Although for the next 24 hours, you should probably use usb-testing as
that has your other changes in it already, before I merge it into
usb-next.
thanks,
greg k-h
next prev parent reply other threads:[~2023-02-02 10:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 14:26 [PATCH v3 0/7] UVC Gadget: Extend color matching support Daniel Scally
2023-01-30 14:26 ` [PATCH v3 1/7] usb: gadget: usb: Remove "default" from color matching attributes Daniel Scally
2023-01-30 14:26 ` [PATCH v3 2/7] usb: uvc: Enumerate valid values for color matching Daniel Scally
2023-01-30 14:26 ` [PATCH v3 3/7] usb: gadget: uvc: Add struct for color matching in configs Daniel Scally
2023-01-30 14:26 ` [PATCH v3 4/7] usb: gadget: uvc: Copy color matching descriptor for each frame Daniel Scally
2023-01-30 14:26 ` [PATCH v3 5/7] usb: gadget: uvc: Remove the hardcoded default color matching Daniel Scally
2023-01-30 14:26 ` [PATCH v3 6/7] usb: gadget: uvc: Make color matching attributes read/write Daniel Scally
2023-01-30 14:26 ` [PATCH v3 7/7] usb: gadget: uvc: Allow creating new color matching descriptors Daniel Scally
2023-02-02 10:18 ` [PATCH v3 0/7] UVC Gadget: Extend color matching support Greg KH
2023-02-02 10:20 ` Dan Scally
2023-02-02 10:29 ` Greg KH [this message]
2023-02-02 10:33 ` Dan Scally
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=Y9uQmDmuG5a3CCIJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=dan.scally@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-usb@vger.kernel.org \
--cc=m.grzeschik@pengutronix.de \
--cc=torleiv@huddly.com \
--cc=w36195@motorola.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