Date: Mon, 5 Oct 2020 17:54:32 +0300 From: Daniel Braniss <danny@cs.huji.ac.il> To: Andriy Gapon <avg@FreeBSD.org> Cc: "freebsd-arm@freebsd.org" <arm@freebsd.org> Subject: Re: nanopi/allwinner i2c not working. Message-ID: <E2E23A4F-9D51-4803-BFF1-B5B2BBE56576@cs.huji.ac.il> In-Reply-To: <d154f62f-cf41-aaac-4bae-89ee48163afa@FreeBSD.org> References: <234D06ED-C99F-477E-8D95-492979084E7A@cs.huji.ac.il> <d154f62f-cf41-aaac-4bae-89ee48163afa@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 5 Oct 2020, at 17:19, Andriy Gapon <avg@FreeBSD.org> wrote: >=20 > On 05/10/2020 11:47, Daniel Braniss wrote: >> Hi, >> latest 12.2-stable r366421, >>=20 >> when nothing is connected, >> i2c -s >> just hangs >> and reboot is required. >>=20 >>=20 >> if anything is connected, it just goes into a loop: >> # i2c -s >> Hardware may not support START/STOP scanning; trinterrupt storm = detected on "gic0,s6:"; throttling interrupt source >> ying less-reliable read method. >> interrupt storm detected on "gic0,s6:"; throttling interrupt source >> interrupt storm detected on "gic0,s6:"; throttling interrupt source >> =E2=80=A6 >>=20 >> im willing to help debug this, but need help. >=20 > What NanoPi model is this? nanopi neo v1.3 and v1.4 >=20 > Can you try to merge r365397 and check if it helps? > If it does not, can you additionally try = https://reviews.freebsd.org/D26049 ? i think i tested this a while back, with the same results. >=20 > If the problem persists, can you try setting hw.i2c.twsi_debug=3D1 and = collect > some logs? last time i tested, debug was on, and it worked, but when turned off it = hung. I have to compile twsi with debug, and will report back ASAP. thanks, danny >=20 > Thanks! >=20 > --=20 > Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E2E23A4F-9D51-4803-BFF1-B5B2BBE56576>