From: Guenter Roeck <linux@roeck-us.net>
To: Eugene Shalygin <eugene.shalygin@gmail.com>
Cc: Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] hwmon: (asus-ec-sensors) add missing sensors for X570-I GAMING
Date: Wed, 13 Jul 2022 06:37:49 -0700 [thread overview]
Message-ID: <20220713133749.GA3732583@roeck-us.net> (raw)
In-Reply-To: <20220710085539.1682869-1-eugene.shalygin@gmail.com>
On Sun, Jul 10, 2022 at 10:55:38AM +0200, Eugene Shalygin wrote:
> VRM and chipset temperature for ROG STRIX X570-I GAMING were missing
> according to a user contribution to the LHM project [1].
>
> [1] https://github.com/LibreHardwareMonitor/LibreHardwareMonitor/pull/767
>
> Signed-off-by: Eugene Shalygin <eugene.shalygin@gmail.com>
Applied.
Thanks,
Guenter
> ---
> drivers/hwmon/asus-ec-sensors.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/hwmon/asus-ec-sensors.c b/drivers/hwmon/asus-ec-sensors.c
> index 625c2baa35ec..0749cd023a32 100644
> --- a/drivers/hwmon/asus-ec-sensors.c
> +++ b/drivers/hwmon/asus-ec-sensors.c
> @@ -366,9 +366,10 @@ static const struct ec_board_info board_info[] = {
> },
> {
> .board_names = {"ROG STRIX X570-I GAMING"},
> - .sensors = SENSOR_TEMP_T_SENSOR | SENSOR_FAN_VRM_HS |
> - SENSOR_FAN_CHIPSET | SENSOR_CURR_CPU |
> - SENSOR_IN_CPU_CORE,
> + .sensors = SENSOR_TEMP_CHIPSET | SENSOR_TEMP_VRM |
> + SENSOR_TEMP_T_SENSOR |
> + SENSOR_FAN_VRM_HS | SENSOR_FAN_CHIPSET |
> + SENSOR_CURR_CPU | SENSOR_IN_CPU_CORE,
> .mutex_path = ASUS_HW_ACCESS_MUTEX_ASMX,
> .family = family_amd_500_series,
> },
prev parent reply other threads:[~2022-07-13 13:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-10 8:55 [PATCH] hwmon: (asus-ec-sensors) add missing sensors for X570-I GAMING Eugene Shalygin
2022-07-13 13:37 ` Guenter Roeck [this message]
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=20220713133749.GA3732583@roeck-us.net \
--to=linux@roeck-us.net \
--cc=eugene.shalygin@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox