[PATCH 3/8] OMAP2+: powerdomain: control power domains next state

2011-10-12 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the corresponding power

[PATCH 3/8] OMAP2+: powerdomain: control power domains next state

2011-09-21 Thread Jean Pihet
When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the corresponding power domain. The power domains get the

[PATCH 3/8] OMAP2+: powerdomain: control power domains next state

2011-09-21 Thread jean . pihet
From: Jean Pihet j-pi...@ti.com When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the corresponding power

Re: [PATCH 3/8] OMAP2+: powerdomain: control power domains next state

2011-09-16 Thread Kevin Hilman
Jean Pihet jean.pi...@newoldbits.com writes: When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the

[PATCH 3/8] OMAP2+: powerdomain: control power domains next state

2011-09-02 Thread Jean Pihet
When a PM QoS device latency constraint is requested or removed the PM QoS layer notifies the underlying layer with the updated aggregated constraint value. The constraint is stored in the powerdomain constraints list and then applied to the corresponding power domain. The power domains get the