don't do mutex locking around kthread_create() call.

Reported by: Maxim Maximov <mcsi__at__mcsi.pp.ru>

Implement passive cooling. It is enabled for tz0 by default where
it is available.

Reviewed by: njl

Set the start of the cooling time later on, when we're actually performing
the switch. Other interim tests (i.e., for minimum runtime) could
invalidate the start time. This fixes transitions to coo

Set the start of the cooling time later on, when we're actually performing
the switch. Other interim tests (i.e., for minimum runtime) could
invalidate the start time. This fixes transitions to cooler states in that
now they go to the next active state (_AC0 -> _AC1) instead of going
straight to off (_AC0 -> off).

Submitted by: Alexandre "Sunny" Kovalenko (Alex.Kovalenko / verizon.net)

show more ...

Initialize the flags value properly. We used to do this in acpi_tz_all_off()
but that function has been removed. This avoids a potential unnecessary
fan switch on boot. Also remove some commented

Initialize the flags value properly. We used to do this in acpi_tz_all_off()
but that function has been removed. This avoids a potential unnecessary
fan switch on boot. Also remove some commented out code.

MFC after: 3 days

show more ...

Clean up rev 1.49 by using the temperature conversion for _PSV also and
wrap a long line.

Don't change the state of the system in acpi_tz_establish(). Before, we
would turn off all fans when initializing a zone. However, the HP Omnibook
500 generates a notify saying the zone needs to be

Don't change the state of the system in acpi_tz_establish(). Before, we
would turn off all fans when initializing a zone. However, the HP Omnibook
500 generates a notify saying the zone needs to be re-evaluated whenever
its fan is switched on or off. This produced an infinite loop. Also, note
that running _SCP can generate the same notify.

Since we need to make sure old fan references are turned off when getting
new ones, run acpi_tz_monitor() first. This will turn off any unneeded
fans. Then, check for new settings. After that, run acpi_tz_monitor()
again to turn on/off any fans referenced by the new settings.

Tested by: brooks

show more ...

Add a suffix descriptor for the acpi thermal values as a hint for the userland
sysctl tool to print a more readable value for temperatures.

MPSAFE locking

* Restructure the event handling path. acpi_tz_thread() now calls
acpi_tz_timeout() any time an event occurs. acpi_tz_timeout() checks
the flags and calls acpi_tz_power_profile(

MPSAFE locking

* Restructure the event handling path. acpi_tz_thread() now calls
acpi_tz_timeout() any time an event occurs. acpi_tz_timeout() checks
the flags and calls acpi_tz_power_profile(), acpi_tz_establish(), and
acpi_tz_monitor() as appropriate. Notifies only do a wakeup and let
acpi_tz_thread() do the actual work. This path is cleaner and allows
locking since the call path is now always a D.A.G.
* Add the acpi_tz_signal() function to set flags and wake the thread.
* Remove the tz_tmp_updating flag since calls are serialized by
acpi_tz_thread().
* Remove Giant locking.

show more ...

Add missing <sys/module.h> includes

Remove call to _INI for thermal devices. ACPI-CA now calls _INI for
Devices, ThermalZones, and Processors.

Add back sys/reboot.h which is needed.

Make unnecessary globals static and remove unused includes.

Pointed out by: cscout

Remove a check for the return value added in rev 1.41. It's not an error
to fail to turn off a fan, since the case is that it's usually already off.

Add MODULE_DEPEND entries so some of these drivers can eventually be
loaded separately from ACPI (i.e., embedded use).

Replace more ad-hoc versions of acpi_GetReference(). Since the type of
Reference objects changed from ACPI_TYPE_ANY to ACPI_TYPE_LOCAL_REFERENCE
in Oct. 2002, this may help systems where switching t

Replace more ad-hoc versions of acpi_GetReference(). Since the type of
Reference objects changed from ACPI_TYPE_ANY to ACPI_TYPE_LOCAL_REFERENCE
in Oct. 2002, this may help systems where switching the cooler on failed.
We support both types for now until this sorts out.

show more ...

A user can set tz_requested via the hw.acpi.thermal.tzX.active sysctl.
The previous logic meant that if a user sets it to a minimal cooling value
acpi_thermal will not use higher cooling levels. Rev

A user can set tz_requested via the hw.acpi.thermal.tzX.active sysctl.
The previous logic meant that if a user sets it to a minimal cooling value
acpi_thermal will not use higher cooling levels. Reverse the logic so that
the user requesting a level (say, 2) also gets 0 - 1 also.

PR: kern/61592
Submitted by: Andrew Thompson <andy@fud.org.nz>

show more ...

Change to acpi_{Get,Set}Integer to provide both methods. Convert all
callers to the new API.

Submitted by: Mark Santcroos <marks@ripe.net>

Call _INI on Thermal Zones as well as devices.

Notify the user (at kern.emerg) that the system will be shutting down if
it is still above the critical temperature on the next poll cycle. This
is a 10 second advance notice by default. Document t

Notify the user (at kern.emerg) that the system will be shutting down if
it is still above the critical temperature on the next poll cycle. This
is a 10 second advance notice by default. Document the private
(non-standard) notify we will be using with devd(8).

show more ...

If the temperature is at _HOT or _CRT for 3 sequential readings, shutdown
the system. Also, decrease the poll interval to 10 seconds from 30
seconds. This is needed because some systems will report

If the temperature is at _HOT or _CRT for 3 sequential readings, shutdown
the system. Also, decrease the poll interval to 10 seconds from 30
seconds. This is needed because some systems will report an invalid high
temperature for one poll cycle. It is suspected this is due to the
embedded controller timing out. A typical value is 138C for one cycle on a
system that is otherwise 65C. This prevents the system from prematurely
shutting down after one invalid reading. It will still shut down after 30
seconds of high temperature, which is the same as previous default
behavior.

Tested by: Scott Lambert <lambert AT lambertfam.org>

show more ...

Bite the bullet and uncomment the shutdown() in case we hit the _CRT or
_HOT temperatures. We have to do this at some point to keep from getting
imp(tm) melted hardware.

Use the appropriate values for the notifies. No change in behavior
since both notifies result in the same function being called.

Found by: documenting the code

Add devctl(4) notify support to ACPI. Various subsystems now notify
userland whenever events occur. See the example in devd.conf below
to see how to use it.

Consistently print attach messages.

Style and whitespace changes. Also, make the ivar functions non-inline
since inlining failed due to the size of BUS_*