CONFIG_USB_ZERO: Gadget Zero (DEVELOPMENT)

General informations

The Linux kernel configuration item CONFIG_USB_ZERO has multiple definitions:

Gadget Zero (DEVELOPMENT) found in drivers/usb/gadget/legacy/Kconfig

The configuration item CONFIG_USB_ZERO:

• prompt: Gadget Zero (DEVELOPMENT)
• type: tristate
• depends on: (none)
• defined in drivers/usb/gadget/legacy/Kconfig
• found in Linux kernels: 3.17–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD
• modules built: g_zero, g_zero

Help text

Gadget Zero is a two-configuration device. It either sinks and sources bulk data; or it loops back a configurable number of transfers. It also implements control requests, for "chapter 9" conformance. The driver needs only two bulk-capable endpoints, so it can work on top of most device-side usb controllers. It's useful for testing, and is also a working example showing how USB "gadget drivers" can be written.

Make this be the first driver you try using on top of any new USB peripheral controller driver. Then you can use host-side test software, like the "usbtest" driver, to put your hardware and its driver through a basic set of functional tests.

Gadget Zero also works with the host-side "usb-skeleton" driver, and with many kinds of host-side test software. You may need to tweak product and vendor IDs before host software knows about this device, and arrange to select an appropriate configuration.

Say "y" to link the driver statically, or "m" to build a dynamically linked module called "g_zero".

Gadget Zero (DEVELOPMENT) found in drivers/usb/gadget/Kconfig

The configuration item CONFIG_USB_ZERO:

• prompt: Gadget Zero (DEVELOPMENT)
• type: tristate
• depends on: (none)
• defined in drivers/usb/gadget/Kconfig
• found in Linux kernels: 2.5.70–2.5.75, 2.6.0–2.6.39, 3.0–3.16
• modules built: g_zero, g_zero

Help text

Gadget Zero is a two-configuration device. It either sinks and sources bulk data; or it loops back a configurable number of transfers. It also implements control requests, for "chapter 9" conformance. The driver needs only two bulk-capable endpoints, so it can work on top of most device-side usb controllers. It's useful for testing, and is also a working example showing how USB "gadget drivers" can be written.

Make this be the first driver you try using on top of any new USB peripheral controller driver. Then you can use host-side test software, like the "usbtest" driver, to put your hardware and its driver through a basic set of functional tests.

Gadget Zero also works with the host-side "usb-skeleton" driver, and with many kinds of host-side test software. You may need to tweak product and vendor IDs before host software knows about this device, and arrange to select an appropriate configuration.

Say "y" to link the driver statically, or "m" to build a dynamically linked module called "g_zero".

Hardware

LKDDb

Raw data from LKDDb:

• lkddb module g_zero CONFIG_USB_ZERO : drivers/usb/gadget/Kconfig : "Gadget Zero (DEVELOPMENT)" # in 2.5.70–2.5.75, 2.6.0–2.6.39, 3.0–3.16
• lkddb module g_zero CONFIG_USB_ZERO : drivers/usb/gadget/legacy/Kconfig : "Gadget Zero (DEVELOPMENT)" # in 3.17–3.19, 4.0–4.20, 5.0–5.19, 6.0–6.8, 6.9-rc+HEAD

Sources

This page is automaticly generated with free (libre, open) software lkddb(see lkddb-sources).

The data is retrived from:

• Linux kernel
• Linux Kernel Driver DataBase (LKDDb)

Automatic links from Google (and ads)

Custom Search

Popular queries: