[lm-sensors] Help wanted: individual alarm files

[lm-sensors] Help wanted: individual alarm files

[Jean Delvare]

Hi all,

The future libsensors assumes that all hardware monitoring drivers
follow the standard sysfs interface defined in
Documentation/hwmon/sysfs-interface. They all mostly do already, except
for one thing: alarms. Most drivers are still only exposing a single
file with all alarms in a bit-vector, in chip-dependent order. In order
to let the new libsenors display the alarms properly, we must add
individual alarm files to these drivers. For some drivers, fault and/or
beep files need to be added too.

Here's the current status, to the best of my knowledge.

Already have individual alarm files:
abituguru.c
coretemp.c
ds1621.c
dme1737.c
f71805f.c
lm63.c
lm83.c
lm85.c
lm90.c
pc87427.c
smsc47m192.c
vt1211.c
w83627ehf.c
w83793.c

Don't have alarms at all:
ad7418.c
adm1029.c
ams
applesmc.c
atxp1.c
hdaps.c
k8temp.c
lm70.c
lm75.c
max6650.c
smsc47b397.c
w83l785ts.c

Need to be converted:
adm1021.c
adm1025.c
adm1026.c
adm1031.c
adm9240.c
asb100.c
fscher.c
fscpos.c
gl518sm.c
gl520sm.c
it87.c
lm77.c
lm78.c
lm80.c
lm87.c
lm92.c
max1619.c
pc87360.c
sis5595.c
smsc47m1.c
via686a.c
vt8231.c
w83627hf.c
w83781d.c
w83791d.c
w83792d.c

As you can see, the list is quite long, so I need help. That's not a
difficult job, but you need chip ship in question to test.

How to add individual alarm files:

* Read Documentation/hwmon/sysfs-interface, so that you know what are
the valid names for individual alarm, fault and beep files.

* Take a look at this patch which adds individual alarm support to 4
drivers:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h-45771e6ea79f56a7d85e448f702f60ef86c228#patch2

* Do the same to your driver. To find out which alarm bit correspond to
what, you can look at the defines used in the current version of
libsensors:
http://www.lm-sensors.org/browser/lm-sensors/branches/lm-sensors-3.0.0/kernel/include/sensors.h?revD73
Or you can look at the datasheet for your chip, but it's likely to take
longer.

* Test. You can test manually (change the limits and read the alarm
files from sysfs) or you can use the next version of libsensors, which
is in branch "lm-sensors-3.0.0" under SVN:
svn checkout http://lm-sensors.org/svn/lm-sensors/branch/lm-sensors-3.0.0 lm-sensors-3

* Submit your patch to the lm-sensors list, I'll review it.

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Ivo Manca]

Hey Jean, Hans,

I will give it a shot. Since I am _completely_ new to this, it might take a 
while.

Ivo


----- Original Message ----- 
From: "Hans de Goede" <j.w.r.degoede@hhs.nl>
To: "Jean Delvare" <khali@linux-fr.org>
Cc: "LM Sensors" <lm-sensors@lm-sensors.org>
Sent: Sunday 1 July 2007 23:13
Subject: Re: [lm-sensors] Help wanted: individual alarm files


