public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: lm-sensors@lm-sensors.org, Yani Ioannou <yani.ioannou@gmail.com>
Cc: Jean Delvare <khali@linux-fr.org>,
	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: Sat, 21 May 2005 20:58:14 -0500	[thread overview]
Message-ID: <200505212058.14851.dtor_core@ameritech.net> (raw)
In-Reply-To: <25381867050520015339f02e9b@mail.gmail.com>

On Friday 20 May 2005 03:53, Yani Ioannou wrote:
> On 5/20/05, Jean Delvare <khali@linux-fr.org> wrote:
> > 
> > Hi Greg,
> > disabled. While this feature was almost not used so far, I think we
> > should have the driver not create interface files for disabled inputs.
> > In the case of temperature channels which can be dynamically enabled and
> > disabled. it would even make sense to dynamically create and delete
> > related sysfs files. Doing so would allow for memory savings and would
> > also be less error-prone for the user (presenting an interface for
> > disabled features is quite confusing IMHO).
> 
> If you think more than a few hwmon/chip drivers will benefit from
> dynamically creating the attributes, then maybe we can create some
> standard method for doing so, bmcsensors of course needs to
> dynamically allocate things, so I'd be using them too.
> 
> An earlier idea was to create a standard sysfs function(s) for
> dynamically creating device_attributes (and others), but now we will
> have custom structures with an embedded device_attribute, it looks to
> me like each attribute type would require it's own function.
>

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...
 
-- 
Dmitry

  reply	other threads:[~2005-05-22  1:58 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 [this message]
2005-05-22  6:50                     ` Jean Delvare
2005-05-22  7:04                       ` Dmitry Torokhov
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=200505212058.14851.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 \
    --cc=yani.ioannou@gmail.com \
    /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