#
d8c616ae |
| 22-Dec-2000 |
Takanori Watanabe <takawata@FreeBSD.org> |
Add ACPI AC adaptor and ACPI Control Method Battery. And install notify handler for thermal zone .
|
#
0ae55423 |
| 08-Dec-2000 |
Mike Smith <msmith@FreeBSD.org> |
- Convert a lot of homebrew debugging output to use the ACPI CA debugging infrastructure. It's not perfect, but it's a lot better than what we've been using so far. The following rules apply
- Convert a lot of homebrew debugging output to use the ACPI CA debugging infrastructure. It's not perfect, but it's a lot better than what we've been using so far. The following rules apply to this: o BSD component names should be capitalised o Layer names should be taken from the non-CA set for now. We may elect to add some new BSD-specific layers later.
- Make it possible to turn off selective debugging flags or layers by listing them in debug.acpi.layer or debug.acpi.level prefixed with !.
- Fully implement support for avoiding nodes in the ACPI namespace. Nodes may be listed in the debug.acpi.avoid environment variable; these nodes and all their children will be ignored (although still scanned over) by ACPI functions which scan the namespace. Multiple nodes can be specified, separated by whitespace.
- Implement support for selectively disabling ACPI subsystem components via the debug.acpi.disable environment variable. The following components can be disabled: o bus creation/scanning of the ACPI 'bus' o children attachment of children to the ACPI 'bus' o button the acpi_button control-method button driver o ec the acpi_ec embedded-controller driver o isa acpi replacement of PnP BIOS for ISA device discovery o lid the control-method lid switch driver o pci pci root-bus discovery o processor CPU power/speed management o thermal system temperature detection and control o timer ACPI timecounter Multiple components may be disabled by specifying their name(s) separated by whitespace.
- Add support for ioctl registration. ACPI subsystem components may register ioctl handlers with the /dev/acpi generic ioctl handler, allowing us to avoid the need for a multitude of /dev/acpi* control devices, etc.
show more ...
|
Revision tags: release/4.2.0 |
|
#
15e32d5d |
| 28-Oct-2000 |
Mike Smith <msmith@FreeBSD.org> |
Initial FreeBSD OSPM (operating system power management) modules for ACPICA. Most of these are still works in progress. Support exists for:
- Fixed feature and control method power, lid and sleep
Initial FreeBSD OSPM (operating system power management) modules for ACPICA. Most of these are still works in progress. Support exists for:
- Fixed feature and control method power, lid and sleep buttons. - Detection of ISA PnP devices using ACPI namespace. - Detection of PCI root busses using ACPI namespace. - CPU throttling and sleep states (incomplete) - Thermal monitoring and cooling control (incomplete) - Interface to platform embedded controllers (mostly complete) - ACPI timer (incomplete) - Simple userland control of sleep states. - Shutdown and poweroff.
show more ...
|
#
cbd59a4f |
| 08-Sep-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC from head@196987
|
#
a56fe095 |
| 20-Aug-2009 |
John Baldwin <jhb@FreeBSD.org> |
Temporarily revert the new-bus locking for 8.0 release. It will be reintroduced after HEAD is reopened for commits by re@.
Approved by: re (kib), attilio
|
#
11e9b8ba |
| 04-Aug-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- MFC @196061
|
#
444b9186 |
| 02-Aug-2009 |
Attilio Rao <attilio@FreeBSD.org> |
Make the newbus subsystem Giant free by adding the new newbus sxlock. The newbus lock is responsible for protecting newbus internIal structures, device states and devclass flags. It is necessary to h
Make the newbus subsystem Giant free by adding the new newbus sxlock. The newbus lock is responsible for protecting newbus internIal structures, device states and devclass flags. It is necessary to hold it when all such datas are accessed. For the other operations, softc locking should ensure enough protection to avoid races.
Newbus lock is automatically held when virtual operations on the device and bus are invoked when loading the driver or when the suspend/resume take place. For other 'spourious' operations trying to access/modify the newbus topology, newbus lock needs to be automatically acquired and dropped.
For the moment Giant is also acquired in some key point (modules subsystem) in order to avoid problems before the 8.0 release as module handlers could make assumptions about it. This Giant locking should go just after the release happens.
Please keep in mind that the public interface can be expanded in order to provide more support, if there are really necessities at some point and also some bugs could arise as long as the patch needs a bit of further testing.
Bump __FreeBSD_version in order to reflect the newbus lock introduction.
Reviewed by: ed, hps, jhb, imp, mav, scottl No answer by: ariff, thompsa, yongari Tested by: pho, G. Trematerra <giovanni dot trematerra at gmail dot com>, Brandon Gooch <jamesbrandongooch at gmail dot com> Sponsored by: Yahoo! Incorporated Approved by: re (ksmith)
show more ...
|
#
7e857dd1 |
| 12-Jun-2009 |
Oleksandr Tymoshenko <gonzo@FreeBSD.org> |
- Merge from HEAD
|
#
129d3046 |
| 05-Jun-2009 |
Jung-uk Kim <jkim@FreeBSD.org> |
Import ACPICA 20090521.
|
#
aaac7452 |
| 03-Jun-2009 |
Jung-uk Kim <jkim@FreeBSD.org> |
Chase ACPICA API changes (for kernel and boot loader).
|
Revision tags: release/7.2.0_cvs, release/7.2.0, release/7.1.0_cvs, release/7.1.0, release/6.4.0_cvs, release/6.4.0 |
|
#
edbb0293 |
| 25-Apr-2008 |
Rui Paulo <rpaulo@FreeBSD.org> |
Initialize tz_active to a new constant TZ_ACTIVE_UNKNOWN and make no assumptions about the state of the cooling devices. Instead, switch them off on init and, only after that, we are in TZ_ACTIVE_NON
Initialize tz_active to a new constant TZ_ACTIVE_UNKNOWN and make no assumptions about the state of the cooling devices. Instead, switch them off on init and, only after that, we are in TZ_ACTIVE_NONE.
Submited by: Andriy Gapon <avg at icyb.net.ua> Reviewed by: njl
show more ...
|
Revision tags: release/7.0.0_cvs, release/7.0.0 |
|
#
d1c0178b |
| 16-Feb-2008 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Create a thread to handle passive cooling for 1st zone which has _PSV, _TSP, _TC1 and _TC2.
Contirmed by: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko_at_verizon.net> Reviewed by: njl MFC after:
Create a thread to handle passive cooling for 1st zone which has _PSV, _TSP, _TC1 and _TC2.
Contirmed by: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko_at_verizon.net> Reviewed by: njl MFC after: 1 week
show more ...
|
#
9e684e54 |
| 16-Feb-2008 |
Rui Paulo <rpaulo@FreeBSD.org> |
Allow the user to override the current active cooling state if state is currently TZ_ACTIVE_NONE.
Submitted by: Andriy Gapon <avg at icyb.net.ua> Reviewed by: njl (mentor) Approved by: njl (
Allow the user to override the current active cooling state if state is currently TZ_ACTIVE_NONE.
Submitted by: Andriy Gapon <avg at icyb.net.ua> Reviewed by: njl (mentor) Approved by: njl (mentor) Requested by: njl (mentor) MFC after: 3 days
show more ...
|
Revision tags: release/6.3.0_cvs, release/6.3.0 |
|
#
c903c5fb |
| 31-Dec-2007 |
John Baldwin <jhb@FreeBSD.org> |
Use devclass_get_count() instead of devclass_get_maxunit() to get the correct number of acpi_thermalX devices. Having this wrong caused the acpi_thermal thread to realloc the array of devices on eac
Use devclass_get_count() instead of devclass_get_maxunit() to get the correct number of acpi_thermalX devices. Having this wrong caused the acpi_thermal thread to realloc the array of devices on each loop iteration.
MFC after: 1 week PR: kern/118497 Submitted by: Pasi Parviainen
show more ...
|
#
0c3e489d |
| 24-Dec-2007 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Add sysctl mibs for _TSP, _TC1 and _TC2 which is user overridable but is blocked on user_override mib. Not a few people want to use a passive cooling without their ACPI BIOS support.
Reviewed by: njl
|
#
3745c395 |
| 21-Oct-2007 |
Julian Elischer <julian@FreeBSD.org> |
Rename the kthread_xxx (e.g. kthread_create()) calls to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it t
Rename the kthread_xxx (e.g. kthread_create()) calls to kproc_xxx as they actually make whole processes. Thos makes way for us to add REAL kthread_create() and friends that actually make theads. it turns out that most of these calls actually end up being moved back to the thread version when it's added. but we need to make this cosmetic change first.
I'd LOVE to do this rename in 7.0 so that we can eventually MFC the new kthread_xxx() calls.
show more ...
|
#
4d44d817 |
| 05-Mar-2007 |
Nate Lawson <njl@FreeBSD.org> |
Check the _TMP value for sanity also. On some systems (HP NX laptops), the EC occasionally times out and provides bogus values (3000C). This change prevents those systems from prematurely shutting
Check the _TMP value for sanity also. On some systems (HP NX laptops), the EC occasionally times out and provides bogus values (3000C). This change prevents those systems from prematurely shutting down while we work on the underlying problem. Also, bump the sanity value to 0...200C from 0...150C.
show more ...
|
Revision tags: release/6.2.0_cvs, release/6.2.0 |
|
#
d45564dc |
| 03-Sep-2006 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
Support Celsius (nn.nC), Fahrenheit (nn.nF) and Kelvin (nnnn) to specify temperature.
Reviewed by: njl MFC after: 3 days
|
#
cf90f178 |
| 25-Jul-2006 |
Nate Lawson <njl@FreeBSD.org> |
Add support for overriding the values for _CRT, _HOT, and _PSV via sysctl. Prevent casual modification by requiring hw.acpi.thermal.user_override to be set first. Fix printing of negative temperatur
Add support for overriding the values for _CRT, _HOT, and _PSV via sysctl. Prevent casual modification by requiring hw.acpi.thermal.user_override to be set first. Fix printing of negative temperatures in the K->C conversion. Document the remaining thermal sysctls.
MFC after: 3 days
show more ...
|
#
197b4dcc |
| 10-Jun-2006 |
Nate Lawson <njl@FreeBSD.org> |
Minor sysctl cleanup. The RW flag means read|write and so it is redundant to add the RD flag. Also, the debug node does not need to be writable.
|
Revision tags: release/5.5.0_cvs, release/5.5.0, release/6.1.0_cvs, release/6.1.0, release/6.0.0_cvs, release/6.0.0 |
|
#
2a191126 |
| 11-Sep-2005 |
David E. O'Brien <obrien@FreeBSD.org> |
Canonize the include of acpi.h.
|
#
83582626 |
| 26-Aug-2005 |
Alexander Kabaev <kan@FreeBSD.org> |
Unbreak compiles with ACPI_DEBUG.
|
#
b3130703 |
| 25-Aug-2005 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
get current temperature from _TMP during passive cooling is active. it makes CPU freq transition smooth.
|
#
9b96aa9a |
| 25-Aug-2005 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
initialize only ACPI_BUFFER to avoid race condition with passive cooling thread which refers psv, tc1, tc2 and tsp. The previous code made the period where sc->tz_zone.tsp was zero, and it caused pa
initialize only ACPI_BUFFER to avoid race condition with passive cooling thread which refers psv, tc1, tc2 and tsp. The previous code made the period where sc->tz_zone.tsp was zero, and it caused panic at msleep().
Reported by: keramida Tested by: keramida
show more ...
|
#
c219fd0c |
| 17-Aug-2005 |
Hajimu UMEMOTO <ume@FreeBSD.org> |
don't raise cpu speed over the value when passive cooling is in effect. since CPU speed is restored by degrees, we cannot use the facility of saving cpu speed by CPUFREQ_set() effectively. so, we ne
don't raise cpu speed over the value when passive cooling is in effect. since CPU speed is restored by degrees, we cannot use the facility of saving cpu speed by CPUFREQ_set() effectively. so, we need to save the value when passive cooling is in effect.
Repoeted by: Kevin Oberman <oberman__at__es.net>
show more ...
|