[PATCH v4 0/8] Add support for best effort block read emulation
From: Irina Tirdea
Date: Tue Aug 04 2015 - 10:04:57 EST
This is version 4 for adding i2c_smbus_read_i2c_block_data_or_emulated
to i2c-core.
Changes from v3:
- when reading an odd number of bytes using word emulation, read an even
number of bytes using word reads and the last byte using byte read
- code styling changes to improve readability
- add a comment about addressing assumptions to the
i2c_smbus_read_i2c_block_data_or_emulated function as Jonathan suggested
- add Acked-by from Jonathan and Srinivas to the iio changes
Changes from v2:
- changed bmc150-accel, kxcjk-1013 and bmg160 drivers to use
i2c_smbus_read_i2c_block_data_or_emulated
Changes from v1:
- dropped the RFC tag
- changed at24 to use i2c_smbus_read_i2c_block_data_or_emulated
- when reading an odd number of bytes using word emulation, read an even
number of bytes and drop the last one
- add a comment that this might not be suitable for all I2C slaves
Adriana Reus (2):
iio: accel: kxcjk-1013: use available_scan_masks
iio: accel: kxcjk-1013: optimize i2c transfers in trigger handler
Irina Tirdea (6):
i2c: core: Add support for best effort block read emulation
eeprom: at24: use i2c_smbus_read_i2c_block_data_or_emulated
iio: accel: bmc150: use available_scan_masks
iio: accel: bmc150: optimize i2c transfers in trigger handler
iio: gyro: bmg160: use available_scan_masks
iio: gyro: bmg160: optimize i2c transfers in trigger handler
drivers/i2c/i2c-core.c | 65 ++++++++++++++++++++++++++++++++++++++++
drivers/iio/accel/bmc150-accel.c | 23 +++++++-------
drivers/iio/accel/kxcjk-1013.c | 24 +++++++--------
drivers/iio/gyro/bmg160.c | 23 +++++++-------
drivers/misc/eeprom/at24.c | 37 ++++-------------------
include/linux/i2c.h | 3 ++
6 files changed, 110 insertions(+), 65 deletions(-)
--
1.9.1
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/