There are some tests that behave differently for some buses than others, so they call a generic "what kind of device is this" function. This function hits the failure internally. -----Original Message----- From: wdmaudiodev-bounce@xxxxxxxxxxxxx [mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Eugene Muzychenko Sent: Tuesday, May 21, 2013 4:49 PM To: Matthew van Eerde Subject: [wdmaudiodev] Re: GAudit and KSPROPERTY_PIN_PROPOSEDATAFORMAT (GET) Hello Matthew, > This test expects drivers to be enumerated from a UAA-compliant bus > (HD Audio, USB, or Bluetooth.) But this error appears only in some property request cases, not on device/driver enumeration stage. It looks like that there is a kind of "get bus information" function that KsTopTest calls in these cases. Maybe it would be more correct to call it once on enumeration stage? Regards, Eugene ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/ ****************** WDMAUDIODEV addresses: Post message: mailto:wdmaudiodev@xxxxxxxxxxxxx Subscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=subscribe Unsubscribe: mailto:wdmaudiodev-request@xxxxxxxxxxxxx?subject=unsubscribe Moderator: mailto:wdmaudiodev-moderators@xxxxxxxxxxxxx URL to WDMAUDIODEV page: http://www.wdmaudiodev.com/
