kaspter has quit [Read error: Connection reset by peer]
kaspter has joined #linux-sunxi
<mripard>
then fix it, instead of claiming it "operates properly"
chewitt has quit [Quit: Zzz..]
<jaganteki>
it's a sensor issue right. for csi controller the initial formats work fine till 720p
aalm has joined #linux-sunxi
IgorPec has joined #linux-sunxi
<mripard>
that definitely doesn't look like a sensor issue
<mripard>
it looks like a memory corruption, and the sensor can't access the mmeory
<wens>
if it really is a "sensor" issue, then it shouldn't work on h3/h5/a31 either
yangxuan has quit [Quit: Leaving]
<jaganteki>
Can't we move with as it is becuase it works with rest of formats with resolutions.
<jaganteki>
we do have similar hacks even in dsi I suppose.
<jaganteki>
wens, true. do you have any inputs..I didn't involv much on sensor before.
<mripard>
there's no way we overlook a memory corruption
<mripard>
or any hard kernel crash for that matter
chewitt has joined #linux-sunxi
tllim has joined #linux-sunxi
anarsoul|2 has joined #linux-sunxi
msimpson has quit [Quit: Leaving]
netlynx has joined #linux-sunxi
tnovotny has quit [Quit: Leaving]
chewitt has quit [Quit: Zzz..]
<captainigloo>
hi, i'm playing on v3s with i2c1
<captainigloo>
i add it to my dtb, and i get an error, when reading the bus
<captainigloo>
it works well with i2c1
<captainigloo>
i get that error : i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0
<captainigloo>
i checked pinctrl, clock, interrupts, everything seems ok with the v3s datasheet
<captainigloo>
no intterupt raised when looking at /proc/interrupts :
<captainigloo>
31: 235 GIC-0 38 Level mv64xxx_i2c
<captainigloo>
32: 0 GIC-0 39 Level mv64xxx_i2cY
<captainigloo>
i tried to detect devices on i2c bus by using i2cdetect
<captainigloo>
do you guys have any idea ?
<captainigloo>
is i2c1 supposed to work on v3s ?
<[TheBug]>
hmm only person I know with experience with v3s is MoeIcenowy but not sure if she is around, you may have to wait a while for someone to answer that
<captainigloo>
i tried with 4.19.5 and 4.20-rc3 btw
<captainigloo>
same problem
<captainigloo>
ok thanks
<[TheBug]>
I have a LicheePi Zero
<[TheBug]>
and I have only used some older kernel versions in my test
<[TheBug]>
and didn't need i2c
<[TheBug]>
only camera interface
<[TheBug]>
and such
<[TheBug]>
so not sure about i2c
chewitt has joined #linux-sunxi
<captainigloo>
[TheBug]: you mean you used CSI camera interface with LicheePI Zero ?
clemens3 has quit [Ping timeout: 240 seconds]
<mripard>
captainigloo: I can't really tell without more details of your setup, but usually that would be caused by missing pull-ups or a device not properly powered on the i2c bus
<[TheBug]>
captainigloo: I have one module that is MSI and other is DVP, believe I only got MSI module working correct in my image and only enough to test, haven't had time to revisit my project
<[TheBug]>
captainigloo: https://licheepizero.us is a reference site I built for LicheePi in case it could be useful
<captainigloo>
mripard: ok thanks, i will check
<captainigloo>
[TheBug]: ok thanks, i already checkd it but i maybe missed something
<[TheBug]>
you can see modules and my boards there
<captainigloo>
[TheBug]: you are the guy behind the LicheePi zero board ?
<[TheBug]>
no, just that site
<[TheBug]>
but MoeIcenowy did some work for LicheePi Zero originally, the 'guy' behind it is a guy named Caesar (Zepan), I like the original sites on that page under references
<[TheBug]>
linked*
<[TheBug]>
captainigloo: is the v3s you have the LicheePi Zero or another board?
<plaes>
captainigloo: IIRC there was a patch against the bus lock issue
LargePrime has quit [Ping timeout: 252 seconds]
<plaes>
but I cannot find it atm
kaspter has quit [Remote host closed the connection]