svcadm(8)을 검색하려면 섹션에서 8 을 선택하고, 맨 페이지 이름에 svcadm을 입력하고 검색을 누른다.
pm(9p)
pm(9P) Kernel Properties pm(9P)
NAME
pm - Power Management properties
DESCRIPTION
The pm-hardware-state property can be used to influence the behavior of
the Power Management framework. Its syntax and interpretation is de‐
scribed below.
Note that this property is only interpreted by the system immediately
after the device has successfully attached. Changes in the property
made by the driver after the driver has attached will not be recog‐
nized.
pm-hardware-state is a string-valued property. The existence of the pm-
hardware-state property indicates that a device needs special handling
by the Power Management framework with regard to its hardware state.
If the value of this property is needs-suspend-resume, the device has a
hardware state that cannot be deduced by the framework. The framework
definition of a device with hardware state is one with a reg property.
Some drivers, such as SCSI disk and tape drivers, have no reg property
but manage devices with "remote" hardware. Such a device must have a
pm-hardware-state property with a value of needs-suspend-resume for the
system to identify it as needing a call to its detach(9E) entry point
with command DDI_SUSPEND when system is suspended, and a call to at‐
tach(9E) with command DDI_RESUME when system is resumed. For devices
using original Power Management interfaces (which are now obsolete) de‐
tach(9E) is also called with DDI_PM_SUSPEND before power is removed
from the device, and attach(9E) is called with DDI_PM_RESUME after
power is restored.
A value of no-suspend-resume indicates that, in spite of the existence
of a reg property, a device has no hardware state that needs saving and
restoring. A device exporting this property will not have its detach()
entry point called with command DDI_SUSPEND when system is suspended,
nor will its attach() entry point be called with command DDI_RESUME
when system is resumed. For devices using the original (and now obso‐
lete) Power Management interfaces, detach(9E) will not be called with
DDI_PM_SUSPEND command before power is removed from the device, nor at‐
tach(9E) will be called with DDI_PM_RESUME command after power is re‐
stored to the device.
A value of parental-suspend-resume indicates that the device does not
implement the detach(9E) DDI_SUSPEND semantics, nor the attach()
DDI_RESUME semantics, but that a call should be made up the device tree
by the framework to effect the saving and/or restoring of hardware
state for this device. For devices using original Power Management in‐
terfaces (which are now obsolete), it also indicates that the device
does not implement the detach(9E) DDI_PM_SUSPEND semantics, nor the
attach(9E) DDI_PM_RESUME semantics, but that a call should be made up
the device tree by the framework to effect the saving and/or restoring
the hardware state for this device.
ATTRIBUTES
See attributes(7) for descriptions of the following attributes:
tab() box; cw(2.75i) |cw(2.75i) lw(2.75i) |lw(2.75i) ATTRIBUTE TYPEAT‐
TRIBUTE VALUE _ Interface StabilityCommitted
SEE ALSO
pm(4D), attach(9E), detach(9E), pm_busy_component(9F), pm_idle_compo‐
nent(9F), pm-components(9P)
Writing Device Drivers in Oracle Solaris 11.4
Oracle Solaris 11.4 30 Jun 2011 pm(9P)