ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
return0e has quit [Ping timeout: 252 seconds]
return0e has joined #linux-rockchip
anarsoul|3 has quit [Remote host closed the connection]
anarsoul|2 has joined #linux-rockchip
vstehle has quit [Ping timeout: 272 seconds]
asciilifeform has joined #linux-rockchip
anarsoul|2 has quit [Ping timeout: 252 seconds]
ramcq has quit [*.net *.split]
phh has quit [*.net *.split]
phh has joined #linux-rockchip
VargaD has quit [Ping timeout: 240 seconds]
VargaD has joined #linux-rockchip
asciilifeform has left #linux-rockchip [#linux-rockchip]
lesderid has quit [*.net *.split]
ojn has quit [*.net *.split]
ayufan has quit [*.net *.split]
lesderid has joined #linux-rockchip
return0e has quit [Remote host closed the connection]
return0e has joined #linux-rockchip
tautologico has joined #linux-rockchip
rellla has quit [*.net *.split]
MoeIcenowy has quit [*.net *.split]
pozzoni has quit [*.net *.split]
seanpaul has quit [*.net *.split]
steev has quit [*.net *.split]
paulk-leonov has quit [*.net *.split]
xevious has quit [*.net *.split]
amstan has quit [*.net *.split]
Esmil has quit [*.net *.split]
VargaD has quit [Ping timeout: 276 seconds]
VargaD has joined #linux-rockchip
MoeIcenowy has joined #linux-rockchip
xevious has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
amstan_ has joined #linux-rockchip
VargaD has quit [Ping timeout: 260 seconds]
VargaD has joined #linux-rockchip
sb35 has quit [Ping timeout: 240 seconds]
sb35 has joined #linux-rockchip
<Ke> hanetzer: # CONFIG_USB_DWC2_HOST is not set
teletype has joined #linux-rockchip
vstehle has joined #linux-rockchip
<teletype> hi all, i've tried several kernels, currently trying walle-kernel-rk3188, trying to get an rk3188 SOM of unknown provenance to boot from SD. this one is the furthest i've gotten, but it hangs early in the boot when the kernel tries to init DDR. anyone know what i might be doing wrong?
<Ke> does kernel init DDR?
<teletype> i don't know. been working with linux forever but pretty new to rockchip. i do know that with the same bootloader image, i tried a kernel i extracted from a rom for an olimex board and it did get past the ddr init, but crashed later in boot
<teletype> this is what i'm seeing w/ the kernel i built https://hastebin.com/xomubuyotu.cs
<Ke> right, it's booting kernel indeed, not sure that is DDR init though, just printing out some details
<teletype> well, the olimex kernel gets further and the next line it prints after that paste is: [ 0.000000] DDR DEBUG: init success!!! freq=300MHz
<teletype> so i assume it's hanging during ddr init
Omegamoon has joined #linux-rockchip
<teletype> hrm, don't have a proper debugger on this, but there's not a whole lot of code between the last line it's logging and the next line i expect to see. time for some printf debugging i guess
raphari has joined #linux-rockchip
<raphari> hi all, trying to identify parts of the code in bsp (uboot/kernel) that need to be patched when you upgrade DDR3 to DDR4 for rk3399. RK3399MINIALL.ini
<raphari> identified ./linux/rkbin/RKBOOT/RK3399MINIALL.ini & ./linuxkernel/arch/arm64/boot/dts/rockchip/rk3399-dram-default-timing.dtsi
stdint has joined #linux-rockchip
lkcl has joined #linux-rockchip
<raphari> The files seems to have the required patch, but the kernel fails to boot itself completely and these are the complete logs set https://pastebin.com/wgnDe54P
<raphari> last message from kernel is "rockchip-dmc dmc: could not find power_model node"
<teletype> printf debugging worked. for some reason the rk3188 dpll stuff doesn't agree with this board. not sure why yet but disabling it makes my kernel boot.
afaerber has quit [Quit: Leaving]
Esmil has joined #linux-rockchip
teletype has left #linux-rockchip [#linux-rockchip]
afaerber has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-rockchip
Kwiboo has quit [Ping timeout: 260 seconds]
Kwiboo has joined #linux-rockchip
Kwiboo has quit [Ping timeout: 252 seconds]
Kwiboo has joined #linux-rockchip
s_frit has joined #linux-rockchip
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
lkcl has quit [Read error: Connection reset by peer]
lkcl_ has joined #linux-rockchip
lkcl_ has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
<hanetzer> Ke: yeah, but DUAL_ROLE is set, which is both _HOST and _PERIPHERAL
<Ke> ok, if you are sure
<hanetzer> I'm not sure :P
<Ke> I remember I once had ext3 journaling on and wondered, why I can't mount ext3 filesystems
<hanetzer> Ke: I'm not sure, but my grasp of how kbuild works leads me to believe that its correct
<Ke> if it would use the same code, I believe the convention would be to depend on CONFIG_USB_DWC2_HOST wouldn't it?
<hanetzer> apparently not. ifneq ($(filter y,$(CONFIG_USB_DWC2_HOST) $(CONFIG_USB_DWC2_DUAL_ROLE)),)
<hanetzer> this adds hcd.o, hdcd_intr.o, hcd_queue.o, hcd_ddma.o to the driver, which are the host dodads
<Ke> I kind of like that there is no way to know which compatibles are found, this is like one command in Microsoft Windows 10
<hanetzer> Ke: rephrase?
<Ke> compatible is the member in dtc that tells which drivers to expect to be needed for hw
<Ke> like pciid
<hanetzer> ah, you can check that in the sysfs
<Ke> I don't believe you can check drivers
<Ke> rockchip,rk3288-usb", "rockchip,rk3066-usb I believe is the device
<Ke> or snps,dwc2
<Ke> though seems to use the same device as the otg so I guess that would not even be informative
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
<hanetzer> usb@ff540000: rockchip,rk3288-usbrockchip,rk3066-usbsnps,dwc2
<Ke> yes that one
<Ke> you need to have a driver for it, but having a driver for it is not sufficient
<hanetzer> Ke: further investigation shows if I boot with a usb device plugged in, it shows up in lsusb, but replugging it to the same port looses it
<hanetzer> which explains why the webcam is always there
<Ke> webcam IIRC was different
<Ke> but anyway
<hanetzer> but it is usb at least
<Ke> yes USB, I remember having this sort of issue also caused by a missing driver
<Ke> thought I don't remember the details
<Ke> anyway, I don't think I have any more useful input
<Ke> https://users.aalto.fi/~jkarlson/files/config-4.9.60 well outside of this config that worked for me
strfry has joined #linux-rockchip
rperier has quit [Remote host closed the connection]
rperier has joined #linux-rockchip
tautologico has left #linux-rockchip [#linux-rockchip]
vagrantc has joined #linux-rockchip
afaerber has quit [Quit: Leaving]
anarsoul|2 has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 246 seconds]
Omegamoon has left #linux-rockchip [#linux-rockchip]
afaerber has joined #linux-rockchip
<hanetzer> so, does anyone have working mali accelerated gfx with the libmali.so blob on rk3288, and would care to assist?
ShapeShifter499 has quit [Read error: Connection reset by peer]
lkcl has quit [Read error: Connection reset by peer]
lkcl has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
vagrantc has quit [Quit: leaving]
<amstan_> hanetzer: CONFIG_USB_DWC2_DUAL_ROLE is fine i think
<amstan_> it just means that it's capable of doing both, the dts is then consulted (the dwc2 entry should say : host;)
<hanetzer> amstan_: theoretically it brings in the same code, so yeah, but in practice I'm seeing usb devices only being recognized/enumerated if they are plugged in during boot
amstan_ is now known as amstan
<amstan> have you tried older kernels? it might be a regression
<hanetzer> I went as far back as 4.17.0, same issue. haven't gone farther than that to be fair
<amstan> try something like 4.14, even 4.10 should work on that device
<amstan> if you ask nicely maybe mmind00 can give you a hand, he might have a couple of similar devices in his farm
<hanetzer> amstan: will do.
lerc has joined #linux-rockchip