Firmware downloading on a USB audio device

[Jeff Claar]

Hi all,

I have a USB audio device that dynamically downloads firmware when Windows
first loads the device. Once the firmware is downloaded, it changes its
device descriptors and re-presents itself as a new device, which then causes
Windows to load the "real" driver. Unfortunately, this is causing the ACPI
S1 and S3 tests to fail, since they expect the device to be playing when the
system returns from hibernation. I don't believe there is any way around
this situation -- since my driver completely reloads when the device loses
power, it is impossible to maintain the current streaming state.

Can such a device still get a Windows logo? Is there some exemption for
devices like this?

Thanks,
Jeff

 

[Robert Harper [MSFT]]

Jeff,

This shouldn't be a problem, since we allow some time for the device to come
back after system wake. Also ACPI Stress will only check the availability
and accessibility for the device, but not checking if the playback was at
where it was left.

Regards,

Robert Harper (MSFT)