[wdmaudiodev] Re: Report a jack state change (plugged/unplugged)
- From: Mitchell Rundle <mitchr@xxxxxxxxxxxxx>
- To: Mitchell Rundle <wdmaudiodev@xxxxxxxxxxxxx>
- Date: Tue, 27 Mar 2007 08:02:20 -0700
I agree that device interface registration/unregistration is overkill for just
changing the state of the plug. We are looking at ways to simplify this for
future releases.
The KSPROPERTY_JACK_DESCRIPTION is sent to every "plug" pin when there is any
device interface removal or arrival. What order are you doing the following:
1) toggle the jack "plugged" state
2) toggle the device interface state
They need to be done in the order above or you will have a race condition.
Regards,
Mitch
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of Eugene Muzychenko
Sent: Thursday, March 22, 2007 12:22 PM
To: Mitchell Rundle
Subject: [wdmaudiodev] Report a jack state change (plugged/unplugged)
Hello Mitchell,
> The audioendpointbuilder service will re-examine the topology if it
> gets a pnp device notification.
Now I have rewritten my code to implement a fixed topology but respond
to KSPROPERTY_JACK_DESCRIPTION property request. And there is the same
problem: even if my driver reports a different connection status in
the IsConnected field, endpoint state (plugged/unplugged) does not change in the
recording device list. And KSPROPERTY_JACK_DESCRIPTION request is not
always sent to the driver when an application enumerates recording
devices.
Is there a way to reflect a jack state change (plugged/unplugged) without
re-registering a topology subdevice? Subdevice re-registration is a
reasonable way when its topology is changed but is too inadequate to
simply report a jack state change.
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/
Other related posts:
