<macc24>
mmind00: battery node is needed for linux rk817 driver to recognize rk817 battery?
<mmind00>
macc24: I don't actually remember how the battery is read on the Go ... but I think I remember that something on the rk817 driver was missing for that whole thing
<robmur01>
AFAIK only the regulator and RTC functions of RK817 have support upstream - I see no trace of the charger, audio codec, or whatever random other functions it has
<macc24>
oh god
<robmur01>
I still love how random the mix of PMIC+audio is :)
<robmur01>
kinda harks back to the days of dedicated "companion chips"
<robmur01>
"buy our CPU but also buy this because it's all the other stuff you need that we couldn't fit in the CPU"
<macc24>
are there any plans to mainline missing stuff from downstream kernel?
matthias_bgg has joined #linux-rockchip
john01 has joined #linux-rockchip
<john01>
I recently obtained a Station P1 (Possibly the same as ROC-RK3399-PC) and I've been struggling to get it to boot from SD Card. I built arm-trusted-binaries and u-boot myself, but does it require the trust blobs in order to boot? The broken english instructions on both RockChip Wiki and Firefly have me a bit confused.
<john01>
for my SD Card, the only partitions so far are: dd if=idbloader.img of=sdb seek=64 && dd if=u-boot.itb of=sdb seek=16384
<john01>
If it requires trust chain then perhaps I need to use the binaries and add additional partitions.
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-rockchip
<robmur01>
john01: if you're using the upstream U-Boot flow, the TF-A binary is included in u-boot.itb; it's not separate like in the downstream miniloader flow
<macc24>
john01: have you tried with seek 512 on u-boot.itb?
<robmur01>
of course, it's all to easy to forget to provide "BL31=..." to the U-Boot build, miss the very subtle error message buried in all the other output, and end up with an image that doesn't actually work... been there done that :)
<john01>
SPI has the stock (very old U-boot from Firefly) with TF-A, I plan to disable that with jumper and have it fall back to SD. I did do the BL31 export :)
<macc24>
yes you HAVE to disable spi flash chip
<macc24>
or 0xff it out
<macc24>
mmind00: btw if your odroid go2 hangs for no reason in linux it might be because disconnected battery
<macc24>
hmm, did 5.10 broke display on odroid go2?
<john01>
macc24: I'm looking for SP1_CLK jumper right? (First time doing this)... https://i.imgur.com/Yhe2HBx.png --> There are also several other SPI on board per
stikonas has quit [Remote host closed the connection]
matthias_bgg has quit [Ping timeout: 260 seconds]
stikonas has joined #linux-rockchip
<macc24>
mmind00: can you check if display is working for you on odroid go2?
<mmind00>
macc24: I don't have it with me at the moment ... earliest sometime next week ... did something break?
<macc24>
yeah i get pattern of white and gray-ish vertical stripes
<macc24>
nothing in dmesg
<mmind00>
macc24: I guess check which the clock summary to check if the dclk frequencies are correct ... (mount none /debug -t debugfs; cat /debug/clk_summary)
<mmind00>
macc24: and after that the logs of dw_dsi in drivers/gpu/drm/bridge/synopsys for interesting changes
<mmind00>
macc24: "git bisect start; git bisect good v5.9; git bisect bad v5.10-rc1" and a lot of patience ;-)
<mmind00>
robmur01: yeah but probably was there already when the display was still working
<robmur01>
yup, according to git history it's been over a year since Doug last tried to improve that area
<robmur01>
so it's unlikely to be involved in a recent regression unless possibly some *other* change has made the panel more sensitive to exact clocks? Seems unlikely TBH :/
alpernebbi has quit [Quit: alpernebbi]
<macc24>
mmind00: i will check later if it works
<mmind00>
also I don't recall seeing any big drm patches for Rockchip go in
ldevulder has quit [Quit: Leaving]
stikonas_ has joined #linux-rockchip
stikonas has quit [Ping timeout: 272 seconds]
stikonas_ is now known as stikonas
azend has quit [Quit: No Ping reply in 180 seconds.]