On Fri, Feb 21, 2025 at 5:13 PM Johannes Erdfelt <johannes@xxxxxxxxxxx> wrote: > > On Wed, Feb 19, 2025, Jimmy Hon <honyuenkwun@xxxxxxxxx> wrote: > > This patchset is looking for testers. I do not have the hardware to test. > > I do have hardware and I gave your branch[1] a test. Thanks for the test results > > The following things tested successfully for me: > - Kernel boots > - Ethernet > - SPI NOR > - Micro SD card > - eMMC > - Bottom M.2 M-key slot (using an NVME drive) > - USB 2.0 ports > - Blue LED (using heartbeat trigger at least) > > I did not test: > - RTC > - UART > - HDMI1 > - HDMI IN > - Analog audio > - Mali GPU > - Heat sink fan > > However, neither of the USB 3.0 ports work. There are no XHCI messages > during boot. I confirmed my kernel config does build XHCI. I haven't > ruled out a mistake on my end yet. Does your kernel config have CONFIG_PHY_ROCKCHIP_USBDP? Both USB 3 ports on the Max/Ultra ports are wired to the usbdp controller and not combphy2_psu controller. It'll be set if you're using the arm64 defconfig. On my Orange Pi 5 Max, dmesg | grep xhci will show (e.g. io mem) [ 0.769699] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller [ 0.769919] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 1 [ 0.770062] xhci-hcd xhci-hcd.4.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000808002000010 [ 0.770119] xhci-hcd xhci-hcd.4.auto: irq 89, io mem 0xfc000000 [ 0.770351] xhci-hcd xhci-hcd.4.auto: xHCI Host Controller [ 0.770585] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 2 [ 0.770602] xhci-hcd xhci-hcd.4.auto: Host supports USB 3.0 SuperSpeed [ 0.770837] usb usb1: Manufacturer: Linux 6.14.0-rc1-2-rockchip-ARCH xhci-hcd [ 0.770844] usb usb1: SerialNumber: xhci-hcd.4.auto [ 0.772069] usb usb2: Manufacturer: Linux 6.14.0-rc1-2-rockchip-ARCH xhci-hcd [ 0.772076] usb usb2: SerialNumber: xhci-hcd.4.auto [ 0.792369] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller [ 0.792640] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 3 [ 0.792781] xhci-hcd xhci-hcd.5.auto: hcc params 0x0220fe64 hci version 0x110 quirks 0x0000808002000010 [ 0.792826] xhci-hcd xhci-hcd.5.auto: irq 90, io mem 0xfc400000 [ 0.793058] xhci-hcd xhci-hcd.5.auto: xHCI Host Controller [ 0.793311] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 4 [ 0.793327] xhci-hcd xhci-hcd.5.auto: Host supports USB 3.0 SuperSpeed [ 0.793530] usb usb3: Manufacturer: Linux 6.14.0-rc1-2-rockchip-ARCH xhci-hcd [ 0.793537] usb usb3: SerialNumber: xhci-hcd.5.auto [ 0.794703] usb usb4: Manufacturer: Linux 6.14.0-rc1-2-rockchip-ARCH xhci-hcd [ 0.794710] usb usb4: SerialNumber: xhci-hcd.5.auto > > Also, the green LED is constantly lit even when the trigger is set to > none and the brightness is set to 0. This made is a bit harder to > confirm that the blue LED was working. I haven't ruled out a mistake on > my end for this one yet either. Checking the schematic for the Max and the Ultra, they both use PWM4_M0 and PWM5_M1 to control the blue and green LEDs. Have you tried booting the vendor BSP 5.10 or 6.1 kernels? What's the behavior on those kernels? It's using GPIO pins there, whereas we're using PWM to be able to control brightness. > > I'll also see if I can give HDMI a test. Please report your results when you do. This is one of the differences from the Orange Pi 5 Max. The HDMI1 pinctrls does not use the default pinctrls like other RK3588 boards (including the Orange Pi 5 Plus). > > JE > > [1] https://github.com/jimmyhon/linux/tree/integrate-6.15 > Jimmy
