From e37d8b5e5d9a9cea78ae8928703faf7867fea31e Mon Sep 17 00:00:00 2001
From: patacongo <patacongo@7fd9a85b-ad96-42d3-883c-3090e2eb8679>
Date: Thu, 12 Apr 2012 16:30:48 +0000
Subject: Extend the USB device/class interface:  Add parameters to pass the
 EP0 OUT data that should accompany the OUT SETUP request

git-svn-id: https://nuttx.svn.sourceforge.net/svnroot/nuttx/trunk@4595 7fd9a85b-ad96-42d3-883c-3090e2eb8679
---
 nuttx/TODO | 6 ++++++
 1 file changed, 6 insertions(+)

(limited to 'nuttx/TODO')

diff --git a/nuttx/TODO b/nuttx/TODO
index a71bf9183..779979955 100644
--- a/nuttx/TODO
+++ b/nuttx/TODO
@@ -532,6 +532,12 @@ o USB (drivers/usbdev, drivers/usbhost)
                2. But EP0 OUT data could be buffered in a buffer in the driver
                   data structure.  However, there is no method currently
                   defined in the USB device interface to obtain the EP0 data.
+
+               Updates:  (1) The USB device-to-class interface as been extended so
+               that EP0 OUT data can accompany the SETUP request sent to the
+               class drivers. (2) The logic in the STM32 F4 OTG FS device driver
+               has been extended to provide this data.  Updates are still needed
+               to other drivers.
   Status:      Open
   Priority:    High for class drivers that need EP0 data.  For example, the
                CDC/ACM serial driver might need the line coding data (that
-- 
cgit v1.2.3