linux-hwmon.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Arnhold <sebastian.arnhold@posteo.de>
To: Guenter Roeck <linux@roeck-us.net>, Denis Pauk <pauk.denis@gmail.com>
Cc: ahmad@khalifa.ws, chunkeey@gmail.com, greg@krypto.org,
	hubert.banas@gmail.com, igor@svelig.com, jaap.dehaan@freenet.de,
	jdelvare@suse.com, jeroen@beerstra.org, jonfarr87@gmail.com,
	jwp@redhat.com, kdudka@redhat.com, kernel@melin.net,
	kpietrzak@disroot.org, linux-hwmon@vger.kernel.org,
	linux-kernel@vger.kernel.org, me@rebtoor.com,
	metalcaedes@gmail.com, michael@theoddone.net,
	mikhail.v.gavrilov@gmail.com, mundanedefoliation@gmail.com,
	nephartyz@gmail.com, oleksandr@natalenko.name, pehlm@pekholm.org,
	renedis@hotmail.com, robert@swiecki.net,
	sahan.h.fernando@gmail.com, sst@poczta.fm, to.eivind@gmail.com,
	torvic9@mailbox.org
Subject: Re: [PATCH v4 2/2] hwmon: (nct6775) B650/B660/X670 ASUS boards support
Date: Fri, 20 Jan 2023 19:50:57 +0000	[thread overview]
Message-ID: <6fd769f9-da0e-c4a8-dc0e-a1e464c2d9fc@posteo.de> (raw)
In-Reply-To: <20230115161224.GA1246527@roeck-us.net>

Is it just me, or is the support for my mainboard "TUF GAMING X670E-PLUS 
WIFI" now implemented into the latest "linux-next" kernel (I verified 
this by looking at the source code at /drivers/hwmon/nct6775-core.c), 
but the actual patch that contains the NCT6799D driver is still missing?

I had to patch my linux-next kernel with the patch from 
https://patchwork.kernel.org/project/linux-hwmon/patch/20221228135744.281752-1-linux@roeck-us.net/ 
to get it working.

Otherwise the nct6775 module refuses to recognize my sensor chip.

Thanks,
Sebastian

Am 15.01.23 um 17:12 schrieb Guenter Roeck:
> On Wed, Jan 11, 2023 at 11:22:41PM +0200, Denis Pauk wrote:
>> Boards such as:
>>    "EX-B660M-V5 PRO D4",
>>    "PRIME B650-PLUS",
>>    "PRIME B650M-A",
>>    "PRIME B650M-A AX",
>>    "PRIME B650M-A II",
>>    "PRIME B650M-A WIFI",
>>    "PRIME B650M-A WIFI II",
>>    "PRIME B660M-A D4",
>>    "PRIME B660M-A WIFI D4",
>>    "PRIME X670-P",
>>    "PRIME X670-P WIFI",
>>    "PRIME X670E-PRO WIFI",
>>    "Pro B660M-C-D4",
>>    "ProArt B660-CREATOR D4",
>>    "ProArt X670E-CREATOR WIFI",
>>    "ROG CROSSHAIR X670E EXTREME",
>>    "ROG CROSSHAIR X670E GENE",
>>    "ROG CROSSHAIR X670E HERO",
>>    "ROG MAXIMUS XIII EXTREME GLACIAL",
>>    "ROG MAXIMUS Z690 EXTREME",
>>    "ROG MAXIMUS Z690 EXTREME GLACIAL",
>>    "ROG STRIX B650-A GAMING WIFI",
>>    "ROG STRIX B650E-E GAMING WIFI",
>>    "ROG STRIX B650E-F GAMING WIFI",
>>    "ROG STRIX B650E-I GAMING WIFI",
>>    "ROG STRIX B660-A GAMING WIFI D4",
>>    "ROG STRIX B660-F GAMING WIFI",
>>    "ROG STRIX B660-G GAMING WIFI",
>>    "ROG STRIX B660-I GAMING WIFI",
>>    "ROG STRIX X670E-A GAMING WIFI",
>>    "ROG STRIX X670E-E GAMING WIFI",
>>    "ROG STRIX X670E-F GAMING WIFI",
>>    "ROG STRIX X670E-I GAMING WIFI",
>>    "ROG STRIX Z590-A GAMING WIFI II",
>>    "ROG STRIX Z690-A GAMING WIFI D4",
>>    "TUF GAMING B650-PLUS",
>>    "TUF GAMING B650-PLUS WIFI",
>>    "TUF GAMING B650M-PLUS",
>>    "TUF GAMING B650M-PLUS WIFI",
>>    "TUF GAMING B660M-PLUS WIFI",
>>    "TUF GAMING X670E-PLUS",
>>    "TUF GAMING X670E-PLUS WIFI",
>>    "TUF GAMING Z590-PLUS WIFI",
>> have got a NCT6799D chip, but by default there's no use of it
>> because of resource conflict with WMI method.
>>
>> This commit adds such boards to the monitoring list with new ACPI device
>> UID.
>>
>> BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=204807
>> Signed-off-by: Denis Pauk <pauk.denis@gmail.com>
>> Co-developed-by: Ahmad Khalifa <ahmad@khalifa.ws>
>> Signed-off-by: Ahmad Khalifa <ahmad@khalifa.ws>
>> Tested-by: Jeroen Beerstra <jeroen@beerstra.org>
>> Tested-by: Slawomir Stepien <sst@poczta.fm>
> Applied to hwmon-next.
>
> Thanks,
> Guenter

  parent reply	other threads:[~2023-01-20 19:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 21:22 [PATCH v4 1/2] hwmon: (nct6775) Directly call ASUS ACPI WMI method Denis Pauk
2023-01-11 21:22 ` [PATCH v4 2/2] hwmon: (nct6775) B650/B660/X670 ASUS boards support Denis Pauk
     [not found]   ` <20230115161224.GA1246527@roeck-us.net>
2023-01-20 19:50     ` Sebastian Arnhold [this message]
2023-01-20 20:28       ` Guenter Roeck
2023-01-20 20:32         ` Sebastian Arnhold
2023-06-06 10:29 ` [PATCH v4 1/2] hwmon: (nct6775) Directly call ASUS ACPI WMI method Geert Uytterhoeven
2023-06-06 13:51   ` Guenter Roeck

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=6fd769f9-da0e-c4a8-dc0e-a1e464c2d9fc@posteo.de \
    --to=sebastian.arnhold@posteo.de \
    --cc=ahmad@khalifa.ws \
    --cc=chunkeey@gmail.com \
    --cc=greg@krypto.org \
    --cc=hubert.banas@gmail.com \
    --cc=igor@svelig.com \
    --cc=jaap.dehaan@freenet.de \
    --cc=jdelvare@suse.com \
    --cc=jeroen@beerstra.org \
    --cc=jonfarr87@gmail.com \
    --cc=jwp@redhat.com \
    --cc=kdudka@redhat.com \
    --cc=kernel@melin.net \
    --cc=kpietrzak@disroot.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=me@rebtoor.com \
    --cc=metalcaedes@gmail.com \
    --cc=michael@theoddone.net \
    --cc=mikhail.v.gavrilov@gmail.com \
    --cc=mundanedefoliation@gmail.com \
    --cc=nephartyz@gmail.com \
    --cc=oleksandr@natalenko.name \
    --cc=pauk.denis@gmail.com \
    --cc=pehlm@pekholm.org \
    --cc=renedis@hotmail.com \
    --cc=robert@swiecki.net \
    --cc=sahan.h.fernando@gmail.com \
    --cc=sst@poczta.fm \
    --cc=to.eivind@gmail.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).