Want to retouch your photos? Are the photos ready?
We can do white background, sharpen, retouching included all for your
photos.
Unlimited revisions .
Send us a test photo, we will start it.
Thanks,
Sara
Want to retouch your photos? Are the photos ready?
We can do white background, sharpen, retouching included all for your
photos.
Unlimited revisions .
Send us a test photo, we will start it.
Thanks,
Sara
On Fri, Jan 18, 2019 at 11:52:57AM -0500, Alan Stern wrote:
> On Fri, 18 Jan 2019, Paul Elder wrote:
>
> > > > I meant the functions (procedures) in the function driver, so the setup
> > > > handler (uvc_function_setup), the completion handler
> > > > (uvc_function_ep0_complete), and the status se
On 1/19/19 9:58 AM, Sergei Shtylyov wrote:
Hello!
On 01/19/2019 12:29 AM, Shuah Khan wrote:
From: Shuah Khan
Fix vhci_urb_enqueue() to print error and return error instead of
failing with WARN_ON.
It's BUG_ON().
Thanks. I will fix it.
-- Shuah
Hi Felipe,
On 12/12/2018 3:43 PM, Minas Harutyunyan wrote:
> Initially resetting device address was done in USB RESET interrupt
> handler. In case, when power saving mode enabled (hibernation) USB
> RESET interrupt handled in dwc2_handle_gpwrdn_intr() and then it
> not seen in dwc2_hsotg_irq() han
A usb gadget function driver may or may not want to delay the status
stage of a control OUT request. An instance where it might want to is to
asynchronously validate the data of a class-specific request.
A function driver that wants an explicit status stage should set the
newly added explicit_stat
We now have a mechanism to signal the UDC driver to reply to a control
OUT request with STALL or ACK, and we have packaged the setup stage data
and the data stage data of a control OUT request into a single
UVC_EVENT_DATA for userspace to consume. After telling the UDC to delay
the status stage, th
This patch series adds a mechanism to allow asynchronously validating
the data stage of a control OUT request, and for stalling or suceeding
the request accordingly. This mechanism is implemented for MUSB, and is
used by UVC. At the same time, UVC packages the setup stage and data
stage data togeth
V4L2_EVENT_PRIVATE_START is used in g_uvc.h but is defined in
videodev2.h, which is not included and causes a compiler warning:
linux/usb/g_uvc.h:15:28: error: ‘V4L2_EVENT_PRIVATE_START’ undeclared here (not
in a function)
#define UVC_EVENT_FIRST (V4L2_EVENT_PRIVATE_START + 0)
Include videode
Currently, for uvc class-specific control IN and OUT requests, in the
setup handler a UVC_EVENT_SETUP with the setup control is enqueued to
userspace. In response to this, the uvc function driver expects
userspace to call ioctl UVCIOC_SEND_RESPONSE containing uvc request
data.
In the case of contr
Since "usb: gadget: uvc: enqueue uvc_request_data in setup handler
for control OUT requests" it is no longer necessary for userspace to
call ioctl UVCIOC_SEND_RESPONSE in response to receiving a
UVC_EVENT_SETUP from the uvc function driver for a control OUT request.
This change means that for cont
Implement the mechanism for optional explicit status stage for the MUSB
driver. This allows a function driver to specify what to reply for the
status stage. The functionality for an implicit status stage is
retained.
Signed-off-by: Paul Elder
v1 Reviewed-by: Laurent Pinchart
v1 Acked-by: Bin Liu
On Mon, Jan 21, 2019 at 11:13:01AM +0800, Yinbo Zhu wrote:
> From: yinbo.zhu
This should read:
From: Yinbo Zhu
right?
> USB erratum-A006918 workaround tries to start internal PHY inside
> uboot (when PLL fails to lock). However, if the workaround also
> fails, then USB initialization i
On Mon, Jan 21, 2019 at 11:13:00AM +0800, Yinbo Zhu wrote:
> From: Suresh Gupta
>
> PHY_CLK_VALID bit for UTMI PHY in USBDR does not set even
> if PHY is providing valid clock. Workaround for this
> involves resetting of PHY and check PHY_CLK_VALID bit
> multiple times. If PHY_CLK_VALID bit is st
14 matches
Mail list logo
