sunxi 6.12: Switch to v6.12.11, Add BananaPi M4 Berry support

[The-going]

Description

• Switch to v6.12.11
• config: Add BananaPi-M4-Berry support.
  Switch the ATF to the new version as well.
• u-boot: v2025.01: Add sun50i-h618-bananapi-m4-berry
• Add BananaPi M4 Berry support

How Has This Been Tested?

• Test build img ./compile.sh build KERNEL_CONFIGURE=no BOARD=bananapim4berry
• Test work on board BPI-M4-Berry

 ___ ___  _   ___ ___    __  __ ___ _  _ ___  
 / __| _ \/_\ / __| __|__|  \/  |_ _| \| |   \ 
 \__ \  _/ _ \ (__| _|___| |\/| || || .` | |) |
 |___/_|/_/ \_\___|___|  |_|  |_|___|_|\_|___/ 
                                               
 v25.02 rolling for BananaPi M4 Berry running Armbian Linux 6.12.11-edge-sunxi64

 Packages:     Debian stable (bookworm)
 Support:      DIY (custom image)
 IP addresses: (LAN) IPv4:  IPv6:  
 Performance:  

 Load:         16%              Up time:       0 min
 Memory usage: 9% of 1.93G  
 CPU temp:     35�°C            Usage of /:    16% of 7.3G

[pyavitz]

I haven't been able to get the M4 Zero to boot above v2024.04 in Armbian for some reason. I figured it was something in the Kernel patching as I am able to do so in my personal builds.

Does this PR have eMMC boot support?

[The-going]

I haven't been able to get the M4 Zero to boot above v2024.04 in Armbian for some reason.

u-boot v2025.01 in the default configuration for h616, implies OF_UPSTREAM to be set to y.
And CONFIG_DEFAULT_DEVICE_TREE="allwinner/sun50i-h618-bananapi-m4-berry".
Therefore, the dts must be placed in the dts/upstream/...... path.

Does this PR have eMMC boot support?

eMMC is detected correctly. I haven't tried downloading from eMMC yet.

Detected problems:
The Ethernet is not working.
The HDMI is not working.

Strange. The same changes on core 6.6, the HDMI works for me,
but the temperature sensor shows a lot and the board turns off.

[The-going]

M4 Zero

Is the Ethernet working?

[pyavitz]

M4 Zero

Is the Ethernet working?

It uses emac1, which at this time requires some special driver and although some one recently added it to Armbian I haven't tried testing it. Doesn't even have an eth port anyway, which I'm guessing means there is a HAT you can use on it.

As for the u-boot, yes I've done all that. The issue for me, is that above U-Boot v2024.04 it won't load the Armbian kernel. It just hangs at the loading stage. If I use my own kernel, it loads fine. Not sure why, just like I haven't been able to figure out why the Bluetooth fails to load in Armbian either.

[The-going]

As for the u-boot, yes I've done all that. The issue for me, is that above U-Boot v2024.04 it won't load the Armbian kernel

I suspect that this is with the 6.6 kernel.
At the boot stage, as soon as the temperature driver is connected and starts working,
it reads a very large temperature value and shuts down the OS.

[pyavitz]

Maybe some of these patches will help?

[igorpecovnik]

You decide when this is ready. Also we need to move CURRENT to 6.12, legacy 6.6, edge 6.13 by the end of 2/2025. Any deep problems preventing this?

[The-going]

You decide when this is ready. Also we need to move CURRENT to 6.12, legacy 6.6, edge 6.13 by the end of 2/2025. Any deep problems preventing this?

We can reschedule it at any time.
I would like to do this soon.
But I think it's better to fix it first:

• The 6.6 core works well, except for the temperature sensors for h6-h618, and temperature control is not possible for them.

• In the 6.12 kernel, for some reason, HDMI does not work for arm64.

• There are several patches in the 6.12 kernel that add drivers from legacy kernels.
  It seems to me that there are problems there.

• In the 6.13 kernel, which all the patches have moved to, I have already started making some changes.
  But they need to be tested. Therefore, I am first adding support for a device with an h618 processor.

What should I do first?
Probably something that will turn out faster.
I will inform you additionally when it will be possible to safely combine pull requests.

[igorpecovnik]

What should I do first?

Kernel 6.12 should be main priority, 6.13 slow.

[The-going]

It's been a long time since I've read so much primary documentation.
I saw some inconsistency with the user manual of the h616 processor.
This applies to syscon and ethernet nodes.

@TheSnowfield @chraac @JohnTheCoolingFan
Please tell me, does Ethernet work for your devices on this 6.12 kernel?
No changes to this pull request.

[JohnTheCoolingFan]

Please tell me, does Ethernet work for your devices on this 6.12 kernel?

Tried this branch on bigtreetech cb1, ethernet works as usual.