-
Notifications
You must be signed in to change notification settings - Fork 1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
minor USB improvements #924
base: master
Are you sure you want to change the base?
Conversation
This allows the pointer table to be in Flash, by using "static const char * const strings[] = { ... };"
Extend usbd_init() docs & describe NAK/read_packet pitfalls.
usb_disconnect() is board/platform specific for chips that don't have built-in handling for this. Allow the application to provide its own version of usb_disconnect() to handle this.
* @li @link stm32f207_usb_driver @endlink | ||
* @li @link st_usbfs_v2_usb_driver @endlink | ||
* @li @link efm32lg_usb_driver @endlink | ||
* @li @link efm32hg_usb_driver @endlink |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oooh nice doxygen. is there anyway to j ust link to a type name? we can then make the drivers be members of that instead. ie, the efm32 driver is already refactored in my local tree.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have no idea, I wrote this with googling and the Doxygen manual open on the side ;)
Can you not just put your desired disconnect function into the driver struct? |
Modifying the driver struct is kindof impossible:
I've thought about it quite a bit and really think a weak |
I've pulled these locally, they all look good. |
This allows the pointer table to be in Flash, by using "static const char * const strings[] = { ... };" See libopencm3#924
Extend usbd_init() docs & describe NAK/read_packet pitfalls. See libopencm3#924
usb_disconnect() is board/platform specific for chips that don't have built-in handling for this. Allow the application to provide its own version of usb_disconnect() to handle this. See libopencm3#924
This allows the pointer table to be in Flash, by using "static const char * const strings[] = { ... };" See #924
usb_disconnect() is board/platform specific for chips that don't have built-in handling for this. Allow the application to provide its own version of usb_disconnect() to handle this. See #924
Extend usbd_init() docs & describe NAK/read_packet pitfalls. See libopencm3#924 REVIEW: check whether the docs are correct, and make sure that TI driver is added
Extend usbd_init() docs & describe NAK/read_packet pitfalls. See libopencm3#924 REVIEW: check whether the docs are correct, and make sure that TI driver is added
This allows the pointer table to be in Flash, by using "static const char * const strings[] = { ... };" See libopencm3#924
usb_disconnect() is board/platform specific for chips that don't have built-in handling for this. Allow the application to provide its own version of usb_disconnect() to handle this. See libopencm3#924
This allows the pointer table to be in Flash, by using "static const char * const strings[] = { ... };" See libopencm3#924
usb_disconnect() is board/platform specific for chips that don't have built-in handling for this. Allow the application to provide its own version of usb_disconnect() to handle this. See libopencm3#924
(see individual commits)