root/lm-sensors/branches/lm-sensors-2.10/doc/chips/mic74

Revision 3007, 1.6 KB (checked in by khali, 7 years ago)

Backport the cleanups and corrections Rudolf Marek and I did when
porting the chips documentation to Linux 2.6.

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
Line 
1Kernel driver `mic74.o'
2=========================
3
4Status: Beta
5
6Supported chips:
7  * Micrel MIC74
8    Prefix: 'mic74'
9    Addresses scanned: I2C 0x20 - 0x27
10    Datasheet: Publicly available at the Micrel website
11               http://www.micrel.com/
12
13Authors: zebo25
14         mds (cleanups and this doc)
15
16Module Parameters
17-----------------
18
19
20Description
21-----------
22The MIC74 is an 8-bit I/O expander for the I2C bus.
23Semiconductors. It is designed to provide a byte I2C interface to up to 8
24separate devices.
25
26This device consists of a quasi-bidirectionnal port. Each of the eight I/Os
27can be independently used as an input or output.
28
29The driver does not initialize the ports, they will be at their
30power-up defaults, or however the BIOS programmed them.
31
32For more information see the datasheet.
33
34
35Accessing MIC74 via /proc interface
36-------------------------------------
37
38! Be careful !
39The chip is plainly impossible to detect ! Stupid chip.
40So every chip with adress in the interval [20..27] could be
41detected as an MIC74 or a PCF8574. Don't load both drivers.
42If you have other chips in this address
43range, the workaround is to load this module after the one
44for your others chips.
45
46On detection, directories are created for each detected chip:
47
48        /proc/sys/dev/sensors/mic74-<0>-<1>/
49        where <0> is the bus the chip was detected on (e. g. i2c-0)
50        and <1> the chip address [20..27]:
51        ./mic74-i2c-0-27/
52
53Inside these directories, there are seven files each,
54one for each of the seven registers in the device.
55
56At this point you really need the datasheet.
57It should be self-explanatory which file is for which register.
Note: See TracBrowser for help on using the browser.