summaryrefslogtreecommitdiff
path: root/drivers/ntb/hw/idt/Kconfig
diff options
context:
space:
mode:
authorSerge Semin <fancer.lancer@gmail.com>2018-07-17 12:24:36 +0300
committerJon Mason <jdmason@kudzu.us>2018-11-01 10:33:12 -0400
commitb8babacbae624da6d244d0721263edda56be3991 (patch)
treed52389c295510d0fdf3110927bad82f7d98b7210 /drivers/ntb/hw/idt/Kconfig
parentaed1b7b31154bdd6f2fccca0ab5cf8a6fe2f52eb (diff)
ntb: idt: Discard temperature sensor IRQ handler
IDT PCIe-switch temperature sensor interface is very broken. First of all only a few combinations of TMPCTL threshold enable bits really cause the interrupts unmasked. Even if an individual bit indicates the event unmasked, corresponding IRQ just isn't generated. Most of the threshold enable bits combinations are in fact useless and non of them can help to create a fully functional alarm interface. So to speak, we can't create a well defined hwmon alarms based on the IDT PCI-switch threshold IRQs. Secondly a single threshold IRQ (not a combination of thresholds) can be successfully enabled without the issue described above. But in this case we experienced an enormous number of interrupts generated by the chip if the temperature got near the enabled threshold value. Filter adjustment didn't help much. It also doesn't provide a hysteresis settings. Due to the temperature sample fluctuations near the threshold the interrupts spate makes the system nearly unusable until the temperature value finally settled so being pushed either to be fully higher or lower the threshold. All of these issues makes the temperature sensor alarm interface useless and even at some point dangerous to be used in the driver. In this case it is safer to completely discard it and disable the temperature alarm interrupts. Signed-off-by: Serge Semin <fancer.lancer@gmail.com> Signed-off-by: Jon Mason <jdmason@kudzu.us>
Diffstat (limited to 'drivers/ntb/hw/idt/Kconfig')
0 files changed, 0 insertions, 0 deletions