Question about i2c troubleshooting June 02, 2019 01:22PM |
Registered: 5 years ago Posts: 255 |
client found at address 0x48This makes me think the chip might be getting into a bad state which requires power cycling to clear.
i2c /dev entries driver rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6 rtc-rs5c372 0-0032: create wakealarm rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
[ 6945.844595] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
Re: Question about i2c troubleshooting June 02, 2019 05:26PM |
Admin Registered: 13 years ago Posts: 18,821 |
[ 6945.844595] i2c i2c-0: mv64xxx: I2C bus locked, block: 1, time_left: 0
[ 7.317743] mousedev: PS/2 mouse device common for all mice [ 7.324295] i2c /dev entries driver [ 7.334774] rtc-pcf8563 0-0051: registered as rtc0 [ 7.343131] hidraw: raw HID events driver (C) Jiri Kosina
i2c /dev entries driver rtc-rs5c372 0-0032: rs5c372a found, 24hr, driver version 0.6 rtc-rs5c372 0-0032: create wakealarm rtc-rs5c372 0-0032: rtc core: registered rtc-rs5c372 as rtc0
rtc@10300 { status = "disabled"; }; <snip> i2c@11000 { status = "okay"; clock-frequency = <100000>; rs5c372: rs5c372@32 { compatible = "ricoh,rs5c372a"; reg = <0x32>; }; };
/* This board uses the pcf8563 RTC instead of the SoC RTC */ rtc@10300 { status = "disabled"; }; i2c@11000 { status = "okay"; pcf8563: pcf8563@51 { compatible = "nxp,pcf8563"; reg = <0x51>; }; };
Re: Question about i2c troubleshooting June 02, 2019 06:20PM |
Registered: 5 years ago Posts: 255 |
Re: Question about i2c troubleshooting June 03, 2019 08:22PM |
Registered: 5 years ago Posts: 255 |
Zhelnov Sergey
Re: Question about i2c troubleshooting December 09, 2020 10:53AM |
Re: Question about i2c troubleshooting December 09, 2020 03:37PM |
Registered: 5 years ago Posts: 255 |