Re: [PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-12-15 Thread Måns Rullgård
Wolfram Sang writes: > On Mon, Nov 02, 2015 at 02:03:37AM +, Mans Rullgard wrote: >> The BYTECNT register holds the transfer size minus one. Setting it >> to the correct value requires a dummy read/write only for zero-length >> transfers as it is impossible to request one from the hardware.

Re: [PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-12-15 Thread Wolfram Sang
On Mon, Nov 02, 2015 at 02:03:37AM +, Mans Rullgard wrote: > The BYTECNT register holds the transfer size minus one. Setting it > to the correct value requires a dummy read/write only for zero-length > transfers as it is impossible to request one from the hardware. If a > zero-length

Re: [PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-12-15 Thread Wolfram Sang
On Mon, Nov 02, 2015 at 02:03:37AM +, Mans Rullgard wrote: > The BYTECNT register holds the transfer size minus one. Setting it > to the correct value requires a dummy read/write only for zero-length > transfers as it is impossible to request one from the hardware. If a > zero-length

Re: [PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-12-15 Thread Måns Rullgård
Wolfram Sang writes: > On Mon, Nov 02, 2015 at 02:03:37AM +, Mans Rullgard wrote: >> The BYTECNT register holds the transfer size minus one. Setting it >> to the correct value requires a dummy read/write only for zero-length >> transfers as it is impossible to request

[PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-11-01 Thread Mans Rullgard
The BYTECNT register holds the transfer size minus one. Setting it to the correct value requires a dummy read/write only for zero-length transfers as it is impossible to request one from the hardware. If a zero-length transfer is requested, changing the length to 1 and setting "buf" to a dummy

[PATCH 2/3] i2c: xlr: fix extra read/write at end of rx transfer

2015-11-01 Thread Mans Rullgard
The BYTECNT register holds the transfer size minus one. Setting it to the correct value requires a dummy read/write only for zero-length transfers as it is impossible to request one from the hardware. If a zero-length transfer is requested, changing the length to 1 and setting "buf" to a dummy