From: Guenter Roeck <guenter.roeck@ericsson.com>
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] tempX_source sysfs attribute needed ?
Date: Tue, 08 Feb 2011 17:10:26 +0000 [thread overview]
Message-ID: <20110208171026.GE13717@ericsson.com> (raw)
Hi all,
in the recent months, I have seen two instances where a sysfs attribute
identifying the source associated with a temperature sensor would have been
helpful.
One is max6639. For this chip, the source of the second temperature channel
can be configured to be local or remote.
The others are W83677HG-B, NCT6775F, and NCT6776F. Those chips have four to six
temperature channels with a configurable source.
Current approach is to stick with whatever is configured by the BIOS for the Nuvoton
chips, and to use the local source for the max6639 driver. For the Nuvoton chips,
my prototype driver for NCT6775F and NCT6776F reports the temperature source
in tempX_label.
Possible solutions might be:
- Stick with the current situation, ie do nothing.
- Use module parameters. Doesn't really work well for max6639 since it affects
all instances of the driver, and if the driver is built into the kernel.
- Use platform data. Might work for max6639, but not for the Nuvoton chips.
- Define a new sysfs attribute to make the temperature source configurable,
and to report the current selection.
Any thoughts/comments ?
Thanks,
Guenter
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
next reply other threads:[~2011-02-08 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 17:10 Guenter Roeck [this message]
2011-02-08 18:03 ` [lm-sensors] tempX_source sysfs attribute needed ? Ian Dobson
2011-02-08 20:06 ` Guenter Roeck
2011-03-07 16:54 ` Jean Delvare
2011-03-07 17:58 ` Guenter Roeck
2011-03-07 18:19 ` Jean Delvare
2011-03-07 18:54 ` Guenter Roeck
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=20110208171026.GE13717@ericsson.com \
--to=guenter.roeck@ericsson.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.