> Hi All,
>
> I'll take care of converting the "fscher" driver as my work PC has such a
> beast. I hope to be able todo this soon.
>
> Ivo, if you are reading this, any chance you could try to convert the 
> sis5595
> driver?
>
> Regards,
>
> Hans
>
>
> Jean Delvare wrote:
>> Hi all,
>>
>> The future libsensors assumes that all hardware monitoring drivers
>> follow the standard sysfs interface defined in
>> Documentation/hwmon/sysfs-interface. They all mostly do already, except
>> for one thing: alarms. Most drivers are still only exposing a single
>> file with all alarms in a bit-vector, in chip-dependent order. In order
>> to let the new libsenors display the alarms properly, we must add
>> individual alarm files to these drivers. For some drivers, fault and/or
>> beep files need to be added too.
>>
>> Here's the current status, to the best of my knowledge.
>>
>> Already have individual alarm files:
>> abituguru.c
>> coretemp.c
>> ds1621.c
>> dme1737.c
>> f71805f.c
>> lm63.c
>> lm83.c
>> lm85.c
>> lm90.c
>> pc87427.c
>> smsc47m192.c
>> vt1211.c
>> w83627ehf.c
>> w83793.c
>>
>> Don't have alarms at all:
>> ad7418.c
>> adm1029.c
>> ams
>> applesmc.c
>> atxp1.c
>> hdaps.c
>> k8temp.c
>> lm70.c
>> lm75.c
>> max6650.c
>> smsc47b397.c
>> w83l785ts.c
>>
>> Need to be converted:
>> adm1021.c
>> adm1025.c
>> adm1026.c
>> adm1031.c
>> adm9240.c
>> asb100.c
>> fscher.c
>> fscpos.c
>> gl518sm.c
>> gl520sm.c
>> it87.c
>> lm77.c
>> lm78.c
>> lm80.c
>> lm87.c
>> lm92.c
>> max1619.c
>> pc87360.c
>> sis5595.c
>> smsc47m1.c
>> via686a.c
>> vt8231.c
>> w83627hf.c
>> w83781d.c
>> w83791d.c
>> w83792d.c
>>
>> As you can see, the list is quite long, so I need help. That's not a
>> difficult job, but you need chip ship in question to test.
>>
>> How to add individual alarm files:
>>
>> * Read Documentation/hwmon/sysfs-interface, so that you know what are
>> the valid names for individual alarm, fault and beep files.
>>
>> * Take a look at this patch which adds individual alarm support to 4
>> drivers:
>> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h-45771e6ea79f56a7d85e448f702f60ef86c228#patch2
>>
>> * Do the same to your driver. To find out which alarm bit correspond to
>> what, you can look at the defines used in the current version of
>> libsensors:
>> http://www.lm-sensors.org/browser/lm-sensors/branches/lm-sensors-3.0.0/kernel/include/sensors.h?revD73
>> Or you can look at the datasheet for your chip, but it's likely to take
>> longer.
>>
>> * Test. You can test manually (change the limits and read the alarm
>> files from sysfs) or you can use the next version of libsensors, which
>> is in branch "lm-sensors-3.0.0" under SVN:
>> svn checkout http://lm-sensors.org/svn/lm-sensors/branch/lm-sensors-3.0.0 
>> lm-sensors-3
>>
>> * Submit your patch to the lm-sensors list, I'll review it.
>>
>> Thanks,
>
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors 


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Hans de Goede]

Hi All,

I'll take care of converting the "fscher" driver as my work PC has such a 
beast. I hope to be able todo this soon.

Ivo, if you are reading this, any chance you could try to convert the sis5595 
driver?

Regards,

Hans


Jean Delvare wrote:
> Hi all,
> 
> The future libsensors assumes that all hardware monitoring drivers
> follow the standard sysfs interface defined in
> Documentation/hwmon/sysfs-interface. They all mostly do already, except
> for one thing: alarms. Most drivers are still only exposing a single
> file with all alarms in a bit-vector, in chip-dependent order. In order
> to let the new libsenors display the alarms properly, we must add
> individual alarm files to these drivers. For some drivers, fault and/or
> beep files need to be added too.
> 
> Here's the current status, to the best of my knowledge.
> 
> Already have individual alarm files:
> abituguru.c
> coretemp.c
> ds1621.c
> dme1737.c
> f71805f.c
> lm63.c
> lm83.c
> lm85.c
> lm90.c
> pc87427.c
> smsc47m192.c
> vt1211.c
> w83627ehf.c
> w83793.c
> 
> Don't have alarms at all:
> ad7418.c
> adm1029.c
> ams
> applesmc.c
> atxp1.c
> hdaps.c
> k8temp.c
> lm70.c
> lm75.c
> max6650.c
> smsc47b397.c
> w83l785ts.c
> 
> Need to be converted:
> adm1021.c
> adm1025.c
> adm1026.c
> adm1031.c
> adm9240.c
> asb100.c
> fscher.c
> fscpos.c
> gl518sm.c
> gl520sm.c
> it87.c
> lm77.c
> lm78.c
> lm80.c
> lm87.c
> lm92.c
> max1619.c
> pc87360.c
> sis5595.c
> smsc47m1.c
> via686a.c
> vt8231.c
> w83627hf.c
> w83781d.c
> w83791d.c
> w83792d.c
> 
> As you can see, the list is quite long, so I need help. That's not a
> difficult job, but you need chip ship in question to test.
> 
> How to add individual alarm files:
> 
> * Read Documentation/hwmon/sysfs-interface, so that you know what are
> the valid names for individual alarm, fault and beep files.
> 
> * Take a look at this patch which adds individual alarm support to 4
> drivers:
> http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h-45771e6ea79f56a7d85e448f702f60ef86c228#patch2
> 
> * Do the same to your driver. To find out which alarm bit correspond to
> what, you can look at the defines used in the current version of
> libsensors:
> http://www.lm-sensors.org/browser/lm-sensors/branches/lm-sensors-3.0.0/kernel/include/sensors.h?revD73
> Or you can look at the datasheet for your chip, but it's likely to take
> longer.
> 
> * Test. You can test manually (change the limits and read the alarm
> files from sysfs) or you can use the next version of libsensors, which
> is in branch "lm-sensors-3.0.0" under SVN:
> svn checkout http://lm-sensors.org/svn/lm-sensors/branch/lm-sensors-3.0.0 lm-sensors-3
> 
> * Submit your patch to the lm-sensors list, I'll review it.
> 
> Thanks,


