Hi Massimo,

On 9/21/26 6:51 PM, Massimo Pegorer wrote:
Hi Jonas,

Il giorno dom 20 set 2026 alle ore 17:49 Jonas Karlman
<[email protected]> ha scritto:

Hi Massimo,

On 9/20/2026 4:15 PM, Massimo Pegorer wrote:
Looking to provide a way to print reset cause on a board equipped with
a PX30 SoC I ran into the following existing issues related to Rockchip
SoCs:

1. It is not possible to select DISPLAY_CPUINFO configuration option
    with ARCH_ROCKCHIP, except for RK3399 RK3288 RK3568 RK3588 SoCs, due
    to incomplete definition of type 'struct rockchip_cru' caused by
    Rockchip common implementation of print_cpuinfo() function: see
    0f9872c4db11 for the RK3588 SoC "workaround", which I feel not
    optimal. Note that DISPLAY_CPUINFO has default y if ARM; therefore,
    it is deselected in each Rockchip defconfig except for listed SoCs.

2. It is not possible to deselect DISPLAY_CPUINFO configuration option
    with TARGET_ROC_PC_RK3399 due to missing get_reset_cause() symbol
    caused by mach-rockchip/Makefile skipping cpu-info.c. I do not see
    how e230c579a3f6 commit separated the reset cause from displaying
    cpuinfo as proposed.

Please see the series "rockchip: Add and use rockchip_sysreset_bind()
helper" [1] that already should resolve above issues.

That series has some loose depends for a clean apply, but the idea is to
fully move the resets status handling into the sysreset driver and start
cleanup of 'struct rockchip_cru' use.

Please try, review and possible build on top of that :-)

Thanks, I will. I missed it as I re-joined U-Boot mailing list just a month ago.


Welcome back!

What's the status of that series? Is it going to be applied to u-boot/next?


The status is that it needs people reviewing and/or testing the series. I'm the sole maintainer at the moment for Rockchip and I have a day job so I put as much time as I can/want to in it but it's limited, but I'll eventually get to it.

You don't need any permission to review or test patches on the mailing list so please feel free to spend some time reviewing other people's patches, any help is welcome :)

Cheers,
Quentin

Reply via email to