headers
Jean Delvare | 1 Mar 2006 12:21
Gravatar

Re: 2.6.15.1 Kernel patch for hardware monitoring support for SMSC 47M192/47M997


Hi Hartmut,

On 2006-02-28, Hartmut Rick wrote:
> > 1* The LPC47M192 chip has two sampling modes, which can be selected
> > using the bit 1 of register 0x4F. Currently your driver leaves the
> > chip in the mode in which it was found. However, given that we do not
> > allow the user to refresh the data more often than every 1.5 second,
> > wouldn't it make sense to switch the device to "cycle mode" so as to
> > save some power?
>
> I have to admit that I've been a bit sloppy at my first attempt at the
> chip driver. I didn't bother to worry about power consumption, since
> the hardware monitoring block needs typically 1.2mA at a voltage of
> 3.3V, which makes a total of about 4mW. And it needs about half a second
> in order to complete all the conversions, so there is not much time
> during which it would not be active anyway.
>
> But of course you're right, as long as we don't read it more often
> anyway we don't need it to sample more frequently.
> I will change that.

Your analysis is correct and I admit it won't change that much the
overall power consumption. But every saving we can get for free is good,
so let's do it still.

> There are more options, the sampling can be completed 8 times faster,
> with fewer conversions averaged. One could imagine to give the user
> access to configuration registers in order to choose these things. You
> could read the faster and (probably) noisier value and average in
(Continue reading)

Permalink | Reply | 13 comments |
headers
Hans de Goede | 1 Mar 2006 12:49
Picon

Re: 2.6.15.1 Kernel patch for hardware monitoring support for SMSC 47M192/47M997


