Power Policy Ownership in Serial Driver

I’m looking for a usb/serial dongle that can give up power policy ownership.
The inbox serial.sys honors a registry setting called SerialRelinquishPowerPolicy.

Also if there is an article that explains what goes wrong when two modules in a stack are power policy owners, I’m interested.

thanks,
m navab

massoud navab wrote:

I’m looking for a usb/serial dongle that can give up power
policy ownership.

Why? What are you trying to do?

I don’t think there is a doc or article that talks about 2 power policy owners in a stack, but the typical problems are

  1. deadlocks
  2. untested code paths
  3. undefined and unpredictable behavior b/c assumptions in one driver are being broken by another

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Wednesday, November 11, 2009 9:53 AM
To: Windows System Software Devs Interest List
Subject: [ntdev] Power Policy Ownership in Serial Driver

I’m looking for a usb/serial dongle that can give up power policy ownership.
The inbox serial.sys honors a registry setting called SerialRelinquishPowerPolicy.

Also if there is an article that explains what goes wrong when two modules in a stack are power policy owners, I’m interested.

thanks,
m navab


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer

Thanks Doran. I notice that resume from sleep or hibernation fail on dongles. They work on standard ports.

Chris, I’m in a hid stack. Hid has to be the power policy owner. Hid assumes usb transport, but this is not always true.

HIDclass assumes nothing about the underlying transport. What it does assume is that it is the PPO. That has nothing to do with the transport, it is a normal assumption to make as the FDO for the stack

d

-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@yahoo.com
Sent: Wednesday, November 11, 2009 1:02 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Power Policy Ownership in Serial Driver

Thanks Doran. I notice that resume from sleep or hibernation fail on dongles. They work on standard ports.

Chris, I’m in a hid stack. Hid has to be the power policy owner. Hid assumes usb transport, but this is not always true.


NTDEV is sponsored by OSR

For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars

To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer