Accept NCT6683D (0xc732)

[mpartel]

This chip controls the fans on ASRock Taichi B550.

I couldn't get fan control to work with any of the in-tree nct6* drivers, but it works with your driver after this change :+1:

Example lm-sensors output:

nct6683-isa-0a20
Adapter: ISA adapter
+12V:            0.00 V  (min =  +0.00 V, max =  +0.00 V)
+5V:             0.00 V  (min =  +0.00 V, max =  +0.00 V)
+3.3V:           0.00 V  (min =  +0.00 V, max =  +3.39 V)
CPU Soc:         0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU Vcore:       0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU 1P8:         0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU VDDP:        0.00 V  (min =  +0.00 V, max =  +0.00 V)
DRAM:            0.00 V  (min =  +0.00 V, max =  +0.00 V)
Chipset:         0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU Fan:          0 RPM  (min =    0 RPM, max =    0 RPM)
Pump Fan:         0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #1:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #2:  625 RPM  (min =    0 RPM, max =  645 RPM)
System Fan #3:  639 RPM  (min =    0 RPM, max = 1430 RPM)
System Fan #4:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #5:    0 RPM  (min =    0 RPM, max =    0 RPM)
System Fan #6:    0 RPM  (min =    0 RPM, max =    0 RPM)
CPU:            +33.0°C  (low  = +25.0°C, high = +38.0°C)
System:         +39.0°C  (low  = +31.0°C, high = +71.0°C)
VRM MOS:         +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
PCH:             +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
CPU Socket:      +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
PCIe x1:         +0.0°C  (low  =  +0.0°C, high =  +0.0°C)
M2_1:            +0.0°C  (low  =  +0.0°C, high =  +0.0°C)

Some notes:

• Most values are missing. From what I've gathered, this board is weird in that it has two NCT6* chips. Most sensors (but not fan sensors) appear to be connected to the other one (nct6798-isa-0290).
• 3.3V had a non-zero value at some point, but it went away. Not sure why. Might be related to suspend/resume :man_shrugging:
• "CPU" and "System" sensors seem to be the wrong way around (not sure what "System" refers to here). Probably an lm-sensors config issue?

[Fred78290]

Hello great news that my module can override nct6683 with readable value.

Could you explain me the last commit flag force because I don't see a reason.

Regards

[mpartel]

Your module declares the parameter force but didn't implement it.

The in-tree nct6683 also has this parameter, and I had to use it to get it to work even partially, so I thought implementing it for your module might be useful for someone in the future. Could also remove it entirely if you're not comfortable with it. I suppose it could be dangerous.

[mpartel]

^ a little follow-up to get the correct device name in lm-sensors.

[Fred78290]

Sorry I forgive to accept PR