Hoan Tran [Thu, 13 Aug 2020 00:02:00 +0000 (17:02 -0700)]
Add ISA ACPI sensor driver name support
ACPI hwmon sensor driver name has a different format such as
APMC0D29:00
APMC0D29:01
compared with DTB. This patch supports this format and gives
the correct device address as below
apm_xgene-isa-0000 => APMC0D29:00
Adapter: ISA adapter
SoC Temperature: +35.0°C
CPU power: 11.00 W
IO power: 20.00 W
apm_xgene-isa-0001 => APMC0D29:01
Adapter: ISA adapter
SoC Temperature: +33.0°C
CPU power: 13.00 W
IO power: 23.83 W
Jean Delvare [Tue, 12 May 2020 14:23:08 +0000 (16:23 +0200)]
sensors-detect: Move Winbond WPCD377I to the non-hwmon table
Move the detection entry for the Winbond WPCD377I to the
@non_hwmon_chip_ids table, where it belongs. This saves one line, and
more importantly prevents "not-a-sensor" from being accidentally
added to the list of kernel drivers.
Jean Delvare [Tue, 12 May 2020 14:22:06 +0000 (16:22 +0200)]
sensors-detect: Fix the driver for Nuvoton W83677HG-I
Originally, support for the Nuvoton W83677HG-I and derivatives was
first added to the w83627ehf driver, so that's the driver recommended
by sensors-detect. Later, support for the same device was added to
the nct6775 driver. In kernel v5.6, support was removed from the
w83627ehf driver to get rid of the duplicate code.
So sensors-detect should now point users of this device to the
nct6775 driver. We can't do that for very old kernels though, as this
driver did not exist back then. I chose v3.10 for the cut-over, as
this is when support for the Nuvoton W83677HG-I was finalized in the
nct6775 driver, at least according to git log.
This is actually a config for TUF GAMING X570-PLUS (Wi-Fi) but I'm
quite sure these two motherboards share sensors configuration.
[olysonek: reformatted description, replaced the config with the
version from
https://github.com/lm-sensors/lm-sensors/pull/216#issuecomment-589585372]
chris-est [Thu, 24 Oct 2019 17:42:34 +0000 (19:42 +0200)]
sensors-detect: add support for FTS Teutates Chip
This patch adds support for the FTS Teutates Chip,
used on Fujitsu Mainboards for Intel Skylake and later Chipsets.
It is based on a patch from Fujitsu and was tested on a D-3446-S Mainboard.
The corresponding kernel module can be found here [1].
This is a revised version of an earlier pull request [2].
Ondřej Lysoněk [Thu, 17 Oct 2019 13:14:16 +0000 (15:14 +0200)]
Replace svn keywords with LM_SENSORS_VER constant
The keywords Revision, Date and Id were being expanded by Subversion
way back when the project was being maintained in Subversion. Now when
the project is maintained in git, the keywords are no longer expanded
and appear e.g. in the output of sensors-detect literally.
Drop the keywords, or replace them with LM_SENSORS_VER where
applicable.
The value of the constant will have to be updated manually every time
a new release is made.
Inspired by a similar change in i2c-tools (commit daa430031ffd;
thanks, Jean).
Ondřej Lysoněk [Thu, 17 Oct 2019 08:07:21 +0000 (10:07 +0200)]
sensors-detect: Fix printing CPU info on ppc and arm
The format of /proc/cpuinfo on other arches is different from the
format on x86. Modify the print_cpu_info function to handle arm and
ppc.
This change also eliminates Perl warnings caused by non-existent
elements in the %cpu hash:
Use of uninitialized value in concatenation (.) or string at
./prog/detect/sensors-detect line 3124.
Based on a patch from Changqing Li <changqing.li@windriver.com>,
GitHub PR: https://github.com/lm-sensors/lm-sensors/pull/168
pablow1422 [Tue, 8 Oct 2019 00:03:53 +0000 (21:03 -0300)]
Better scaling for +12V reading
Apparently, Gigabyte uses a 8kOhm and a 2.7kOhm resistor for the
voltage divider (both are commercially available SMD resistors). It
matches my BIOS reading.
Applied from PR
https://github.com/lm-sensors/lm-sensors/pull/203
makefile: use target arch when determining what programs to compile
To better support cross-compilation, the Makefile should detect the
compiler's target architecture instead of using `uname -m`, which
returns the host architecture. This approach uses the `gcc`/`clang`
compatible `-dumpmachine` option.
Cross-compilation worked but because of this bug, `isadump` and
`isaset` x86 ISA specific tools were built for PCC and ARM.
This run-time issue became a compile-time issue when `glibc` 2.30
removed the `sys/io.h` I/O port functions on ARM.
Also renamed `MACHINE` to `ARCH` to match cross-compiler conventions
for specifying the target architecture. For example,
Lech Perczak [Sun, 23 Jun 2019 21:53:07 +0000 (23:53 +0200)]
configs: fix Supermicro X7DCL VTT limits
According to:
"Quad-Core Intel® Xeon(R) Processor 5400 Series Electrical Specifications"
(table 2-12), FSB termination voltage of the CPUs (VTT) is 1.1V +/-5%.
Initial configuration set it to 1.2V - fix that.
Michal Simek [Thu, 20 Jun 2019 11:30:35 +0000 (13:30 +0200)]
sensors: Scale voltage and current values
scale_value is generic function for scaling values. There is a lower
resolution then json format provides for voltage and current.
The patch is calling scale_value() and showing values with higher
resolution.
For example on Xilinx ZynqMP platform:
ina226-i2c-3-41
Adapter: i2c-0-mux (chan_id 0)
in0: 2.00 mV
in1: 848.00 mV
power1: 287.50 mW
curr1: 330.00 mA
Ondřej Lysoněk [Sun, 5 May 2019 09:17:45 +0000 (11:17 +0200)]
sensors: json: Do not print a stray comma
Previously, if an error happened when reading the value of a subfeature,
subCnt would get incremented and a stray comma would get printed in the
following iteration, even though nothing was printed in the previous
iteration. This would produce a syntactically incorrect JSON.
This is based on a patch from the su8 user on GitHub.
projects / thirdparty / lm-sensors.git / log
