| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
A warning is emitted again if the temperature became briefly valid
meanwhile. This avoids spamming the user when the sensor is broken.
Other values (ie. not _TMP) always raise a warning.
|
|
|
|
|
|
|
| |
device_method_t arrays
Reviewed by: cognet
Approved by: cognet
|
|
|
|
|
|
|
|
| |
ASUS P8Z77-V board reports _AC2, _AC3 and _AC4 setpoints as 0C. With active
cooling already automatically set to _AC2, that still caused driver to print
two useless lines about temperature above _AC3 and _AC4 every ten seconds.
Three setponts of 0C is probably a board bug, but the same spam could happen
also in correct case if system is runnign not with the lowest cooling level.
|
|
|
|
|
|
| |
... and not just _ALx as it is now.
MFC after: 20 days
|
|
|
|
|
| |
Approved by: jhb
MFC after: 3 days
|
|
|
|
|
|
| |
Submitted by: Oliver Pinter <oliver.pntr@gmail.com>
Approved by: jhb
MFC after: 3 days
|
| |
|
|
|
|
|
| |
Reported by: Taku YAMAMOTO < taku AT tackymt DOT homeip DOT net >
Tested by: Nick Ulen < uncle AT wolfman DOT devio DOT us >
|
|
|
|
|
|
|
| |
This got broken after r217586.
Pointy hat: to me
Tested by: David Wolfskill < davit AT catwhisker DOT org >
|
|
|
|
|
|
|
|
|
|
| |
via %s
Most of the cases looked harmless, but this is done for the sake of
correctness. In one case it even allowed to drop an intermediate buffer.
Found by: clang
MFC after: 2 week
|
|
|
|
|
|
| |
reintroduced after HEAD is reopened for commits by re@.
Approved by: re (kib), attilio
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
_TSP, _TC1 and _TC2.
Contirmed by: "Alexandre \"Sunny\" Kovalenko" <alex.kovalenko_at_verizon.net>
Reviewed by: njl
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
| |
specify temperature.
Reviewed by: njl
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
to add the RD flag. Also, the debug node does not need to be writable.
|
| |
|
| |
|
|
|
|
| |
it makes CPU freq transition smooth.
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
| |
Reported by: Maxim Maximov <mcsi__at__mcsi.pp.ru>
|
|
|
|
|
|
| |
it is available.
Reviewed by: njl
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
wrap a long line.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
sysctl tool to print a more readable value for temperatures.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* 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.
|
| |
|
|
|
|
| |
Devices, ThermalZones, and Processors.
|
| |
|
|
|
|
| |
Pointed out by: cscout
|
|
|
|
| |
to fail to turn off a fan, since the case is that it's usually already off.
|
|
|
|
| |
loaded separately from ACPI (i.e., embedded use).
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
|
| |
callers to the new API.
Submitted by: Mark Santcroos <marks@ripe.net>
|
| |
|
|
|
|
|
|
| |
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).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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>
|
|
|
|
|
| |
_HOT temperatures. We have to do this at some point to keep from getting
imp(tm) melted hardware.
|
|
|
|
|
|
| |
since both notifies result in the same function being called.
Found by: documenting the code
|