Hi,
I have chosen "hwmon" because those drivers are placed in the kernel's
drivers/hwmon subdirectory. "temp" sounds to much like "temporary" for
me :-)
We can name it "sensor" - inspired by the lm-sensors projects that
takes care of such sensors. Because these type of devices are not always
used to monitor the whatever hardware ... sensor could even be better.
So my favorites are sensor@ or [EMAIL PROTECTED]
Sean, I can take your "adi" instead of "analog" for this special sensor.
Matthias
On Saturday 06 September 2008 02:17:03 Sean MacLennan wrote:
> On Fri, 5 Sep 2008 11:00:18 -0500
>
> "Scott Wood" <[EMAIL PROTECTED]> wrote:
> > On Fri, Sep 05, 2008 at 12:19:43PM +0200, Stefan Roese wrote:
> > > > +
> > > > + [EMAIL PROTECTED] {
> > >
> > > Not sure if we shouldn't use
> > >
> > > [EMAIL PROTECTED] {
> > >
> > > here. This is the way it is already done in warp.dts.
> >
> > We shouldn't. Node names are supposed to be generic:
> > http://playground.sun.com/1275/practice/gnames/gnamv14a.html
>
> Damn. Where were you a year ago when I first introduced this? ;)
>
> And if it is really supposed to be generic, would [EMAIL PROTECTED] be a
> better name since this is basically a generic temperature chip?
>
> Now that the i2c driver is a full of platform driver, I think I
> can change the name with no repercussions. So I can live with whatever
> decision is made. Can't do anything about the systems that are out in
> the field though....
>
> Cheers,
> Sean
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
