| /titanic_44/usr/src/man/man4/ |
| H A D | power.conf.4 | 6 .TH POWER.CONF 4 "Feb 27, 2009"
8 power.conf \- Power Management configuration information file
12 \fB/etc/power.conf\fR
18 The \fBpower.conf\fR file is used by the Power Management configuration program
19 \fBpmconfig\fR(1M), to initialize the settings for Power Management. If you
25 allowed by this file. For ease-of-use, it is recommended that you use
27 for information on disabling Power Management.
30 Power Management addresses two specific management scenarios: management of
31 individual devices and management of the whole system. An individual device is
32 power managed if the device supports multiple power levels and if the device
[all …]
|
| /titanic_44/usr/src/man/man9p/ |
| H A D | pm-components.9p | 6 .TH PM-COMPONENTS 9P "Jan 6, 2004"
8 pm-components \- Power Management device property
12 A device is power manageable if the power consumption of the device can be
13 reduced when it is idle. In general, a power manageable device consists of a
14 number of power manageable hardware units called components. Each component is
15 separately controllable and has its own set of power parameters.
18 An example of a one-component power manageable device is a disk whose spindle
19 motor can be stopped to save power when the disk is idle. An example of a
20 two-component power manageable device is a frame buffer card with a connected
21 monitor. The frame buffer electronics (with power that can be reduced when not
[all …]
|
| H A D | pm.9p | 8 pm \- Power Management properties
12 The \fBpm-hardware-state\fR property can be used to influence the behavior of
13 the Power Management framework. Its syntax and interpretation is described
22 \fBpm-hardware-state\fR is a string-valued property. The existence of the
23 \fBpm-hardware-state\fR property indicates that a device needs special handling
24 by the Power Management framework with regard to its hardware state.
27 If the value of this property is \fBneeds-suspend-resume\fR, the device has a
32 \fBpm-hardware-state\fR property with a value of \fBneeds-suspend-resume\fR for
36 devices using original Power Management interfaces (which are now obsolete)
37 \fBdetach\fR(9E) is also called with \fBDDI_PM_SUSPEND\fR before power is
[all …]
|
| /titanic_44/usr/src/man/man1m/ |
| H A D | pmconfig.1m | 8 pmconfig \- Configure the Power Management system
12 \fB/usr/sbin/pmconfig\fR [\fB-r\fR]
18 The \fBpmconfig\fR utility sets the Power Management and suspend-resume
19 configuration. User has permission to change Power Management configuration
21 \fBPMCHANGEPERM \fRkeyword of \fB/etc/default/power\fR. User has permission to
22 change the suspend-resume configuration using \fBpmconfig\fR only if he is
24 \fB/etc/default/power\fR. See FILES section below for a description of the
26 \fB/etc/default/power\fR.
29 Based on user permissions, \fBpmconfig\fR first resets the Power Management
30 and/or suspend-resume state back to its default and then reads the new
[all …]
|
| H A D | powertop.1m | 8 powertop \- report and analyze events that affect power management
12 \fBpowertop\fR [\fB-c\fR \fIprocessor_id\fR] [\fB-d\fR \fIcount\fR] [\fB-t\fR \fIinterval\fR] [\fB-…
19 is taking advantage of the CPU's power management features. By running the tool
21 at dif- ferent power states. Ideally, an unutilized (idle) system spends 100%
22 of its time running at the lowest power state, but because of background user
24 systems can consume more power than they should.
28 long the processor is executing at each supported power state. It also displays
31 of the system and optimize its power efficiency.
35 entering a lower power state and presents it on the "Wakeups-from-idle per
36 second" field. This value represents the total number of wake-ups divided by
[all …]
|
| H A D | powerd.1m | 8 powerd \- power manager daemon
12 \fB/usr/lib/power/powerd\fR [\fB-n\fR]
19 activity and perform an automatic shutdown using the suspend-resume feature.
21 before power is removed. On reboot, the system automatically starts a resume
35 \fB\fB-n\fR\fR
46 \fB\fB/etc/power.conf\fR\fR
49 Power Management configuration information file
71 \fBpmconfig\fR(1M), \fBdtpower\fR(1M), \fBsyslogd\fR(1M), \fBpower.conf\fR(4),
75 \fIUsing Power Management\fR
|
| /titanic_44/usr/src/man/man7d/ |
| H A D | pm.7d | 8 pm \- Power Management driver
18 The Power Management ( \fBpm\fR) driver provides an interface for applications
19 to configure devices within the system for Power Management. The interface is
22 .SS "Power Management Framework"
25 The Power Management framework model allows the system to be viewed as a
27 the smallest power manageable units. The device driver controls the definition
28 of a device's power manageable components.
31 A component can either be \fBbusy\fR or \fBidle\fR at the current power level.
32 Normally, the Power Management framework takes an \fBidle\fR component to the
33 next lower power level. The Power Management framework uses two factors to
[all …]
|
| /titanic_44/usr/src/man/man9f/ |
| H A D | pm_power_has_changed.9f | 8 pm_power_has_changed \- Notify Power Management framework of autonomous power
39 Number of the component that has changed power level
48 Power level to which the indicated component has changed
54 The \fBpm_power_has_changed\fR(9) function notifies the Power Management
55 framework that the power level of component of \fIdip \fR has changed to
59 Normally power level changes are initiated by the Power Management framework
62 change power levels on their own. For the framework to track the power level of
64 autonomous power level changes by a call to \fBpm_power_has_changed()\fR.
67 Because of the asynchronous nature of these events, the Power Management
68 framework might have called \fBpower\fR(9E) between the device's autonomous
[all …]
|
| H A D | pm_raise_power.9f | 8 pm_raise_power, pm_lower_power \- Raise or lower power of components
44 The number of the \fIcomponent\fR for which a power level change is desired
53 The power level to which the indicated \fIcomponent\fR will be raised
72 Number of the \fIcomponent\fR for which a power level change is desired
81 Power level to which the indicated \fIcomponent\fR will be lowered
87 The \fBpm_raise_power\fR(9F) function requests the Power Management framework
88 to raise the power level of \fIcomponent \fRof \fIdip\fR to at least \fIlevel.
94 the required power level if the operation to be performed requires the
95 \fIcomponent \fR to be at a power level higher than its current power level.
99 guaranteed to be at least at the requested power level. All devices that depend
[all …]
|
| H A D | usb_create_pm_components.9f | 8 usb_create_pm_components \- Create power management components for USB devices
39 Address into which a mask which lists power states capable by device is
49 Corresponds to USB_DEV_OS_PWR_3 or full power.
76 Corresponds to USB_DEV_OS_PWR_0 or no power.
83 that assume the standard USB D0-D3 powerlevels (USB_DEV_PWR_D0 -
85 device's power management capabilities and account for bus-powered devices. The
86 \fBusb_create_pm_components()\fR function also updates the pm-components
90 Note that these USB power levels are inverse of OS power levels. For example,
92 powered-down.
100 Power management facilities in device are recognized by system.
[all …]
|
| H A D | pci_report_pmcap.9f | 8 pci_report_pmcap \- Report Power Management capability of a PCI device
40 Power management capability
55 Some PCI devices provide power management capabilities in addition to those
56 provided by the PCI Power Management Specification. The
57 \fBpci_report_pmcap()\fR function reports those Power Management capabilities
92 In this case, one offending device can keep the entire bus from being power
176 \fIPCI Bus Power Management Interface Specification Version 1.1\fR
|
| H A D | pm_busy_component.9f | 8 pm_busy_component, pm_idle_component \- control device component availability
9 for Power Management
46 The number of the component to be power-managed.
55 When a device is busy it will not be power-managed by the system.
61 to be power-managed by the system. The \fBpm_idle_component()\fR function has
67 \fBattach\fR(9E), \fBdetach\fR(9E) or \fBpower\fR(9E) entry point, these
69 \fBdetach\fR(9E) or \fBpower\fR(9E).
96 also be called from interrupt context, providing they are not the first Power
97 Management function called by the driver.
117 \fBpower.conf\fR(4), \fBpm\fR(7D), \fBattach\fR(9E), \fBdetach\fR(9E),
[all …]
|
| /titanic_44/usr/src/pkg/manifests/ |
| H A D | system-kernel-power.mf | 27 # The default for payload-bearing actions in this package is to appear in the
32 set name=pkg.fmri value=pkg:/system/kernel/power@$(PKGVERS)
33 set name=pkg.description value="Power Management binaries"
34 set name=pkg.summary value="Power Management binaries"
51 dir path=usr/lib/power group=sys
59 file path=etc/default/power group=sys
60 file path=etc/power.conf group=sys original_name=SUNWpm:etc/power.conf \
62 file path=lib/svc/manifest/system/power.xml group=sys mode=0444
63 file path=lib/svc/method/svc-power mode=0555
64 file path=usr/bin/sys-suspend mode=4555
[all …]
|
| H A D | driver-i86pc-fipe.mf | 27 # The default for payload-bearing actions in this package is to appear in the
34 value="Intel 5000/7300 memory power management driver"
35 set name=pkg.summary value="Intel 5000/7300 memory power management driver"
49 legacy pkg=SUNWfipe desc="Intel 5000/7300 memory power management driver" \
50 name="Intel 5000/7300 memory power management driver"
|
| /titanic_44/usr/src/lib/libsecdb/ |
| H A D | prof_attr.txt | 33 …Console User:profiles=Suspend To RAM,Suspend To Disk,Brightness,CPU Power Management,Network Autoc…
35 Device Management:::Control Access to Removable Media:auths=solaris.device.*;help=RtDeviceMngmnt.ht…
36 Printer Management:::Manage printers, daemons, spooling:auths=solaris.print.*,solaris.label.print,s…
37 Cron Management:::Manage at and cron jobs:auths=solaris.jobs.*,solaris.smf.manage.cron;help=RtCronM…
38 Log Management:::Manage log files:help=RtLogMngmnt.html
41 DHCP Management:::Manage the DHCP service:auths=solaris.dhcpmgr.*;help=RtDHCPMngmnt.html
42 …ing Flow Management:::Manage the Flow Extended Accounting service:auths=solaris.smf.manage.extende…
43 …ocess Management:::Manage the Process Extended Accounting service:auths=solaris.smf.manage.extende…
44 …ing Task Management:::Manage the Task Extended Accounting service:auths=solaris.smf.manage.extende…
45 …nting Net Management:::Manage the Net Extended Accounting service:auths=solaris.smf.manage.extende…
[all …]
|
| /titanic_44/usr/src/uts/common/os/ |
| H A D | cpu_pm.c | 32 * Solaris Event Based CPU Power Manager
34 * This file implements platform independent event based CPU power management.
36 * query the platform to determine if the CPU belongs to any power management
37 * domains. That is, sets of CPUs that share power management states.
39 * Active Power Management domains represent a group of CPUs across which the
42 * performance for power savings.
44 * Idle Power Management domains can enter power savings states when they are
45 * unutilized. These states allow the Operating System to trade off power
49 * For each active and idle power domain the CMT subsystem instantiates, a
52 * enumerated power domains. Significant changes in utilization will result
[all …]
|
| /titanic_44/usr/src/man/man9e/ |
| H A D | power.9e | 6 .TH POWER 9E "Dec 12, 2003"
8 power \- power a device attached to the system
17 \fBint prefix\fR\fBpower\fR(\fBdev_info_t\fR \fI*dip\fR, \fBint\fR \fIcomponent\fR, \fBint\fR \fIle…
51 Desired component power level.
57 The \fBpower\fR(9E) function is the device-specific Power Management entry
59 power level of \fIcomponent\fR to \fIlevel\fR.
62 The \fIlevel\fR argument is the driver-defined power level to which the
63 component needs to be set. Except for power level \fB0\fR, which is interpreted
69 power-managed. The interpretation of \fIcomponent\fR is entirely up to the
73 When a requested power transition would cause the device to lose state, the
[all …]
|
| H A D | attach.9e | 8 attach \- Attach a device to the system, or resume it
48 The \fBattach\fR(9E) function is the device-specific initialization entry
68 At attach time, all components of a power-manageable device are assumed to be
70 required component(s) to a known power level. The \fBpm_raise_power\fR(9F)
71 function can be used to set the power level of a component. This function must
72 not be called before data structures referenced in \fBpower\fR(9E) have been
83 the hardware state of a device (power may have been removed from the device),
86 restore the state of the device except for the power level of components.
89 If the device driver uses the automatic device Power Management interfaces
90 (driver exports the \fBpm-components\fR(9P) property), the Power Management
[all …]
|
| /titanic_44/usr/src/uts/i86pc/io/fipe/ |
| H A D | fipe.conf | 26 # Device property "fipe_pm_policy": configure power management policy.
28 # "0": disable power management
30 # "2": balance between performance and power saving
35 # Device property "disable_fipe_pm": disable fipe power management if its value
40 # -B disable_fipe_pm="true"
42 # Force attach driver to enable power management at boot time.
43 ddi-forceattach=1;
|
| /titanic_44/usr/src/man/man7/ |
| H A D | cpr.7 | 9 cpr \- Suspend and resume module
13 \fB/platform/'uname -m'/kernel/misc/cpr\fR
20 system. You may wish to suspend a system to save power or to power off
25 state is preserved in non-volatile storage until a resume operation is
29 \fBdtpower\fR(1M) or \fBpower.conf\fR(4) are used to configure the
30 suspend-resume feature.
38 allow them to do any special processing in response to suspend-resume
40 because of suspend-resume, but some specialized processes can use
48 might not support suspend-resume operations. In this case, the suspend fails
52 suspend-resume.
[all …]
|
| /titanic_44/usr/src/uts/intel/io/acpica/ |
| H A D | ahids.c | 3 * Module Name: ahids - Table of ACPI/PNP _HID/_CID values
8 * Copyright (C) 2000 - 2016, Intel Corp.
22 * 3. Neither the names of the above-listed copyright holders nor the names
65 {"ACPI0003", "Power Source Device"},
75 {"ACPI000D", "Power Meter Device"},
99 {"INT3396", "Standard Power Management Controller"},
101 {"INT33A1", "Intel Power Engine"},
125 {"INT33FB", "MIPI-CSI Camera Sensor OV2722"},
127 {"INT33FD", "Intel Baytrail Power Management IC"},
129 {"INT3400", "Intel Dynamic Power Performance Management"},
[all …]
|
| /titanic_44/usr/src/uts/common/sys/ |
| H A D | sunpm.h | 32 * Sun Specific Power Management definitions
54 * Power cycle transition check is supported for SCSI and SATA devices.
62 int lifemax; /* lifetime max power cycles */
83 * Power levels for devices supporting ACPI based D0, D1, D2, D3 states.
85 * Note that 0 is off in Solaris PM framework but D0 is full power
88 #define PM_LEVEL_D3 0 /* D3 state - off */
91 #define PM_LEVEL_D0 3 /* D0 state - fully on */
94 * Useful strings for creating pm-components property for these devices.
95 * If a device driver wishes to provide more specific description of power
108 * These are obsolete power management interfaces, they will be removed from
[all …]
|
| /titanic_44/usr/src/lib/libsecdb/help/profiles/ |
| H A D | RtCPUPowerManagement.html | 2 <!--
22 -- Copyright 2008 Sun Microsystems, Inc. All rights reserved.
23 -- Use is subject to license terms.
24 -->
31 <!-- ident "%Z%%M% %I% %E% SMI" -->
33 When CPU Power Management is in the Rights Included column, it grants the right to configure CPU po…
35 If CPU Power Management is grayed, then you are not entitled to Add or Remove this right.
|
| H A D | RtSysPowerMgmt.html | 2 <!--
22 -- Copyright 2008 Sun Microsystems, Inc. All rights reserved.
23 -- Use is subject to license terms.
24 -->
31 <!-- ident "%Z%%M% %I% %E% SMI" -->
33 When System Power Management is in the Rights Included column, it grants the right to configure sys…
35 If System Power Management is grayed, then you are not entitled to Add or Remove this right.
|
| /titanic_44/usr/src/lib/libsecdb/help/auths/ |
| H A D | SmfPowerStates.html | 2 <!--
25 -->
26 <!-- SCCS keyword
28 -->
29 <!--
30 <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
31 -->
33 When Manage Power Management Service States is in the Authorizations
35 Power Management Daemon.
37 If Manage Power Management Service States is grayed, then you are not
|