Re: [PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Noralf Trønnes
Den 27.09.2016 15:01, skrev Martin Sperl: On 27 Sep 2016, at 13:57, Noralf Trønnes wrote: Writing to an AT24C32 generates on average 2x i2c transfer errors per 32-byte page write. Which amounts to a lot for a 4k write. This is due to the fact that the chip doesn't respond

Re: [PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Noralf Trønnes
Den 27.09.2016 15:01, skrev Martin Sperl: On 27 Sep 2016, at 13:57, Noralf Trønnes wrote: Writing to an AT24C32 generates on average 2x i2c transfer errors per 32-byte page write. Which amounts to a lot for a 4k write. This is due to the fact that the chip doesn't respond during it's internal

Re: [PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Martin Sperl
> On 27 Sep 2016, at 13:57, Noralf Trønnes wrote: > > Writing to an AT24C32 generates on average 2x i2c transfer errors per > 32-byte page write. Which amounts to a lot for a 4k write. This is due > to the fact that the chip doesn't respond during it's internal write > cycle

Re: [PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Martin Sperl
> On 27 Sep 2016, at 13:57, Noralf Trønnes wrote: > > Writing to an AT24C32 generates on average 2x i2c transfer errors per > 32-byte page write. Which amounts to a lot for a 4k write. This is due > to the fact that the chip doesn't respond during it's internal write > cycle when the at24

[PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Noralf Trønnes
Writing to an AT24C32 generates on average 2x i2c transfer errors per 32-byte page write. Which amounts to a lot for a 4k write. This is due to the fact that the chip doesn't respond during it's internal write cycle when the at24 driver tries and retries the next write. Reduce this flooding of the

[PATCH v2 3/8] i2c: bcm2835: Use ratelimited logging on transfer errors

2016-09-27 Thread Noralf Trønnes
Writing to an AT24C32 generates on average 2x i2c transfer errors per 32-byte page write. Which amounts to a lot for a 4k write. This is due to the fact that the chip doesn't respond during it's internal write cycle when the at24 driver tries and retries the next write. Reduce this flooding of the