• Introduction to USB
• USB Gadget API
• Existing Gadgets
• Design your own Gadget
• Demo
• Conclusio

• Linux, Android
• Main activities:

• Focused on USB not general driver development
• Nothing on the host side

• Using a generic embedded device, see how we cancreate a USB Gadget

• How to fulfill every need

• Industry standard developed in the mid-1990s
• Defines the cables, connectors and protocols used forconnection, communication and power supplybetween computers and electronic devices
• 2 billion USB devices were sold each year (as of 2008)

• Replace lots of old buses
• Automatic configuration
• Multiple speeds
• Reliable

• Distance
• Peer-To-Peer
• Broadcasting

• Master-Slave protocol
• Up to 127 devices addressable
• Can be hot-plugged
• Identification to the host
• Supports high speeds
• Supports high speeds

• Source and Sink of data
• Uniquely identifiable
• Unique direction (except setup)

• Control
  Configuration and control information
• Interrupt
  Small quantities time-sensitive data
• Bulk
  Large quantities time-insensitive data
• Isochronous
  Real-time data at predictable bit rates

• Device Firmware Driver
  • Hardware specific routines
  • USB interrupts/events

• Chapter 9
  • Enumeration process
  • Transfer data to upper layer

• USB Class Driver
  • Defines the behavior
  • Provides configuration

• Provides essential infrastructure
• Similar to Chapter 9 in typical USB device software
• Handles USB protocol specific requirements
• Flexible enough to expose more complex USB devicecapabilities

• Similarities
  • Share common definitions for the standard USB messages,structures and constants
  • Use queues of request objects to package I/O buffers
  • Both APIs bind and unbind drivers to devices

• Differences
  • Control transfers
  • Configuration management

• handling setup requests (ep0 protocol responses)possibly including class-specific functionality
• returning configuration and string descriptors
• (re)setting configurations and interface alternate settings, including enabling and configuring endpoints
• handling life cycle events, such as managing bindingsto hardware, USB suspend/resume, remote wakeup,and disconnection from the USB host
• managing IN and OUT transfers on all currentlyenabled endpoints

• user mode code, using generic (gadgetfs) or applicationspecific files in /dev
• networking subsystem (for network gadgets, like theCDC Ethernet Model gadget driver)
• data capture drivers, perhaps video4Linux or a scannerdriver; or test and measurement hardware
• input subsystem (for HID gadgets)
• sound subsystem (for audio gadgets)
• file system (for PTP gadgets)
• block i/o subsystem (for usb-storage gadgets)

• probe_driver / unregister_driver
• set_selfpowered / clear_selfpowered
• vbus_connect / vbus_disconnect
• connect / disconnect
• frame_number

• autoconf / autoconf_reset
• enable / disable
• alloc / free
• queue / dequeue
• set_halt / clear_halt
• fifo_status / fifo_flush

• usb_descriptor_fillbuf
• usb_gadget_config_buf

• Register driver for a particular device controller
• Register gadget driver (bind)
• Hardware powered, enumeration starts
• Gadget driver returns descriptors (setup)
• Gadget driver returns interfaces configuration
• Do real work (data transfer) until disconnect
• Gadget driver unloaded (unbind)

• Enumerate to the host as an Ethernet device
• Can easily be bridging, routing, or firewalling access to other networks
• Interoperability with hosts running Linux, MS Windows among others
• Possibility to set parameters such as MAC address,IP configuration or DHCP use thanks to the bootargs if using a boot firmware like U-Boot

• Provides User-Mode API
• Each endpoint presented as single I/O file descriptor
• Normal read() and write() calls
• Async I/O supported
• Configuration and descriptors written into files

• Implements the USB Mass Storage Class
• Up to 8 disk drives can be set
• Store file or block device is called the “backing storage”
• Backing storage requires preparation
  • If a file is used, it must created with its desired size before launching the driver
  • If a block device, it must match host requirements (DOS partition for MS-Windows host)
• The backing storage must not change while FBS is running, only the host should access it

• Acts as a composite USB Audio and Video Class device
• Provides a user space API to process UVC control requests and stream video data

• Useful for TTY style operation
• Supports a CDC-ACM module option

• Exposes an ALSA MIDI interface
• Both recording and playback support

• Useful to test device controller driver
• Helps verify that the driver stack pass USB-IF (forUSB branding)
• On the host side, useful to test USB stack

• Hardware
• Functional
• Endpoints

• First implement the register/unregister functions
  • usb_gadget_probe_driver
    • Resgistration of the usb_gadget_driver
    • Responsible for binding the gadget driver and powering upthe device
  • usb_gadget_unregister_driver
    • Responsible for unbinding the gadget from the functionaldriver and powering down the device

• Then define callbacks hardware related
  • Fill usb_ep_ops and usb_gadget_ops
  • Not necessary to support all functions

• Implement the control request handles (ep0)
  • Gadget driver handles only a part of it
  • The rest is routed to the class driver

• Power Management requests
  • Comes from the PDC to the Gadget
  • The Gadget must pass the events to the class driver

• Once enumeration is done, class driver requests usb_request structure for IN/OUT transfers
  • Gadget receives data in interrupt routine (OUT)    
    • Only when the expected amount is received the Gadgetcalls the complete function
  • Gadget sends data to the PDC (IN)
    • Wait send completion to inform the class driver

• ARM™ Cortex™-A8 1000 MHz
• USB connectivity:
  • 4 host ports
  • 1 OTG port (used as device)

• Bootloader
  • U-boot 2011.12 r4
• Kernel
  •  3.0.17 r115c   
• Root filesystem
  • Console image
    • Custom recipe (lighttpd)
  • Additional modules

• Easy to implement
• Hardware independent
• Scalability
• Large panel of existing gadgets
• Awareness of limitations

• Linux-USB Gadget API Framework: Generalpresentation. 
  Linux-USB Gadget API Framework
• USB Gadget API for Linux: Full description of the API.
  https://archive.kernel.org/oldlinux/htmldocs/gadget/index.html
• Essential Linux Device Drivers (SreekrishnanVenkateswaran) : General device driver bookcontaining a useful USB section.
• Bootstrap Yourself with Linux-USB Stack (RajaramRegupathy): Very detailed and easy-to-read book aboutLinux-USB.

• USB Raw Gadget — The Linux Kernel documentation
• USB Gadget API for Linux — The Linux Kernel documentation (Current newest version docs)