From: "Christian Engelmayer" <Christian.Engelmayer@frequentis.com>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] [PATCH 2.6.29.3 1/1] hwmon: added support for the
Date: Tue, 19 May 2009 20:52:01 +0000 [thread overview]
Message-ID: <000401c9d8c3$aae3fbe0$00abf3a0$@Engelmayer@frequentis.com> (raw)
In-Reply-To: <9EE81EBECB70824985BE0EDA8DC9B5150214E42C@VIECLEX01.frequentis.frq>
> Extending the supported alarms would be fine, although I would not aggregate
> them all under one sysfs file, just make a gpio#_alarm sysfs file, and make
the
> presence of this file conditional on the configuration of the gpio pins.
> Would that work for you ?
It would.
I suggested combining the status into a single file because that file name
is already supported. In case an extension is accptable and for further
clarification I would suggest the following:
device alarm | alarm file
---------------------+------------------
gpio 2 pulled low | gpio2_alarm
gpio 1 pulled low | gpio1_alarm
Tachometer overflow | fan1_tach_alarm
Minimum output level | fan1_min_alarm
Maximum output level | fan1_max_alarm
All 5 sources can be enabled independently with POR 'all disabled'.
The first 2 sources make only sense depending on the gpio definitions,
while the other 3 would be provided just by the chip itself.
After the previous discussion I would then leave the setup of the gpios
and the enabling of appropriate alarm sources completely to the firmware.
The driver shall discover the alarms enabled by the firmware at startup
and use that information as a condition for adding the alarm files as shown
above for enabled alarms.
Regards,
Christian
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next prev parent reply other threads:[~2009-05-19 20:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-19 8:39 [lm-sensors] [PATCH 2.6.29.3 1/1] hwmon: added support for the Engelmayer Christian
2009-05-19 9:11 ` Hans de Goede
2009-05-19 10:45 ` Engelmayer Christian
2009-05-19 17:08 ` Hans de Goede
2009-05-19 20:52 ` Christian Engelmayer [this message]
2009-05-19 21:11 ` Jean Delvare
2009-05-20 10:52 ` Engelmayer Christian
2009-05-20 18:31 ` Hans de Goede
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='000401c9d8c3$aae3fbe0$00abf3a0$@Engelmayer@frequentis.com' \
--to=christian.engelmayer@frequentis.com \
--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.