diff options
| author | Tom Rini <trini@konsulko.com> | 2024-07-22 13:48:24 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2024-07-22 13:48:24 -0600 |
| commit | cfaa58b8b7839617a74a44a8f08b94b011f8edbc (patch) | |
| tree | c95a63857d6c0cb43505def8826bbe8035bdb277 /drivers/clk | |
| parent | f1aa32d65d31c8f8a43617e724495d0aad011620 (diff) | |
| parent | f1296bfff71b0cbac2241c0d6f1a88468c5af16d (diff) | |
| download | u-boot-cfaa58b8b7839617a74a44a8f08b94b011f8edbc.tar.gz u-boot-cfaa58b8b7839617a74a44a8f08b94b011f8edbc.tar.bz2 u-boot-cfaa58b8b7839617a74a44a8f08b94b011f8edbc.zip | |
Merge patch series "Generalize PHYTEC Overlay Handling"
Daniel Schultz <d.schultz@phytec.de> says:
The overlays are specified in the bootenv.txt file that is loaded into
the environment. Then these overlays get loaded and applied via a script.
These scripts for loading and applying devicetree overlays are identical
for many phytec boards.
Create a common overlays.env that can be included.
Add support for devicetree overlays to phycore-imx8mp and include the
overlays.env for phycore-imx93.
Rename existing environment variables according to bootstd doc.
Move MMC boot logic into a common k3_mmc.env file and include the new
overlays.env file as well.
Diffstat (limited to 'drivers/clk')
0 files changed, 0 insertions, 0 deletions