warpme_ has quit [Quit: Connection closed for inactivity]
kaspter has quit [Ping timeout: 276 seconds]
kaspter has joined #linux-rockchip
levd has quit [Quit: Goodbye!]
levd has joined #linux-rockchip
levd has quit [Client Quit]
levd has joined #linux-rockchip
perr has joined #linux-rockchip
vstehle has quit [Ping timeout: 265 seconds]
stikonas has quit [Remote host closed the connection]
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 240 seconds]
kevery1 is now known as kevery
perr has quit [Remote host closed the connection]
perr has joined #linux-rockchip
perr has quit [Ping timeout: 276 seconds]
_whitelogger has joined #linux-rockchip
<anarsoul>
I confirmed that that's no 5V on usb in u-boot with voltmeter
<anarsoul>
voltage on gpio pin is weird
<anarsoul>
it's 1.42v
<anarsoul>
when it's 1
<anarsoul>
and 0 when it's 0
<anarsoul>
it's 3v in linux
<anarsoul>
how do I change gpio voltage from 1.8v to 3.3v?
<anarsoul>
(and why u-boot doesn't do that for me?)
lopsided98_ has quit [Quit: Disconnected]
lopsided98 has joined #linux-rockchip
<anarsoul>
OK, "mw 0xff77e640 00080008" is enough to get USB working
<anarsoul>
so looks like I need a driver for "rockchip,rk3399-io-voltage-domain" in u-boot
lopsided98 has quit [Quit: Disconnected]
lopsided98 has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
<anarsoul>
hm
<anarsoul>
actually it's supposed to be 0
<anarsoul>
since vcc_3v0 is higher than 1.8v
<anarsoul>
I wonder if rk808 driver is broken
_whitelogger has joined #linux-rockchip
<anarsoul>
nope, rk808 regs look OK
<anarsoul>
hm
<anarsoul>
or actually they're not...
vstehle has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
<anarsoul>
nah, they're OK
<anarsoul>
USB power switch has 2v raising threshold on EN pin
<anarsoul>
so 1.42 is definitely not enough
<anarsoul>
mmind00: any ideas what can be wrong? I.e. why one on GPIO4 PD2 is lower than 3v?
<anarsoul>
GRF_IO_VSEL is 0x0
<anarsoul>
so all io domains are 3.3v
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
<mmind00>
anarsoul: in general IO_VSEL is just to tell the soc what voltage to expect, but I have no idea why that pin would be so low for you ... maybe kevery has some idea?
jwerner has quit [Remote host closed the connection]
Kwiboo has quit [Ping timeout: 246 seconds]
warpme_ has joined #linux-rockchip
<kevery>
anarsoul: The fixed regulator is always work for me ...
<kevery>
For the GPIO control output in reg level, make sure the IOMUX in GRF and IO setting is correct.
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 265 seconds]
kevery1 is now known as kevery
kevery has quit [Ping timeout: 245 seconds]
matthias_bgg has joined #linux-rockchip
mearon has quit [Ping timeout: 244 seconds]
mearon has joined #linux-rockchip
aalm has quit [Quit: xyz 2.3]
vicencb has joined #linux-rockchip
vstehle has quit [Ping timeout: 265 seconds]
field^Mop has joined #linux-rockchip
<micken>
anarsoul: what kevey said, the settings in GRF might be wrong (I am repeating myself) :)
nlhowell has joined #linux-rockchip
nlhowell has quit [Read error: Connection reset by peer]
cristian_c has quit [Ping timeout: 268 seconds]
return0e has quit [Read error: Connection reset by peer]
return0e has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 268 seconds]
wadim_ has quit [Quit: Leaving.]
Kwiboo has joined #linux-rockchip
cristian_c has joined #linux-rockchip
<anarsoul>
micken: GRF settings seems to be correct
<anarsoul>
micken: also I can't find a reg that controls GPIO voltage
<anarsoul>
there's only drive strenght
<anarsoul>
and i/o domain is configured correctly
vicencb has quit [Quit: Leaving.]
<anarsoul>
just checked, drive strenght for gpio4 pd2 is 3mA, function is gpio
<anarsoul>
i.e. 0xff77e13c and 0xff77e02c return zeroes
<anarsoul>
micken: anything else to check? :)
matthias_bgg has quit [Quit: Leaving]
vstehle has joined #linux-rockchip
stikonas has joined #linux-rockchip
<anarsoul>
I found some diff between rk808 configuration in linux and in u-boot
<anarsoul>
will look into it tonight
ldevulder_ is now known as ldevulder
jwerner has joined #linux-rockchip
vicencb has joined #linux-rockchip
<micken>
anarsoul: why dont you diff the u-boot I use and mainline ?
<micken>
is there a license issue?
<anarsoul>
I think I already found the issue
<micken>
ok
<anarsoul>
see rk808_pre_init_reg in linux driver
<anarsoul>
it changes ILMIN for number of regulators
<anarsoul>
u-boot doesn't do that
<anarsoul>
if I boot linux, then press 'reset' and get into u-boot it works fine
<micken>
I see
<anarsoul>
I'll port these changes to u-boot to see if it works
<micken>
ok
<anarsoul>
hope it fixes it :)
<micken>
crossing fingers
<anarsoul>
I don't think it's anything in CPU configuration
<anarsoul>
since it's supposed to be reset when I press reset button
<micken>
no that sounds unlikely
<micken>
I had such sympotoms with tinkerboard
<micken>
hdmi vdo wasn't on by default
<micken>
from uboot
<micken>
if first boot linux , hdmi phy responded after
<micken>
n that case I just used the pmic command and programmed it as part of bootsequence
<micken>
( i was lazy ) :D
adjtm has quit [Read error: Connection reset by peer]
adjtm_ has joined #linux-rockchip
<micken>
good night
<tuxd3v>
micken: I would say "highly likely" :D
<anarsoul>
tuxd3v: ?
<tuxd3v>
hi anarsoul
<anarsoul>
hi tuxd3v
<tuxd3v>
the dtsi for the CPU is the same on both sides?
<anarsoul>
yes
<anarsoul>
well
<anarsoul>
to the extent that is possible
<anarsoul>
anyway
<anarsoul>
power on boot -> usb doesn't work in u-boot, linux boots -> usb works -> hard reset -> usb works in u-boot
<anarsoul>
I bet on rk808 configiration difference
<tuxd3v>
maybe if you do a make menuconfig in uboot compilation you could see if usb is active or not?
<anarsoul>
tuxd3v: I'm not stupid.
<anarsoul>
'usb start' shows USB controllers but no devices
<anarsoul>
I mesured voltage on USB ports and there's none
<anarsoul>
I measured regulator EN pin and it's below 1.5v in u-boot, but it's 3v in linux
<tuxd3v>
the device you want attached to usb, is a pendrive?
<tuxd3v>
I say this because power needs to be negotiated..
<tuxd3v>
starting testing by a low power device its the best way..
<anarsoul>
again
<anarsoul>
<anarsoul> I mesured voltage on USB ports and there's none
<anarsoul>
<anarsoul> I measured regulator EN pin and it's below 1.5v in u-boot, but it's 3v in linux
<anarsoul>
gpio pin voltage is below expected level
<anarsoul>
it's not enough to enable regulator which needs at least 2v
vicencb has quit [Quit: Leaving.]
Kwiboo has quit [Quit: .]
Kwiboo has joined #linux-rockchip
<micken>
anarsoul: is there a i2c command in your uboot? If so you should be able to walk thru the sequence
<anarsoul>
yes
* micken
couldnt sleep
<anarsoul>
that's how I dumped i2c regs
<anarsoul>
for working and non-working cases
<anarsoul>
*rk808 regs
<micken>
ok
<micken>
and they differs?
<anarsoul>
yes
<micken>
ok
<micken>
so you know the regs you need to change?
<micken>
can you do i2c writes?
<anarsoul>
yes
<anarsoul>
I'll test it tonight and let you know
<micken>
ok!
<anarsoul>
(so you finally can switch to blobless boot for rk3399!)
<anarsoul>
:)
<micken>
:D
<micken>
Yes that would be nice
<micken>
My problem right now is that sometimes I get blurred image from hdmi. I checked my clocking and compared with running linux. It is stable 40Mhz
<micken>
it seems like random :/
ldevulder_ has joined #linux-rockchip
<micken>
I first thought it was something with riscos screenmode that differs from hdmi/vop, but it isnt. I just copy out a bitmap image now and get same blurr
<anarsoul>
well, I have no experience with video on rk3399 yet
<micken>
I know
<micken>
I just needs to write my agony somewhere :)