mmind00 changed the topic of #linux-rockchip to: Rockchip development discussion | public log at https://libera.irclog.whitequark.org/linux-rockchip
Daanct12 has joined #linux-rockchip
naoki has quit [Quit: naoki]
naoki has joined #linux-rockchip
hipboi has joined #linux-rockchip
f476 has joined #linux-rockchip
f476_ has joined #linux-rockchip
hexdump0815 has quit [Ping timeout: 252 seconds]
f476 has quit [Ping timeout: 272 seconds]
hexdump0815 has joined #linux-rockchip
vagrantc has joined #linux-rockchip
hipboi has quit [Quit: hipboi]
<tlwoerner> does the rock-pi-s (rk3308) have the ability to report its cpu/soc temperature the way some other rockchip boards can?
<tlwoerner> i don't see it showing up in /sys/class/hwmon
vagrantc has quit [Quit: leaving]
leming has quit [Ping timeout: 276 seconds]
leming has joined #linux-rockchip
<dsimic> tlwoerner: I see no required tsadc definitions in rk3308.dtsi, so I'd guess that still needs to be implemented
<dsimic> hmm, there are even larger issues, e.g. no thermal maps and trips, and CPU OPPs enabled
dlg has quit [Ping timeout: 276 seconds]
<dsimic> which means a thermal runaway and possible damage to the SoC are possible :/
dlg has joined #linux-rockchip
<dsimic> I'll send a hotfix patch to have the OPPs disabled until the CPU throttling gets implemented
<dsimic> we don't want to see damaged SoCs :)
hipboi has joined #linux-rockchip
naoki has quit [Remote host closed the connection]
naoki has joined #linux-rockchip
hipboi has quit [Quit: hipboi]
franoosh has joined #linux-rockchip
raster has joined #linux-rockchip
erg_ has joined #linux-rockchip
franoosh has quit [Ping timeout: 276 seconds]
hanetzer has quit [Ping timeout: 252 seconds]
hanetzer has joined #linux-rockchip
erg__ has joined #linux-rockchip
erg_ has quit [Read error: Connection reset by peer]
ldevulder has joined #linux-rockchip
erg__ has quit [Ping timeout: 255 seconds]
hipboi has joined #linux-rockchip
diederik has quit [Quit: Going to see what happens IRL, see ya!]
diederik has joined #linux-rockchip
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
ldevulder has quit [Ping timeout: 246 seconds]
System_Error has quit [Read error: Connection reset by peer]
erg_ has joined #linux-rockchip
franoosh has quit [Read error: Connection reset by peer]
System_Error has joined #linux-rockchip
naoki has quit [Quit: naoki]
hipboi has quit [Quit: hipboi]
erg_ has quit [Remote host closed the connection]
erg_ has joined #linux-rockchip
<dsimic> tlwoerner: have a look at the patch linked below
hipboi has joined #linux-rockchip
erg_ has quit [Read error: Connection reset by peer]
erg__ has joined #linux-rockchip
erg__ has quit [Ping timeout: 260 seconds]
erg__ has joined #linux-rockchip
hipboi has quit [Quit: hipboi]
ldevulder has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 265 seconds]
ldevulder has joined #linux-rockchip
ldevulder_ has quit [Ping timeout: 265 seconds]
Daanct12 has quit [Quit: WeeChat 4.4.2]
ldevulder has quit [Ping timeout: 264 seconds]
erg_ has joined #linux-rockchip
erg__ has quit [Ping timeout: 252 seconds]
<tlwoerner> wow, i hope not. i've got about a dozen of these guys deployed, some in awkward places
<dsimic> tlwoerner: it depends on the CPU workload they're handling
<dsimic> e.g. bursty CPU load might go just fine even with no thermal configuration in place
<dsimic> but it's too risky anyway
<tlwoerner> agreed. mine are mostly monitoring sensors, ssh connections, getting updates, nothing too strenuous
<dsimic> anyway, it would be much better to have the thermal configuration implemented, tested, and upstreamed
<tlwoerner> perhaps that is something i could take a look at, do you recommend an example i could follow?
<dsimic> pretty much any Rockchip board is a good example
<dsimic> however, I could ask Radxa to send me a ROCK Pi S0, and I'd be willing to get that implemented and tested
<Kwiboo> dsimic, tlwoerner: I do not think there is that big of a thermal issue for rk3308b, the soc is rated for up to 1.3 ghz and max opp in dtsi is 1 ghz, and the soc does not seem to get that hot, however there is also a rk3308bs variant that has different voltage and cpu rate limits
<tlwoerner> in any case it would be nice to have the infrastructure in place to be able to monitor its temperature
<tlwoerner> (as i can with the others)
<dsimic> hmm, the user manual says it goes up to 1.0 GHz, whish the DT confirms?
<dsimic> s/whish/which/
<dsimic> while the vendor kernel goes up to 1.3 Ghz
<dsimic> the BS variant goes up to 1.1 GHz :)
<dsimic> anyway, it's much better to get it done right
<tlwoerner> none of my cpus seem to currently ever use the slowest speed
<dsimic> hmm, that's a bit strange
<dsimic> alright, I'll ask Radxa for the S0 and some more hardware for another nice upstream endeavor :)
<tlwoerner> nice
<dsimic> just keep an eye on rockchip-linux
<dsimic> I hope you'll be willing to test the patches :)
<tlwoerner> here are the stats from one of my devices: https://paste.ack.tf/d8762b
<tlwoerner> absolutely! please ping me when you post them
<dsimic> let me paste a few lines here, for future reference... pastebins can go away...
<dsimic> 408000 0
<dsimic> 600000 3878241
<dsimic> 816000 15107
<dsimic> 1008000 33148
<dsimic> it's really suspicious that the lowest CPU OPP isn't used at all
raster has quit [Quit: Gettin' stinky!]
<dsimic> actually, can you give me your full name and email address, and I'll include your Reported-by tag?
<tlwoerner> coincidentally i updated my fleet last night, so the uptime is only about 12 hours
<tlwoerner> thanks for the tag! (i appreciate it)
<dsimic> still, 12 hours is fairly long
<dsimic> sure
<dsimic> thank you for reporting this issue :)
<tlwoerner> so far i have about a dozen rockchip-based devices around the farm (and many more planned!) monitoring bunches of sensors
<tlwoerner> everything built with yocto master, upstream kernels and bootloaders
<tlwoerner> full A/B updates with rauc
<tlwoerner> i'm starting to implement the sensor monitoring and dashboard phase
<tlwoerner> starting with mqtt, but will be moving to kafka
<tlwoerner> i was only recording the actual sensors so far, but then noticed that most are also reporing cpu/gpu/soc temperatures and thought: why not?
<tlwoerner> then noticed my rk3308
<tlwoerner> my server is a rock-pi-4a running the penta sata hat
<dsimic> very nice!
<tlwoerner> i've been lucky enough to have radxa send me some free hardware too, my backup server is a rock-5a they sent me
<tlwoerner> but i don't have a penta sata hat on that one (yet)
<dsimic> that's some rather serious operation you're running :)
<tlwoerner> i also have a board farm (as opposed to... and actual farm) with one of everything i'm using in there
<tlwoerner> so if you've got stuff to test... :-)
<tlwoerner> i'm all setup for easy patching, building, deploying, testing
franoosh has joined #linux-rockchip
dsimic has quit [Ping timeout: 252 seconds]
erg_ has quit [Ping timeout: 246 seconds]
dsimic has joined #linux-rockchip
<dsimic> I've been disconnected for the last 10 minutes or so, have I lost some messages?
<dsimic> have you written some articles about it?
<dsimic> it's great that you have a test environemnt, which is actually mandatory before deploying the updates to the boards in the field
<dsimic> s/environemnt/environment/
warpme has joined #linux-rockchip
<dsimic> do you have any RK3566-based board in the test farm? I'll have some patches for testing later today :)
<tlwoerner> dsimic: yes, i have a bunch of radxa-zero-3e devices
<tlwoerner> i'm really hoping to get hdmi working on those, so i can use them for camera kiosks
<tlwoerner> i'm also hoping to start making my own cameras with them as a basis
<tlwoerner> someday i'll get around to blogging about the whole setup... too busy implementing for now ;-)
<dsimic> very nice :)
<dsimic> perhaps you'd also benefit from subscribing to the linux-rockchip ML :)
<dsimic> I'll send my RK3566 patches there
<tlwoerner> subscribed, i am. watching/following... not so much :-)
<tlwoerner> i really should start using bleeding edge upstream u-boot and kernels, especially in my board farm
<dsimic> I'll ping you with the link to the patches :)
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
krei-se has joined #linux-rockchip
krei-se- has quit [Ping timeout: 265 seconds]
warpme has quit [Ping timeout: 272 seconds]
franoosh has quit [Remote host closed the connection]
Stat_headcrabbed has joined #linux-rockchip
mripard has quit [Quit: mripard]
mripard has joined #linux-rockchip
mripard has quit [Quit: mripard]
mripard has joined #linux-rockchip
<dsimic> tlwoerner: actually, could you, please, test the RK3308 SoC dtsi patch that's on the ML already first?
dliviu has quit [Ping timeout: 260 seconds]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
raster has joined #linux-rockchip
<tlwoerner> dsimic: i've been running that patch in my board farm for ~3h now
<tlwoerner> # cat /sys/bus/cpu/devices/cpu0/cpufreq/stats/time_in_state
<tlwoerner> 408000 1043025
<tlwoerner> i can read my spi, i2c, and w1 sensors, so it works for me
raster has quit [Quit: Gettin' stinky!]
warpme has joined #linux-rockchip
stikonas has joined #linux-rockchip
warpme has quit [Ping timeout: 260 seconds]
raster has joined #linux-rockchip
dliviu has joined #linux-rockchip
warpme has joined #linux-rockchip
<dsimic> tlwoerner: great, thanks!
<dsimic> it woould be great if you'd reply to the ML with your Tested-by tag
<dsimic> it would be great if you'd reply to the ML thread with your Tested-by tag *
<tlwoerner> dsimic: now who is not following the mailing list!! ;-)
<tlwoerner> i replied with my tag about an hour ago
<diederik> ... I'm not seeing it ...
warpme has quit [Ping timeout: 252 seconds]
<dsimic> tlwoerner: diederik: ah, the ML has been really slow in the last few days when it comes to delivering messages
<dsimic> thanks for replying :)
<tlwoerner> interesting, i'm not seeing it on lore either
<tlwoerner> i'll resend tomorrow if it doesn't show up
<tlwoerner> np
<dsimic> I think it should appear rather soon
<dsimic> but sometimes delivery takes multiple hours
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 260 seconds]
<diederik> tlwoerner: it arrived :)
<dsimic> yup :)
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
eballetbo has quit [Quit: Connection closed for inactivity]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 244 seconds]
franoosh has joined #linux-rockchip
warpme has joined #linux-rockchip
vagrantc has joined #linux-rockchip
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
warpme has quit [Ping timeout: 276 seconds]
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
franoosh has quit [Read error: Connection reset by peer]
franoosh has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
naoki has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 246 seconds]
warpme has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme has quit [Ping timeout: 244 seconds]
vagrantc has quit [Quit: leaving]
franoosh has quit [Ping timeout: 245 seconds]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
warpme has joined #linux-rockchip
<Kwiboo> dsimic: I have been running stress with performance gov for ~2h on a rk3308b rock-pi-s board and soc temp seem to top out at ~50 deg c with ambient temp ~21 deg, vendor kernel use 115 deg as critical temp, similar to px30, so probably not that big of a risk of damage with current opps ;-)
warpme has quit [Ping timeout: 248 seconds]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 265 seconds]
warpme has joined #linux-rockchip
UndrWater has quit [Quit: ZNC 1.8.2+deb2ubuntu0.1 - https://znc.in]
UndrWater has joined #linux-rockchip
warpme has quit [Ping timeout: 246 seconds]
vagrantc has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 244 seconds]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
vagrantc has quit [Quit: leaving]