Re: [PATCH v2] i2c: bcm2835: Clear current buffer pointers and counts after a transfer

2019-02-15 Thread Wolfram Sang
On Thu, Dec 27, 2018 at 04:42:25PM +0100, Paul Kocialkowski wrote: > The driver's interrupt handler checks whether a message is currently > being handled with the curr_msg pointer. When it is NULL, the interrupt > is considered to be unexpected. Similarly, the i2c_start_transfer > routine checks

Re: [PATCH v2] i2c: bcm2835: Clear current buffer pointers and counts after a transfer

2019-02-05 Thread Stefan Wahren
Am 05.02.19 um 13:09 schrieb Wolfram Sang: > On Thu, Dec 27, 2018 at 04:42:25PM +0100, Paul Kocialkowski wrote: >> The driver's interrupt handler checks whether a message is currently >> being handled with the curr_msg pointer. When it is NULL, the interrupt >> is considered to be unexpected.

Re: [PATCH v2] i2c: bcm2835: Clear current buffer pointers and counts after a transfer

2019-02-05 Thread Wolfram Sang
On Thu, Dec 27, 2018 at 04:42:25PM +0100, Paul Kocialkowski wrote: > The driver's interrupt handler checks whether a message is currently > being handled with the curr_msg pointer. When it is NULL, the interrupt > is considered to be unexpected. Similarly, the i2c_start_transfer > routine checks

[PATCH v2] i2c: bcm2835: Clear current buffer pointers and counts after a transfer

2018-12-27 Thread Paul Kocialkowski
The driver's interrupt handler checks whether a message is currently being handled with the curr_msg pointer. When it is NULL, the interrupt is considered to be unexpected. Similarly, the i2c_start_transfer routine checks for the remaining number of messages to handle in num_msgs. However, these