Re: [PATCH v2] clk: sunxi-ng: a733: Keep SCP firmware bus clocks enabled
From: Enzo Adriano
Date: Thu Nov 19 2026 - 13:09:09 EST
Hi Chen-Yu, Andre,
>>> But I think there is still the arisc on
>>> the A733, so this would more likely run the management processor (SCP) code?
The A733 CPUS domain has both an E902 and an OR100 (manual section 1.2,
figure 1-1). The vendor SCP firmware Radxa ships for Cubie A7S, called
"arisc" by Allwinner, runs on the E902: vendor BL31 writes its entry
point to E902_RST_START_ADDR_REG at 0x07032204 (manual section 5.2.3).
Radxa's BL31, in its system reset path, sends a reboot request to the
E902 through the CPUX-to-CPUS msgbox. Exactly where the no-flag reboot
stalls is not known.
> The question now is whether this SCP use case is something we deem
> useful, for mainline. If it's just about to run the BSP firmware, I
> think we shouldn't bother, we just don't support that. But if we end up
> running something like crust on the E902, then it's a different story.
For me this is only about the vendor BSP firmware; I have no other SCP
firmware for the E902 to test with. Upstream Crust has no A733 target,
and the A733 TF-A port under review resets through the watchdog, not
the msgbox [1].
>>>> So, not a fan of this. If the loaded firmware somehow needs some resources
>>>> then perhaps the software that loaded it needs to somehow tell the kernel
>>>> they are needed, like the bootloader patching the DT passed to the kernel.
Vendor U-Boot already applies DT fixups, but the A733 CCU binding and
driver do not accept protected-clocks today. A loader-declared handoff
would need a new binding and driver support, plus loader changes.
> So I wonder if we should just pragmatically add CLK_IGNORE_UNUSED, to
> not shut on the door on this SCP use case later.
> If we ever only want to use remoteproc, I think we don't need this patch.
CLK_IGNORE_UNUSED would also leave a future remoteproc driver free to
gate the core. Chen-Yu, if you are fine with it, I will test it on A7S
and send v3 based on linux-sunxi for-next, with Andre's comment wording
and a short test note. Otherwise I will drop the patch.
[1] https://review.trustedfirmware.org/c/TF-A/trusted-firmware-a/+/55200
Thanks,
Enzo