08:30 <CounterPillow> why did robo-rob go absolutely crazy on the RKNN v3 binding patch, I have 18 replies to that patch by his test robot in my inbox lmao

08:48 <mmind00> CounterPillow: beginning of the robot uprising?

08:49 <mmind00> CounterPillow: at least judging by the message in the devicetree channel ... the npu isn't the only thread affected

08:49 <CounterPillow> oh dear

08:53 <mmind00> CounterPillow: this week it's mails ... next week they're replaying that episode with the robo-vacuum from "Love-Death-Robots season2" ... and the following week it's Terminator-1

08:53 <CounterPillow> :D

10:36 <CounterPillow> hahahaha it's still going

13:41 <Kwiboo-> CounterPillow: regarding rocket patches for rk3588, if I look correctly at the patches it will only run at 200mhz using normal pll and not 1ghz using pvtpll?, is devfreq support missing in the driver at this time?

13:42 <CounterPillow> Kwiboo: I've not looked into what frequency it runs at at all for now, just that it runs at all. It's possible it's not doing devfreq atm.

13:43 <CounterPillow> Kwiboo: for how to use the userspace part of it, see https://gitlab.collabora.com/hardware-enablement/rockchip-3588/notes-for-rockchip-3588/-/merge_requests/45/diffs

13:44 <CounterPillow> (tflite is a Google project so by nature it is terrible and requires an older Python, and it's also abandoned and superseded by a new Google project that also requires an older Python.)

13:57 <Kwiboo> CounterPillow: thanks, I guess it may need similar workaround to use scmi clock at higher rates, will try to post my scmi gpu clk patches with lima/panfrost/panthor workaround any day now

13:57 <CounterPillow> Alright, good to hear :) I'll be sure to give them a test when you post them

23:14 <CounterPillow> Kwiboo: oh yeah I forgot to mention, looks like I'll be sent a ROCK 2A, so for RK3528 SAI and HWRNG bindings+dts if they're not already done by then I'll likely do those