devu-dcd-usbumass-mx8-ci.so
Driver for the USB device (peripheral) controller on NXP i.MX8 boards for mass storage devices
Syntax:
io-usb-otg -d dcd-usbumass-mx8-ci [option[,option ...]]
or
io-usb-otg -d usbumass-mx8-ci [option[,option ...]]
Runs on:
QNX OS
Targets:
aarchle64
Options:
- fullspeed
- Force the device controller into full speed.
- ioport=addr
- Register the base address of the USB controller. The default is to scan the PCI bus.
- irq=num
- The interrupt request number.
- linkup
- Enables the target to be detected as the device controller driver is loaded. This option asserts "SOFT-CONNECT".
- linkdown
- The link must be manually enabled once the USB subsystem is ready. This option de-asserts the "SOFT-CONNECT". This is the default option.
- memory=name
- Set typed memory name for descriptors. The default is /memory/below4G.
- ser=serstring
- Override the serial string descriptor with the specified serstring. When you use this option, it overrides the default serial number for this driver, which is 123456789ABC.
- verbose=num
- Set the verbosity level (0-7).
Description:
This is the device-side controller driver for USBUMASS (USB Mass Storage driver).
You can't run the devu-hcd-ehci-mx28.so driver as a host controller and the devu-dcd-usbumass-mx8-ci.so as a device controller at the same time. If you've run devu-hcd-ehci-mx28.so as a host controller, you must first slay the io-usb-otg instance associated with the host controller before you start devu-dcd-usbumass-mx8-ci.so as the device controller.
Examples:
Attach to the controller by specifying the I/O port and IRQ.
io-usb-otg -d dcd-usbumass-mx8-ci ioport=0x5B0D0000,irq=299
If you are already running an instance of io-usb-otg with the
default resource manager path (e.g., /dev/usb/io-usb-otg),
you must use the -n option to specify a different resource manager path.
io-usb-otg -d dcd-usbumass-mx8-ci ioport=0x5B0D0000,irq=299
-n /dev/otg/io-usb-otg
Page updated: