ungeskriptet has quit [Killed (copper.libera.chat (Nickname regained by services))]
ungeskriptet has joined #linux-rockchip
digetx has quit [Read error: Connection reset by peer]
<warpme>
Kwiboo qschulz : just FYI: my "issue" with nonworking pcie on 35xx was on my side: when i was adding pcie support for 2712 (rpi5) (i have common kernel for 11+ socs) - one option (taken from rpi defconfig) was too much. https://github.com/warpme/minimyth2/commit/ed811fde6cffa0f38c257213a429b5d128b5ffc8 fixes issue and now all works nicely on 6.10.7 :-)
digetx has joined #linux-rockchip
kevery1 has joined #linux-rockchip
mripard has joined #linux-rockchip
kevery has quit [Ping timeout: 248 seconds]
kevery1 is now known as kevery
digetx has quit [Read error: Connection reset by peer]
digetx has joined #linux-rockchip
raster has joined #linux-rockchip
psydroid has quit [Read error: Connection reset by peer]
psydroid has joined #linux-rockchip
Spirit532 has quit [Killed (NickServ (GHOST command used by Spirit5326))]
Spirit532 has joined #linux-rockchip
erg_ has joined #linux-rockchip
erg_ has quit [Remote host closed the connection]
franoosh has quit [Ping timeout: 272 seconds]
franoosh has joined #linux-rockchip
franoosh has quit [Read error: Connection reset by peer]
franoosh has joined #linux-rockchip
franoosh has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
erg_ has joined #linux-rockchip
franoosh has quit [Read error: Connection reset by peer]
UndrWater has quit [Quit: ZNC 1.8.2+deb2build5 - https://znc.in]
UndrWater has joined #linux-rockchip
erg_ has quit [Remote host closed the connection]
franoosh has joined #linux-rockchip
franoosh has quit [Read error: Connection reset by peer]
erg_ has joined #linux-rockchip
franoosh has joined #linux-rockchip
erg_ has quit [Ping timeout: 245 seconds]
erg_ has joined #linux-rockchip
franoosh has quit [Ping timeout: 252 seconds]
franoosh has joined #linux-rockchip
erg_ has quit [Ping timeout: 252 seconds]
franoosh has quit [Read error: Connection reset by peer]
<dsimic>
basically, you need to adjust the lowest non-zero value in cooling-levels so the fan starts spinning reliably
<dsimic>
also, I'm not sure you're gaining anything by having four cooling maps
<dsimic>
having two should be just fine, e.g. the way it's defined for the RockPro64
<dsimic>
regarding adjusting the lowest non-zero value in cooling-levels, it's the best to tune it using an official heatsink/fan combo for the particular board
<dsimic>
because that's the cooling setup that most users will have installed
<dsimic>
having those two thermal trips ensures fanless operation until certain CPU/SoC temperature
<dsimic>
which should result in quiet operation most of the time, hopefully :)
<dsimic>
which also makes it more important to have reliable fan start-up, to ensure as low fan RPM as possible
<dsimic>
when it actually starts spinning
<Kwiboo>
qschulz: hehe, that is usually my initial take, do not trust downstream, they could possible have made some mistake ;-)
<Kwiboo>
dsimic: thanks for pointers, hardkernel typically seem to stress test and calibrate vendor kernel pretty decent, so not sure if I should trust it or not :-), https://forum.odroid.com/viewtopic.php?f=230&t=48953 have a graph that show pref of stock fan and vendor used trip points
<diederik>
I liked that they published those graphs ... which means they at least tested it :)
<dsimic>
Kwiboo: regarding cooling-levels, you can rather easily verify those downstream values
<dsimic>
but ehwn it comes to having four thermal trips, that simply seems wrong
<Kwiboo>
dsimic: if I understand correctly RP64 will just use 2 stage points of the fan, it has cooling-levels = <0 100 150 200 255>, so at 55deg it will use 100 and at 65 use 150, how does it use the higher steps/cooling-levels?
<dsimic>
it just stays at 0 or 100 below 65 oC, and ramps up to 255 over 65 oC, as needed
<dsimic>
actually, it will remain at 0 until 55 oC and then start ramping up
<Kwiboo>
dsimic: thanks, the ramping up part was mostly what was unclear to me
<dsimic>
anytime... that's why having more than two thermal trips makes little sense
<dsimic>
unless the fan is really strange and it can't rotate at unexact PWM levels, which I doubt
<dsimic>
in that rather unbelievable :) case, you'd actually need those four thermal trips, to have it run at those exact PWM levels
<dsimic>
but that would also sound much worse... it would sound like changing gearts in a car with manual transmission :)
<dsimic>
s/gearts/gears/
<Kwiboo>
I think the fan should be able to ramp up and not require those exact values, will try to run some stress tests over the weekend while completeing other work/series :-)
<dsimic>
let us know the test results, please
<robmur01>
FWIW my understanding/experience is that pwm-fan just steps from level to level as the trip points are passed
<robmur01>
hence why I added a more-cooling-but-still-not-annoyingly-loud point between min and max for NanoPC-T4
<robmur01>
scaling the PWM reactively based on temperature is a userspace thing
dsimic has quit [Ping timeout: 245 seconds]
dsimic has joined #linux-rockchip
mripard has quit [Quit: mripard]
ldevulder has quit [Quit: Leaving]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 248 seconds]
SystemError has quit [Remote host closed the connection]
digetx has quit [Ping timeout: 260 seconds]
Stat_headcrabed has joined #linux-rockchip
Stat_headcrabed has quit [Client Quit]
Stat_headcrabed has joined #linux-rockchip
digetx has joined #linux-rockchip
warpme has joined #linux-rockchip
digetx has quit [Read error: Connection reset by peer]
warpme has quit [Ping timeout: 252 seconds]
digetx has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 248 seconds]
digetx has quit [Ping timeout: 252 seconds]
digetx has joined #linux-rockchip
digetx has quit [Read error: Connection reset by peer]
vagrantc has joined #linux-rockchip
warpme has joined #linux-rockchip
digetx has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
digetx has quit [Ping timeout: 255 seconds]
digetx has joined #linux-rockchip
SystemError has joined #linux-rockchip
_whitelogger has quit [Ping timeout: 252 seconds]
_whitelogger has joined #linux-rockchip
warpme has joined #linux-rockchip
digetx has joined #linux-rockchip
digetx has quit [Ping timeout: 252 seconds]
dTal has quit [Ping timeout: 260 seconds]
dTal has joined #linux-rockchip
warpme has quit [Ping timeout: 248 seconds]
digetx has joined #linux-rockchip
digetx has quit [Ping timeout: 246 seconds]
digetx has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 244 seconds]
Stat_headcrabed has quit [Quit: Stat_headcrabed]
digetx has quit [Ping timeout: 265 seconds]
digetx has joined #linux-rockchip
naoki has joined #linux-rockchip
stikonas has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 260 seconds]
warpme has joined #linux-rockchip
digetx has quit [Read error: Connection reset by peer]
digetx has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
warpme has quit [Ping timeout: 246 seconds]
stikonas has joined #linux-rockchip
<dsimic>
robmur01: hmm, are all your changes for NanoPC-T4 upstreamed? if not, where can I have a look at them?
<dsimic>
regarding userspace and PWM fans, I'm not really sure why should userspace have to do anything?
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 260 seconds]
stikonas has quit [Read error: Connection reset by peer]
stikonas has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
stikonas has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Ping timeout: 252 seconds]
SystemError has quit [Remote host closed the connection]