| BGardner@Wabtec.com | c3bc4ca | 2005-06-03 13:03:27 -0400 | [diff] [blame] | 1 | Kernel driver max6875 |
| 2 | ===================== |
| 3 | |
| 4 | Supported chips: |
| 5 | * Maxim max6874, max6875 |
| 6 | Prefixes: 'max6875' |
| 7 | Addresses scanned: 0x50, 0x52 |
| 8 | Datasheets: |
| 9 | http://pdfserv.maxim-ic.com/en/ds/MAX6874-MAX6875.pdf |
| 10 | |
| 11 | Author: Ben Gardner <bgardner@wabtec.com> |
| 12 | |
| 13 | |
| 14 | Module Parameters |
| 15 | ----------------- |
| 16 | |
| 17 | * allow_write int |
| 18 | Set to non-zero to enable write permission: |
| 19 | *0: Read only |
| 20 | 1: Read and write |
| 21 | |
| 22 | |
| 23 | Description |
| 24 | ----------- |
| 25 | |
| 26 | The MAXIM max6875 is a EEPROM-programmable power-supply sequencer/supervisor. |
| 27 | It provides timed outputs that can be used as a watchdog, if properly wired. |
| 28 | It also provides 512 bytes of user EEPROM. |
| 29 | |
| 30 | At reset, the max6875 reads the configuration eeprom into its configuration |
| 31 | registers. The chip then begins to operate according to the values in the |
| 32 | registers. |
| 33 | |
| 34 | See the datasheet for details on how to program the EEPROM. |
| 35 | |
| 36 | |
| 37 | Sysfs entries |
| 38 | ------------- |
| 39 | |
| 40 | eeprom_user - 512 bytes of user-defined EEPROM space. Only writable if |
| 41 | allow_write was set and register 0x43 is 0. |
| 42 | |
| 43 | eeprom_config - 70 bytes of config EEPROM. Note that changes will not get |
| 44 | loaded into register space until a power cycle or device reset. |
| 45 | |
| 46 | reg_config - 70 bytes of register space. Any changes take affect immediately. |
| 47 | |
| 48 | |
| 49 | General Remarks |
| 50 | --------------- |
| 51 | |
| 52 | A typical application will require that the EEPROMs be programmed once and |
| 53 | never altered afterwards. |
| 54 | |