From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Jean Delvare <khali@linux-fr.org>
Cc: LM Sensors <lm-sensors@lm-sensors.org>, Greg KH <greg@kroah.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [lm-sensors] [PATCH 2.6.12-rc4 15/15] drivers/i2c/chips/adm1026.c: use dynamic sysfs callbacks
Date: Sun, 22 May 2005 02:04:52 -0500 [thread overview]
Message-ID: <200505220204.52907.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050522085026.40e73d49.khali@linux-fr.org>
On Sunday 22 May 2005 01:50, Jean Delvare wrote:
> Hi Dmitry,
>
> > I really think that as far as I2C subsystem goes instead of creating
> > arrays of attributes we should move in direction of drivers
> > registering individual sensor class devices. So for example it87 would
> > register 3 fans, 3 temp, sensors and 8 voltage sensors...
>
> First, it's a matter of hardware monitoring drivers, not i2c subsystem
> (both are tightly binded at the moment but I'd like this to change).
>
Right, it's just i2c is pretty much the only supplier of these for now.
> Second, not all devices have the same attributes for a temperature, fan
> or voltage channel. Sure there are commonly found feature sets, but some
> channels will lack some feature (e.g. it87's in8 has no min and max
> limits), other chips will provide additional features (extra limits or
> enhanced configurability). So I don't think you can have all devices
> (and thus all drivers) fit into a single sensor class.
>
Well, userspace code manages it somehow, plus nothing stops driver from
adding some additional attributes to class devices.
> But of course I can be convinced your approach is better, with patches.
Heh, I was afraid you'd say so... Input sysfs conversion first and then
we'll see...
--
Dmitry
next prev parent reply other threads:[~2005-05-22 7:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-17 10:47 [PATCH 2.6.12-rc4 15/15] drivers/i2c/chips/adm1026.c: use dynamic sysfs callbacks Yani Ioannou
2005-05-17 11:04 ` [lm-sensors] " Jean Delvare
2005-05-17 11:18 ` Yani Ioannou
2005-05-17 20:23 ` Grant Coady
2005-05-17 20:56 ` Yani Ioannou
2005-05-17 23:13 ` Grant Coady
2005-05-17 23:21 ` Yani Ioannou
2005-05-18 1:58 ` Grant Coady
[not found] ` <253818670505172136613abb43@mail.gmail.com>
2005-05-19 20:02 ` Jean Delvare
2005-05-19 20:52 ` Greg KH
2005-05-19 20:57 ` Jean Delvare
2005-05-19 21:35 ` Greg KH
2005-05-20 7:46 ` Jean Delvare
2005-05-20 8:53 ` Yani Ioannou
2005-05-22 1:58 ` Dmitry Torokhov
2005-05-22 6:50 ` Jean Delvare
2005-05-22 7:04 ` Dmitry Torokhov [this message]
2005-05-22 12:15 ` Yani Ioannou
2005-05-22 12:32 ` Jean Delvare
2005-05-22 13:05 ` Yani Ioannou
2005-05-22 13:39 ` Jean Delvare
2005-05-19 21:14 ` Yani Ioannou
2005-06-05 8:51 ` Jean Delvare
2005-06-06 6:14 ` Greg KH
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=200505220204.52907.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox