From: Guenter Roeck <linux@roeck-us.net>
To: Sebastian Arnhold <sebastian.arnhold@posteo.de>
Cc: Christian Lamparter <chunkeey@gmail.com>,
linux-hwmon@vger.kernel.org, Ahmad Khalifa <ahmad@khalifa.ws>
Subject: Re: [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D
Date: Fri, 30 Dec 2022 14:46:01 -0800 [thread overview]
Message-ID: <20221230224601.GA1220968@roeck-us.net> (raw)
In-Reply-To: <b31ed9ec-3bd5-e032-ea03-b116ece4dac3@posteo.de>
On Fri, Dec 30, 2022 at 10:13:48PM +0000, Sebastian Arnhold wrote:
> Thank you very much for the patch, Guenter Roeck!
>
> I just compiled it using the mainline Kernel as a basis, but
> "sensors-detect" still claims there are no sensors detected on my ASUS TUF
> GAMING X670E-PLUS WIFI.
>
> Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
> Found unknown chip with ID 0xd802
> (logical device B has address 0x290, could be sensors)
>
> dmesg yields the following output:
>
> [ 465.372161] nct6775: Found NCT6799D or compatible chip at 0x2e:0x290
> [ 465.372166] ACPI Warning: SystemIO range
> 0x0000000000000295-0x0000000000000296 conflicts with OpRegion
> 0x0000000000000290-0x0000000000000299 (\RMTW.SHWM) (20221020/utaddress-204)
> [ 465.372170] ACPI: OSL: Resource conflict; ACPI support missing from
> driver?
>
> So the driver definitely works and recognizes the chip. Any idea why
> lm-sensors can't access it?
>
You need ll to add "acpi_acpi_enforce_resources=lax" to the kernel command
line to be able to access/test it. Of course that is less than perfect and
may affect other devices.
Ultimately it will be necessary to add WMI support for this board to the
driver, but I can not do that since I have no means to test it, and there
is some indication that WMI may no longer be supported in the X670 boards
from ASUS.
Guenter
next prev parent reply other threads:[~2022-12-30 22:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20221228135744.281752-1-linux () roeck-us ! net>
2022-12-30 17:32 ` [PATCH RFT] hwmon: (nct6755) Add support for NCT6799D Christian Lamparter
2022-12-30 17:50 ` Guenter Roeck
2022-12-30 20:34 ` Christian Lamparter
2022-12-30 21:48 ` Guenter Roeck
2022-12-30 22:13 ` Sebastian Arnhold
2022-12-30 22:46 ` Guenter Roeck [this message]
2022-12-30 22:58 ` Christian Lamparter
2022-12-31 23:42 ` Sebastian Arnhold
2023-01-04 3:41 ` Guenter Roeck
2023-01-05 12:46 ` Sebastian Arnhold
2023-01-07 18:37 ` Denis Pauk
2023-01-07 18:50 ` Denis Pauk
2022-12-28 13:57 Guenter Roeck
2023-05-11 21:02 ` Denis Pauk
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=20221230224601.GA1220968@roeck-us.net \
--to=linux@roeck-us.net \
--cc=ahmad@khalifa.ws \
--cc=chunkeey@gmail.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=sebastian.arnhold@posteo.de \
/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.