rockchip: add 9tripod x3568 v4 support

[rbqvq]

Description

Add support for the 9tripod x3568 v4 support

How Has This Been Tested?

I have built current and edge image based on trixie for the board locally, it boots and worked fine.

Checklist:

• 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

---

Notes:

Linux mainline upstreaming...
U-Boot upstreaming pending

[github-actions]

Hey @rbqvq! 👋

Thanks for submitting your first pull request to the Armbian project — we're excited to have you contributing! 🧡
Your effort doesn’t just improve Armbian — it benefits the entire community of users and developers.

If you'd like to stay informed about project updates or collaborate more closely with the team,
you can optionally share some personal contact preferences at armbian.com/update-data.
This helps us keep in touch without relying solely on GitHub notifications.

Also, don’t forget to ⭐ star the repo if you haven’t already — and welcome aboard! 🚀

[coderabbitai]

Walkthrough

This PR adds a new board configuration file for the 9Tripod X3568 v4 (RK3568-based board). It includes board metadata and partitioning information, configures mainline U-Boot sources with specific defconfig, branch, and patch directory mappings, and defines U-Boot blob placement logic. Additionally, it introduces persistent network interface renaming rules via udev for eth0/eth1 based on PCI/ethernet identifiers, and configures LED behavior for ethernet interfaces to reflect link states and activity.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

• Verify the U-Boot blob mapping in the nested write_uboot_platform helper function is correct for this board variant
• Confirm network interface identification strings in udev rules match actual hardware identifiers
• Validate LED configuration syntax and interface names in armbian-leds.conf format
• Check that global variables (BOOTCONFIG, BOOTSOURCE, BOOTBRANCH, BOOTPATCHDIR, UBOOT_TARGET_MAP) are properly initialized and cleaned up

Possibly related PRs

• board: add BesTV R3300-L support #8754: Adds board config with UBOOT_TARGET_MAP and nested write_uboot_platform helper following similar pattern
• u-boot: v2025.10: prepare 0000.patching_config.yaml for null-patch-free u-boot #8739: Introduces mainline U-Boot override with identical global boot variables and write_uboot_platform logic
• lckfb-taishanpi: update u-boot patches, add current&edge kernel support #8428: Modifies board-specific post_family_config for mainline U-Boot migration with comparable variable setup and helper function structure

Suggested reviewers

• clee
• prahal
• rpardini
• krachlatte
• igorpecovnik
• paolosabatino
• pyavitz

Pre-merge checks and finishing touches

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and concisely describes the main change: adding support for a specific rockchip board variant.
Description check	✅ Passed	The description is directly related to the changeset, explaining what is being added, how it was tested, and providing relevant context about upstream status.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

Disabled knowledge base sources:

• Jira integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 38c85a6 and 2e9d35b.

⛔ Files ignored due to path filters (9)

