From: Jonathan McDowell <noodles@earth.li>
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
Ken Moffat <zarniwhoop73@googlemail.com>
Subject: Re: [PATCH v2 0/5] hwmon: k10temp driver improvements
Date: Sun, 19 Jan 2020 10:18:55 +0000 [thread overview]
Message-ID: <20200119101855.GA15446@earth.li> (raw)
In-Reply-To: <20200118172615.26329-1-linux@roeck-us.net>
In article <20200118172615.26329-1-linux@roeck-us.net> (earth.lists.linux-kernel) you wrote:
> This patch series implements various improvements for the k10temp driver.
...
> The voltage and current information is limited to Ryzen CPUs. Voltage
> and current reporting on Threadripper and EPYC CPUs is different, and the
> reported information is either incomplete or wrong. Exclude it for the time
> being; it can always be added if/when more information becomes available.
> Tested with the following Ryzen CPUs:
Tested-By: Jonathan McDowell <noodles@earth.li>
Tested on a Ryzen 7 2700 (patched on top of 5.4.13):
| k10temp-pci-00c3
| Adapter: PCI adapter
| Vcore: +0.80 V
| Vsoc: +0.81 V
| Tdie: +37.0°C
| Tctl: +37.0°C
| Icore: +8.31 A
| Isoc: +6.86 A
Like the 1300X case I see a discrepancy compared to what the nct6779
driver says Vcore is:
| nct6779-isa-0290
| Adapter: ISA adapter
| Vcore: +0.33 V (min = +0.00 V, max = +1.74 V)
| in1: +0.32 V (min = +0.00 V, max = +0.00 V) ALARM
| AVCC: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
| +3.3V: +3.39 V (min = +0.00 V, max = +0.00 V) ALARM
| in4: +1.88 V (min = +0.00 V, max = +0.00 V) ALARM
| in5: +0.82 V (min = +0.00 V, max = +0.00 V) ALARM
| in6: +0.30 V (min = +0.00 V, max = +0.00 V) ALARM
| 3VSB: +3.42 V (min = +0.00 V, max = +0.00 V) ALARM
| Vbat: +3.25 V (min = +0.00 V, max = +0.00 V) ALARM
| in9: +0.00 V (min = +0.00 V, max = +0.00 V)
| in10: +0.22 V (min = +0.00 V, max = +0.00 V) ALARM
| in11: +1.06 V (min = +0.00 V, max = +0.00 V) ALARM
| in12: +1.70 V (min = +0.00 V, max = +0.00 V) ALARM
| in13: +1.04 V (min = +0.00 V, max = +0.00 V) ALARM
| in14: +1.79 V (min = +0.00 V, max = +0.00 V) ALARM
| fan1: 0 RPM (min = 0 RPM)
| fan2: 1708 RPM (min = 0 RPM)
| fan3: 0 RPM (min = 0 RPM)
| fan4: 0 RPM (min = 0 RPM)
| fan5: 0 RPM (min = 0 RPM)
| SYSTIN: +33.0°C (high = +0.0°C, hyst = +0.0°C) ALARM
| sensor = thermistor
| CPUTIN: -62.5°C (high = +80.0°C, hyst = +75.0°C)
| sensor = thermistor
| AUXTIN0: +79.0°C sensor = thermistor
| AUXTIN1: +96.0°C sensor = thermistor
| AUXTIN2: +23.0°C sensor = thermistor
| AUXTIN3: -22.0°C sensor = thermistor
| SMBUSMASTER 0: +39.0°C
| PCH_CHIP_CPU_MAX_TEMP: +0.0°C
| PCH_CHIP_TEMP: +0.0°C
| PCH_CPU_TEMP: +0.0°C
| intrusion0: ALARM
| intrusion1: ALARM
| beep_enable: disabled
I suspect the nct6779 is not reporting correctly (or needs some
configuration) here, as I see that's what Ken is using with his 1300X as
well.
(ASRock B450M Pro4 motherboard, fwiw.)
J.
--
Verily go thee not unto the internet for they will tell you both yea
and nay
next prev parent reply other threads:[~2020-01-19 10:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-18 17:26 [PATCH v2 0/5] hwmon: k10temp driver improvements Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 1/5] hwmon: (k10temp) Use bitops Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 2/5] hmon: (k10temp) Convert to use devm_hwmon_device_register_with_info Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 3/5] hwmon: (k10temp) Report temperatures per CPU die Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 4/5] hwmon: (k10temp) Show core and SoC current and voltages on Ryzen CPUs Guenter Roeck
2020-01-18 17:26 ` [PATCH v2 5/5] hwmon: (k10temp) Don't show temperature limits on Ryzen (Zen) CPUs Guenter Roeck
2020-01-19 0:33 ` [PATCH v2 0/5] hwmon: k10temp driver improvements Ken Moffat
2020-01-19 0:48 ` Guenter Roeck
2020-01-19 1:08 ` Ken Moffat
2020-01-19 3:13 ` Brad Campbell
2020-01-19 10:18 ` Jonathan McDowell [this message]
2020-01-19 15:46 ` Guenter Roeck
2020-01-19 19:38 ` Jonathan McDowell
2020-01-19 13:38 ` Holger Kiehl
2020-01-19 15:49 ` Guenter Roeck
2020-01-21 6:27 ` Andreas Hartmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200119101855.GA15446@earth.li \
--to=noodles@earth.li \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=zarniwhoop73@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.