Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-19 Thread Sricharan R
Hi Abhishek, On 2/19/2018 6:51 PM, Abhishek Sahu wrote: > On 2018-02-16 13:14, Sricharan R wrote: >> Hi Abhishek, >> >> On 2/3/2018 1:28 PM, Abhishek Sahu wrote: >>> Following are the major issues in current driver code >>> >>> 1. The current driver simply assumes the transfer completion >>>   

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-19 Thread Sricharan R
Hi Abhishek, On 2/19/2018 6:51 PM, Abhishek Sahu wrote: > On 2018-02-16 13:14, Sricharan R wrote: >> Hi Abhishek, >> >> On 2/3/2018 1:28 PM, Abhishek Sahu wrote: >>> Following are the major issues in current driver code >>> >>> 1. The current driver simply assumes the transfer completion >>>   

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 13:14, Sricharan R wrote: Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: Following are the major issues in current driver code 1. The current driver simply assumes the transfer completion whenever its gets any non-error interrupts and then simply do the polling of

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-19 Thread Abhishek Sahu
On 2018-02-16 13:14, Sricharan R wrote: Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: Following are the major issues in current driver code 1. The current driver simply assumes the transfer completion whenever its gets any non-error interrupts and then simply do the polling of

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-15 Thread Sricharan R
Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > Following are the major issues in current driver code > > 1. The current driver simply assumes the transfer completion >whenever its gets any non-error interrupts and then simply do the >polling of available/free bytes in FIFO. >

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-15 Thread Sricharan R
Hi Abhishek, On 2/3/2018 1:28 PM, Abhishek Sahu wrote: > Following are the major issues in current driver code > > 1. The current driver simply assumes the transfer completion >whenever its gets any non-error interrupts and then simply do the >polling of available/free bytes in FIFO. >

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-05 Thread kbuild test robot
Hi Abhishek, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.15 next-20180205] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url:

Re: [PATCH 11/12] i2c: qup: reorganization of driver code to remove polling for qup v1

2018-02-05 Thread kbuild test robot
Hi Abhishek, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on wsa/i2c/for-next] [also build test WARNING on v4.15 next-20180205] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: