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: [lm-sensors] dynamic chip support
Date: Tue, 10 Apr 2007 11:54:43 +0000	[thread overview]
Message-ID: <461B7F5C.5080409@hhs.nl> (raw)

Hi,

I just committed a rewrite of parts of the dyn chip support, changes:
-rewrite dyn chip code, it now uses sensors_feature_get_type() to
  identify sysfs entries. Reasons for this rewrite / bugs fixed:
  -Don't give features like alarms / sensor type / fault flag a
   compute mapping only a normal mapping
  -Don't generate features for sysfs entries like uvent, modalias, etc.
   instead only generate features for features known by
   sensors_feature_get_type()
  -Sort the list of found features logically instead of sorted in alphabet order
   of the sysfs entry. So now it starts with all in entries, then all fan and
   then all temp. Just like the order of most entries in lib/chips.c. Also
   this means that it now contains in0 - in10 in that order and not in0, in10,
   in1 - in9

Some observations, in an ideal world this dyn chipsupport could replace most of 
the 5000 lines of code in prog/sensors/chips.c, however some chips seem to use 
non standard sysfs names <sigh> like remote_temp and zone_xxxxx, etc. I'm 
thinking of adding support to often used non standard names to 
sensors_feature_get_type(), but all in all not having a standard API is not good.

Also I've not added support for pwm features, because AFAIK libsensors is about 
sensors, thus I also was amazed to still see eeprom and edid "feature" lists in 
lib/chips.c

Regards,

Hans

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

             reply	other threads:[~2007-04-10 11:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-10 11:54 Hans de Goede [this message]
2007-05-25  7:53 ` [lm-sensors] dynamic chip support Jean Delvare
2007-05-25  8:34 ` Hans de Goede
2007-05-25 13:25 ` 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=461B7F5C.5080409@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.