The USB mass storage driver is used to communicate with mass storage devices such as flash drives, external hard drives, and other types of removable media connected through USB. The USB mass storage driver is split into two parts.
The block device implements BlockImplQuery, and BlockImplQueue. It supports read and write operations, but flush is not implemented. If power is lost after a write operation, changes written to a USB mass storage device may not be persisted to the device.The driver has no mechanism to inform drivers higher up in the stack of when a write has actually been written to physical media. For the purposes of USB mass storage, a write is considered complete when the device acknowledges the write.
The core device serves as the interface between the block device and the USB stack. The core accepts requests from the block device, and converts them into USB requests which are eventually sent to hardware through the USB stack. For each request, the following steps are performed:
- Request is added to a queue.
- Request is picked up by the worker thread.
- Request is encoded as a SCSI command and sent to the device.
- Request status is read back from the device.
- Completion callback is invoked, informing the block device layer that the request has been completed.
Some USB mass storage devices may have multiple block devices such as an array of disks. In this case, the core driver creates one block device per disk.
Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.
Last updated 2019-12-18.