From: sashiko-bot@kernel.org
To: "Asai Neko" <sugar@sne.moe>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] hwmon: (asus-ec-sensors) add ROG STRIX X670E-A GAMING WIFI
Date: Sun, 30 Aug 2026 13:11:42 +0000 [thread overview]
Message-ID: <20260830131143.410D91F000E9@smtp.kernel.org> (raw)
In-Reply-To: <20260830-asus-x670e-a-hwmon-fix-v1-1-cf0a680ccbe2@sne.moe>
> From: Asai Neko <sugar@sne.moe>
>
> The ROG STRIX X670E-A GAMING WIFI is missing from the driver's DMI
> table. Consequently, the board lookup fails with -ENODEV,
> asus_ec_sensors does not load, and no asusec hwmon device or EC
> temperature readings are available.
>
> Add a board definition using the AMD 600-series register layout and the
> ACPI mutex used by the board firmware. Expose CPU, CPU package,
> motherboard, and VRM temperatures, and add the board to the supported
> hardware documentation.
>
> Before the change, there was no asusec device under /sys/class/hwmon and
> there were no EC readings. After the change, the driver registered four
> sensors with representative readings of 57-61 C for CPU, 68-71 C for
> CPU package, 43-44 C for motherboard, and 49-52 C for VRM.
>
> The readings correlated with nct6775 and k10temp. Repeated polling with
> both hwmon drivers loaded produced no EC access, bank-switch, concurrent
> access, or locking errors.
>
> Tested on an ASUS ROG STRIX X670E-A GAMING WIFI with BIOS 2704.
>
> Signed-off-by: Asai Neko <sugar@sne.moe>
Sashiko has reviewed this patch and found no issues. It looks great!
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260830-asus-x670e-a-hwmon-fix-v1-1-cf0a680ccbe2@sne.moe?part=1
next prev parent reply other threads:[~2026-08-30 13:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-30 13:03 [PATCH] hwmon: (asus-ec-sensors) add ROG STRIX X670E-A GAMING WIFI Asai Neko
2026-08-30 13:03 ` Asai Neko via B4 Relay
2026-08-30 13:11 ` sashiko-bot [this message]
2026-08-31 14:18 ` Eugene Shalygin
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=20260830131143.410D91F000E9@smtp.kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=sugar@sne.moe \
/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.