- Oct 11, 2024
-
-
Move this section to rst, changing it just enough so that it builds. Signed-off-by:Simon Glass <sjg@chromium.org>
-
This should not be in the generic README file, so drop it. Signed-off-by: -
Update the various references to SPL in this document. Make sure to refer to 'phases' instead of 'stages', which is not a U-Boot term. Fix a few U-boot typos and try to improve grammar a little while we are here. Signed-off-by: -
This should now refer to xPL rather than SPL, so update it throughout the tree. Signed-off-by: -
Use simpler names for these functions. Signed-off-by: -
Rename this to use the xpl prefix. Signed-off-by: -
Add the opposite function to not_xpl() for completeness. Signed-off-by: -
Give this function a slightly easier name. Signed-off-by: -
Rename this function to indicate that it refers to any xPL phase. Signed-off-by: -
This name fits better with the new naming scheme, so update it. Signed-off-by: -
This is a better name for this function, so update it. Tidy up the function comment to mention VPL. Signed-off-by: -
This now appears in the code base, so add it to the list of ignored symbols in qconfig Signed-off-by: -
The new name 'xPL' is intended to indicate a build of any phase which is not U-Boot proper. Define it for all such phases. Note that we also define CONFIG_SPL_BUILD for all xPL builds. This preserves existing behaviour, but future patches will adjust that. Signed-off-by: -
Now that the conversion of all CONFIG options to Kconfig is complete, these files only contain the xPL_BUILD defines. Add a comment to make this clear. Signed-off-by: -
Rename this file to indicate that it refers to any non-U-Boot-proper phase, not just SPL, which is the phase immediately before U-Boot proper. Signed-off-by: -
This is always enabled for U-Boot proper, so simplify the condition in the common Makefile. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
This is always enabled for U-Boot proper, so simplify the condition in the common Makefile. Signed-off-by: -
SPL_BUILD is not a Kconfig symbol. Perhaps the intent here is to use SPL instead. However, this causes build errors, e.g. with T1024RDB_NAND So drop the dependency on !SPL_BUILD since it does nothing. Signed-off-by: -
SPL_BUILD is not a Kconfig symbol so perhaps the intent here is to use SPL instead. But that changes the output size. So drop the dependency on !SPL_BUILD since it does nothing. Signed-off-by: -
Use the normal SPL_TPL_ approach for this option. Signed-off-by:
-
Create this file for VPL as well, for consistency. Signed-off-by:
-
- Sep 20, 2024
-
-
Padmarao Begari authored
U-Boot is not picking boot.scr script address from device tree rather it's using default address for Microblaze platform, and it's picking for other platforms. Remove conditional check for Microblaze platform, so that u-boot pick up boot.scr script address for all platforms from device tree. Signed-off-by:
Padmarao Begari <padmarao.begari@amd.com> Link: https://lore.kernel.org/r/20240913093231.2343528-1-padmarao.begari@amd.com Signed-off-by:
Michal Simek <michal.simek@amd.com>
-
Padmarao Begari authored
There are lot of device_is_compatible() present in the driver. Remove them and replace with a variables "SDHCI_COMPATIBLE_SDHCI_89A" and "SDHCI_COMPATIBLE_VERSAL_NET_EMMC" with match data. This change saves the space and reduce the execution time. Signed-off-by:
-
Prasad Kummari authored
Remove device tree overlay (DTBO) entries for the ZynqMP target from the Makefile. Add new device tree binaries (DTBs) for the zynqmp-sm-k24-revA and zynqmp-smk-k24-revA configurations. Signed-off-by:
Prasad Kummari <prasad.kummari@amd.com> Signed-off-by:
-
Prasad Kummari authored
Linux commits: 15d16d6dadf6 kbuild: Add generic rule to apply fdtoverlay 44f87191d105 kbuild: parameterize the .o part of suffix-search The Linux commit 15d16d6dadf6 adds a generic rule in Makefile.lib to automatically apply fdtoverlay, so that each platform doesn't need to include a complex rule. This also automatically appends DTC_FLAGS_foo_base += -@ to all base files The platform's Makefile only needs to have this now: foo-dtbs := foo_base.dtb foo_overlay1.dtbo foo_overlay2.dtbo dtb-y := foo.dtb Signed-off-by:
-
Michal Simek authored
Add missing vc7_xin fixed clock as clock input for some clock generators. Signed-off-by:
-
Sean Anderson authored
Set NIDEN, enabling non-invasive debug for the CCI-400 PMU. Otherwise, the PMU is effectively disabled. Signed-off-by:
Sean Anderson <sean.anderson@linux.dev> Reviewed-by:
-
Sean Anderson authored
Boot devices (QSPI, MMC, NAND, and Ethernet) use secure access for DMA by default. As this causes problems when using the SMMU [1], configure them for normal access instead. [1] https://support.xilinx.com/s/article/72164 Signed-off-by:
-
Michal Simek authored
Enable simple-pm-bus driver to handle case where axi bus coming between PS (fixed) part to PL (programmable) part has own clock or power domain. That's why enable driver to be ready for this configuration. Signed-off-by:
-
Prasad Kummari authored
To boot into the firmware recovery tool, the user currently needs to press a button on the board while powering the system up. To simplify this process, a U-Boot command was added to allow booting directly into the recovery tool. For example: ZynqMP> zynqmp reboot <multiboot offset in hex> Co-develop-by:
-
Prasad Kummari authored
Included the SPI header to resolve the no previous prototypes for function. Removed unused mode variable. sparse warnings warning: no previous prototype for 'spi_get_env_dev' [-Wmissing-prototypes] warning: variable 'mode' set but not used [-Wunused-but-set-variable] Signed-off-by:
-
- Sep 19, 2024
-
-
This patch fixes timeout issues seen on large NOR flash. For full-chip erase, where we use the SPINOR_OP_CHIP_ERASE (0xc7) opcode. Use a different timeout for full-chip erase than for other commands. [Ported from Linux kernel commit 09b6a377687b ("mtd: spi-nor: scale up timeout for full-chip erase") ] Signed-off-by:Venkatesh Yadav Abbarapu <venkatesh.abbarapu@amd.com>
-
Tom Rini authored
Merge tag 'u-boot-imx-next-20240919' of https://gitlab.denx.de/u-boot/custodians/u-boot-imx into next CI: https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/22363 - Several updates to i.MX9 SOC and i.MX93 EVK. - Power domain fixes. - TRDC cleanup and update. - MAC address layout update. - Add support for the i.MX9301/9302 variants. - Add runtime detection of voltage mode. - Generalize some code for i.MX8M and i.MX9. - Add support for Comvetia imx6q-lxr board.
-
https://source.denx.de/u-boot/custodians/u-boot-tpmTom Rini authored
This PR contains various improvements in the A/B update logic for EFI - Read both copies of metadata, in case one of the is corrupted - Check the metadata version against the running firmware to make sure it's allowed - Limit the use of a revert capsule if the board is on a trial state and make sure it's not applied if the max counter has expired
-
When dealing with processing of the empty capsule, the capsule gets applied only when the checks for the empty capsule pass. Print a message to highlight if empty capsule checks fail, and return an error value, similar to the normal capsules. Signed-off-by:
Sughosh Ganu <sughosh.ganu@linaro.org> Tested-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org>
-
When in Trial State, the platform keeps a count of the number of times it has booted in the Trial State. Once the threshold of the maximum allowed count exceeds, the platform reverts to boot from a different bank on subsequent boot, thus coming out of the Trial State. It is expected that all the updated images would be accepted or rejected while the platform is in Trial State. Put in checks so that it is not possible to apply an empty capsule once the max Trial Count exceeds. Signed-off-by:
-
The FWU code supports both versions of the FWU metadata, i.e. v1 and v2. A platform can then select one of the two versions through a config symbol. Put a dependency in the FWU metadata version selection config symbol to ensure that both versions of the metadata cannot be enabled. Signed-off-by:
-
The platform transitions out of Trial State into the Regular State only when all the images in the update bank have been accepted. Check for this condition before transitioning out of Trial State. Signed-off-by:
-
Do a sanity check that the version of the FWU metadata that has been read aligns with the version enabled in the image. This allows to indicate an early failure as part of the FWU module initialisation. Signed-off-by:
-
In the version 2 of the FWU metadata, the metadata is broken into two parts, a top-level structure, which provides information on the total size of the structure among other things. Try reading the primary partition first, and if that fails, try reading the secondary partition. This will help in the scenario where the primary metadata partition has been corrupted, but the secondary partition is intact. Signed-off-by:
-
