Lines Matching defs:up
30 * Assumes: all backwards compat. device components wake up on &
68 * up to the driver to decide when a transition requires saving or restoring
98 * -ensure that the console frame buffer is powered up before being referenced
100 * -maintain implicit dependencies (e.g. parent must be powered up if child is)
119 * cdrom is always up whenever the console framebuffer is up, so that the user
124 * of a "keeps up" and a "kept up" device. A relationship can be established
125 * where one device keeps up another. That means that if the keepsup device
127 * "kept up" device must be brought to full power. This relationship is
128 * asynchronous. When the keeping device is powered up, a request is queued
129 * to a worker thread to bring up the kept device. The caller does not wait.
130 * Scan will not turn down a kept up device.
230 * frame buffer are off (so we know if we have to bring up the
284 * seconds to spin up a disk drive), this is locked separately.
296 * up or after a CPR operation. It is per-dip to keep from
337 * Autopm must be turned on by a PM_START_PM ioctl, so we don't end up
405 * PMD(), which will prevent debug output from bringing up the console
447 * By default nexus has 0 threshold, and depends on its children to keep it up
788 return ("up");
922 cmn_err(CE_WARN, "Device %s failed to power up.",
1122 * Returns true if device needs to be kept up because it exported the
1124 * fb case) or it is an ancestor of such a device and has used up the "one
1163 * need to look up the tree. An ancestor cannot use up the free cycle
1440 * A node which was voluntarily power managed has just used up its "free cycle"
1459 * A node which was voluntarily power managed has used up the "free cycles"
1587 * If some other devices were also powered up (e.g. other cpus in
1597 * -This is comp 0 and we have successfully powered it up
1675 * Cases which require us to bring up devices we keep up ("wekeepups") for
1677 * component 0 is off and we're bringing it up from 0
1678 * bring up wekeepup first
1680 * component up from 0
1705 * either deadlocking or bringing up the console because of debug
1736 * brought up all the ancestors, otherwise, we have to go back to the
1852 * Device dip is being un power managed, it keeps up count other devices.
1920 * Device kept is being un power managed, it is kept up by keeper.
1951 * then free up the kept lists.
2149 * Look up an entry in the blocked list by dip and component
2179 * we're giving up control, let any pending op continue
2328 /* Schedule a request to clean up dependency records */
2625 * If we were called in the path that brings up the console fb in the
2722 * Create an entry for a process to pick up indicating a power level change.
3308 * device up to full power on the assumption the detach will succeed.
3329 * console and old-style devices get brought up when detaching.
3450 * Look up pm-components property and create components accordingly
3523 * to play autopm. Look up the pm model and manage the device accordingly.
3549 * Now set up parent's kidsupcnt. BC nodes are assumed to start
3550 * out at their normal power, so they are "up", others start out
3551 * unknown, which is effectively "up". Parent which want notification
3816 * Bring up the 'kept' device passed as argument
3833 PMD(PMD_BRING, ("%s: can't bring up PM_DIRECT %s@%s(%s#%d) "
4036 * Read the pm-components property (if there is one) and use it to set up
4101 /* finish up previous component levels */
5044 "left up\n", pmf, PM_DEVICE(dip)))
5120 * and it is up to the user to issue the ioctl again if they want it
5169 * Look up this device in the set of devices we've seen ioctls for
5200 int j, up = 0, circ;
5211 cmn_err(CE_CONT, "!device %s@%s(%s#%d) keeps up device "
5223 up++;
5227 if (up) {
5242 * Should this device keep up another device?
5243 * Look up this device in the set of devices we've seen ioctls for
5307 * Should this device be kept up by another device?
5308 * Look up all dependency recorded from PM_ADD_DEPENDENT and
5442 * keeper is already known to be the device that keeps up the other (kept) one.
5573 * watch all state transitions (dip == NULL). Set up data
5703 * If dip is NULL, process is closing "clone" clean up all its registrations.
5704 * Otherwise only clean up those for dip because process is just giving up
5767 * be passed up to the controlling process.
6360 * Called when we are just released from direct PM. Bring ourself up
6361 * if our keeper is up since dependency is not honored while a kept
6372 int up = 0, circ;
6393 "%d is up\n", pmf, j))
6394 up++;
6397 if (up) {
6425 /* Bring up the kept devices and put a hold on them */
6441 * it again and bring ourselves up.
6691 * 'now' should be rounded up to full day.
6826 * Bring parent of a node that is about to be probed up to full power, and
6827 * arrange for it to stay up until pm_post_probe() or pm_post_attach() decide
6905 * If the dip is a leaf node, don't power it up.
6911 * Do not power up the node if it is called due to auto-modunload.
7279 * If this child's detach will be holding up its ancestors, then we
7330 * brought up all components)
7370 * Called after vfs_mountroot has got the clock started to fix up timestamps
7481 * Now walk up the tree decrementing devi_pm_noinvolpm
7550 * go away, then we give up, as
7662 * We set up here as if the driver were power manageable in case
7689 * Walk up the tree incrementing
7718 * bring up the frame buffer power from above lock level. So if we need to,
7774 * returns 1 when power is off (power-up is needed)
7775 * returns 0 when power is on (power-up not needed)
7839 * Check if the console framebuffer is powered up. If not power it up.
7852 * Trigger a low level interrupt to power up console frame buffer.
7865 * it up (by generating a softint to do the work). If a second attempt
7871 panic(panicstr); /* does a power up at any intr level */
8015 * a driver could get hung up in a pm_raise_power()
8230 * First we look up the ancestor's dip. If we find it, then we
8231 * adjust counts up the tree
8339 * Returns true if (detached) device needs to be kept up because it exported the
8341 * fb case) or it is an ancestor of such a device and has used up the "one
8416 * A wrapper of pm_all_to_normal() to power up a dip
8505 * power up the node as it is needed. There is nothing
8518 * we presume that the parent needs to be up in
8615 * For attach, detach, power up:
8619 * path and the target dip passed in is up to and incl.
8755 /* Powering up */
8865 * back up to full power.
9006 * gives it up or makes the requested power level change, unless
9190 * A power up could come in between and