PoFx Beheivor on Windows 8

Hi
I’m working on a driver for Windows 8 that I would like to support component power states (F0 and F1).

My device power states are as following:
D0 - Fully On - Power On
D3 - Powered Off
F0 - Like D0
F1 - Semi powered off.

I would like use PoFx to control our power state. when the driver is idle I would like to move between F1 and F0 and not to move to D3.

the problem is when I use PoFx, I see the following behavior, when the driver start:
Move to D0 (D0Entry)
Move to Idle (IdleConditionCallback)
Move To F1 (IdleStateCallback)
Move to D3 (D0Exit)

Is it possible to disable the move to D3?
I only want to move to D3 when system Move to Sx (S4, S3, S5) and not in idle…

Thanks in advance…

Don’t be idle. This is what moves you out of f0.

  • pa

On 02-Aug-2012 12:06, xxxxx@gmail.com wrote:

Hi
I’m working on a driver for Windows 8 that I would like to support component power states (F0 and F1).

My device power states are as following:
D0 - Fully On - Power On
D3 - Powered Off
F0 - Like D0
F1 - Semi powered off.

I would like use PoFx to control our power state. when the driver is idle I would like to move between F1 and F0 and not to move to D3.

the problem is when I use PoFx, I see the following behavior, when the driver start:
Move to D0 (D0Entry)
Move to Idle (IdleConditionCallback)
Move To F1 (IdleStateCallback)
Move to D3 (D0Exit)

Is it possible to disable the move to D3?
I only want to move to D3 when system Move to Sx (S4, S3, S5) and not in idle…

Thanks in advance…

yes, but I want to move out of F0…
I want to move to F1, but I don’t want to move to D0 after I move to F1…

Add another component. Mark that one active. The entire device will remain
in D0 for as long as a component needs to be in F0.

But the bigger question here is what you think you're going to get out of
this. F-state power management is mostly useful only in a machine with a
Power-Engine Plugin, or PEP, which is responding to your device's F-state
transitions by turning external clocks and power rails on and off.

If you're not targeting a machine with a PEP, then you can do everything you
need to do internally, without using F-states at all. If you are targeting
a machine with a PEP, you need to talk to the person who's developing the
PEP to coordinate what you're doing.

Jake Oshins
Windows Kernel Team

The message offers no warranties and confers no rights.

wrote in message news:xxxxx@ntdev...

Hi
I'm working on a driver for Windows 8 that I would like to support component
power states (F0 and F1).

My device power states are as following:
D0 - Fully On - Power On
D3 - Powered Off
F0 - Like D0
F1 - Semi powered off.

I would like use PoFx to control our power state. when the driver is idle I
would like to move between F1 and F0 and not to move to D3.

the problem is when I use PoFx, I see the following behavior, when the
driver start:
Move to D0 (D0Entry)
Move to Idle (IdleConditionCallback)
Move To F1 (IdleStateCallback)
Move to D3 (D0Exit)

Is it possible to disable the move to D3?
I only want to move to D3 when system Move to Sx (S4, S3, S5) and not in
idle...

Thanks in advance...