_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Carlos Olalla Martínez]

I will take care of the w83627hf.c driver.
However I wont have time until the weekend.

Carlos

On Sun,
1 Jul 2007 22:00:05 +0200, you wrote:

>Hi all,
>
>The future libsensors assumes that all hardware
monitoring drivers
>follow the standard sysfs interface defined in
>Documentation/hwmon/sysfs-interface. They
all mostly do already, except
>for one thing: alarms. Most drivers are still only exposing a single
>file with
all alarms in a bit-vector, in chip-dependent order. In order
>to let the new libsenors display the alarms properly, we
must add
>individual alarm files to these drivers. For some drivers, fault and/or
>beep files need to be added
too.
>
>Here's the current status, to the best of my knowledge.
>
>Already have individual alarm
files:
>abituguru.c
>coretemp.c
>ds1621.c
>dme1737.c
>f71805f.c
>lm63.c
>lm83.c
>lm85.c
>lm90.c
>pc87427.c
>smsc47m192.c
>vt1211.c
>w83627ehf.c
>w83793.c
>
>Don't have alarms at all:
>ad7418.c
>adm1029.c
>ams
>applesmc.c
>atxp1.c
>hdaps.c
>k8temp.c
>lm70.c
>lm75.c
>max6650.c
>smsc47b397.c
>w83l785ts.c
>
>Need to be converted:
>adm1021.c
>adm1025.c
>adm1026.c
>adm1031.c
>adm9240.c
>asb100.c
>fscher.c
>fscpos.c
>gl518sm.c
>gl520sm.c
>it87.c
>lm77.c
>lm78.c
>lm80.c
>lm87.c
>lm92.c
>max1619.c
>pc87360.c
>sis5595.c
>smsc47m1.c
>via686a.c
>vt8231.c
>w83627hf.c
>w83781d.c
>w83791d.c
>w83792d.c
>
>As you can see,
the list is quite long, so I need help. That's not a
>difficult job, but you need chip ship in question to test.
>
>How to add individual alarm files:
>
>* Read Documentation/hwmon/sysfs-interface, so that you
know what are
>the valid names for individual alarm, fault and beep files.
>
>* Take a look at this
patch which adds individual alarm support to 4
>drivers:
>http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h-45771e6ea79f56a7d85e448f702f60ef86c228#patch2
>
>* Do the same to your driver. To find out which alarm bit correspond to
>what, you can look at the
defines used in the current version of
>libsensors:
>http://www.lm-sensors.org/browser/lm-sensors/branches/lm-sensors-3.0.0/kernel/include/sensors.h?revD73
>Or you
can look at the datasheet for your chip, but it's likely to take
>longer.
>
>* Test. You can test
manually (change the limits and read the alarm
>files from sysfs) or you can use the next version of libsensors,
which
>is in branch "lm-sensors-3.0.0" under SVN:
>svn checkout
http://lm-sensors.org/svn/lm-sensors/branch/lm-sensors-3.0.0 lm-sensors-3
>
>* Submit your patch to the
lm-sensors list, I'll review it.
>
>Thanks,



_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[JGong]

Hi Jean,

>The future libsensors assumes that all hardware monitoring drivers
>follow the standard sysfs interface defined in
>Documentation/hwmon/sysfs-interface. They all mostly do already, except
>for one thing: alarms. Most drivers are still only exposing a single
>file with all alarms in a bit-vector, in chip-dependent order. In order
>to let the new libsenors display the alarms properly, we must add
>individual alarm files to these drivers. For some drivers, fault and/or
>beep files need to be added too.

I'd like to take care of w83792d chip's converting work. It will be
finished in the next week.

And could you please give me some information about the ASUS motherboard
with w83791d chip using for hardware monitor function? 

Any help will be welcome.

Best regards,
Gong Jun


=============================================The privileged confidential information contained in this email is intended for use only by the addressees as indicated by the original sender of this email. If you are not the addressee indicated in this email or are not responsible for delivery of the email to such  a person, please kindly reply to the sender indicating this fact and delete all copies of it from your computer and network server immediately. Your cooperation is highly appreciated. It is advised that any unauthorized use of confidential information of Winbond is strictly prohibited; and any information in this email irrelevant to the official business of Winbond shall be deemed as neither given nor endorsed by Winbond.

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Jean Delvare]

Hi Gong Jun,

On Thu, 5 Jul 2007 19:27:40 +0800, JGong@winbond.com wrote:
> >The future libsensors assumes that all hardware monitoring drivers
> >follow the standard sysfs interface defined in
> >Documentation/hwmon/sysfs-interface. They all mostly do already, except
> >for one thing: alarms. Most drivers are still only exposing a single
> >file with all alarms in a bit-vector, in chip-dependent order. In order
> >to let the new libsenors display the alarms properly, we must add
> >individual alarm files to these drivers. For some drivers, fault and/or
> >beep files need to be added too.
> 
> I'd like to take care of w83792d chip's converting work. It will be
> finished in the next week.

