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

2015-07-10 Thread Pandruvada, Srinivas
vger.kernel.org > > Cc: linux-ker...@vger.kernel.org; Pandruvada, Srinivas; Peter Meerwald > > Subject: 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.: Synop

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

2015-07-10 Thread Tirdea, Irina
ubject: 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 > >

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

2015-07-05 Thread Jonathan Cameron
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

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

2015-07-03 Thread Irina Tirdea
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 one i2c transfer for each axis. This has an impact on