On Thu, 2019-05-16 at 15:54 -0500, Andreas Dannenberg wrote:
> From: Lokesh Vutla <lokeshvu...@ti.com>
>
> In order to load the sysfw.itb from an MMC device, clocks should be
> hard
> coded to the same value as ROM configured frequency. Clock updates
> cannot
> happen at this point as SYSFW is not yet available. So updating the
> clock
> properties for MMC nodes.
>
> Furthermore, create a new node for the FS loader framework which we
> want
> to use to load the actual firmware file from the boot media.
>
> Signed-off-by: Andreas Dannenberg <dannenb...@ti.com>
> ---
> arch/arm/dts/k3-am654-r5-base-board.dts | 24
> ++++++++++++++++++++++++
> 1 file changed, 24 insertions(+)
>
> diff --git a/arch/arm/dts/k3-am654-r5-base-board.dts
> b/arch/arm/dts/k3-am654-r5-base-board.dts
> index a07038be70..75880158a2 100644
> --- a/arch/arm/dts/k3-am654-r5-base-board.dts
> +++ b/arch/arm/dts/k3-am654-r5-base-board.dts
> @@ -22,6 +22,12 @@
> chosen {
> stdout-path = "serial2:115200n8";
> tick-timer = &timer1;
> + firmware-loader = &fs_loader0;
> + };
> +
> + fs_loader0: fs_loader@0 {
> + u-boot,dm-pre-reloc;
> + compatible = "u-boot,fs-loader";
Why not using phandlepart = <&mmc 1>, this would help to avoid mmc init
duplication in a few places such as patch [05/11].
> };
>
> aliases {
> @@ -96,6 +102,12 @@
> u-boot,dm-spl;
> };
>
> + clk_200mhz: dummy_clock {
> + compatible = "fixed-clock";
> + #clock-cells = <0>;
> + clock-frequency = <200000000>;
> + u-boot,dm-spl;
> + };
> };
>
> &dmsc {
> @@ -137,3 +149,15 @@
> pinctrl-names = "default";
> pinctrl-0 = <&wkup_vtt_pins_default>;
> };
> +
> +&sdhci0 {
> + clock-names = "clk_xin";
> + clocks = <&clk_200mhz>;
> + /delete-property/ power-domains;
> +};
> +
> +&sdhci1 {
> + clock-names = "clk_xin";
> + clocks = <&clk_200mhz>;
> + /delete-property/ power-domains;
> +};
_______________________________________________
U-Boot mailing list
U-Boot@lists.denx.de
https://lists.denx.de/listinfo/u-boot
