djlasas.blogg.se

Usb xhci compliant host controller code 43
Usb xhci compliant host controller code 43






  1. #Usb xhci compliant host controller code 43 driver
  2. #Usb xhci compliant host controller code 43 archive
  3. #Usb xhci compliant host controller code 43 Patch

Usb: cdns3: Change file names for cdns3 driver.

#Usb xhci compliant host controller code 43 driver

Usb: cdnsp: Add tracepoints for CDNSP driver Usb: cdnsp: cdns3 Add main part of Cadence USBSSP DRD Driver Usb: cdnsp: Device side header file for CDNSP driver Usb: cdns3: Changed type of gadget_dev in cdns structure

usb xhci compliant host controller code 43

Usb: cdns3: Refactoring names in reusable code Usb: cdns3: Moves reusable code to separate module Usb: cdns3: Split core.c into cdns3-plat and core.c file some less improtant changes sugested by Chunfeng Yun added cdns3 prefixes to file related with USBSS driver removed duplicate code from cdnsp_ep0_set_config function moved cdnsp driver files to cdns3 as sugested by Peter Chan updated common code to latest cdns3 driver

#Usb xhci compliant host controller code 43 Patch

The patch 10: Adds USBSSP DRD IP driver entry to MAINTAINERS file. The patch 9: Adds cdns3 prefixes to files related with USBSS driver. Header file for driver, 7 is the main part that implements allįunctionality of driver and 8 introduces tracepoints. In my opinion such division should notĪffect understanding and reviewing the driver, and cause that The patches 6-8: add the main part of driver and has been intentionally The patch 5: adopts gadget_dev pointer in cdns structure to make possible The patch 4: changes prefixes in reusable code from cdns3 to common cdns. The patch 3: moves reusable code to separate module. The patch 2: separates common code that can be reusable by cdnsp driver. Is USBSSP but it's to generic so I've decided to use CDNSP. The last letter of this acronym means PLUS.

usb xhci compliant host controller code 43

The prefix cdnsp used in driver has chosen by analogy to cdn3 driver. This controller and driver support Full Speed, Hight Speed, Supper Speed The architecture for device side is almost the same as for host side,Īnd most of the XHCI specification can be used to understand how The device side of USBSS DRD controller is compliant with XHCI.

usb xhci compliant host controller code 43

Specification, so it works with standard XHCI Linux driver. The host side of USBSS-DRD controller is compliance with XHCI We have supportįor PCIe bus, which is used on FPGA prototyping. The current driver has been validated with FPGA burned. The Cadence USBSS DRD Controller is a highly configurable IP Core whichĬan be instantiated as Dual-Role Device (DRD), Peripheral Only and This patch introduce new Cadence USBSS DRD driver to linux kernel. ` (10 more replies) 0 siblings, 11 replies 25+ messages in threadįrom: Pawel Laszczak 11:42 UTC ( / raw)Ĭc: gregkh, linux-usb, linux-kernel, balbi, colin.king, rogerq, 11:42 ` usb: cdns3: Add support for DRD CDNSP Pawel Laszczak

#Usb xhci compliant host controller code 43 archive

LKML Archive on help / color / mirror / Atom feed * Introduced new Cadence USBSSP DRD Driver. Introduced new Cadence USBSSP DRD Driver.








Usb xhci compliant host controller code 43