[PATCH] ARM: stm32: Use firwmare property instead of loadables

There shouldn't be a need to use loadables propertyn because u-boot can be pointed by firmware property. This change should also speedup boot process because loadables property is list of strings which code is going through. On the other hand firmware can just point to one image.
Signed-off-by: Michal Simek michal.simek@xilinx.com ---
Only done based on grepping the code. Please retest. --- board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its b/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its index 905be57dffd7..dfe89bfad67e 100644 --- a/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its +++ b/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its @@ -39,28 +39,28 @@ config-1 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-pdk2_somrev0_boardrev0"; - loadables = "uboot"; + firmware = "uboot"; fdt = "fdt-1"; };
config-2 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-pdk2_somrev1_boardrev0"; - loadables = "uboot"; + firmware = "uboot"; fdt = "fdt-1"; };
config-3 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-drc02_somrev0_boardrev0"; - loadables = "uboot"; + firmware = "uboot"; fdt = "fdt-2"; };
config-4 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-drc02_somrev1_boardrev0"; - loadables = "uboot"; + firmware = "uboot"; fdt = "fdt-2"; };

Hi,
On 07. 09. 20 10:35, Michal Simek wrote:
There shouldn't be a need to use loadables propertyn because u-boot can be pointed by firmware property. This change should also speedup boot process because loadables property is list of strings which code is going through. On the other hand firmware can just point to one image.
Signed-off-by: Michal Simek michal.simek@xilinx.com
Only done based on grepping the code. Please retest.
board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its b/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its index 905be57dffd7..dfe89bfad67e 100644 --- a/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its +++ b/board/dhelectronics/dh_stm32mp1/u-boot-dhcom.its @@ -39,28 +39,28 @@ config-1 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-pdk2_somrev0_boardrev0";
loadables = "uboot";
firmware = "uboot"; fdt = "fdt-1";
};
config-2 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-pdk2_somrev1_boardrev0";
loadables = "uboot";
firmware = "uboot"; fdt = "fdt-1";
};
config-3 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-drc02_somrev0_boardrev0";
loadables = "uboot";
firmware = "uboot"; fdt = "fdt-2";
};
config-4 { /* DT+SoM+board model */ description = "dh,stm32mp15xx-dhcom-drc02_somrev1_boardrev0";
loadables = "uboot";
};firmware = "uboot"; fdt = "fdt-2";
Marek: I see there is also dhcor which has the same issue. Will send v2 when someone confirms that this works properly.
Thanks, Michal
participants (1)
-
Michal Simek