Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-27 Thread Andy Gross
On Mon, Feb 19, 2018 at 04:26:18PM +0530, Abhishek Sahu wrote: > On 2018-02-16 10:18, Sricharan R wrote: > >On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > >>Currently the completion timeout is being taken according to > >>maximum transfer length which is too high if SCL is operating in > >>high

Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-27 Thread Andy Gross
On Mon, Feb 19, 2018 at 04:26:18PM +0530, Abhishek Sahu wrote: > On 2018-02-16 10:18, Sricharan R wrote: > >On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > >>Currently the completion timeout is being taken according to > >>maximum transfer length which is too high if SCL is operating in > >>high

Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 10:18, Sricharan R wrote: On 2/3/2018 1:28 PM, Abhishek Sahu wrote: Currently the completion timeout is being taken according to maximum transfer length which is too high if SCL is operating in high frequency. This patch calculates timeout on the basis of one-byte transfer time

Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 10:18, Sricharan R wrote: On 2/3/2018 1:28 PM, Abhishek Sahu wrote: Currently the completion timeout is being taken according to maximum transfer length which is too high if SCL is operating in high frequency. This patch calculates timeout on the basis of one-byte transfer time

Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-15 Thread Sricharan R
On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > Currently the completion timeout is being taken according to > maximum transfer length which is too high if SCL is operating in > high frequency. This patch calculates timeout on the basis of > one-byte transfer time and uses the same for completion

Re: [PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-15 Thread Sricharan R
On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > Currently the completion timeout is being taken according to > maximum transfer length which is too high if SCL is operating in > high frequency. This patch calculates timeout on the basis of > one-byte transfer time and uses the same for completion

[PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-03 Thread Abhishek Sahu
Currently the completion timeout is being taken according to maximum transfer length which is too high if SCL is operating in high frequency. This patch calculates timeout on the basis of one-byte transfer time and uses the same for completion timeout. Signed-off-by: Abhishek Sahu

[PATCH 08/12] i2c: qup: change completion timeout according to transfer length

2018-02-03 Thread Abhishek Sahu
Currently the completion timeout is being taken according to maximum transfer length which is too high if SCL is operating in high frequency. This patch calculates timeout on the basis of one-byte transfer time and uses the same for completion timeout. Signed-off-by: Abhishek Sahu ---