Jean Delvare wrote:
> This was the whole point of the sysfs interface in the first place, but
> we failed for some points, in particular the chip status
> (alarm/fault/beep etc.) :( Good if we can get it right for the
> smsc47m192 driver right away.
> 

Notice that I have posted a proposal to extend the sysfs interface with 
a coherent alarm / beep interface, unfortunatly I haven't had any 
reactions. I can repost it if you want.

Regards,

Hans

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Permalink | Reply | 0 comments |
headers
Bruce Allen | 1 Mar 2006 17:14
Picon
Favicon

HT1000 support (see lm_sensors ticket 2031, new chips page)

I'd like to get lm_sensors support for a system with an HT1000 chip.
References are on http://www2.lm-sensors.nu/~lm78/newdrivers.html

-- I've rebuilt a stock 2.6.15.4 kernel using the HT1000 patch referenced
    on the newdrivers page:
    http://khali.linux-fr.org/devel/i2c/linux-2.6/i2c-piix4-add-ht1000-support.patch

-- I then built and installed sysfsutils-2.0.0

-- I then built and installed lm_sensors-2.10.0.

-- I loaded the i2c_piix4 module using modprobe.

-- I mounted sysfs on /sysfs

However sensors-detect does not find ANYTHING.  Not even eeprom!  Am I 
doing something stupid?

(Note: for kicks I also went into the lm_sensors source and 'hacked' the 
SERVERWORKS CSB6 0x0203 PCI-id to be 0x0205 both the sensors-detect script 
and in the i2c_piix4 code contained there. It didn't help.)

One other possibility is that because I have a BMC card plugged in to the 
motherboard (SuperMicro H8SSL-i) the BMC card is not allowing access to 
the devices from lm_sensors.

Cheers,
 	Bruce

_______________________________________________
(Continue reading)

Permalink | Reply | 9 comments |
headers
Jean Delvare | 1 Mar 2006 20:19
Gravatar

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

Hi Bruce,

> I'd like to get lm_sensors support for a system with an HT1000 chip.
> References are on http://www2.lm-sensors.nu/~lm78/newdrivers.html
> 
> -- I've rebuilt a stock 2.6.15.4 kernel using the HT1000 patch referenced
>     on the newdrivers page:
>     http://khali.linux-fr.org/devel/i2c/linux-2.6/i2c-piix4-add-ht1000-support.patch
> 
> -- I then built and installed sysfsutils-2.0.0
> 
> -- I then built and installed lm_sensors-2.10.0.
> 
> -- I loaded the i2c_piix4 module using modprobe.
> 
> -- I mounted sysfs on /sysfs
> 
> However sensors-detect does not find ANYTHING.  Not even eeprom!  Am I 
> doing something stupid?

The HT-1000 is (from our simplified point of view) an SMBus master. It
may give you access to I2C/SMBus hardware monitoring chips, but isn't
itself a hardware monitoring chip.

> (Note: for kicks I also went into the lm_sensors source and 'hacked' the 
> SERVERWORKS CSB6 0x0203 PCI-id to be 0x0205 both the sensors-detect script 
> and in the i2c_piix4 code contained there. It didn't help.)

The i2c-piix4 driver found in the lm_sensors is a Linux 2.4 driver, so
it is of no use to you.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Martin Devera | 1 Mar 2006 21:23
Picon
Favicon

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

> One other possibility is that because I have a BMC card plugged in to 
> the motherboard (SuperMicro H8SSL-i) the BMC card is not allowing access 
> to the devices from lm_sensors.

it works well for me for the same MB, only loaded patched piix4 and then
adm1026 module. Then even supermicro's superodoctor started to work on 
the bow :) But I can imagine that it may become unavailable after BMC is 
plugged in. I havn't bought BMC yet but I want to.

By the way, Jean, is it possible to have two masters on one i2c bus ? 
How are priorities handled then ?

devik

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Permalink | Reply | 6 comments |
headers
Bruce Allen | 1 Mar 2006 21:53
Picon
Favicon

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

>> One other possibility is that because I have a BMC card plugged in to the 
>> motherboard (SuperMicro H8SSL-i) the BMC card is not allowing access to the 
>> devices from lm_sensors.
>
> it works well for me for the same MB, only loaded patched piix4 and then
> adm1026 module. Then even supermicro's superodoctor started to work on the 
> bow :) But I can imagine that it may become unavailable after BMC is plugged 
> in. I havn't bought BMC yet but I want to.

I loaded the adm1026 module by hand:

[root <at> nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
adm1026                46736  0
i2c_piix4              14480  0
adm1025                27156  0
hwmon_vid               7040  2 adm1026,adm1025
i2c_isa                10624  0
i2c_dev                17408  0
i2c_core               30720  6 adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev

I have:
[root <at> nemo-slave0017 ~]# ls /sysfs
block  bus  class  devices  firmware  kernel  module  power
[root <at> nemo-slave0017 ~]# ls /sys
block  bus  class  devices  firmware  kernel  module  power

sensors-detect reports: "Sorry, no chips were detected."

[root <at> nemo-slave0017 ~]# sensors
Can't access procfs/sysfs file
(Continue reading)

Permalink | Reply | 4 comments |
headers
Martin Devera | 1 Mar 2006 21:57
Picon
Favicon

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

> I loaded the adm1026 module by hand:
> 
> [root <at> nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
> adm1026                46736  0
> i2c_piix4              14480  0
> adm1025                27156  0
> hwmon_vid               7040  2 adm1026,adm1025
> i2c_isa                10624  0
> i2c_dev                17408  0
> i2c_core               30720  6 
> adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev
> 
> I have:
> [root <at> nemo-slave0017 ~]# ls /sysfs
> block  bus  class  devices  firmware  kernel  module  power
> [root <at> nemo-slave0017 ~]# ls /sys
> block  bus  class  devices  firmware  kernel  module  power
> 

send
dmesg|tail -n 30
and try
ls /sys/class
(there is typicaly hwmon class, if yes, list it too)

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
(Continue reading)

Permalink | Reply | 3 comments |
headers
Thomas E Lackey | 1 Mar 2006 22:01

Re: Proposed Patch for default sensors.conf

Rudolf Marek wrote:
> Hello,
>
> Sorry for the delay. Applied
>
> Thanks,
>
> Regards
> Rudolf
>   
Thanks!

--

-- 
Thomas E Lackey

_______________________________________________
lm-sensors mailing list
lm-sensors <at> lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
Permalink | Reply | 0 comments |
headers
Bruce Allen | 1 Mar 2006 22:03
Picon
Favicon

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

>> -- I've rebuilt a stock 2.6.15.4 kernel using the HT1000 patch referenced
>>     on the newdrivers page:
>>     http://khali.linux-fr.org/devel/i2c/linux-2.6/i2c-piix4-add-ht1000-support.patch
>>
>> -- I then built and installed sysfsutils-2.0.0
>>
>> -- I then built and installed lm_sensors-2.10.0.
>>
>> -- I loaded the i2c_piix4 module using modprobe.
>>
>> -- I mounted sysfs on /sysfs
>>
>> However sensors-detect does not find ANYTHING.  Not even eeprom!  Am I
>> doing something stupid?
>
> The HT-1000 is (from our simplified point of view) an SMBus master. It
> may give you access to I2C/SMBus hardware monitoring chips, but isn't
> itself a hardware monitoring chip.

OK.  I tried loading the adm1026 module that Martin uses -- no go.
>
>> (Note: for kicks I also went into the lm_sensors source and 'hacked' the
>> SERVERWORKS CSB6 0x0203 PCI-id to be 0x0205 both the sensors-detect script
>> and in the i2c_piix4 code contained there. It didn't help.)
>
> The i2c-piix4 driver found in the lm_sensors is a Linux 2.4 driver, so
> it is of no use to you.

OK.  In any case I am loading the i2c-piix4 modules from the (modified) 
2.6.15 tree.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Bruce Allen | 1 Mar 2006 23:07
Picon
Favicon

Re: HT1000 support (see lm_sensors ticket 2031, new chips page)

>> I loaded the adm1026 module by hand:
>> 
>> [root <at> nemo-slave0017 ~]# lsmod | egrep '(i2c|adm)'
>> adm1026                46736  0
>> i2c_piix4              14480  0
>> adm1025                27156  0
>> hwmon_vid               7040  2 adm1026,adm1025
>> i2c_isa                10624  0
>> i2c_dev                17408  0
>> i2c_core               30720  6 
>> adm1026,i2c_piix4,adm1025,eeprom,i2c_isa,i2c_dev
>> 
>> I have:
>> [root <at> nemo-slave0017 ~]# ls /sysfs
>> block  bus  class  devices  firmware  kernel  module  power
>> [root <at> nemo-slave0017 ~]# ls /sys
>> block  bus  class  devices  firmware  kernel  module  power
>> 
>
> send
> dmesg|tail -n 30

[root <at> nemo-slave0017 ~]# modprobe i2c_piix4
[root <at> nemo-slave0017 ~]# modprobe adm1026
[root <at> nemo-slave0017 ~]# dmesg | tail -n 30
md: ... autorun DONE.
device-mapper: 4.4.0-ioctl (2005-01-12) initialised: dm-devel <at> redhat.com
cdrom: open failed.
cdrom: open failed.
EXT3 FS on sda3, internal journal
(Continue reading)

Permalink | Reply | 2 comments |

Gmane