mxms0 has left #linux-rockchip ["WeeChat 1.9-dev"]
ganbold has joined #linux-rockchip
ganbold_ has joined #linux-rockchip
ganbold has quit [Ping timeout: 240 seconds]
cnxsoft has joined #linux-rockchip
cnxsoft1 has joined #linux-rockchip
cnxsoft has quit [Ping timeout: 240 seconds]
cnxsoft1 is now known as cnxsoft
_whitelogger has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
ganbold_ has quit [Remote host closed the connection]
lkcl has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter1 has joined #linux-rockchip
kaspter1 is now known as kaspter
wzyy2 has joined #linux-rockchip
wadim_ has joined #linux-rockchip
<rperier>
mmind00: I plan to send a patch for adding basic DVFS support (currently supported frequencies) for RK3368. If we need improvements in other components for supporting other frequencies, I can help
<rperier>
currently, only frequencies from ~300Mhz to ~1Ghz are working for cluster0 and cluster1 (I tested these one by one, that's booting and stable)
<rperier>
that's not the case for other
leah2 has quit [Ping timeout: 255 seconds]
<beeble>
rperier: am i missing something? i had dvfs with mainline already running on rk3368. only run into some problems if i try to run the clusters at unequal frequencies
<rperier>
beeble: there is no opp table right ?
leah2 has joined #linux-rockchip
<rperier>
from what I have saw, armclkl and armclkb are missing and opp table (either binding v1 or v2)
<beeble>
rperier: thats right. the opp table is missing, but no driver changes are nescessary
<rperier>
I never said that driver changes were necessary :)
<beeble>
sorry my missunderstanding
<rperier>
np ;)
<beeble>
and since it seems that i have deleted my opp table yesterday during a git clean -dxf your work is very welcome :)
<rperier>
that's not an awesome patch, that only adds basic support for the current supported frequencies
<beeble>
btw, i could clock up to 1.2ghz on all cores
<beeble>
when clocking higher power consumption goes through the roof and you need a lot of cooling
<rperier>
your Tested-by tag is welcome if you want (like you prefer)
<rperier>
:)
<rperier>
beeble: yeah, but that's not working, currently
<rperier>
unfortunately
<rperier>
I have selected and tested one by one the same frequencies as found in rk3368.dtsi from the linux rk kernel 4.4
<rperier>
so I tested up to 1.2Ghz for little cores and up to ~1.5Ghz (something like this) for big cores
<rperier>
either I get an unstable boot (freeze or strange backtrace) or cpufreq can set the clock rate
<rperier>
:(
<beeble>
i have to be in a call right now, but i can look up if i have copy of the file somewhere else
<rperier>
but I agree, ideally we should support all
descend-irc__ has quit [Quit: Connection closed for inactivity]
hramrach has joined #linux-rockchip
lkcl has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-rockchip
lurchi_ has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-rockchip
<lurchi_>
Hi, everyone, I have a small problem with my RK3399 device
<lurchi_>
I can put the device into rockusb from the bootloader menu, and access it with rkdeveloptool
<lurchi_>
but when I try to force the device into maskrom rom by shorting eMMC clock, the device enumerate as 2207:330c USB device, but rkdeveloptool accesses fail
<lurchi_>
anything I have missed?
<beeble>
you have to first load the loader it will change the vid pid afterwards