Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

acpiec(4) [netbsd man page]

ACPIEC(4)						   BSD Kernel Interfaces Manual 						 ACPIEC(4)

NAME
acpiec -- ACPI Embedded Controller SYNOPSIS
acpiec* at acpi? acpiecdt* at acpi? DESCRIPTION
The acpiec driver supports ACPI Embedded Controllers. An ACPI Embedded Controller (EC) is typically a small microprocessor that is responsible for various tasks related to ACPI. The primary task is to handle ACPI specific interrupts, which are mapped to so-called ACPI General Purpose Events (GPEs). Other possible functions include embedded access to other buses such as the iic(4). The ACPI specific events range from user initiated events to events triggered by the hardware. When such an event occurs, typically either a System Management Interrupt (SMI) or a System Control Interrupt (SCI) is raised. The latter is an active, visible, shareable, level inter- rupt. On most Intel chipsets SCI is hardwired to the interrupt number 9. The main task of an EC is to raise a system control interrupt. All GPEs generate SCIs. A typical example of the internal wiring of GPEs could involve gpio(4): when, e.g., the AC adapter is connected, a certain GPIO line becomes active, a given GPE is flagged, and a SCI interrupt is raised by the EC, leading to execution of ACPI machine code in order to locate the handler associated with the event. A corresponding driver, acpiacad(4) in this case, will finally finish the process- ing of the event. Due to the reasons described above, majority of ACPI specific drivers are dysfunctional without acpiec. It is therefore recommended that acpiec is always enabled, even though it may not be required on some older systems. SEE ALSO
acpi(4) HISTORY
The acpiec driver appeared in NetBSD 1.6. CAVEATS
Many machines depend on early attachment of acpiec. In such cases the information required by acpiec should be available as a separate and optional Embedded Controller Descriptor Table (ECDT). If an ECDT is not available or early attachment can not be carried out due other rea- sons, the initialization of the whole acpi(4) subsystem may be problematic. BSD
February 27, 2010 BSD

Check Out this Related Man Page

tzmon(7d)							      Devices								 tzmon(7d)

NAME
tzmon - ACPI Thermal Zone Monitor DESCRIPTION
The tzmon is a pseudo driver that serves as an ACPI thermal zone monitor. Thermal zones are logical regions within a computer system for which ACPI performs temperature monitoring and control functions. The number of thermal zones on a system with ACPI support varies. For example, some systems may have one or more thermal zones, while others may have none. See the Advanced Configuration and Power Interface Specification, (ACPI) Version 3.0A. for more details. The tzmon handles thermal Zone events from ACPI and polls the temperature for each zone exposed by the ACPI implementation. If threshold temperatures are reached, tzmon takes appropriate action. For example, if the temperature is sufficiently high and the ACPI implementation supports it, tzmon initiates system shutdown. Note that by default, system temperature control functions are usually performed by the BIOS and may supersede tzmon functions, depending on the BIOS implementation. Also, many ACPI implementations expose no thermal zones and in these cases, tzmon performs no functions. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWckr | +-----------------------------+-----------------------------+ |Architecture |x86/x64 only | +-----------------------------+-----------------------------+ |Interface stability |Private | +-----------------------------+-----------------------------+ SEE ALSO
attributes(5) Advanced Configuration and Power Interface Specification, (ACPI), Version 3.0A. SunOS 5.11 31 Oct 2006 tzmon(7d)
Man Page