RFC PCI PM: Fix radeonfb vs pci_set_power_state() problem
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest2 patches 2 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/2 | PCI PM: Introduce __pci_[start|complete]_power_transition()drivers/ include/ | +49 | 0 replies | |
| 1/2 | PCI PM: Introduce __pci_[start|complete]_power_transition()drivers/ include/ | +49 | 2 replies | |
| 2/2 | radeonfb: Use __pci_complete_power_transition()drivers/ | +1 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC][PATCH 0/2] PCI PM: Fix radeonfb vs pci_set_power_state() problem
Hi,
The following two patches are intended to fix the problem that will arise when the PM patches queued up for 2.6.30 are merged and which is that pci_set_power_state() called by radeonfb to complete the transition into D2 will return immediately due to the device's current_state being already PCI_D2.
1/2 introduces low level PM core functions one of which may be called by the radeonfb driver to complete the power transition.
2/2 actually makes radeonfb use the new function.
The patches (on top of the linux-next branch of suspend-2.6) have not been tested yet, but they compile (at least on x86_64).
Comments welcome.
Thanks,
Rafael