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
vicencb has joined #linux-rockchip
stikonas_ has quit [Remote host closed the connection]
vagrantc has quit [Quit: leaving]
xerpi has quit [Remote host closed the connection]
vicencb has quit [Quit: Leaving.]
vstehle has quit [Ping timeout: 272 seconds]
anarsoul|2 has quit [Ping timeout: 245 seconds]
kever has joined #linux-rockchip
field^Mop has joined #linux-rockchip
field^Zzz4 has quit [Ping timeout: 246 seconds]
<hanetzer> nashpa: is the device supported by coreboot? you can extract the proper ddr data from it :)
<nashpa> hanetzer: no idea, tbh
anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-rockchip
kever has quit [Ping timeout: 245 seconds]
kever has joined #linux-rockchip
hl has quit [Ping timeout: 246 seconds]
vagrantc has joined #linux-rockchip
vstehle has joined #linux-rockchip
_whitelogger has quit [Ping timeout: 250 seconds]
_whitelogger has joined #linux-rockchip
sb35 has joined #linux-rockchip
kever has quit [Ping timeout: 245 seconds]
kever has joined #linux-rockchip
sb35 has quit [Ping timeout: 258 seconds]
xerpi has joined #linux-rockchip
vagrantc has quit [Ping timeout: 252 seconds]
stikonas_ has joined #linux-rockchip
stikonas_ has quit [Remote host closed the connection]
ldevulder has joined #linux-rockchip
ldevulder is now known as ldevulder_
ldevulder_ is now known as ldevulder
sb35 has joined #linux-rockchip
jaganteki has joined #linux-rockchip
kever has quit [Ping timeout: 272 seconds]
kever has joined #linux-rockchip
ldevulder has quit [Quit: Leaving]
jailbox has quit [Ping timeout: 245 seconds]
ldevulder has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
chewitt has quit [Quit: Zzz..]
chewitt has joined #linux-rockchip
jailbox has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
sb35 has quit [Ping timeout: 272 seconds]
vicencb has joined #linux-rockchip
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
xerpi has joined #linux-rockchip
xerpi has quit [Remote host closed the connection]
Pix has joined #linux-rockchip
<bunn> What rockchip devices and what distros are you guys running? I'm curious
<Pix> two 3399 with a centos 7 and a fedora 29.. and one bricked 3328 :p
<jaganteki> anyone tried rk3399 u-boot w/o PLATDATA in Mainline?
aalm has quit [Ping timeout: 250 seconds]
<jaganteki> I'm encountering Pinctrl init failed: -19 even the same node defined as u-boot,dm-pre-reloc
<Pix> hmm nope
<Pix> does some here have a rl3399 videostrong board ?
<Pix> i have an issue with an irq being stalled and putting my load to 1 permanently
anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-rockchip
<nashpa> jaganteki: anyone other than me? ;)
<nashpa> jaganteki: is than in SPL or main U-Boot?
<jaganteki> PLATDATA is for SPL
<jaganteki> I'm trying to disable PLATDATA and create spl with ddr bin
<jaganteki> seems like PINCTRL bound failed. but the node is marked u-boot,dm-pre-reloc
<jaganteki> my plan to boot this way and get the ddr config on running u-boot
<nashpa> have you looked at boards/puma README file?
<nashpa> it shows the steps to build an u-boot with the DDR bin and without SPL
<nashpa> U-Boot tree
<nashpa> I think your problem is not pinctrl, but clock support in SPL
<beeble> puma is using spl and devicetree ramtimings. so i think you mean the evb readme
<jaganteki> look like all rk3399 boards in mainline using spl dt ramtimings and with SPL_PLATDATA enabled
<nashpa> jaganteki: I'm running a firefly-rk3399, a (now a couple) of nanopc-t4 and a K99 TVBOX with an U-Boot without SPL_OF_PLATDATA
<nashpa> not mainlined yet, because I'm not sure how to do the "generic" rk3399 discovery of board ID
<jaganteki> so your ddr timings were with dts and dmc node is u-boot,dm-pre-reloc
<jaganteki> correct?
<jaganteki> how much is your SPL size. if possible can you share the code via github or something
<nashpa> jaganteki: ok, let me make sure I'm commiting everything and I'll push something into github
aalm has joined #linux-rockchip
ayaka has quit [Ping timeout: 246 seconds]
ayaka has joined #linux-rockchip
<quark_> jaganteki: there is new dram driver available in github https://github.com/keveryang/u-boot/tree/rockchip
<quark_> or is there some reason why trying to use ddr blob?
<jaganteki> becuase I'm unable to convert proper offsets in ddr bin to dtsi file
<jaganteki> I have got information from nashpa, but that doesn't work for me.
<jaganteki> looking for adequate or proper way to get ddr timings from bin
<jaganteki> on the otherhand, booting with ddr bin give proper cross checking the values used in dtsi is proper
<quark_> just extracting values from bin is not enough. that ddr 1.15 blob changes values during init
<quark_> that new driver is quite close 1.15 blob driver
<jaganteki> sorry what is 1.15 blob you mean CONFIG_ROCKCHIP_SDRAM_COMMON in this repo
<jaganteki> okay
<quark_> from paste I was thinking you are using that one
<nashpa> jaganteki: I've pushed my patches here: https://github.com/dliviu/u-boot
<nashpa> duh, I've left the fixups in there :(
<quark_> that blob includes 5 sets of ddr init values. ddr3, lpddr3, lpddr4 (50Mhz), lpddr4 (400Mhz), lpddr4 (933Mhz)
<nashpa> I'm going to force push the patches again
<jaganteki> quark_: how? from offsets
<nashpa> quark_: 933Mhz has 2 sets of settings in the blob?
<nashpa> at least by my decoding I've found two sets of numbers where the relevant value has 933000000
<quark_> Did reverse decompile with IDA for that blob.
<nashpa> jaganteki: probably the patch from Zhihuan is also of interest to you
<jaganteki> quark_: any idea how to do this "decompile with IDA"
<quark_> you need ida pro 7.0 at least
<quark_> if you are not familiar with software then couple of days to find out how it works :)
<quark_> first part is code up to 0x7B98
<quark_> then strings and other variables
<quark_> first set data set is starting from 0x9A4C
anarsoul|2 has joined #linux-rockchip
<quark_> if I remeber correctly that one is LPDDR4 400Mhz
<jaganteki> quark_: first set start with 4b52 3333
nashpa has quit [Ping timeout: 244 seconds]
nashpa has joined #linux-rockchip
<quark_> but anyway just extracting values does not work. as that blob does autodetect things and changes values based on that
<quark_> current mainline u-boot sdram driver does not do that
<quark_> that kevenryang repo u-boot has same kind of sdram driver. code looks much same as that 1.15 blob code
<jaganteki> Okay, may be I can try do you have blobs on this particular 1.15 bin
stikonas has joined #linux-rockchip
Substring has joined #linux-rockchip
<quark_> I did not extract ddr3 data as I was interested in lpddr4 part
<quark_> if you trying to get some board working which is not working now. then might be worth of just trying that newer sdram driver
<jaganteki> for new boards?
<quark_> yep for example
<jaganteki> OK, thanks
<stikonas> quark_: you tried with rockpro64?
jaganteki has quit [Ping timeout: 256 seconds]
Substring has quit [Quit: Leaving]
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 258 seconds]
<bunn> Pix: which board is that for rk3399? :o