All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <j.w.r.degoede@hhs.nl>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] Howto handle alarms which need to be reset?
Date: Wed, 04 Jul 2007 09:03:31 +0000	[thread overview]
Message-ID: <468B6263.3020906@hhs.nl> (raw)
In-Reply-To: <468B4474.5070309@hhs.nl>

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



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

  reply	other threads:[~2007-07-04  9:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-04  6:55 [lm-sensors] Howto handle alarms which need to be reset? Hans de Goede
2007-07-04  9:03 ` Hans de Goede [this message]
2007-07-05 12:46 ` Jean Delvare
2007-07-05 14:26 ` Hans de Goede
2007-07-05 16:01 ` Hans de Goede
2007-07-08 17:08 ` Jean Delvare

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=468B6263.3020906@hhs.nl \
    --to=j.w.r.degoede@hhs.nl \
    --cc=lm-sensors@vger.kernel.org \
    /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.