summaryrefslogtreecommitdiff
path: root/nuttx/drivers/usbdev
diff options
context:
space:
mode:
authorGregory Nutt <gnutt@nuttx.org>2014-03-20 15:20:24 -0600
committerGregory Nutt <gnutt@nuttx.org>2014-03-20 15:20:24 -0600
commitec7904d89eb37a7ccb0ef130f2089206f185ebe5 (patch)
tree9fbe4e4e850e86075cf8da3ae73480696bc65536 /nuttx/drivers/usbdev
parent641ed1fd58895554a604c5314fff44330c9e9bf0 (diff)
downloadnuttx-ec7904d89eb37a7ccb0ef130f2089206f185ebe5.tar.gz
nuttx-ec7904d89eb37a7ccb0ef130f2089206f185ebe5.tar.bz2
nuttx-ec7904d89eb37a7ccb0ef130f2089206f185ebe5.zip
If DCD supports queuing of stall requests then USB MSC delay work-around is not necessary
Diffstat (limited to 'nuttx/drivers/usbdev')
-rw-r--r--nuttx/drivers/usbdev/Kconfig16
1 files changed, 16 insertions, 0 deletions
diff --git a/nuttx/drivers/usbdev/Kconfig b/nuttx/drivers/usbdev/Kconfig
index f512bd4a7..8da9d9e35 100644
--- a/nuttx/drivers/usbdev/Kconfig
+++ b/nuttx/drivers/usbdev/Kconfig
@@ -72,6 +72,22 @@ bool "Board DMA Allocation Hooks"
memory of the specified size; usbdev_dma_free() is the corresponding
function that will be called to free the DMA-capable memory.
+config ARCH_USBDEV_STALLQUEUE
+ bool
+ default n
+ ---help---
+ This option is set by the USB device controller driver (DCD)
+ selection. These selection means that the DCD can support
+ queuing of stall requests. By this, it is meant that, (1) the
+ stall is not sent until all write requests preceding the stall
+ request are sent, (2) the stall is sent, and then after the
+ stall is cleared, (3) all write requests queued after the stall
+ are sent.
+
+ If the driver does not support this feature, that the class drivers
+ will enable some hokey and inefficient delay logic to workaround
+ the lack of queuing.
+
config USBDEV_TRACE
bool "Enable USB tracing for debug"
default n