> Do we want to insist on a much larger change (conversion to regmap)
> when if this in place, a simple single functional call change will do the
> job?
I'd assume that regmap conversion will happen later quite likely anyhow.
Most of those devices will have I2C/SPI dual interfaces; or people
Do we want to insist on a much larger change (conversion to regmap)
when if this in place, a simple single functional call change will do the
job?
I'd assume that regmap conversion will happen later quite likely anyhow.
Most of those devices will have I2C/SPI dual interfaces; or people will
On 22/08/15 05:02, Wolfram Sang wrote:
>
The series[1] I am working on implements a i2c smbus block data
regmap
bus driver. Regmap should then automatically do a block read in
regmap_bulk_read.
>>>
>>> Hmm, so doesn't your series make Irina's series obsolete? It
>>>
On 22/08/15 05:02, Wolfram Sang wrote:
The series[1] I am working on implements a i2c smbus block data
regmap
bus driver. Regmap should then automatically do a block read in
regmap_bulk_read.
Hmm, so doesn't your series make Irina's series obsolete? It
addresses
the same problem only
> > > The series[1] I am working on implements a i2c smbus block data
> > > regmap
> > > bus driver. Regmap should then automatically do a block read in
> > > regmap_bulk_read.
> >
> > Hmm, so doesn't your series make Irina's series obsolete? It
> > addresses
> > the same problem only at a
On Fri, 2015-08-21 at 12:21 +0200, Wolfram Sang wrote:
> On Mon, Aug 17, 2015 at 11:09:43AM +0200, Markus Pargmann wrote:
> > On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
> > > On 12/08/15 15:31, Irina Tirdea wrote:
> > > > Some i2c busses (e.g.: Synopsys DesignWare I2C
On Mon, Aug 17, 2015 at 11:09:43AM +0200, Markus Pargmann wrote:
> On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
> > On 12/08/15 15:31, Irina Tirdea wrote:
> > > Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
> > > enable/disable the bus at each i2c transfer
The series[1] I am working on implements a i2c smbus block data
regmap
bus driver. Regmap should then automatically do a block read in
regmap_bulk_read.
Hmm, so doesn't your series make Irina's series obsolete? It
addresses
the same problem only at a different layer (i2c
On Fri, 2015-08-21 at 12:21 +0200, Wolfram Sang wrote:
On Mon, Aug 17, 2015 at 11:09:43AM +0200, Markus Pargmann wrote:
On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
On 12/08/15 15:31, Irina Tirdea wrote:
Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
On Mon, Aug 17, 2015 at 11:09:43AM +0200, Markus Pargmann wrote:
On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
On 12/08/15 15:31, Irina Tirdea wrote:
Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
enable/disable the bus at each i2c transfer and must
nivas; Peter Meerwald
> Subject: Re: [PATCH v5 6/8] iio: gyro: bmg160: optimize i2c transfers in
> trigger handler
>
> On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
> > On 12/08/15 15:31, Irina Tirdea wrote:
> > > Some i2c busses (e.g.: Synopsys Desi
; Subject: Re: [PATCH v5 6/8] iio: gyro: bmg160: optimize i2c transfers in
> trigger handler
>
> On 12/08/15 15:31, 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
>
On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
> On 12/08/15 15:31, 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.
Subject: Re: [PATCH v5 6/8] iio: gyro: bmg160: optimize i2c transfers in
trigger handler
On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
On 12/08/15 15:31, Irina Tirdea wrote:
Some i2c busses (e.g.: Synopsys DesignWare I2C adapter) need to
enable/disable the bus at each i2c
On Sun, Aug 16, 2015 at 10:24:47AM +0100, Jonathan Cameron wrote:
On 12/08/15 15:31, 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.
] iio: gyro: bmg160: optimize i2c transfers in
trigger handler
On 12/08/15 15:31, 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
On 12/08/15 15:31, 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 12/08/15 15:31, 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
one i2c
18 matches
Mail list logo
