b0fdbfcec5
The FDT bindings for eeprom parts don't include any metadata about the device other than the part name encoded in the compatible property. Instead, a driver is required to have a compiled-in table of information about the various parts (page size, device capacity, addressing scheme). So much for FDT being an abstract description of hardware characteristics, huh? In addition to the FDT-specific changes, this also switches to using the newer iicbus_transfer_excl() mechanism which holds bus ownership for the duration of the transfer. Previously this code held the bus across all the transfers needed to complete the user's IO request, which could be up to 128KB of data which might occupy the bus for 10-20 seconds. Now the bus will be released and re-aquired between every page-sized (8-256 byte) transfer, making this driver a much nicer citizen on the i2c bus. The hint-based configuration mechanism is still in place for non-FDT systems. Michal Meloun contributed some of the code for these changes. |
||
|---|---|---|
| .. | ||
| ad7417.c | ||
| ad7418.c | ||
| adm1030.c | ||
| adt746x.c | ||
| ds133x.c | ||
| ds1307.c | ||
| ds1307reg.h | ||
| ds1374.c | ||
| ds1631.c | ||
| ds1672.c | ||
| ds1775.c | ||
| ds3231.c | ||
| ds3231reg.h | ||
| icee.c | ||
| if_ic.c | ||
| iic.c | ||
| iic.h | ||
| iicbb_if.m | ||
| iicbb.c | ||
| iicbus_if.m | ||
| iicbus.c | ||
| iicbus.h | ||
| iicoc.c | ||
| iicoc.h | ||
| iiconf.c | ||
| iiconf.h | ||
| iicsmb.c | ||
| lm75.c | ||
| max6690.c | ||
| pcf8563.c | ||
| pcf8563reg.h | ||
| s35390a.c | ||