From: Guenter Roeck <linux@roeck-us.net>
To: Oleksandr Natalenko <oleksandr@natalenko.name>
Cc: linux-kernel@vger.kernel.org,
Eugene Shalygin <eugene.shalygin@gmail.com>,
Denis Pauk <pauk.denis@gmail.com>,
matt-testalltheway <sefoci9222@rerunway.com>,
Kamil Dudka <kdudka@redhat.com>,
Robert Swiecki <robert@swiecki.net>,
Kamil Pietrzak <kpietrzak@disroot.org>, Igor <igor@svelig.com>,
Tor Vic <torvic9@mailbox.org>, Poezevara <nephartyz@gmail.com>,
Andy Shevchenko <andriy.shevchenko@intel.com>,
Jean Delvare <jdelvare@suse.com>,
linux-hwmon@vger.kernel.org
Subject: Re: [PATCH 1/3] hwmon: (nct6775) add Pro WS X570-ACE
Date: Fri, 8 Oct 2021 07:13:34 -0700 [thread overview]
Message-ID: <20211008141334.GA2079491@roeck-us.net> (raw)
In-Reply-To: <20211003133344.9036-2-oleksandr@natalenko.name>
On Sun, Oct 03, 2021 at 03:33:42PM +0200, Oleksandr Natalenko wrote:
> ASUS Pro WS X570-ACE board has got an nct6775 chip, but by default
> there's no use of it because of resource conflict:
>
> ```
> ACPI Warning: SystemIO range 0x0000000000000295-0x0000000000000296 conflicts with OpRegion 0x0000000000000290-0x0000000000000299 (\AMW0.SHWM) (20210604/utaddress-204
> )
> ACPI: OSL: Resource conflict; ACPI support missing from driver?
> ACPI: OSL: Resource conflict: System may be unstable or behave erratically
> ```
>
> A workaround is to use `acpi_enforce_resources=lax`, but a proper
> support needs to be added instead.
>
> This commit adds Pro WS X570-ACE to the list of boards that can be monitored
> using ASUS WMI.
>
> Tested by me on this hardware:
>
> ```
> Base Board Information
> Manufacturer: ASUSTeK COMPUTER INC.
> Product Name: Pro WS X570-ACE
>
> BIOS Information
> Vendor: American Megatrends Inc.
> Version: 3801
> Release Date: 07/30/2021
> ```
>
> Signed-off-by: Oleksandr Natalenko <oleksandr@natalenko.name>
Applied.
Thanks,
Guenter
> ---
> drivers/hwmon/nct6775.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/hwmon/nct6775.c b/drivers/hwmon/nct6775.c
> index ba18c1cbf572..ff28ba70a8b3 100644
> --- a/drivers/hwmon/nct6775.c
> +++ b/drivers/hwmon/nct6775.c
> @@ -5000,6 +5000,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[] = {
> + "Pro WS X570-ACE",
> "PRIME B360-PLUS",
> "PRIME B460-PLUS",
> "PRIME X570-PRO",
next prev parent reply other threads:[~2021-10-08 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 13:33 [PATCH 0/3] hwmon: add ASUS Pro WS X570-ACE support Oleksandr Natalenko
2021-10-03 13:33 ` [PATCH 1/3] hwmon: (nct6775) add Pro WS X570-ACE Oleksandr Natalenko
2021-10-08 14:13 ` Guenter Roeck [this message]
2021-10-03 13:33 ` [PATCH 2/3] hwmon: (asus_wmi_sensors) split out T_Sensor Oleksandr Natalenko
2021-10-11 14:25 ` Guenter Roeck
2021-10-03 13:33 ` [PATCH 3/3] hwmon: (asus_wmi_sensors) add Pro WS X570-ACE Oleksandr Natalenko
2021-10-03 17:30 ` [PATCH 0/3] hwmon: add ASUS Pro WS X570-ACE support Andy Shevchenko
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=20211008141334.GA2079491@roeck-us.net \
--to=linux@roeck-us.net \
--cc=andriy.shevchenko@intel.com \
--cc=eugene.shalygin@gmail.com \
--cc=igor@svelig.com \
--cc=jdelvare@suse.com \
--cc=kdudka@redhat.com \
--cc=kpietrzak@disroot.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nephartyz@gmail.com \
--cc=oleksandr@natalenko.name \
--cc=pauk.denis@gmail.com \
--cc=robert@swiecki.net \
--cc=sefoci9222@rerunway.com \
--cc=torvic9@mailbox.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;
as well as URLs for NNTP newsgroup(s).