Lines Matching refs:power
990 * pci_raw_set_power_state - Use PCI PM registers to set the power state of
993 * @state: PCI power state (D0, D1, D2, D3hot) to put the device into.
1000 * 0 if device's power state has been successfully changed.
1019 * we're already in a low-power state, we can only go deeper. E.g.,
1025 pci_err(dev, "invalid power transition (from %s to %s)\n",
1038 pci_err(dev, "can't change power state from %s to %s (config space inaccessible)\n",
1072 * Mandatory power management transition delays; see PCI PM 1.1
1083 pci_info_ratelimited(dev, "refused to change power state from %s to %s\n",
1110 * pci_update_current_state - Read power state of given device and cache it
1114 * The power state is read from the PMCSR register, which however is
1117 * reports an incorrect state or the device isn't power manageable by the
1137 * pci_refresh_power_state - Refresh the given device's power state data
1140 * Ask the platform to refresh the devices power state information and invoke
1141 * pci_update_current_state() to update its current PCI power state.
1152 * pci_platform_power_transition - Use platform to change device power state
1239 * @dev: PCI device to power up
1246 * Mandatory power management transition delays are handled in
1287 * pci_set_power_state - Set the power state of a PCI device
1289 * @state: PCI power state (D0, D1, D2, D3hot) to put the device into.
1291 * Transition a device to a new power state, using the platform firmware and/or
1301 * 0 if device's power state has been successfully changed.
1346 /* Powering off a bridge may power off the whole hierarchy */
1355 * pci_choose_state - Choose the power state of a PCI device
1360 * Returns PCI power state suitable for given device and given system
1876 * boot or a device removal call. So get the current power state
2116 * NOTE: This function is a backend of PCI power management routines and is
2290 * If bridge is in low power state, the
2373 * hit, and the power savings from the devices will still be a
2429 * Devices with legacy power management (no standard PCI PM capabilities)
2443 * Bridges that are not power-manageable directly only signal
2446 * power-manageable may signal wakeup for themselves (for example,
2520 * D3_hot and D3_cold and the platform is unable to enable wake-up power for it.
2531 * pci_target_state - find an appropriate low power state for a given PCI dev
2535 * Use underlying platform code to find a supported low power state for @dev.
2569 * If the device is in D3cold even though it's not power-manageable by
2600 * Choose the power state appropriate for the device depending on whether
2601 * it can wake up the system and/or is power manageable by the platform
2643 * power state.
2683 /* PME-capable in principle, but not from the target power state */
2713 * suspend, or the current power state of it is not suitable for the upcoming
2727 * If the earlier platform check has not triggered, D3cold is just power
2743 * Note that if the device's power state is D3cold and the platform check in
2751 spin_lock_irq(&dev->power.lock);
2757 spin_unlock_irq(&dev->power.lock);
2775 spin_lock_irq(&dev->power.lock);
2780 spin_unlock_irq(&dev->power.lock);
2820 * which allows Linux to power manage it. However, this
2821 * confuses the BIOS SMI handler so don't power manage root
4665 * PCI_D0. If that's the case and the device is not in a low-power state
4668 * NOTE: This causes the caller to sleep for twice the device power transition
4921 * Devices on the secondary bus are left in power-on state.
5487 * independent of other slots. For instance, some slots may support slot power
6103 return adev->power.flags.power_resources &&