Re: [PATCH v2 1/2] i2c: mediatek: add i2c first write then read optimization

2015-11-30 Thread Wolfram Sang
On Mon, Nov 09, 2015 at 01:43:58PM +0800, Liguo Zhang wrote: > For platform with auto restart support, between every transfer, > i2c controller will trigger an interrupt and SW need to handle > it to start new transfer. When doing write-then-read transfer, > instead of restart mechanism, using WRRD

Re: [PATCH v2 1/2] i2c: mediatek: add i2c first write then read optimization

2015-11-09 Thread Yingjoe Chen
On Mon, 2015-11-09 at 16:25 +0200, Andy Shevchenko wrote: > On Mon, Nov 9, 2015 at 7:43 AM, Liguo Zhang wrote: > > For platform with auto restart support, between every transfer, > > i2c controller will trigger an interrupt and SW need to handle > > it to start new transfer. When doing write-then-

Re: [PATCH v2 1/2] i2c: mediatek: add i2c first write then read optimization

2015-11-09 Thread Daniel Kurtz
On Mon, Nov 9, 2015 at 10:25 PM, Andy Shevchenko wrote: > On Mon, Nov 9, 2015 at 7:43 AM, Liguo Zhang wrote: >> For platform with auto restart support, between every transfer, >> i2c controller will trigger an interrupt and SW need to handle >> it to start new transfer. When doing write-then-read

Re: [PATCH v2 1/2] i2c: mediatek: add i2c first write then read optimization

2015-11-09 Thread Andy Shevchenko
On Mon, Nov 9, 2015 at 7:43 AM, Liguo Zhang wrote: > For platform with auto restart support, between every transfer, > i2c controller will trigger an interrupt and SW need to handle > it to start new transfer. When doing write-then-read transfer, > instead of restart mechanism, using WRRD mode to

[PATCH v2 1/2] i2c: mediatek: add i2c first write then read optimization

2015-11-08 Thread Liguo Zhang
For platform with auto restart support, between every transfer, i2c controller will trigger an interrupt and SW need to handle it to start new transfer. When doing write-then-read transfer, instead of restart mechanism, using WRRD mode to have controller send both transfer in one request to reduce