8c6a54ca0a
Display tearing functionality on SXR devices makes use of both bulk-in and bulk-out endpoints of cdev driver to acquire real time audio/video data from usb host. Currently if the userspace application making use of cdev driver requests 50KB of data from host, the cdev_read function queues multiple usb requests to host till it gets 50KB of data. In Display Tearing, although the userspace application requests 50KB of data per frame, the actual amount sent by host for every frame is variable and can be less than the requested amount. If host is sending packets of size less that requested amount per frame, driver ends up appending multiple frames in a single cdev_read call and returns corrupt information to userspace causing low frame rate on display. To resolve this add a configfs property to specify the buffer size for every usb request on out ep and a flag to specify if we need single packet mode. If single packet mode is enabled, only one usb request is queued on out endpoint per cdev_read call and buffer corresponding to that request contains only one frame of data coming from host. The driver appends data from one usb request in read_queued pool to userspace buffer to avoid corrupting video frame information. CRs-Fixed: 3038067 Change-Id: I1ba0b954d14f187eeddc511f4ac199784248b33b Signed-off-by: Ligui Deng <ldeng@codeaurora.org> |
||
---|---|---|
.. | ||
atm | ||
c67x00 | ||
chipidea | ||
class | ||
common | ||
core | ||
dwc2 | ||
dwc3 | ||
early | ||
gadget | ||
host | ||
image | ||
isp1760 | ||
misc | ||
mon | ||
mtu3 | ||
musb | ||
pd | ||
phy | ||
renesas_usbhs | ||
roles | ||
serial | ||
storage | ||
typec | ||
usbip | ||
wusbcore | ||
Kconfig | ||
Makefile | ||
README | ||
usb-skeleton.c |
To understand all the Linux-USB framework, you'll use these resources: * This source code. This is necessarily an evolving work, and includes kerneldoc that should help you get a current overview. ("make pdfdocs", and then look at "usb.pdf" for host side and "gadget.pdf" for peripheral side.) Also, Documentation/usb has more information. * The USB 2.0 specification (from www.usb.org), with supplements such as those for USB OTG and the various device classes. The USB specification has a good overview chapter, and USB peripherals conform to the widely known "Chapter 9". * Chip specifications for USB controllers. Examples include host controllers (on PCs, servers, and more); peripheral controllers (in devices with Linux firmware, like printers or cell phones); and hard-wired peripherals like Ethernet adapters. * Specifications for other protocols implemented by USB peripheral functions. Some are vendor-specific; others are vendor-neutral but just standardized outside of the www.usb.org team. Here is a list of what each subdirectory here is, and what is contained in them. core/ - This is for the core USB host code, including the usbfs files and the hub class driver ("hub_wq"). host/ - This is for USB host controller drivers. This includes UHCI, OHCI, EHCI, and others that might be used with more specialized "embedded" systems. gadget/ - This is for USB peripheral controller drivers and the various gadget drivers which talk to them. Individual USB driver directories. A new driver should be added to the first subdirectory in the list below that it fits into. image/ - This is for still image drivers, like scanners or digital cameras. ../input/ - This is for any driver that uses the input subsystem, like keyboard, mice, touchscreens, tablets, etc. ../media/ - This is for multimedia drivers, like video cameras, radios, and any other drivers that talk to the v4l subsystem. ../net/ - This is for network drivers. serial/ - This is for USB to serial drivers. storage/ - This is for USB mass-storage drivers. class/ - This is for all USB device drivers that do not fit into any of the above categories, and work for a range of USB Class specified devices. misc/ - This is for all USB device drivers that do not fit into any of the above categories.