00:26 <PhoenixMage> watching nomis and robmur01 talk makes my head hurt

09:44 <nomis> Does anybody with a rk3328-based tv box know, where the button behind the headphone-socket is connected?

10:04 <robmur01> in the reference design, the "recovery" button is connected to SARADC channel 0 - see the "adc-keys" node in most DTs

10:08 <robmur01> my old RK3288 box also has it wired in parallel to the reset pin, which rather prevents it from being repurposed as a general input :)

10:09 <nomis> robmur01: ah.

10:10 <nomis> robmur01: does your tv box also has a funky led wiring for the power-led? I have two leds (red/blue) that apparently share a common GPIO pin, one LED being inverted to the other.

10:15 <robmur01> that sounds like the "work/standby" setup straight from the reference design

10:15 <robmur01> if you don't have it already - http://opensource.rock-chips.com/images/0/09/Rk3328_hardware_reference.zip

10:16 <nomis> I don't, thank you.

12:22 <nomis> yep, headphones-key works. A little bit of a slow sampling rate, but it'll do for now.

13:21 <nomis> robmur01: may I ask you how you've configured your usb3-port in mainline? The rockchip-kernel apparently uses a "rockchip-inno"-family of drivers unavailable in mainline. Did you adapt some rk3399-based devicetree snippets for the 3328?

13:22 <nomis> (the rk3328-based compatible-lines are not recognized at all in my linux-yocto_5.4

13:35 <robmur01> you may ask, but be prepared for disappointment since the answer is "I haven't" ;)

13:36 <robmur01> I think the old patches for the controller itself still apply: https://lore.kernel.org/linux-arm-kernel/20171204094041.25439-2-heiko@sntech.de/

13:36 <robmur01> but that only gets it as far as "more-or-less works until you unplug anything" state

13:37 <robmur01> there was an attempt at porting the phy driver more recently, which seems to have stalled: https://lore.kernel.org/linux-usb/20191028182254.30739-1-pgwipeout@gmail.com/

13:37 <nomis> hm, no nodes for the respective phys at all?

13:40 <robmur01> I've been meaning to take another look at some point, but I have far too much else to get on top of just at the moment ;)

13:44 <nomis> ok, thank you.

16:33 <TomTheDragon> anyone else have issues with mainline linux kernel getting a display on boot? seems I have to fiddle with xrandr and flip things back and forth before it finally posts video

16:44 <robmur01> TomTheDragon: on what? HDMI output is working just fine on my RK3399 and RK3328 boards here. My old RK3288 box is a bit unhappy, with the display vanishing a few seconds after the login prompt appears, but I suspect that might be down to the new u-boot display support doing something weird (and right now the kernel's not even starting, and I can't remember what I've done to it...)

16:46 <TomTheDragon> robmur01: rock pi 4 and rockpro64

16:46 <TomTheDragon> robmur01: both rk3399

16:47 <TomTheDragon> also, various versions of armbian with mainline kernel, up to 5.6

16:48 <TomTheDragon> Seems to be just fine on a rockchip kernel... but I really want panfrost. Mainly because it's likely better than my current mali/gl4es setup.

16:50 <robmur01> Hmm, should be pretty much equivalent to my NanoPC-T4 since they're all minor variations on the reference design, and I've been running stock Arch kernels since forever. What U-boot version is Armbian deploying for those?

16:54 <robmur01> (I've forgotten what the deal is with their distinct-but-sort-of-overlapping "rk3399" and "rockchip64" branches)