[PATCH v3 1/3] rockchip: Add initial RK3582 support

[Kever Yang]

Hi Quentin, Jonas,


On 2025/8/11 23:44, Quentin Schulz wrote:
> Hi Jonas,
>
> On 8/11/25 12:26 AM, Jonas Karlman wrote:
>> The RK3582 SoC is a variant of the RK3588S with some IP blocks disabled.
>> What blocks are disabled/non-working is indicated by ip-state in OTP.
>>
>> This add initial support for RK3582 by using ft_system_setup() to mark
>> any cpu and/or vdec/venc node with status=fail as indicated by ip-state.
>>
>> This apply same policy as vendor U-Boot for RK3582, i.e. two big cpu
>> cores and one vdec/venc core is always failed/disabled.
>>
>> Enable Kconfig option OF_SYSTEM_SETUP in board defconfig to make use of
>> the required DT fixups for RK3582 board variants.
>>
>> Signed-off-by: Jonas Karlman <jonas at kwiboo.se>
>> ---
>> Changes in v3:
>> - Apply same policy for RK3582/RK3583 to match vendor U-Boot
>>    linux-6.1-stan-rkr6 tag, allow use of the GPU and one vdec core.
>
> Isn't the GPU supposed to be possibly non-fonctional on RK3582/RK3583? 
> If we don't disable it in the DT, how will the system actually behave?
>
> @Kever may have more official info on that?

RK3582 and RK3583 is different on GPU,  RK3582 do not have GPU, while 
RK3583 has limited GPU.

Did you see any RK3583 device on the market, it should only available in 
limited device instead of public, so maybe we can support rk3582 first 
due to

we have a ROCK 5C Lite with this chipset.

Thanks,

- Kever

>
> See remarks on v2 otherwise, most of them still apply.
>
>> - Update rkvdec node name to match latest mainling Linux DT patches.
>
> Should we rather wait for the patches to be actually merged before 
> trying to patch the device tree nodes that do not exist yet?
>
> Cheers,
> Quentin