summaryrefslogtreecommitdiffstats
path: root/sys/dev/amdtemp/amdtemp.c
Commit message (Collapse)AuthorAgeFilesLines
* MFC: r273034brueffer2014-10-211-0/+2
| | | | | | Add one more AMD Kaveri APU device ID. Submitted by: Remy Nonnenmacher <remy.nonnenmacher@activnetworks.com>
* MFC: r263169brueffer2014-03-281-0/+4
| | | | | | | Add support for AMD Family 16h (Kabini) sensor devices. PR: 186587 Submitted by: David Rufino <david.rufino at gmail.com>
* Add support for my:jmg2013-08-261-0/+2
| | | | CPU: AMD A10-5700 APU with Radeon(tm) HD Graphics (3393.89-MHz K8-class CPU)
* Use DEVMETHOD_END macro defined in sys/bus.h instead of {0, 0} sentinel on ↵sbz2013-01-301-1/+1
| | | | | | | device_method_t arrays Reviewed by: cognet Approved by: cognet
* This isn't functionally identical. In some cases a hint to disableeadler2012-10-221-0/+3
| | | | | | | | unit 0 would in fact disable all units. This reverts r241856 Approved by: cperciva (implicit)
* Now that device disabling is generic, remove extraneous code from theeadler2012-10-221-3/+0
| | | | | | | | device drivers that used to provide this feature. Reviewed by: des Approved by: cperciva MFC after: 1 week
* - Add support for Family 12h, 14h and 15h processors.jkim2012-02-241-109/+146
| | | | | | | | | | | | | | - Remove all attempts to guess physical temperature using DiodeOffset. There are too many reports that it varies wildly depending on motherboard. Instead, if it is known to scale well and its offset is known from other temperature sensors on board, the user may set "dev.amdtemp.0.sensor_offset" tunable to compensate the difference. Document the caveats in amdtemp(4). - Add a quirk for Socket AM2 Revision G processors. These processors are known to have a different offset according to Linux k8temp driver. - Warn about Family 10h Erratum 319. These processors have broken sensors. - Report temperature in more logical orders under dev.amdtemp node. For example, "dev.amdtemp.0.sensor0.core0" is now "dev.amdtemp.0.core0.sensor0". - Replace K8, K10 and K11 with official processor names in amdtemp(4).
* Restore (undocumented) support for early revisions and add more comments.jkim2009-09-141-43/+77
| | | | Reported by: kris
* Fix typos in comments from the previous commit.jkim2009-09-111-2/+2
|
* Improve amdtemp(4) significantly:jkim2009-09-111-125/+226
| | | | | | | | | | | | | | | - Improve newer AMD processor support (Family 0Fh Revision F and later). - Adjust offset if DiodeOffet is set and valid. Note it is experimental but it seems to give us more realistic temperatures. Newer Linux driver blindly adds 21C for Family 0Fh desktop processors, however. - Always populate dev.cpu and dev.amdtemp sysctl trees regardless of probe order for consistency. Previously, dev.cpu.N.temperature was not populated if amdtemp was loaded later than ACPI CPU driver and temperatures were not accessible from dev.amdtemp.N.sensor0 tree for Family 10h/11h processors. - Read the CPUID from PCI register instead of CPUID instruction to prevent possible revision mismatches on multi-socket system. - Change macros and variables to make them closer to AMD documents. - Fix style(9) nits and improve comments.
* Temporarily revert the new-bus locking for 8.0 release. It will bejhb2009-08-201-2/+0
| | | | | | reintroduced after HEAD is reopened for commits by re@. Approved by: re (kib), attilio
* Make the newbus subsystem Giant free by adding the new newbus sxlock.attilio2009-08-021-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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)
* Fix comment explaining where this driver came from.rpaulo2009-03-131-1/+1
| | | | MFC after: 2 weeks
* Rename all the variables/function names/structs/etc. to reflect therpaulo2009-03-131-86/+121
| | | | | | | driver name change. While there, update copyright. MFC after: 2 weeks
* Rename the k8temp driver to amdtemp.rpaulo2009-03-131-0/+342
MFC after: 2 weeks
OpenPOWER on IntegriCloud