nzxt-kraken3: PWM setting fixes; status reporting optimization

[aleksamagicka]

This should resolve the issues noted in #7 and optimize Z series status reporting.

• Values that convert to less than PUMP_DUTY_MIN will now be silently set to it without returning error codes
• When setting PWM duty directly, the same value that was set will be reported until the next sensor report interrupt comes through, so that userspace tools will be happ(y/ier)
• I've removed priv->duty_input in favor of recording the value in kraken3_channel_info for each channel
• Z series don't send the sensor report on their own. Instead of requesting it every time something is read, request it only when the validity interval has passed
• Reformatted code

---

Seems to work when using fan2go, here's my config: fan2go.txt. I had to set maxRpmDiffForSettledFan: 20 because X53 varied between 14-20 as far as I've seen, and the default value is 10. Didn't yet test with pwmconfig and fancontrol.

[stalkerg]

Thanks a lot! I will check today or tomorrow!

[stalkerg]

It seems like working as expected, I also have no any significant issues with fan2go. Thanks again!

[amezin]

@aleksamagicka @stalkerg By the way, have you tested the driver with lm-sensors (i. e. pwmconfig+fancontrol)? These utilities sometimes fail in surprising ways. As far as I remember, they treat almost any sysfs read error as "oh the device is completely broken let's die".

[stalkerg]

@amezin I didn't test it in fancontrol but fan2go has totally the same behavior for read error (and it's ok).