Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pmu(4) [netbsd man page]

PMU(4)							   BSD Kernel Interfaces Manual 						    PMU(4)

pmu -- support for Power Management Units found in all Apple laptops and some desktop Power Macintosh computers SYNOPSIS
pmu* at obio? nadb* at pmu? battery* at pmu? smartbat* at pmu? DESCRIPTION
The pmu driver provides support for the Power Management Unit found in Apple laptops and some desktop Power Macintosh computers. Functions controlled by the PMU include the real time clock, ADB, power, batteries, on some laptops like the PowerBook 3400c and similar machines it also controls hotkeys and display brightness, on others it provides an iic(9) bus and on some it controls CPU speed. On many older machines it also provides access to some non-volatile memory and thermal sensors. Not all those features are present on all machines, for instance Power Macintosh G4 and later machines don't have ADB, many more recent laptops have display brightness and backlight control built into the graphics controller instead of the PMU, only a few older PowerBooks use the PMU for CPU speed control and newer machines use a different way to access non-volatile memory. However, all known PMUs so far provide a real time clock and power control. Notes by model Real time clock and power control are present and supported on all machines that can run NetBSD/macppc, ADB is supported when present. PowerBook 2400, 3400c, and 3500 Battery status and thermal sensors found on the mainboard and in the battery pack are supported by the battery(4) driver, val- ues can be read via envsys(4). Hotkeys for brightness control are supported, CPU speed control and parameter RAM are present but unsupported. Power Macintosh G4 ADB is not present, iic(9) is present but unsupported. SEE ALSO
battery(4), cuda(4), nadb(4), nvram(4), obio(4), iic(9) BUGS
Some features are currently unsupported, like the iic(9) bus, access to parameter RAM and CPU speed control. BSD
May 14, 2007 BSD

Check Out this Related Man Page

ACPITZ(4)						   BSD Kernel Interfaces Manual 						 ACPITZ(4)

acpitz -- ACPI Thermal Zone SYNOPSIS
acpitz* at acpi? DESCRIPTION
The acpitz driver supports so-called ACPI ``Thermal Zones''. The temperature can be monitored by the envsys(4) API or the envstat(8) com- mand. The distinction between ``active'' and ``passive'' cooling is central to the abstractions behind acpitz. These are inversely related to each other: 1. Active cooling means that the system increases the power consumption of the machine by performing active thermal management (for exam- ple, by turning on a fan) in order to reduce the temperatures. 2. Passive cooling means that the system reduces the power consumption of devices at the cost of system performance (for example, by low- ering the CPU frequencies) in order to reduce the temperatures. Only active cooling is currently supported on NetBSD. It should be also noted that the internal functioning of these cooling policies vary across machines. On some machines the operating system may have little control over the thermal zones as the firmware manages the thermal control internally, whereas on other machines the policies may be exposed to the implementation at their full extent. EVENTS
The acpitz driver knows about the active cooling levels, the current temperatures, and critical, hot, and passive temperature thresholds (as supported by the hardware). The driver is able to send events to powerd(8) when the sensor's state has changed. When a Thermal Zone is either critical or ``hot'', the /etc/powerd/scripts/sensor_temperature script will be invoked with a critical-over event. The critical temperature is the threshold for system shutdown. Depending on the hardware, the mainboard will take down the system instantly and no event will have a chance to be sent. SEE ALSO
acpi(4), acpifan(4), envsys(4), envstat(8), powerd(8) HISTORY
The acpitz driver appeared in NetBSD 2.0. AUTHORS
Jared D. McNeill <> CAVEATS
While no pronounced bugs are known to exist, several caveats can be mentioned: o Passive cooling is not implemented. o There is no user-controllable way to switch between active and passive cooling, although the specifications support such transforms on some machines. o The ``hot'' temperature is a threshold in which the system ought to be put into S4 sleep. This sleep state (``suspend to disk'') is not supported on NetBSD. BSD
January 9, 2011 BSD
Man Page