Linux USB Device Driver Tutorial Part-1 - Basics

-
The USB System architecture consists of three main components:

  • USB Host
  • One or more USB Devices
  • A physical bus represented by USB cable that connects devices with the host computer

USB Host is in charge of asking each and every USB device, if it has any data to send. A USB device can never start sending data without first being asked to by the host controller.

 Which devices needs a Linux USB Driver and which do not?

USB Protocol specification define a set of standards that any device of a specific type can follow. If a device follows that standard, then a special driver for that device is not necessary. These different types are called classes (e.g. storage devices, keyboards, mice, joysticks, network devices and modems). Other type of devices that do not fit into these classes require a special vendor-specific driver to be written for that specific device.

USB Gadget Driver vs USB Host Driver:

 USB Host: Driver running on the host (desktop for example) controlling the USB devices that are plugged into it.

USB Gadget: Driver running on the device controlling how the device looks to the host computer as a USB device.

Decoding a USB Device:

All valid USB devices contain one or more configurations. A configuration of a USB Device is like a profile, where the default one is the commonly used one. Linux only supports one configuration per device.

Each and every configuration can have multiple interfaces. You can assume interface as a feature or functionality of the device.
E.g. Mouse, Keyboard or audio interface.

Number of interfaces = Number of independent functionalities provided by the device.

E.g. Multifunction USB Printer can do printing, scanning, faxing then it would likely have three interfaces - one for each of the functionality.

USB Speaker might consists of two interfaces : USB  audio stream, and USB keyboard for the button interface.

Each and every USB Interface needs a special USB Driver. So, a single USB Device can have multiple USB device drivers. It is common to have a single USB device driver handle all the interfaces of the USB device.

Each and every interface has multiple endpoints. Endpoint is like a pipe carrying information from the host computer to device (OUT endpoint) or from the device to the host computer (IN endpoint). Depending on the type of the information, the endpoints have four types:

  • Control
  • Interrupt
  • Bulk
  • Isochronous
As per USB Standard, all valid USB Devices will have control endpoint zero. This is a bi-directional endpoint

Comments

  1. Munish Bhardwaj16 February 2021 at 22:00

    Hi, thanks for the article.

    Can you please help in this error :

    Accessory sent USB HOST HID COMPONENT with Interface Number 3, But not matching HID interface was seeing during USB enumeration.

    Can you please Tell How to get correct Interface Number at time of USB enumeration.

    ReplyDelete
  2. Eddam Stephen19 February 2021 at 22:37

    this is a very nice post and very informative, thanks alot for sharing keep it up..
    Best Linux Shared Hosting in USA

    ReplyDelete

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

make config vs oldconfig vs defconfig vs menuconfig vs savedefconfig

-
Image
Building the Linux Kernel is a two-step process: Configuring the Kernel options Building the Kernel with those options. There are many methods available for configuring the kernel. make config: Text-based Configuration.  Options are prompted one after another. All options need to be answered Access to former options is not possible make menuconfig: Menu-driven user interface Allows to navigate forwards and backward directly between features Allows to load and save files with filenames different from ".config" Provides search feature It uses ncurses library for GUI. If the ncurses library is not installed, make menuconfig option fails. To install ncurses library on Ubuntu: sudo apt-get install libncurses5-dev make defconfig: Creates a ".config" file with default options from the ARCH supplied defconfig Configurations are generally stored in the directory: arch/$(ARCH)/configs $ ls arch/x86/configs/ i386_defconfi
Read more