Found 5 other functions taking a
tBTA_SYS_HW_MSG
argument:
* Function bta_sys_hw_error * Description In case the HW device stops answering... Try to turn it off, then re-enable all * previously active SW modules. * Returns success or failure
* Function bta_sys_hw_disable * Description if no other module is using the HW, this function will call ( if defined ) a user-macro to turn off the HW * Returns success or failure
* Function bta_sys_hw_event_enabled * Description * Returns success or failure
* Function bta_sys_hw_event_disabled * Description * Returns success or failure
* Function bta_sys_hw_event_stack_enabled * Description we receive this event once the SW side is ready ( stack, FW download,... ), * i.e. we can really start using the device. So notify the app. * Returns success or failure