Bitweasil has quit [Quit: ZNC 1.8.2+deb2ubuntu0.1 - https://znc.in]
Bitweasil has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
System_Error has quit [Ping timeout: 264 seconds]
System_Error has joined #linux-rockchip
psydroid has quit [Ping timeout: 272 seconds]
psydroid has joined #linux-rockchip
hexdump0815 has quit [Ping timeout: 276 seconds]
hexdump0815 has joined #linux-rockchip
Daanct12 has joined #linux-rockchip
naoki has quit [Ping timeout: 268 seconds]
Daanct12 has quit [Ping timeout: 252 seconds]
Daanct12 has joined #linux-rockchip
raster has joined #linux-rockchip
Daanct12 has quit [Ping timeout: 252 seconds]
ldevulder has joined #linux-rockchip
Daanct12 has joined #linux-rockchip
Daanct12 has quit [Quit: WeeChat 4.6.3]
Daanct12 has joined #linux-rockchip
hexdump0815 has quit [Quit: WeeChat 3.8]
hexdump0815 has joined #linux-rockchip
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
<CounterPillow>
mmind00: for https://lore.kernel.org/linux-rockchip/20250425-rk3576-tsadc-upstream-v5-0-0c840b99c30e@collabora.com/ is there anything you'd want in a V6 once 6.16-rc1 is out, or should I resend V5 if it still applies by then? No rush about reviews right now because it's way too late for this cycle anyway, but I thought I'd poke you about it early so it doesn't slip through the cracks next cycle :)
<mmind00>
CounterPillow: I should probably give that series a spin on my rk3576 :-) ... other than that looks great and all ... if you're updating/resending, one option would be to split the rk3576-hwsupport and the trim parts ... all the patches are already split along those lines
<mmind00>
CounterPillow: i.e. for subsystem maintainers (that don't know the soc in depth) it is often harder to discern if it makes sense to apply parts of a series
<mmind00>
CounterPillow: especially as the rk3576 hw-support itself is so nicely minimal
System_Error has quit [Remote host closed the connection]
System_Error has joined #linux-rockchip
<CounterPillow>
Yeah but if I split it into two patch series that'll just be the base one which will give us sensor readings that are off by a couple degrees, and then another one that depends on the base one, and I'm not sure this will help it get any review/merge. The spicy part imho is the trim bindings, which have robh's R-b already. Basically I don't want it to look like the series is still undergoing changes that it needs because if anything
<CounterPillow>
that'll delay review+merge even further, because it looks like it hasn't "settled down" yet.
<mmind00>
CounterPillow: also a fair point
raster has quit [Quit: Gettin' stinky!]
ungeskriptet has joined #linux-rockchip
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
stikonas has joined #linux-rockchip
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
punit has joined #linux-rockchip
punit has quit [Remote host closed the connection]
punit has joined #linux-rockchip
Daanct12 has quit [Quit: WeeChat 4.6.3]
paulk has quit [Ping timeout: 245 seconds]
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
ungeskriptet has quit [Remote host closed the connection]
ungeskriptet has joined #linux-rockchip
<diederik>
Is the rk3576 TRM publicly available?
ldevulder has quit [Ping timeout: 244 seconds]
ldevulder has joined #linux-rockchip
paulk has joined #linux-rockchip
paulk has quit [Changing host]
paulk has joined #linux-rockchip
dsimic has quit [Ping timeout: 265 seconds]
dsimic has joined #linux-rockchip
<CounterPillow>
not that I'm aware of, no
raster has joined #linux-rockchip
eballetbo has joined #linux-rockchip
<diederik>
ok, thanks for the info
mripard has quit [Quit: WeeChat 4.6.2]
diederik has quit [Ping timeout: 252 seconds]
raster has quit [Quit: Gettin' stinky!]
vagrantc has joined #linux-rockchip
ldevulder has quit [Ping timeout: 260 seconds]
raster has joined #linux-rockchip
diederik has joined #linux-rockchip
eballetbo has quit [Quit: Connection closed for inactivity]
<CounterPillow>
diederik: I don't know what developments happened in the kernel wrt DT overlays since then, but that explains how to apply them by having mainline u-boot apply them to the DT it passes to Linux
<diederik>
ok, cool. Thanks :-)
<mmind00>
I think runtime-application of overlays is not inside the kernel
<mmind00>
But having u-boot apply overlays definitly is the safer method ... either from extlinux, or you can also add everything (kernel, dtb, dtbo's) into a FIT image for u-boot to load
<CounterPillow>
alright, so I guess the only change kernel wise is that overlays now are included in the repo in an overlays subdirectory
<diederik>
I noticed errors wrt Rock 5B regarding mmc2 (M.2 E-key) ... probably because its empty. So I guess it could/should be moved into an overlay, but then I need a way to test it with an overlay (and then I should see the error again)
paulk has quit [Ping timeout: 268 seconds]
paulk has joined #linux-rockchip
paulk has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]