From: Denis Pauk <pauk.denis@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: pauk.denis@gmail.com, "Joel Wirāmu Pauling" <jwp@redhat.com>,
"Guenter Roeck" <linux@roeck-us.net>,
"Jean Delvare" <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] hwmon: (nct6775) add ProArt X570-CREATOR WIFI.
Date: Mon, 25 Oct 2021 22:47:48 +0300 [thread overview]
Message-ID: <20211025194748.6784-1-pauk.denis@gmail.com> (raw)
ASUS ProArt X570-CREATOR WIFI board has got an nct6775 chip, but by default
there's no use of it because of resource conflict with WMI method.
This commit adds ProArt X570-CREATOR WIFI to the list of boards that can be
monitored using ASUS WMI.
Tested on:
```
Base Board Information
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ProArt X570-CREATOR WIFI
Version: Rev X.0x
BIOS Information
Vendor: American Megatrends Inc.
Version: 0402
Release Date: 08/04/2021
```
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=204807
Signed-off-by: Denis Pauk <pauk.denis@gmail.com>
Tested-by: Joel Wirāmu Pauling <jwp@redhat.com>
---
drivers/hwmon/nct6775.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/hwmon/nct6775.c b/drivers/hwmon/nct6775.c
index f345e1902ad9..93dca471972e 100644
--- a/drivers/hwmon/nct6775.c
+++ b/drivers/hwmon/nct6775.c
@@ -4986,6 +4986,7 @@ static int __init nct6775_find(int sioaddr, struct nct6775_sio_data *sio_data)
static struct platform_device *pdev[2];
static const char * const asus_wmi_boards[] = {
+ "ProArt X570-CREATOR WIFI",
"Pro WS X570-ACE",
"PRIME B360-PLUS",
"PRIME B460-PLUS",
base-commit: c0d79987a0d82671bff374c07f2201f9bdf4aaa2
prerequisite-patch-id: e807e002a40988118b5a99c3a5d7362578e3ed54
prerequisite-patch-id: 9a221a9db6d74526910c26c9b41e34c480105ca3
--
2.33.0
reply other threads:[~2021-10-25 20:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20211025194748.6784-1-pauk.denis@gmail.com \
--to=pauk.denis@gmail.com \
--cc=jdelvare@suse.com \
--cc=jwp@redhat.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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;
as well as URLs for NNTP newsgroup(s).