i2c: bcm2835: Use dev_dbg logging on transfer errors
authorNoralf Trønnes <noralf@tronnes.org>
Mon, 3 Oct 2016 20:06:10 +0000 (22:06 +0200)
committerWolfram Sang <wsa@the-dreams.de>
Mon, 7 Nov 2016 00:48:31 +0000 (01:48 +0100)
commit23c9540b3ad1d7473fe40df80074d0fb0bf04869
treebd1bb5afcd74ae53e232ae942dd5a324060238ce
parentd4030d75c7cbb434b2a3e5f6af5065879d2615a5
i2c: bcm2835: Use dev_dbg logging on transfer errors

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: Eric Anholt <eric@anholt.net>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
drivers/i2c/busses/i2c-bcm2835.c