Possible bug in USB 5.0 Audio class driver

johnstrohm — Wed, 19 Nov 2014 16:52:56 GMT

In file usb_audio.c, at line 146, you have:

/* Callback to application */

if (audio_obj_ptr->class_specific_callback.callback != NULL)

{

/* notify the app of the send complete */

audio_obj_ptr->class_specific_callback.callback(USB_DEV_EVENT_SEND_COMPLETE, USB_REQ_VAL_INVALID,NULL,0,

audio_obj_ptr->audio_application_callback.arg);

}

Reformatting for readability:

/* Callback to application */

if (audio_obj_ptr->class_specific_callback.callback != NULL)

{

/* notify the app of the send complete */

audio_obj_ptr->class_specific_callback.callback(USB_DEV_EVENT_SEND_COMPLETE,

USB_REQ_VAL_INVALID,

NULL,

audio_obj_ptr->audio_application_callback.arg);

}

I believe this should be:

/* Callback to application */

if (audio_obj_ptr->class_specific_callback.callback != NULL)

{

/* notify the app of the send complete */

audio_obj_ptr->class_specific_callback.callback(USB_DEV_EVENT_SEND_COMPLETE,

USB_REQ_VAL_INVALID,

NULL,

audio_obj_ptr->class_specific_callback.arg);

}

That is, calls to the class_specific_callback should use the class_specific.callback.arg.

Re: Possible bug in USB 5.0 Audio class driver

makeshi — Mon, 24 Nov 2014 10:06:44 GMT

Thanks for you raising the issue, it is a typo issue in USB audio class driver, USB software team will fix

it in subsequent release.