- 10 10月, 2009 2 次提交
-
-
由 Luca Tettamanti 提交于
On newer ASUS boards (e.g. P7P55D) the EC (that - among other things - is responsible for updating the readings from the hwmon sensors) is disabled by default since ASUS detected conflict with some tools under Windows. The following patch checks the state of the EC and enable it if needed; under Linux, native drivers are locked out from ACPI owned resources so there's no risk of conflict. Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com> Tested-by: NRobert Hancock <hancockrwd@gmail.com> Tested-by: NThomas Backlund <tmb@mandriva.org> Signed-off-by: NJean Delvare <khali@linux-fr.org>
-
由 Luca Tettamanti 提交于
Refactor the code of the new style interface around GGRP (enumeration) and GITM (read) helpers to mimic ASL code. Also switch the read path to use dynamic buffers (handled by ACPI core) since ASUS expanded the return buffer (ASBF) in newer boards (e.g. P7P55D). Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com> Tested-by: NRobert Hancock <hancockrwd@gmail.com> Tested-by: NThomas Backlund <tmb@mandriva.org> Signed-off-by: NJean Delvare <khali@linux-fr.org>
-
- 28 7月, 2009 1 次提交
-
-
由 Luca Tettamanti 提交于
On newer Asus boards the "upper" limit of a sensor is encoded as delta from the "lower" limit. Fix the driver to correctly handle this case. Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com> Tested-by: NAlex Macfarlane Smith <nospam@archifishal.co.uk> Signed-off-by: NJean Delvare <khali@linux-fr.org>
-
- 09 5月, 2009 1 次提交
-
-
由 Luca Tettamanti 提交于
atk_sensor_type is only used when DEBUG is defined. Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com> Signed-off-by: NJean Delvare <khali@linux-fr.org>
-
- 07 4月, 2009 1 次提交
-
-
由 Luca Tettamanti 提交于
Asus boards have an ACPI interface for interacting with the hwmon (fan, temperatures, voltages) subsystem; this driver exposes the relevant information via the standard sysfs interface. There are two different ACPI interfaces: - an old one (based on RVLT/RFAN/RTMP) - a new one (GGRP/GITM) Both may be present but there a few cases (my board, sigh) where the new interface is just an empty stub; the driver defaults to the old one when both are present. The old interface has received a considerable testing, but I'm still awaiting confirmation from my tester that the new one is working as expected (hence the debug code is still enabled). Currently all the attributes are read-only, though a (partial) control should be possible with a bit more work. Signed-off-by: NLuca Tettamanti <kronos.it@gmail.com> Signed-off-by: NHans de Goede <hdegoede@redhat.com> Signed-off-by: NJean Delvare <khali@linux-fr.org>
-