Great, thanks!

> And could you please give me some information about the ASUS motherboard
> with w83791d chip using for hardware monitor function? 
> 
> Any help will be welcome.

I don't know, sorry. The only system I know using a W83791D is the Acer
Altos R300 server. Charles Spirakis (Cc'd) wrote the Linux 2.6 w83791d
driver, he should be able to tell you which system he was using.

-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Krzysztof Helt]

On Sun, 1 Jul 2007 22:00:05 +0200
Jean Delvare <khali@linux-fr.org> wrote:

> Need to be converted:
> adm1021.c

I'll take care of it. I have already converted it to dynamic sysfs calls. The next patch will add alarm
files.

Regards,
Krzysztof

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Charles Spirakis]

A little late to the party, but I'll take care of converting the w83791d.

I'll try to get this done either this weekend or next (is there a
preferred time frame)?

-- charles


On 7/9/07, Krzysztof Helt <krzysztof.h1@wp.pl> wrote:
> On Sun, 1 Jul 2007 22:00:05 +0200
> Jean Delvare <khali@linux-fr.org> wrote:
>
> > Need to be converted:
> > adm1021.c
>
> I'll take care of it. I have already converted it to dynamic sysfs calls. The next patch will add alarm
> files.
>
> Regards,
> Krzysztof
>
> _______________________________________________
> lm-sensors mailing list
> lm-sensors@lm-sensors.org
> http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
>

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Jean Delvare]

Hi Charles,

On Thu, 19 Jul 2007 18:27:37 -0700, Charles Spirakis wrote:
> A little late to the party, but I'll take care of converting the w83791d.
> 
> I'll try to get this done either this weekend or next (is there a
> preferred time frame)?

"As your time permits" if the preferred time frame :)

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Jean Delvare]

Hi Ivo,

Hans de Goede wrote:
> > Ivo, if you are reading this, any chance you could try to convert the 
> > sis5595 driver?

On Sun, 1 Jul 2007 23:05:55 +0200, Ivo Manca wrote:
> I will give it a shot. Since I am _completely_ new to this, it might take a 
> while.

Any news on this?

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Jean Delvare]

On Sun, 1 Jul 2007 22:00:05 +0200, Jean Delvare wrote:
> The future libsensors assumes that all hardware monitoring drivers
> follow the standard sysfs interface defined in
> Documentation/hwmon/sysfs-interface. They all mostly do already, except
> for one thing: alarms. Most drivers are still only exposing a single
> file with all alarms in a bit-vector, in chip-dependent order. In order
> to let the new libsenors display the alarms properly, we must add
> individual alarm files to these drivers. For some drivers, fault and/or
> beep files need to be added too.
> 
> Here's the current status, to the best of my knowledge.

Updated list:

Recently converted:
adm1021.c (Krzysztof Helt)
lm78.c (Jean Delvare)
lm85.c (Jean Delvare)
lm87.c (Jean Delvare)
thmc50.c (Krzysztof Helt)
w83791d.c (Charles Spirakis)
w83792d.c (Gong Jun)

Superseded by a newer driver:
fscher.c
fscpos.c

Still need to be converted:
adm1025.c
adm1026.c
adm1031.c
adm9240.c
asb100.c
gl518sm.c
gl520sm.c
it87.c
lm77.c
lm80.c
lm92.c
max1619.c
pc87360.c
sis5595.c (Ivo Manco volunteered)
smsc47m1.c
via686a.c
vt8231.c
w83627hf.c (Carlos Olalla Martínez volunteered)
w83781d.c

The list is shorter, thanks to everyone who helped so far. More help
would of course be appreciated, as we are about to release lm-sensors
3.0.0 and it needs these individual alarm files. I will try to convert
some more drivers this afternoon, next on my list is w83781d.

Thanks,
-- 
Jean Delvare

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors

Re: [lm-sensors] Help wanted: individual alarm files

[Ivo Manca]

Hey Jean,

To be honest, I've haven't looked into it, yet. I'll try to hook up my 
machine this evening to get it running. Then, I'll try to convert it as 
soon as possible.

I'll report back next weekend.

Ivo

Jean Delvare wrote:
> Hi Ivo,
>
> Hans de Goede wrote:
>   
>>> Ivo, if you are reading this, any chance you could try to convert the 
>>> sis5595 driver?
>>>       
>
> On Sun, 1 Jul 2007 23:05:55 +0200, Ivo Manca wrote:
>   
>> I will give it a shot. Since I am _completely_ new to this, it might take a 
>> while.
>>     
>
> Any news on this?
>
> Thanks,
>   

_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors