Lines Matching full:pm

83  * dev_pm_domain_attach - Attach a device to its PM domain.
87 * The @dev may only be attached to a single PM domain. By iterating through
88 * the available alternatives we try to find a valid PM domain for the device.
94 * power management through PM domains.
99 * Returns 0 on successfully attached PM domain, or when it is found that the
100 * device doesn't need a PM domain, else a negative error code.
118 * dev_pm_domain_attach_by_id - Associate a device with one of its PM domains.
119 * @dev: The device used to lookup the PM domain.
120 * @index: The index of the PM domain.
122 * As @dev may only be attached to a single PM domain, the backend PM domain
129 * in case its device requires power management through multiple PM domains. The
133 * the power to the PM domains independently from each other.
138 * Returns the virtual created device when successfully attached to its PM
139 * domain, NULL in case @dev don't need a PM domain, else an ERR_PTR().
154 * dev_pm_domain_attach_by_name - Associate a device with one of its PM domains.
155 * @dev: The device used to lookup the PM domain.
156 * @name: The name of the PM domain.
171 * dev_pm_domain_detach - Detach a device from its PM domain.
177 * detaches @dev from its PM domain. Typically it should be invoked during the
191 * dev_pm_domain_start - Start the device through its PM domain.
195 * when it needs to start its device from the PM domain's perspective. Note
196 * that, it's assumed that the PM domain is already powered on when this
211 * dev_pm_domain_set - Set PM domain of a device.
212 * @dev: Device whose PM domain is to be set.
213 * @pd: PM domain to be set, or NULL.
215 * Sets the PM domain the device belongs to. The PM domain of a device needs
226 "PM domains can only be changed for unbound devices\n"); in dev_pm_domain_set()
238 * requested for a device that is attached to a PM domain. Note that, the
239 * support for performance scaling for PM domains is optional.