Linux Hardware Monitor development
 help / color / mirror / Atom feed
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: Tue, 3 Jan 2023 19:41:36 -0800	[thread overview]
Message-ID: <20230104034136.GA228903@roeck-us.net> (raw)
In-Reply-To: <3ba37e2d-413b-4d7d-e99b-8e0a53bd7f4e@posteo.de>

On Sat, Dec 31, 2022 at 11:42:57PM +0000, Sebastian Arnhold wrote:
> I tried to add acpi_enforce_resources=lax, but sadly, it does not solve the
> problem.
> 
What do you see in the kernel log after adding that ?

Thanks,
Guenter

> Maybe Ahmad can help add support for the board?
> 
> Thanks,
> Sebastian
> 
> Am 30.12.22 um 23:58 schrieb Christian Lamparter:
> > Hi Sebastian,
> > 
> > On 12/30/22 23:13, 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.
> > 
> > Unfortunately, this might be because ASUS has some "new" ideas :/.
> > See this RFC from Ahmad back from October (Author is in Cc)
> > for an in-depth view why this is happening:
> > 
> > https://patchwork.kernel.org/project/linux-hwmon/patch/20221018173428.71080-1-ahmad@khalifa.ws/
> > 
> > 
> > Regards,
> > Christian
> > 

  reply	other threads:[~2023-01-04  3:41 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
2022-12-30 22:58           ` Christian Lamparter
2022-12-31 23:42             ` Sebastian Arnhold
2023-01-04  3:41               ` Guenter Roeck [this message]
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=20230104034136.GA228903@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox