Hi all,
I wrote:
---
Anonymous has been so kind as to send me a datasheet for the fscpos sensor.
Because of this I'm working on improved individual alarm file patches for the
fscher (which is documented in Documentation/hwmon/fscher) and the fscpos as I
now have a better understanding of these 2 chips.
Once an alarm condition has been signaled, it needs to be reset by software
otherwise the alarm will stay present even if there no longer is a cause.
I see 2 solutions for this:
1) clear an alarm when it gets read by userspace, assuming the chip will set it
again if the condition prevails (I need to test if this is true)
2) make the fooX_alarm file rw and make a write of 0 from userspace clear it
I prefer 1), asumming my assumption is true.
Suggestions, comments, advice?
---
It looks like its going to be 2) as the hardware only raises the alarm once
when an alarm condition occurs, it will only raise it again when the condition
has been cleared and the reoccurs.
Regards,
Hans
