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] question about dyn chip support generic temp print
Date: Mon, 18 Jun 2007 12:37:49 +0000	[thread overview]
Message-ID: <46767C9D.8040006@hhs.nl> (raw)

Hi all,

As said already I'm working on the fintek 71882 driver, I've currently given it 
a tempX_input tempX_max tempX_max_hyst and a tempX_crit, with the current dyn 
chip + generic print support this results in:
CPU:            +38.0°C  (high = +80.0°C, hyst =  +4.0°C)  sensor = transistor
temp1_crit:     +81.0°C

This is because currently for max + hyst chips the first line gets printed, and 
then for chips which have a crit to a sensors_get_label_and_valid is done on 
the sensors_feature_data describing tempX_crit. Wouldn't it be better to reuse 
the main temp label and value, resulting in:
CPU:            +38.0°C  (high = +80.0°C, hyst =  +4.0°C)  sensor = transistor
CPU:            +38.0°C  (crit = +81.0°C)

Maybe change the label into all whitespace / "CPU (continued)"? The current 
printout seems very wrong, but my suggested one doesn't feel right either.

Also as already "explained" in my previous question, this chip has one 
hysteresis for both max and crit, now to make the current code work I would 
need to put that twice into sysfs, which would result in to both changing if 
one gets written (I can make only one rw to make this obvious).

Or we need to add a tempX_hyst type, and update the generic temp print code to 
handle this scenario too.


Regards,

Hans


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

             reply	other threads:[~2007-06-18 12:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-18 12:37 Hans de Goede [this message]
2007-06-18 15:52 ` [lm-sensors] question about dyn chip support generic temp print Juerg Haefliger
2007-06-23 16:03 ` 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=46767C9D.8040006@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.