fix: add some patch to repair eMMC startup issues

[CodeChenL]

Description

The main content is to modify the frequency of the SDIO and reset when the start failure is added to the uboot to repair a series of compatibility issues of Samsung eMMC, such as: the launch failure and IO error

uboot boot failure issue: https://forum.radxa.com/t/rzero-autoboot-from-emmc/24764

io error issue：

root@radxa-zero:~# sudo /usr/sbin/cryptsetup luksFormat --type luks2 --batch-mode /dev/mmcblk1
Enter passphrase for /dev/mmcblk1: 
Device wipe error, offset 32768.
Cannot wipe header on device /dev/mmcblk1.
root@radxa-zero:~# sudo dmesg | grep blk
......
[ 1546.780637] I/O error, dev mmcblk1, sector 64 op 0x1:(WRITE) flags 0xc800 phys_seg 64 prio class 0
[ 1546.781847] I/O error, dev mmcblk1, sector 575 op 0x1:(WRITE) flags 0xc800 phys_seg 65 prio class 0
[ 1546.782272] I/O error, dev mmcblk1, sector 1086 op 0x1:(WRITE) flags 0xc800 phys_seg 65 prio class 0
[ 1546.784501] I/O error, dev mmcblk1, sector 1597 op 0x1:(WRITE) flags 0xc800 phys_seg 65 prio class 0

How Has This Been Tested?

• Performed 200 reboot tests, all rebooted successfully
• Use echo -n "rock" | /usr/sbin/cryptsetup luksFormat --type luks2 --batch-mode /dev/{emmc_blk} pressing eMMC for 48 hours, the kernel is not reported to IO Error

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

[SteeManMI]

I see that you are only patching the 6.6 current kernel. Does this issue not exist in the 6.12 edge kernel, which will likely become the new current version soon.

[CodeChenL]

I see that you are only patching the 6.6 current kernel. Does this issue not exist in the 6.12 edge kernel, which will likely become the new current version soon.

I will test it

[CodeChenL]

I see that you are only patching the 6.6 current kernel. Does this issue not exist in the 6.12 edge kernel, which will likely become the new current version soon.

There are also this problem after testing the edge kernel, and it also can be repaired through this patch