Fix a few issues related to new USB device boardctl() commands

This commit is contained in:
Gregory Nutt 2016-03-25 14:24:01 -06:00
parent a31300cb05
commit e01e664ccb
3 changed files with 8 additions and 3 deletions

View File

@ -1567,3 +1567,8 @@
* apps/examples/sched_note: Add a simple example to exercise
the scheduler instrumentation logic. Kind of buggy right now
(2016-03-17).
* apps/system/cdcacm, usbmsc, and composite, apps/examples/usbserial,
composite, usbterm: Use new boardctl() instead of callinig directly
in the OS when possible. There are still a few bad OS calls for
USB device interfaces that do not yet have boardctl() commands
(2016-03-25).

View File

@ -514,7 +514,7 @@ static void usbmsc_disconnect(void)
{
struct boardioc_usbdev_ctrl_s ctrl;
ctrl.usbdev = BOARDIOC_USBDEV_USBMSC;
ctrl.usbdev = BOARDIOC_USBDEV_MSC;
ctrl.action = BOARDIOC_USBDEV_DISCONNECT;
ctrl.instance = 0;
ctrl.handle = &g_composite.mschandle;

View File

@ -410,7 +410,7 @@ static void usbmsc_disconnect(FAR void *handle)
{
struct boardioc_usbdev_ctrl_s ctrl;
ctrl.usbdev = BOARDIOC_USBDEV_USBMSC;
ctrl.usbdev = BOARDIOC_USBDEV_MSC;
ctrl.action = BOARDIOC_USBDEV_DISCONNECT;
ctrl.instance = 0;
ctrl.handle = &handle;
@ -481,7 +481,7 @@ int msconn_main(int argc, char *argv[])
printf("mcsonn_main: Creating block drivers\n");
ctrl.usbdev = BOARDIOC_USBDEV_USBMSC;
ctrl.usbdev = BOARDIOC_USBDEV_MSC;
ctrl.action = BOARDIOC_USBDEV_INITIALIZE;
ctrl.instance = 0;
ctrl.handle = NULL;