new branch rk3576 to family rk35xx and armsom sige5

[amazingfate]

Description

There is no official SDK released for rk3576 so we have to use kernel and uboot from rockchip's internal (beta I guess) repo.
I wish this rk3576 family can get deleted when rockchip release new SDK for all rk35xx socs in the future.
I created kernel config based on rk35xx-vendor and enabled rk3576 soc support on top of it.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• ./compile.sh BOARD=armsom-sige5 BRANCH=vendor BUILD_DESKTOP=no BUILD_MINIMAL=no DEB_COMPRESS=xz KERNEL_CONFIGURE=no RELEASE=bookworm KERNEL_GIT=shallow
• board boots fine

Checklist:

Please delete options that are not relevant.

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[amazingfate]

We have to build uboot of rk3576 with BL32 blob, so I add env TEE to UBOOT_TARGET_MAP and add a patch to uboot to make use of this env.
And we have to use extlinux to boot kernel. boot.scr failed to execute.

[paolosabatino]

ehm, do we really want again another rockchip family?

edit: after having a quick look into, and after having a refresh of what was my initial idea I expressed in the forum thread, I guess this is coherent with having a single and unique per-soc family addressing the vendor kernel.

[igorpecovnik]

Agree. Its worth doing some extra work to keep it sane.

[amazingfate]

I guess this is coherent with having a single and unique per-soc family addressing the vendor kernel

We will merge work of rk3576 to rk35xx-vendor after rockchip's releases SDK for rk3528/rk356x/rk3588/rk3576. So another choice is adding a new branch rk35xx-vendor-rk3576 like rk35xx-vendor-boogie-panthor @rpardini added.

[rpardini]

like rk35xx-vendor-boogie-panthor @rpardini added

btw AF I think that BRANCH might be removed? If I understand, you've operated the magics needed to have panthor as an option directly in the vendor BRANCH and thus vendor-boogie-panthor is no longer necessary?

[amazingfate]

like rk35xx-vendor-boogie-panthor @rpardini added

btw AF I think that BRANCH might be removed? If I understand, you've operated the magics needed to have panthor as an option directly in the vendor BRANCH and thus vendor-boogie-panthor is no longer necessary?

That branch lacks maintenance, but it provides an out-of-box panthor image. It's better to update documents on how to toogle panthor driver with vendor kernel if we delete that.

[rpardini]

That branch lacks maintenance, but it provides an out-of-box panthor image.

Indeed, I won't have the cycles to keep it updated.

It's better to update documents on how to toogle panthor driver with vendor kernel if we delete that.

Ooops, I already sent the removal (and it was merged very fast)...

From what I could gather in armbian/linux-rockchip#171 we could come up with an panthor extension that:

1. Enables the panthor-gpu overlay by default
2. Adds obibaf-mesa extension

Anything else?

Thanks for the help and sorry for the hijack of this PR

[amazingfate]

• Enables the panthor-gpu overlay by default
• Adds obibaf

That would be enough.

[amazingfate]

• Add a new branch rk3576 to rk35xx.
• Enable RK806 I2C.
• Diable panfrost because there will be kernel panic when probing it.