All of lore.kernel.org
 help / color / mirror / Atom feed
From: yani.ioannou@gmail.com (Yani Ioannou)
To: lm-sensors@vger.kernel.org
Subject: [lm-sensors] Re: [PATCH 2.6.12-rc5-mm1 3/3] i2c: modify sensors
Date: Fri, 03 Jun 2005 21:00:06 +0000	[thread overview]
Message-ID: <253818670506031159466bf3b8@mail.gmail.com> (raw)
In-Reply-To: <20050602033727.GD4906@jupiter.solarsys.private>

Hi Greg,

> > The problem essentially is, unlike the i2c/isa sensor chip drivers,
> > ipmi_sensors isn't a device driver as such, it is an lm-sensors
> > interface to the sensors available to an IPMI BMC.
> 
> Which is a platform device.  Or if not, it should be.  There is your
> struct device.

Yes, I agree, I'm going to have to see if I can find away to make the
low level device (assuming that exists..) for each IPMI interface type
available at a higher level, without annoying Corey too much :-).
 
> > I just come back to my previous line of thought that we really should
> > be using class_device_attributes for hwmon class sensor attributes
> > rather than assuming that every hwmon class_device has an associated
> > device...
> 
> No, every hwmon class_device should have a struct device associated with
> it.  If not, it needs to be fixed :)

Well even assuming that every hwmon class_device does have a device
associated with it, it still makes sense to me to be using
class_device_attributes.

First of all they are attributes of the hwmon class, not that
neccessarily that device, for example assuming I add the sensor
device_attributes to the ipmi low level interface device, now I have a
device entry with a whole load of sensor attributes when that low
level interface hasn't actually got sensors hanging off it, it is just
a way of accessing the IPMI BMC (which by the way can be accessed
through more than one interface). It simply doesn't make sense in the
way that the sysfs tree should IMHO.

Furthermore I've added attributes for the device from a hwmon class,
shouldn't the device be responsible for device_attributes?

Thanks,
Yani

  parent reply	other threads:[~2005-06-03 21:00 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-02  5:38 [lm-sensors] Re: [PATCH 2.6.12-rc5-mm1 3/3] i2c: modify sensors Mark M. Hoffman
2005-06-02  8:03 ` Greg KH
2005-06-03  6:00 ` Mark M. Hoffman
2005-06-03  6:47 ` Greg KH
2005-06-03  8:26 ` Yani Ioannou
2005-06-03  8:53 ` Greg KH
2005-06-03 21:00 ` Yani Ioannou [this message]
2005-06-04 18:13 ` Jean Delvare
2005-06-04 18:23 ` Jean Delvare
2005-06-04 22:32 ` Yani Ioannou
2005-06-04 23:21 ` Jean Delvare
2005-06-05  1:35 ` Yani Ioannou
2005-06-05  5:42 ` Mark M. Hoffman
2005-06-05  8:06 ` Jean Delvare
2005-06-09  9:28 ` Greg KH
2005-06-09  9:58 ` Yani Ioannou
2005-06-09 10:23 ` Jean Delvare
2005-06-10  6:26 ` Mark M. Hoffman
2005-06-10  6:40 ` Greg KH
2005-06-10 18:45 ` 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=253818670506031159466bf3b8@mail.gmail.com \
    --to=yani.ioannou@gmail.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.