From: Denis Pauk <pauk.denis@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux@roeck-us.net, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
mundanedefoliation@gmail.com
Subject: Re: [PATCH] hwmon: (nct6775) add ASUS CROSSHAIR VIII/TUF/ProArt B550M
Date: Tue, 15 Nov 2022 00:16:24 +0200 [thread overview]
Message-ID: <20221115001322.31d4f44d@gmail.com> (raw)
In-Reply-To: <20221114214456.3891-1-pauk.denis@gmail.com>
Hi,
Patch is tested with "TUF GAMING B550M-PLUS WIFI II".
I have checked other boards by comparing methods implementations in UEFI
firmware's from ASUS support site.
On Mon, 14 Nov 2022 23:44:56 +0200
Denis Pauk <pauk.denis@gmail.com> wrote:
> Boards such as
> * ProArt B550-CREATOR
> * ProArt Z490-CREATOR 10G
> * ROG CROSSHAIR VIII EXTREME
> * ROG CROSSHAIR VIII HERO (WI-FI)
> * TUF GAMING B550M-E
> * TUF GAMING B550M-E (WI-FI)
> * TUF GAMING B550M-PLUS WIFI II
> have got a nct6775 chip, but by default there's no use of it
> because of resource conflict with WMI method.
>
> This commit adds such boards to the WMI monitoring list.
>
> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=204807
> Signed-off-by: Denis Pauk <pauk.denis@gmail.com>
> Reported-by: yutesdb <mundanedefoliation@gmail.com>
> Tested-by: yutesdb <mundanedefoliation@gmail.com>
> ---
> drivers/hwmon/nct6775-platform.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> diff --git a/drivers/hwmon/nct6775-platform.c
> b/drivers/hwmon/nct6775-platform.c index 41c97cfacfb8..50fe9533cf43 100644
> --- a/drivers/hwmon/nct6775-platform.c
> +++ b/drivers/hwmon/nct6775-platform.c
> @@ -1043,7 +1043,9 @@ static struct platform_device *pdev[2];
>
> static const char * const asus_wmi_boards[] = {
> "PRO H410T",
> + "ProArt B550-CREATOR",
> "ProArt X570-CREATOR WIFI",
> + "ProArt Z490-CREATOR 10G",
> "Pro B550M-C",
> "Pro WS X570-ACE",
> "PRIME B360-PLUS",
> @@ -1055,8 +1057,10 @@ static const char * const asus_wmi_boards[] = {
> "PRIME X570-P",
> "PRIME X570-PRO",
> "ROG CROSSHAIR VIII DARK HERO",
> + "ROG CROSSHAIR VIII EXTREME",
> "ROG CROSSHAIR VIII FORMULA",
> "ROG CROSSHAIR VIII HERO",
> + "ROG CROSSHAIR VIII HERO (WI-FI)",
> "ROG CROSSHAIR VIII IMPACT",
> "ROG STRIX B550-A GAMING",
> "ROG STRIX B550-E GAMING",
> @@ -1080,8 +1084,11 @@ static const char * const asus_wmi_boards[] = {
> "ROG STRIX Z490-G GAMING (WI-FI)",
> "ROG STRIX Z490-H GAMING",
> "ROG STRIX Z490-I GAMING",
> + "TUF GAMING B550M-E",
> + "TUF GAMING B550M-E (WI-FI)",
> "TUF GAMING B550M-PLUS",
> "TUF GAMING B550M-PLUS (WI-FI)",
> + "TUF GAMING B550M-PLUS WIFI II",
> "TUF GAMING B550-PLUS",
> "TUF GAMING B550-PLUS WIFI II",
> "TUF GAMING B550-PRO",
prev parent reply other threads:[~2022-11-14 22:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 21:44 [PATCH] hwmon: (nct6775) add ASUS CROSSHAIR VIII/TUF/ProArt B550M Denis Pauk
2022-11-14 22:16 ` Denis Pauk [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=20221115001322.31d4f44d@gmail.com \
--to=pauk.denis@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mundanedefoliation@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox