Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 5 Oct 2020 17:19:43 +0300
From:      Andriy Gapon <avg@FreeBSD.org>
To:        Daniel Braniss <danny@cs.huji.ac.il>, "freebsd-arm@freebsd.org" <arm@freebsd.org>
Subject:   Re: nanopi/allwinner i2c not working.
Message-ID:  <d154f62f-cf41-aaac-4bae-89ee48163afa@FreeBSD.org>
In-Reply-To: <234D06ED-C99F-477E-8D95-492979084E7A@cs.huji.ac.il>
References:  <234D06ED-C99F-477E-8D95-492979084E7A@cs.huji.ac.il>

next in thread | previous in thread | raw e-mail | index | archive | help
On 05/10/2020 11:47, Daniel Braniss wrote:
> Hi,
> latest 12.2-stable r366421,
> 
> when nothing is connected,
> 	i2c -s
> just hangs
> and reboot is required.
> 
> 
> 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
> …
> 
> im willing to help debug this, but need help.

What NanoPi model is this?

Can you try to merge r365397 and check if it helps?
If it does not, can you additionally try https://reviews.freebsd.org/D26049 ?

If the problem persists, can you try setting hw.i2c.twsi_debug=1 and collect
some logs?

Thanks!

-- 
Andriy Gapon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d154f62f-cf41-aaac-4bae-89ee48163afa>