All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Arnhold <sebastian.arnhold@posteo.de>
To: Guenter Roeck <linux@roeck-us.net>
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: Thu,  5 Jan 2023 12:46:07 +0000	[thread overview]
Message-ID: <767c4090-007c-a819-e047-11971ea9cc17@posteo.de> (raw)
In-Reply-To: <20230104034136.GA228903@roeck-us.net>

Hello Guenter & friends,

I'm such an idiot! The patch works, of course. I did everything 
correctly and then simply forgot to load the module. :D

Adding "acpi_enforce_resources=lax" is necessary for my system, but then 
it works! Other people on the lm-sensors project report that, too. So 
the driver seems to be working for a first release.

Watching my fanspeeds with the "Vitals" GNOME extension and generating 
fancurves with pwmconfig/fanspeed as we speak! Awesome!

Now we should get it into the Linux kernel for the next release asap. 
I've heard on Phoronix that the driver additions queque for Kernel 6.3 
has now begun. I don't think there would be any negative side effects, 
since the module was based on the datasheet. Some values seem to be off, 
though - I'll attach my "sensors" output.

Thank you all very much! :)
Sebastian


nct6799-isa-0290
Adapter: ISA adapter
in0:                      840.00 mV (min =  +0.00 V, max =  +1.74 V)
in1:                      1000.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in2:                        3.41 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in3:                        3.33 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in4:                      992.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in5:                        1.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in6:                      472.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in7:                        3.39 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in8:                        3.30 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in9:                        1.66 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in10:                     560.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in11:                     552.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in12:                       1.05 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
in13:                     216.00 mV (min =  +0.00 V, max =  +0.00 V)  ALARM
in14:                       2.04 V  (min =  +0.00 V, max =  +0.00 V)  ALARM
fan1:                      607 RPM  (min =    0 RPM)
fan2:                        0 RPM  (min =    0 RPM)
fan3:                        0 RPM  (min =    0 RPM)
fan4:                      910 RPM  (min =    0 RPM)
fan5:                      625 RPM  (min =    0 RPM)
fan6:                        0 RPM  (min =    0 RPM)
fan7:                        0 RPM  (min =    0 RPM)
SYSTIN:                    +34.0°C  (high = +80.0°C, hyst = +75.0°C)  
sensor = thermistor
CPUTIN:                    +40.5°C  (high = +80.0°C, hyst = +75.0°C)  
sensor = thermistor
AUXTIN0:                   +61.0°C    sensor = thermistor
AUXTIN1:                   +19.0°C    sensor = thermistor
AUXTIN2:                   +20.0°C    sensor = thermistor
AUXTIN3:                   -62.0°C    sensor = thermistor
PECI Agent 0 Calibration:  +40.5°C
PCH_CHIP_CPU_MAX_TEMP:      +0.0°C
PCH_CHIP_TEMP:              +0.0°C
PCH_CPU_TEMP:               +0.0°C
TSI0_TEMP:                 +50.6°C
intrusion0:               ALARM
intrusion1:               OK
beep_enable:              disabled


Am 04.01.23 um 04:41 schrieb Guenter Roeck:
> 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-05 12: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
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 [this message]
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=767c4090-007c-a819-e047-11971ea9cc17@posteo.de \
    --to=sebastian.arnhold@posteo.de \
    --cc=ahmad@khalifa.ws \
    --cc=chunkeey@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=linux@roeck-us.net \
    /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.