From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Michael Grzeschik <mgr@pengutronix.de>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-usb@vger.kernel.org, linux-media@vger.kernel.org,
Andrzej Pietrasiewicz <andrzej.p@samsung.com>
Subject: Re: [PATCH 2/2] usb: gadget: f_uvc: Move to video_ioctl2
Date: Wed, 20 Aug 2014 19:04:16 +0200 [thread overview]
Message-ID: <1727644.isLCCA1H9e@avalon> (raw)
In-Reply-To: <20140820075510.GA10389@pengutronix.de>
Hi Michael,
On Wednesday 20 August 2014 09:55:10 Michael Grzeschik wrote:
> On Mon, Aug 18, 2014 at 11:16:36PM +0200, Laurent Pinchart wrote:
> > On Monday 18 August 2014 18:24:26 Hans Verkuil wrote:
> > > On 08/18/2014 05:06 PM, Laurent Pinchart wrote:
> > > > Simplify ioctl handling by using video_ioctl2.
> > >
> > > Are you able to test this on actual hardware? And if so, can you run
> > > v4l2-compliance?
> >
> > I'm afraid not. I don't have a platform with an up and running USB
> > peripheral controller at the moment.
>
> You could test it with dummy_hcd gadget on an virtual or non usb machine.
Thank you for pointing this out.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2014-08-20 17:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 17:06 [PATCH 0/2] Move UVC gagdet to video_ioctl2 Laurent Pinchart
2014-08-18 17:06 ` [PATCH 1/2] usb: gadget: f_uvc: Store EP0 control request state during setup stage Laurent Pinchart
2014-08-18 17:06 ` [PATCH 2/2] usb: gadget: f_uvc: Move to video_ioctl2 Laurent Pinchart
2014-08-18 18:24 ` Hans Verkuil
2014-08-18 21:16 ` Laurent Pinchart
2014-08-20 7:55 ` Michael Grzeschik
2014-08-20 17:04 ` Laurent Pinchart [this message]
2014-08-27 15:16 ` [PATCH] usb: gadget: f_uvc fix transition " Andrzej Pietrasiewicz
2014-08-28 11:28 ` Laurent Pinchart
2014-08-28 14:39 ` Andrzej Pietrasiewicz
2014-08-28 14:48 ` Felipe Balbi
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=1727644.isLCCA1H9e@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=andrzej.p@samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mgr@pengutronix.de \
/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).