11:54 <CounterPillow> Kwiboo: do you need any help with the RK3576 mainline u-boot stuff? I've been running a branch based on that for a while now, with this patch on top to make sure u-boot initialises the FUSB302 controller before Linux makes it a footgun: https://gitlab.collabora.com/hardware-enablement/rockchip-3588/u-boot/-/commit/26b4e128e2a32548fdd431ff5eefc7f01f60af13

13:06 <Woutervanh> Hello. Still struggling with my display on rk3288. ultimate goal is to have dual display running. 1 via direct LVDS, the other via an edp to LVDS bridge (nxp ptn3460). Now I'm trying to get the bridge up and running, but failing to. No devices pop up in /sys/class/drm. If I ignore the ptn3460 completely, and just connect the edp to a edp-panel

13:06 <Woutervanh> (virtually), I have some jumping visual with a lot of artifacts. However, when putting the bridge in between, it seems things are not running correctly. https://gist.github.com/woutervanh/db8abfe1e7250aa8d5042cb2cd100cfa => here is my dts + dmesg output with drm debug on. Anyone seeing something obviously I missed?

13:21 <robmur01> Woutervanh: the GPIOs aren't optional - you'll either have to specify _something_ in the DT, or modify the driver to be happy without them

13:22 <robmur01> (the nxp-ptn3460 driver, that is)

13:26 <Woutervanh> rubmur01, even if they're just connected to VDD? They are not connected to an io whatsoever

13:29 <robmur01> seems like not having a reset might possibly be an issue, but either way, the GPIOs are the reason the driver is not probing right now

13:29 <robmur01> [ 2.638570] nxp,ptn3460 1-0020: cannot get gpio_pd_n -2

13:30 <qschulz> they all are requested with devm_gpiod_get by the driver, so they aren't optional

13:30 <qschulz> and they are among the required properties according to the DT binding

13:32 <qschulz> if i'm not mistaken, you should be able to make them optional by simply changing the calls to devm_gpiod_get_optional?

13:38 <Woutervanh> forgot to remove the comment on the gpio's. I just added some unused io's to it for now. Now the error is gone, but still no drm devices popping up

13:38 <Woutervanh> https://gist.github.com/woutervanh/db8abfe1e7250aa8d5042cb2cd100cfa?permalink_comment_id=5456597#gistcomment-5456597

17:32 <Kwiboo> CounterPillow: it was mmind00 who sent first rk3576 u-boot series, my branch mainly contains feedback, suggested changes and a few improvements, along with me sprialing out and porting rk3528 and rebasing on top of that

17:32 <Kwiboo> would be nice if someone can send an updated rk3576 series before merge window opens for 2025.07 :-)

17:33 <CounterPillow> Oh I see, thanks for the clarification :)

17:34 <Kwiboo> hoping to get a v2 of rk3528 series out soon, changing to use mainline Linux cru dt-bindings headers and adding basic usb support

17:37 <Kwiboo> tested some usb otg on rk3576, but did not get it working, probably some clock or usb3 phy may be needed

17:39 <Kwiboo> also picked up a second rk3576 board, toybrick tb-rk3576d, so can help with more testing on something beside the sige5

17:45 <mmind00> Kwiboo: *sigh* ... I'll try to find some time for the rk3576 ;-) ... way too many shiny things going on at the same time