If DCD supports queuing of stall requests then USB MSC delay work-around is not necessary

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