Some UVC commands require additional data (non zero uvc->event_length).
Add usb_ep_queue() call, so uvc_function_ep0_complete() can be called
and send received data to the userspace.
Signed-off-by: Petr Cvek
---
drivers/usb/gadget/function/f_uvc.c | 7 +++
1 file changed, 7 insertions(+)
di
On Thu, 2016-08-04 at 13:44 -0400, Robert Foss wrote:
>
> On 2016-08-03 06:39 AM, Oliver Neukum wrote:
> > On Tue, 2016-08-02 at 10:37 -0400, Robert Foss wrote:
> > How can that depend on what we return to user space?
> > In the driver we can continue just ignoring errors.
> > Now, if user space
On Sun, 7 Aug 2016, ican realizeum wrote:
> Hey, I tried to send this to list but I didn't have Plain text mode(in
> gmail) so it bounced back, resending now below, however meanwhile I
> made a bug report for it too:
> https://bugzilla.kernel.org/show_bug.cgi?id=151641
> Thanks.
> ---
> Here's a s
On Sun, Aug 7, 2016 at 6:49 PM, Alan Stern wrote:
> On Sun, 7 Aug 2016, ican realizeum wrote:
>
>> Hey, I tried to send this to list but I didn't have Plain text mode(in
>> gmail) so it bounced back, resending now below, however meanwhile I
>> made a bug report for it too:
>> https://bugzilla.kern
Hi
We are working on a project where a user-space application (a device
emulator) creates a USB device on the host machine (thus allowing the
emulated device to emulate a USB slave and to act as a usb dongle on the
host machine).
We have done this using usbip so far, but we'd rather do it directly
On Sun, 7 Aug 2016, ican realizeum wrote:
> > This doesn't seem like anything you need to worry about. If it only
> > happens on shutdown or reboot then it won't affect your use of the
> > computer.
> Cool!
> So, apparently something(?) is turning off something(as in power
> off/suspend?), so tha
Hi!
> > With these boards, you will not see anything on the screen that is
> > attached to a Type-C connector until the OS has booted to the point
> > where it has negotiated the power contract and entered a mode.
> >
> > If the system has BIOS/FW/EC capable of negotiating the power contract
> >
udriver struct allocated by kzalloc() will not be freed
if usb_register() and next calls fail. This patch fixes this
by adding one more step with kfree(udriver) in error path.
Cc: Alan Stern
Signed-off-by: Alexey Klimov
---
drivers/usb/serial/usb-serial.c | 4 +++-
1 file changed, 3 insertions(
On Mon, 8 Aug 2016, Alexey Klimov wrote:
> udriver struct allocated by kzalloc() will not be freed
> if usb_register() and next calls fail. This patch fixes this
> by adding one more step with kfree(udriver) in error path.
>
> Cc: Alan Stern
> Signed-off-by: Alexey Klimov
> ---
> drivers/usb/s
On Sat, Aug 06, 2016 at 02:00:08PM +0200, Oscar wrote:
> El 2016-08-02 05:30, Peter Chen escribió:
> >Hi all,
> >
> >This is a follow-up for my last power sequence framework patch set
> >[1].
> >According to Rob Herring and Ulf Hansson's comments[2], I use a
> >generic
> >power sequence library for
10 matches
Mail list logo
