usb: move the request handler buffer to the USB device code
In order to unify the legacy and composite code, move the class and vendor request handler buffer into the USB device code, just like in composite mode. The option is renamed from USB_COMPOSITE_BUFFER_SIZE into USB_REQUEST_BUFFER_SIZE and also replaces the USB_DFU_MAX_XFER_SIZE and USB_HID_MAX_PAYLOAD_SIZE options. Signed-off-by: Aurelien Jarno <aurelien@aurel32.net> Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>
This commit is contained in:
parent
67de7ec86d
commit
819e749ccd
20 changed files with 13 additions and 108 deletions
|
@ -159,19 +159,6 @@ struct usb_interface_cfg_data {
|
|||
* handler.
|
||||
*/
|
||||
usb_request_handler custom_handler;
|
||||
/**
|
||||
* This data area, allocated by the application, is used to store
|
||||
* Class specific command data and must be large enough to store the
|
||||
* largest payload associated with the largest supported Class'
|
||||
* command set. This data area may be used for USB IN or OUT
|
||||
* communications.
|
||||
*/
|
||||
u8_t *payload_data;
|
||||
/**
|
||||
* This data area, allocated by the application, is used to store
|
||||
* Vendor specific payload.
|
||||
*/
|
||||
u8_t *vendor_data;
|
||||
};
|
||||
|
||||
/**
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue