Messages in this thread | | | Subject | Re: [PATCH v3 3/7] i2c: bcm2835: Use dev_dbg logging on transfer errors | From | Martin Sperl <> | Date | Thu, 29 Sep 2016 13:05:01 +0200 |
| |
On 28.09.2016, at 19:50, Noralf Trønnes <noralf@tronnes.org> 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 driver tries and retries the next write. > Only a handful drivers use dev_err() on transfer error, so switch to > dev_dbg() instead. > > Signed-off-by: Noralf Trønnes <noralf@tronnes.org> Reviewed-by: Martin Sperl <kernel@martin.sperl.org>
| |