Re: [PATCH v3 8/8] iio: accel: kxcjk-1013: optimize i2c transfers in trigger handler

On 03/07/15 10:33, Irina Tirdea wrote: > From: Adriana Reus > > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to > enable/disable the bus at each i2c transfer and must wait for > the enable/disable to happen before sending the data. > > When reading data in the trigger handler, th

Re: [PATCH v3 7/8] iio: accel: kxcjk-1013: use available_scan_masks

On 03/07/15 10:33, Irina Tirdea wrote: > From: Adriana Reus > > Use available_scan_masks to allow the iio core to select > the data to send to userspace depending on which axes are > enabled, instead of doing this in the driver's interrupt > handler. > > Signed-off-by: Adriana Reus > Signed-off

Re: [PATCH v3 3/8] iio: accel: bmc150: use available_scan_masks

On 03/07/15 10:33, Irina Tirdea wrote: > Use available_scan_masks to allow the iio core to select > the data to send to userspace depending on which axes are > enabled, instead of doing this in the driver's interrupt > handler. > > Signed-off-by: Irina Tirdea I guess people almost always want all

Re: [PATCH v3 6/8] iio: gyro: bmg160: optimize i2c transfers in trigger handler

On 03/07/15 10:33, Irina Tirdea wrote: > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to > enable/disable the bus at each i2c transfer and must wait for > the enable/disable to happen before sending the data. > > When reading data in the trigger handler, the bmg160 driver does > on

Re: [PATCH v3 4/8] iio: accel: bmc150: optimize i2c transfers in trigger handler

On 03/07/15 10:33, Irina Tirdea wrote: > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to > enable/disable the bus at each i2c transfer and must wait for > the enable/disable to happen before sending the data. > > When reading data in the trigger handler, the bmc150 accel driver doe

Re: [PATCH v3 1/8] i2c: core: Add support for best effort block read emulation

On 03/07/15 10:33, Irina Tirdea wrote: > There are devices that need to handle block transactions > regardless of the capabilities exported by the adapter. > For performance reasons, they need to use i2c read blocks > if available, otherwise emulate the block transaction with word > or byte transac

Re: i2c: i2c-mv64xxx: rework offload support to fix several problems

Dear Antony Pavlov, On Sat, 4 Jul 2015 09:59:08 +0300, Antony Pavlov wrote: > I have found your commit in the linux kernel mainline > > commit 00d8689b85a7bb37cc57ba4c40bd46325f51ced4 > Author: Thomas Petazzoni > Date: Thu Dec 11 17:33:46 2014 +0100 > > i2c: mv64xxx: rework offlo

Re: i2c: i2c-mv64xxx: rework offload support to fix several problems

Hi! I have found your commit in the linux kernel mainline commit 00d8689b85a7bb37cc57ba4c40bd46325f51ced4 Author: Thomas Petazzoni Date: Thu Dec 11 17:33:46 2014 +0100 i2c: mv64xxx: rework offload support to fix several problems see also https://patchwork.ozlabs.org/patch/420180/