• patch/kernel/archive/rockchip64-6.12/dt/rk3568-9tripod-x3568-v4.dts is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.12/overlay/Makefile is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.12/overlay/rk3568-9tripod-x3568-v4-camera-demo.dtso is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.12/overlay/rk3568-9tripod-x3568-v4-video-demo.dtso is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.18/dt/rk3568-9tripod-x3568-v4.dts is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.18/overlay/Makefile is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.18/overlay/rk3568-9tripod-x3568-v4-camera-demo.dtso is excluded by !patch/**
• patch/kernel/archive/rockchip64-6.18/overlay/rk3568-9tripod-x3568-v4-video-demo.dtso is excluded by !patch/**
• patch/u-boot/v2025.10/board_9tripod-x3568-v4/0001-arm-rockchip-Add-support-for-the-9Tripod-X3568-v4.patch is excluded by !patch/**

📒 Files selected for processing (1)

• config/boards/9tripod-x3568-v4.csc (1 hunks)

🧰 Additional context used

🧠 Learnings (18)

📓 Common learnings

Learnt from: HackingGate
Repo: armbian/build PR: 8665
File: config/boards/photonicat2.csc:4-4
Timestamp: 2025-10-26T10:41:35.118Z
Learning: In the Armbian build system, rk3576 boards consistently use BOARDFAMILY="rk35xx" for both vendor and edge kernel targets. The rk35xx family configuration sources rockchip64_common.inc, which provides edge and current kernel branch definitions, making these branches available even though they're not defined directly in rk35xx.conf.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8428
File: config/boards/lckfb-taishanpi.csc:5-9
Timestamp: 2025-07-25T03:51:50.830Z
Learning: When reviewing PRs in the Armbian build system, U-Boot defconfig files and patches may be added as part of the PR changes but might not be visible in the current repository clone state during review. It's important to check the actual PR file changes directly via GitHub or the PR API to get the complete picture of what files are being added or modified.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8428
File: config/boards/lckfb-taishanpi.csc:5-9
Timestamp: 2025-07-25T03:51:50.830Z
Learning: When reviewing PRs in the Armbian build system, U-Boot defconfig files and patches may be added as part of the PR changes but might not be visible in the current repository clone state during review. It's important to check the actual PR file changes directly via GitHub API (https://api.github.com/repos/armbian/build/pulls/{pr_number}/files) to get the complete picture of what files are being added or modified, especially for U-Boot patches that will be applied during the build process.

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:222-230
Timestamp: 2025-09-14T06:32:29.806Z
Learning: In the Armbian build system, the write_uboot_platform() function implementations follow different patterns across Rockchip family files. The newer standard (used in rockchip64_common.inc and rk3506) includes 'status=none' parameter in dd commands, while older implementations (rk3288, rk322x) use an older pattern without this parameter. The rk3506 implementation correctly follows the current Rockchip family standard.

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:29:18.958Z
Learning: In the Armbian build system, vendor branch configurations in family files are designed to be shared across multiple SoCs within the same family that use the same vendor kernel tree. For example, rk35xx and rockchip-rk3588 families both use identical vendor branch settings (same KERNELSOURCE, KERNELBRANCH, and KERNELPATCHDIR), demonstrating that vendor branches are intentionally generic rather than SoC-specific.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:10:25.610Z
Learning: In the Armbian build system, rk32xx and rk33xx Rockchip SoCs no longer have BSP-based (vendor) kernel branches. The rk3506 is the first 32-bit Rockchip SoC to use the vendor branch in the current codebase.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files (regardless of file extension), the standard pattern is to have only one line as a comment describing the board hardware specifications. This single-line description typically includes the SoC model, core count, RAM options, and key features like connectivity options, storage interfaces, and special features. The file extensions indicate board support status: .conf (standard support), .csc (community supported), .eos (end of support), .tvb (tvbox), .wip (work in progress).

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files, .wip and .conf extensions require BOARD_MAINTAINER to be present and contain at least one maintainer. If no maintainer is present, the board support rules state it does not qualify for standard support and must be moved to community support (.csc extension). This is documented at https://docs.armbian.com/User-Guide_Board-Support-Rules/

Learnt from: EvilOlaf
Repo: armbian/build PR: 8417
File: config/boards/orangepi5pro.csc:57-58
Timestamp: 2025-07-23T07:30:52.265Z
Learning: In the Armbian build system, BOOTPATCHDIR can contain board-specific subdirectories (e.g., board_orangepi5pro) for applying patches to specific boards only. The framework automatically checks if such board-specific subdirectories exist for the board being built and applies those patches accordingly.

Learnt from: igorpecovnik
Repo: armbian/build PR: 8849
File: config/boards/radxa-e54c.csc:14-28
Timestamp: 2025-11-02T20:49:56.719Z
Learning: In Armbian board configuration files (config/boards/*.conf, *.csc, etc.), do not use kernel_config_set, kernel_config_set_m, kernel_config_set_y, or custom_kernel_config__* functions to modify kernel configuration. Kernel configuration is associated with LINUXFAMILY/BOARDFAMILY, not individual BOARD. Board-specific kernel modifications cause inconsistency in kernel packages published to the apt repository because boards within a family share the same kernel packages. Kernel configuration changes must be made in the appropriate kernel config file (e.g., config/kernel/linux-*-*.config) or in family configuration files (config/sources/families/*.conf, *.inc) instead.

Learnt from: EvilOlaf
Repo: armbian/build PR: 8754
File: config/boards/bestv-r3300-l.csc:14-16
Timestamp: 2025-10-14T05:08:11.785Z
Learning: In the Armbian build system, BOOTBRANCH_BOARD is a valid framework variable used as a fallback when BOOTBRANCH is unset. The framework checks BOOTBRANCH_BOARD before applying the default bootloader branch value (see config/sources/common.conf). Board configuration files can use BOOTBRANCH_BOARD to specify the bootloader branch.

Learnt from: rpardini
Repo: armbian/build PR: 8044
File: patch/u-boot/v2025.04/cmd-fileenv-read-string-from-file-into-env.patch:76-86
Timestamp: 2025-03-31T22:20:48.475Z
Learning: For the Armbian build project, maintaining consistency with existing patches across U-Boot versions (such as between 2025.01 and 2025.04) is prioritized over refactoring individual patches for code improvements.

📚 Learning: 2025-11-02T20:49:56.719Z

Learnt from: igorpecovnik
Repo: armbian/build PR: 8849
File: config/boards/radxa-e54c.csc:14-28
Timestamp: 2025-11-02T20:49:56.719Z
Learning: In Armbian board configuration files (config/boards/*.conf, *.csc, etc.), do not use kernel_config_set, kernel_config_set_m, kernel_config_set_y, or custom_kernel_config__* functions to modify kernel configuration. Kernel configuration is associated with LINUXFAMILY/BOARDFAMILY, not individual BOARD. Board-specific kernel modifications cause inconsistency in kernel packages published to the apt repository because boards within a family share the same kernel packages. Kernel configuration changes must be made in the appropriate kernel config file (e.g., config/kernel/linux-*-*.config) or in family configuration files (config/sources/families/*.conf, *.inc) instead.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-10-26T10:41:35.118Z

Learnt from: HackingGate
Repo: armbian/build PR: 8665
File: config/boards/photonicat2.csc:4-4
Timestamp: 2025-10-26T10:41:35.118Z
Learning: In the Armbian build system, rk3576 boards consistently use BOARDFAMILY="rk35xx" for both vendor and edge kernel targets. The rk35xx family configuration sources rockchip64_common.inc, which provides edge and current kernel branch definitions, making these branches available even though they're not defined directly in rk35xx.conf.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-18T03:36:17.862Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files, .wip and .conf extensions require BOARD_MAINTAINER to be present and contain at least one maintainer. If no maintainer is present, the board support rules state it does not qualify for standard support and must be moved to community support (.csc extension). This is documented at https://docs.armbian.com/User-Guide_Board-Support-Rules/

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-14T06:32:29.806Z

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:222-230
Timestamp: 2025-09-14T06:32:29.806Z
Learning: In the Armbian build system, the write_uboot_platform() function implementations follow different patterns across Rockchip family files. The newer standard (used in rockchip64_common.inc and rk3506) includes 'status=none' parameter in dd commands, while older implementations (rk3288, rk322x) use an older pattern without this parameter. The rk3506 implementation correctly follows the current Rockchip family standard.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-18T03:36:17.862Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8537
File: config/boards/qcom-robotics-rb5.conf:1-1
Timestamp: 2025-09-18T03:36:17.862Z
Learning: In Armbian board configuration files (regardless of file extension), the standard pattern is to have only one line as a comment describing the board hardware specifications. This single-line description typically includes the SoC model, core count, RAM options, and key features like connectivity options, storage interfaces, and special features. The file extensions indicate board support status: .conf (standard support), .csc (community supported), .eos (end of support), .tvb (tvbox), .wip (work in progress).

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-07-17T04:12:33.125Z

Learnt from: pyavitz
Repo: armbian/build PR: 8388
File: config/boards/kickpik2b.conf:1-14
Timestamp: 2025-07-17T04:12:33.125Z
Learning: In the Armbian build system, board configuration files (*.conf) follow a project standard of not including shebang lines, even though they contain bash code and are sourced by the build system. This is an established Armbian convention that individual contributors are expected to follow, and changes to this standard would require broader project maintainer approval.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-10-05T19:31:16.930Z

Learnt from: rpardini
Repo: armbian/build PR: 8718
File: config/boards/thinkpad-x13s.conf:185-185
Timestamp: 2025-10-05T19:31:16.930Z
Learning: In config/boards/thinkpad-x13s.conf, the x13s_obtain_firmware() function is reference-only utility code that never runs. It is kept for documentation purposes. Updates to firmware must be done at the armbian/firmware repository. TODO comments in this function are intentional reminders and should not be flagged.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-07-25T03:51:50.830Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8428
File: config/boards/lckfb-taishanpi.csc:5-9
Timestamp: 2025-07-25T03:51:50.830Z
Learning: When reviewing PRs in the Armbian build system, U-Boot defconfig files and patches may be added as part of the PR changes but might not be visible in the current repository clone state during review. It's important to check the actual PR file changes directly via GitHub or the PR API to get the complete picture of what files are being added or modified.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-14T06:29:18.958Z

Learnt from: amazingfate
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:29:18.958Z
Learning: In the Armbian build system, vendor branch configurations in family files are designed to be shared across multiple SoCs within the same family that use the same vendor kernel tree. For example, rk35xx and rockchip-rk3588 families both use identical vendor branch settings (same KERNELSOURCE, KERNELBRANCH, and KERNELPATCHDIR), demonstrating that vendor branches are intentionally generic rather than SoC-specific.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-07T17:39:32.272Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8586
File: config/boards/nanopi-r76s.conf:15-21
Timestamp: 2025-09-07T17:39:32.272Z
Learning: In the Armbian build system, the variables $BOARD and $SDCARD are always set by the build framework, so guard checks for these variables are unnecessary in board configuration files and hook functions.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-06-25T03:40:52.109Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8330
File: config/sources/families/sun55iw3.conf:32-36
Timestamp: 2025-06-25T03:40:52.109Z
Learning: In Armbian build system configuration files like config/sources/families/*.conf, when KERNELSOURCE is not explicitly declared in a case branch, the system falls back to a default KERNELSOURCE value, so missing KERNELSOURCE declarations are not critical issues.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-14T06:10:25.610Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8619
File: config/sources/families/rockchip.conf:64-70
Timestamp: 2025-09-14T06:10:25.610Z
Learning: In the Armbian build system, rk32xx and rk33xx Rockchip SoCs no longer have BSP-based (vendor) kernel branches. The rk3506 is the first 32-bit Rockchip SoC to use the vendor branch in the current codebase.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-10-14T05:08:11.785Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8754
File: config/boards/bestv-r3300-l.csc:14-16
Timestamp: 2025-10-14T05:08:11.785Z
Learning: In the Armbian build system, BOOTBRANCH_BOARD is a valid framework variable used as a fallback when BOOTBRANCH is unset. The framework checks BOOTBRANCH_BOARD before applying the default bootloader branch value (see config/sources/common.conf). Board configuration files can use BOOTBRANCH_BOARD to specify the bootloader branch.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-06-12T21:03:39.686Z

Learnt from: djurny
Repo: armbian/build PR: 8287
File: config/bootscripts/boot-sunxi.cmd:148-161
Timestamp: 2025-06-12T21:03:39.686Z
Learning: In Armbian U-Boot bootscripts, the `${cpu}` environment variable is always pre-set by U-Boot (or defaults to a valid value), so additional guards against it being unset are unnecessary.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-06-25T03:42:09.086Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8330
File: config/sources/families/sun55iw3.conf:32-36
Timestamp: 2025-06-25T03:42:09.086Z
Learning: In Armbian build system configuration files like config/sources/families/*.conf, KERNELSOURCE is explicitly declared when using unofficial or 3rd party kernel repositories (like the "dev" branch using https://github.com/apritzel/linux), but can be omitted when using the standard mainline kernel (like the "edge" branch) since it will fall back to the default mainline source.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-07-23T07:30:52.265Z

Learnt from: EvilOlaf
Repo: armbian/build PR: 8417
File: config/boards/orangepi5pro.csc:57-58
Timestamp: 2025-07-23T07:30:52.265Z
Learning: In the Armbian build system, BOOTPATCHDIR can contain board-specific subdirectories (e.g., board_orangepi5pro) for applying patches to specific boards only. The framework automatically checks if such board-specific subdirectories exist for the board being built and applies those patches accordingly.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

📚 Learning: 2025-09-12T21:44:09.061Z

Learnt from: Grippy98
Repo: armbian/build PR: 8624
File: config/boards/sk-am62p.conf:8-8
Timestamp: 2025-09-12T21:44:09.061Z
Learning: For TI K3 family boards in Armbian, BOOT_FDT_FILE uses .dts extension (not .dtb) as the standard convention. The build system handles this correctly by automatically compiling .dts to .dtb during kernel build and using the BOOT_FDT_FILE value directly in bootloader configurations.

Applied to files:

• config/boards/9tripod-x3568-v4.csc

🔇 Additional comments (4)

config/boards/9tripod-x3568-v4.csc (4)

1-14: LGTM! Board metadata is well-configured.

The metadata section correctly configures all required fields. The use of BOOT_SOC="rk3568" at Line 8 is the recommended approach that automatically provides BL31_BLOB and DDR_BLOB variables. The version suffix in the board name aligns with the maintainer-approved approach due to distinct hardware revisions requiring different device tree files.

---

43-86: Verify the LED paths match the actual hardware.

The LED configuration follows the correct armbian-leds.conf format with appropriate netdev trigger settings. The amber LEDs are configured to show link + activity (tx/rx), while green LEDs show link state only, which is a sensible configuration.

However, the LED sysfs paths (e.g., /sys/class/leds/stmmac-0:03:amber:lan) are hardware-specific and depend on the PHY addresses and driver behavior. Please verify these paths exist on the actual hardware when the board is booted.

---

15-31: I need to examine the patch file to determine if it includes the defconfig or if additional files are needed.

Let me examine the patch file content to determine if it includes the defconfig:

Based on my verification, I can now provide a comprehensive assessment. The patch file for adding 9Tripod X3568 v4 board support is present in the PR. Let me examine the actual patch content more closely to confirm it includes the defconfig:

Based on my verification analysis:

Code configuration is correct; defconfig will be provided by the U-Boot patch.

The U-Boot patch patch/u-boot/v2025.10/board_9tripod-x3568-v4/0001-arm-rockchip-Add-support-for-the-9Tripod-X3568-v4.patch is present in the PR. A standard board support patch for U-Boot contains all necessary files including the defconfig file in the configs/ directory as part of the unified diff format. The defconfig 9tripod-x3568-v4-rk3568_defconfig will be created when this patch is applied to U-Boot v2025.10 during the Armbian build process, making it available for the BOOTCONFIG reference in the board configuration. The write_uboot_platform implementation correctly uses the modern Rockchip standard with status=none.

---

33-41: No issues found - ethernet controller addresses are correct.

The addresses fe010000 and fe2a0000 are the MMIO base addresses for the RK3568 on-chip Gigabit MAC controllers and appear in RK3568 device trees as ethernet@fe010000 and ethernet@fe2a0000. The udev rules correctly map these KERNELS values to eth0 and eth1, which aligns with the board's device tree aliases (ethernet0 = &gmac0, ethernet1 = &gmac1).

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[EvilOlaf]

@coderabbitai review

[coderabbitai]

✅ Actions performed

Review triggered.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

[igorpecovnik]

I would propose to drop version number from board config name (and board name) as it is unlikely to ever have other version. Usually and evenutally all versions are gettion supported or, like in some cases, only some.

[rbqvq]

Different boards have different DeviceTree :(
There seems to be a v2 version of this board.

It's probably like this.
The v2 version is for retail and the v4 version is for enterprise sales (but is already in the 2-hand market)

They are in Taobao (China's e-commerce platform) sells X3568 v2.

So I want to be consistent with what the main line submitted.

[igorpecovnik]

The v2 version is for retail and the v4 version is for enterprise sales (but is already in the 2-hand market)

Ordinary mess :(

So I want to be consistent with what the main line submitted.

OK, follow as planned.

[chainsx]

/lgtm

It is quite normal for different boards to have variations in hardware and versions. Once everything is finalized, this PR can be merged.

[github-actions]

✅ This PR has been reviewed and approved — all set for merge!

[rbqvq]

I think all things are done.
Let's prepare it for v25.11 😉

---

Kernel is still upstreaming.
UBoot upstreaming work will begin after kernel merged.

[igorpecovnik]

it boots and worked fine.

Great!

Code looks good too. Tnx.

[github-actions]

✅ This PR has been reviewed and approved — all set for merge!