d6a8bd5870
In my opinion, the user is supposed to configure the speed of the stack and drivers ough to honor that choice. However current Zephyr USB maintainer imposes that the dependency is the other way round, i.e. that user first needs to disable High-Speed chirp at driver level and only then can select Full-Speed only operation. Adhere to the arbitrarily set up rule to allow this really necessary functionality to enter Zephyr. I consider this change to be harmful because it opens up a Kconfig trap that allows configuring High-Speed capable stack with a device driver limited to Full-Speed only operation. Signed-off-by: Tomasz Moń <tomasz.mon@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| app | ||
| class | ||
| CMakeLists.txt | ||
| Kconfig | ||
| usbd_ch9.c | ||
| usbd_ch9.h | ||
| usbd_class_api.h | ||
| usbd_class.c | ||
| usbd_class.h | ||
| usbd_config.c | ||
| usbd_config.h | ||
| usbd_core.c | ||
| usbd_data.ld | ||
| usbd_desc.c | ||
| usbd_desc.h | ||
| usbd_device.c | ||
| usbd_device.h | ||
| usbd_endpoint.c | ||
| usbd_endpoint.h | ||
| usbd_init.c | ||
| usbd_init.h | ||
| usbd_interface.c | ||
| usbd_interface.h | ||
| usbd_msg.c | ||
| usbd_msg.h | ||
| usbd_shell.c | ||