aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* cyclic: doc: Update documentation for CONFIG_CYCLIC_MAX_CPU_TIME_USWeizhao Ouyang2023-10-121-5/+5
| | | | | | | | | | | Cyclic now just print a warning once instead of disabling the cyclic function when the cyclic function upon exceeding CPU time usage. Fixes: ddc8d36a7455 ("cyclic: Don't disable cylic function upon exceeding CPU time") Signed-off-by: Weizhao Ouyang <o451686892@gmail.com> Rephrase the paragraph. Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
* sphinx: Bump urllib3 versionTom Rini2023-10-121-1/+1
| | | | | | | | | | | | While not a direct issue for us, urllib3 before 1.26.17 is vulnerable to CVE-2023-43804 to bump our version up. Reported-by: GitHub dependabot Signed-off-by: Tom Rini <trini@konsulko.com> Reviewed-by: Simon Glass <sjg@chromium.org> Use urllib3 2.0.6 Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
* Merge branch '2023-10-11-port-gen_compile_commands_py'Tom Rini2023-10-116-0/+330
|\ | | | | | | | | | | | | | | | | | | | | To quote the author: I'm submitting a patch series that ports the gen_compile_commands.py script from the Linux kernel's sources to U-Boot. This script, originally located in scripts/clang-tools/gen_compile_commands.py, enables the generation of compile_commands.json file for improved code navigation and analysis. The series consists of the initial script import, the necessary modifications for U-Boot compatibility, and finally some documentation.
| * scripts/gen_compile_commands: fix usage messageJoao Marcos Costa2023-10-111-2/+2
| | | | | | | | | | | | | | Replace mentions to 'kernel' by 'U-Boot' to avoid confusion. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * doc: add ide_integration.rst to doc/developJoao Marcos Costa2023-10-112-0/+13
| | | | | | | | | | | | | | | | | | | | | | Add 'Integration with IDEs' chapter. For now, this chapter is mostly a reference to the documentation of gen_compile_commands, in doc/build, but it can be futurely used as a guide for other IDE-friendly features. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * doc: add documentation for gen_compile_commands.pyJoao Marcos Costa2023-10-113-0/+85
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This documentation briefly explains what is a compilation database, and how to use the script to generate one. This is not a portage, as there was no original documentation in the Linux sources. Acknowledge the documentation in the script's header and in doc/build index. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * .gitignore: add compile_commands.jsonJoao Marcos Costa2023-10-111-0/+3
| | | | | | | | | | | | | | | | Add Clang's compilation database file (i.e. compile_commands.json) to .gitignore, at the root of the repository. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * scripts/gen_compile_commands.py: add acknowledgmentsJoao Marcos Costa2023-10-111-0/+1
| | | | | | | | | | | | | | | | | | Add acknowledgments for porting and modifying the script. Of course, the license, author, and copyright notice remain the same as in the original script. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * scripts/gen_compile_commands.py: fix docstringJoao Marcos Costa2023-10-111-1/+1
| | | | | | | | | | | | | | | | The referred tool is now in U-Boot. Replace "the Linux kernel" by "U-Boot" to make the docstring coherent. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * scripts/gen_compile_commands.py: adapt _LINE_PATTERNJoao Marcos Costa2023-10-111-1/+1
| | | | | | | | | | | | | | | | For U-Boot's context, the regular expression defined by _LINE_PATTERN should be adapted. Replace 'savedcmd' by 'cmd'. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
| * scripts: Port Linux's gen_compile_commands.py to U-BootJoao Marcos Costa2023-10-111-0/+228
|/ | | | | | | | | | | | | | | | This script generates a database of compiler flags, namely compile_commands.json. It is quite useful for text editors that use clangd LSP (e.g. Vim, Neovim). It was ported from Linux's sources: - tag: v6.4 - revision 6995e2de6891c724bfeb2db33d7b87775f913ad1 Modifications for U-Boot compatibility will be added in a follow-up commit. Signed-off-by: Joao Marcos Costa <jmcosta944@gmail.com> Tested-by: Joao Paulo Goncalves <joao.goncalves@toradex.com>
* configs: Resync with savedefconfigTom Rini2023-10-1115-37/+18
| | | | | | Rsync all defconfig files using moveconfig.py Signed-off-by: Tom Rini <trini@konsulko.com>
* Merge branch '2023-10-11-assorted-fixes-and-updates'Tom Rini2023-10-1172-543/+724
|\ | | | | | | | | | | - Assorted TI K3 updates, use ".dtso" for device tree overlays to match general usage, mkimage fixes/improvements, assorted platform updates/fixes, other assorted driver/platform fixes.
| * configs: Make TI_SECURE_DEVICE default for K3Andrew Davis2023-10-1114-12/+2
| | | | | | | | | | | | | | | | | | | | | | | | All K3 boards now are secure by default, instead of setting this in each defconfig, make it implied by the ARCH config. The only exception is IOT2050, which I do not believe will have any problems with being a TI_SECURE_DEVICE, but for now turn it off to keep its config the same. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com>
| * configs: am65x: Merge the HS and non-HS defconfigsAndrew Davis2023-10-117-296/+5
| | | | | | | | | | | | | | | | | | | | | | K3 devices have runtime type board detection. Make the default defconfig include the secure configuration. Then remove the HS specific config. Non-HS devices will continue to boot due to runtime device type detection. Signed-off-by: Andrew Davis <afd@ti.com> Tested-by: Tom Rini <trini@konsulko.com> Reviewed-by: Manorit Chawdhry <m-chawdhry@ti.com>
| * ARM: psci: move GIC address override to KconfigAndre Przywara2023-10-114-7/+14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As the code to switch an ARM core from secure to the non-secure state needs to know the base address of the Generic Interrupt Controller (GIC), we read an Arm Cortex defined system register that is supposed to hold that base address. However there are SoCs out there that get this wrong, and this CBAR register either reads as 0 or points to the wrong address. To accommodate those systems, so far we use a macro defined in some platform specific header files, for affected boards. To simplify future extensions, replace that macro with a Kconfig variable that holds this override address, and define a default value for SoCs that need it. Signed-off-by: Andre Przywara <andre.przywara@arm.com> Reviewed-by: Sam Edwards <CFSworks@gmail.com>
| * misc: fs_loader: Fix alignment of fs_loader driverSean Anderson2023-10-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | DM_DRIVER_GET will redeclare the fs_loader driver without the correct alignment. This causes GCC to use the default section alignment of 32 bytes. This in turn creates a gap in the linker list due to the padding required to achieve the correct alignment, corrupting all further entries. Use DM_DRIVER_REF instead, which doesn't redeclare anything. Fixes: 0998a20cfc6 ("misc: fs_loader: Add function to get the chosen loader") Signed-off-by: Sean Anderson <seanga2@gmail.com>
| * mkimage: update man page and -h outputRasmus Villemoes2023-10-112-3/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The man page correctly said that -B was ignored without -E, while the `mkimage -h` output suggested otherwise. Now that -B can actually be used by itself, update the man page. While at it, also amend the `mkimage -h` line to mention the connection with -E. The FDT header is a fixed 40 bytes, so its size cannot (and is not) modified, while its alignment is a property of the address in RAM one loads the FIT to, so not something mkimage can affect in any way. (In the file itself, the header is of course at offset 0, which has all possible alignments already.) Reported-by: Sean Anderson <seanga2@gmail.com> Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by: Simon Glass <sjg@chromium.org>
| * doc: use .dtso as extension for device tree overlay sourcesRasmus Villemoes2023-10-112-4/+4
| | | | | | | | | | | | | | | | Moving towards using .dtso for overlay sources, update the documentation examples to follow that pattern. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by: Simon Glass <sjg@chromium.org>
| * sandbox: rename overlay sources to .dtsoRasmus Villemoes2023-10-112-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso. Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by: Simon Glass <sjg@chromium.org>
| * arm64: zynqmp: rename overlay sources to .dtsoRasmus Villemoes2023-10-114-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso. Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * iot2050: rename overlay sources to .dtsoRasmus Villemoes2023-10-112-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso. Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by: Jan Kiszka <jan.kiszka@siemens.com>
| * arm: dts: imx8mm-cl-iot-gate: rename overlay sources to .dtsoRasmus Villemoes2023-10-117-0/+0
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Distinguish more clearly between source files meant for producing .dtb from those meant for producing .dtbo. No functional change, as we currently have rules for producing a foo.dtbo from either foo.dts or foo.dtso. Note that in the linux tree, all device tree overlay sources have been renamed to .dtso, and the .dts->.dtbo rule is gone since v6.5 (commit 81d362732bac). So this is also a step towards staying closer to linux with respect to both Kbuild and device tree sources. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
| * arm: apple: Add initial Apple M2 Ultra supportJanne Grunau2023-10-111-0/+183
| | | | | | | | | | | | | | | | | | Apple's M2 Ultra SoC are somewhat similar to the M1 Ultra but needs a tweaked memory map as the M2 Pro/Max SoCs. USB, NVMe, UART, WDT and PCIe are working with the existing drivers. Signed-off-by: Janne Grunau <j@jannau.net> Reviewed-by: Mark Kettenis <kettenis@openbsd.org>
| * event: Rename rest of EVENT_SPY to EVENT_SPY_FULL or EVENT_SPY*Marek Vasut2023-10-112-4/+4
| | | | | | | | | | | | | | | | Fix up remaining occurances of EVENT_SPY with no suffix. Fixes: 6c4cad7438 ("event: Rename EVENT_SPY to EVENT_SPY_FULL") Signed-off-by: Marek Vasut <marek.vasut+renesas@mailbox.org> Reviewed-by: Simon Glass <sjg@chromium.org>
| * env: Improve ENV_OFFSET help messagePaul Barker2023-10-111-1/+11
| | | | | | | | | | | | | | | | | | | | When reading Kconfig help messages to understand ENV_OFFSET and ENV_OFFSET_REDUND, developers may not realise that they need to also look at the chosen ENV_IS_IN_* options to see how the offsets will be interpreted. Signed-off-by: Paul Barker <paul.barker.ct@bp.renesas.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * driver: rng: Add DM_RNG interface for ARMv8.5 RNDR registersAndre Przywara2023-10-114-0/+90
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ARMv8.5 architecture extension defines architectural RNDR/RNDRRS system registers, that provide 64 bits worth of randomness on every read. Since it's an extension, and implementing it is optional, there is a field in the ID_AA64ISAR0_EL1 ID register to query the availability of those registers. Add a UCLASS_RNG driver that returns entropy via repeated reads from those system registers, if the extension is implemented. The driver always binds, but checks the availability in the probe() routine. This helps systems which suffer from low boot entropy, since U-Boot can provide entropy via the generic UEFI entropy gathering protocol to the OS, at an early stage. Signed-off-by: Andre Przywara <andre.przywara@arm.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * tools: ensure zeroed padding in external FIT imagesRoman Azarenko2023-10-111-3/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Padding the header of an external FIT image is achieved by truncating the existing temporary FIT file to match the required alignment before appending image data. Reusing an existing file this way means that the padding will likely contain a portion of the original data not overwritten by the new header. Zero out any data past the end of the new header, and stop at either the end of the desired padding, or the end of the old FIT file, whichever comes first. Fixes: 7946a814a319 ("Revert "mkimage: fit: Do not tail-pad fitImage with external data"") Signed-off-by: Roman Azarenko <roman.azarenko@iopsys.eu> Reviewed-by: Simon Glass <sjg@chromium.org>
| * bootstd: Drop some TODOsSimon Glass2023-10-111-3/+1
| | | | | | | | | | | | | | The existing TODOs are done, so remove them. Add another that came up today. Signed-off-by: Simon Glass <sjg@chromium.org>
| * arm: dts: k3-am625-verdin: fix bootMarcel Ziswiler2023-10-111-36/+36
| | | | | | | | | | | | | | | | | | | | A53 U-Boot proper got broken because nodes marked as 'bootph-pre-ram' are no longer available in U-Boot proper before relocation. Fix this by marking all nodes in u-boot.dtsi as 'bootph-all'. Fixes: 9e644284ab812 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation") Signed-off-by: Marcel Ziswiler <marcel.ziswiler@toradex.com>
| * malloc: Enable assertions if UNIT_TEST is enabledSean Anderson2023-10-111-4/+4
| | | | | | | | | | | | | | | | | | | | dlmalloc has some sanity checks it performs on free() which can help detect memory corruption. However, they are only enabled if DEBUG is defined before including common.h. Define DEBUG earlier if UNIT_TEST is enabled so that assertions are enabled in sandbox. Signed-off-by: Sean Anderson <seanga2@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * arm: dts: k3-j721e-sk/common-proc-board: Fix bootNishanth Menon2023-10-112-76/+76
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 9e644284ab81 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation") A53 u-boot proper is broken. This is because nodes marked as 'bootph-pre-ram' are not available at u-boot proper before relocation. To fix this we mark all nodes in u-boot.dtsi as 'bootph-all'. Fixes: 69b19ca67bcb ("arm: dts: k3-j721e: Sync with v6.6-rc1") Cc: Neha Francis <n-francis@ti.com> Signed-off-by: Nishanth Menon <nm@ti.com> Tested-by: Tom Rini <trini@konsulko.com> # J721E-EVM GP Tested-by: Neha Malcom Francis <n-francis@ti.com> Reviewed-by: Roger Quadros <rogerq@kernel.org>
| * arm: mach-k3: Remove secure device makefileAndrew Davis2023-10-112-45/+0
| | | | | | | | | | | | | | | | This is now done using binman but this file was leftover and is now unused, remove it. Signed-off-by: Andrew Davis <afd@ti.com> Reviewed-by: Neha Malcom Francis <n-francis@ti.com>
| * board: siemens: iot2050: Fix logical bug in PG1/PG2 detectionJan Kiszka2023-10-111-1/+1
| | | | | | | | | | | | | | | | This caused the wrong fdtfile to be set and was failing to apply M.2 settings. Fixes: badaa1f6a7a9 ("boards: siemens: iot2050: Unify PG1 and PG2/M.2 configurations again") Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
| * arm: dts: k3-am65-iot2050: Fix bootJan Kiszka2023-10-111-22/+22
| | | | | | | | | | | | | | | | | | | | | | | | | | Since commit 9e644284ab812 ("dm: core: Report bootph-pre-ram/sram node as pre-reloc after relocation") A53 u-boot proper is broken. This is because nodes marked as 'bootph-pre-ram' are not available at u-boot proper before relocation. To fix this we mark all nodes in u-boot.dtsi as 'bootph-all'. Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com> Reviewed-by: Roger Quadros <rogerq@kernel.org> Reviewed-by: Nishanth Menon <nm@ti.com>
| * spi: mtk_spim: prevent global pll clock overrideNicolò Veronese2023-10-111-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | With commit 793e62301180 ("spi: mtk_spim: get spi clk rate only once") a new system to calculate the SPI clocks has been added. Unfortunately, the do_div macro overrides the global priv->pll_clk_rate field. This will cause to have a reduced clock rate on each subsequent SPI call. Signed-off-by: Valerio 'ftp21' Mancini <ftp21@ftp21.eu> Signed-off-by: Nicolò Veronese <nicveronese@gmail.com>
| * Makefile: make u-boot-initial-env target depend explicitly on scripts_basicRasmus Villemoes2023-10-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | We're seeing sporadic errors like ENVC include/generated/env.txt HOSTCC scripts/basic/fixdep ENVP include/generated/env.in ENVT include/generated/environment.h HOSTCC tools/printinitialenv /bin/sh: 1: scripts/basic/fixdep: not found make[1]: *** [scripts/Makefile.host:95: tools/printinitialenv] Error 127 make[1]: *** Deleting file 'tools/printinitialenv' make: *** [Makefile:2446: u-boot-initial-env] Error 2 make: *** Waiting for unfinished jobs.... where sometimes the "fixdep: not found" is instead "fixdep: Permission denied" and the Error 127 becomes 126. This smells like a race condition, and indeed it is: Currently, u-boot-initial-env is a prerequisite of the envtools target, which also lists scripts_basic as a prerequisite: envtools: u-boot-initial-env scripts_basic $(version_h) $(timestamp_h) tools/version.h $(Q)$(MAKE) $(build)=tools/env However, the u-boot-initial-env rule involves building the printinitialenv helper, which in turn is built using an if_changed_dep rule. That means we must ensure scripts/basic/fixdep is built and ready before trying to build printinitialenv, i.e. the u-boot-initial-env rule itself must depend on the phony scripts_basic target. Signed-off-by: Rasmus Villemoes <rasmus.villemoes@prevas.dk> Reviewed-by: Simon Glass <sjg@chromium.org>
| * board: xen: introduce virtio-blk supportAndrii Chepurnyi2023-10-115-3/+181
| | | | | | | | | | | | | | | | | | | | | | | | Added new xenguest_arm64_virtio_defconfig which enables support for virtio-blk using various types of transport like virtio-pci, vrtio-mmio. Currently supported: up to 2 PCI host bridges and 10 MMIO devices. Note: DT parsing code was partly taken from pci-uclass.c Limitation: All memory regions should be below 4GB address space. Signed-off-by: Andrii Chepurnyi <andrii_chepurnyi@epam.com>
| * board: synquacer: set actual gd->ram_top and gd->ram_sizeMasahisa Kojima2023-10-111-1/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Current gd->ram_size and gd->ram_top reflect only the first DRAM bank even if the SynQuacer Developerbox could have up to three DRAM banks. With the commit 06d514d77c37 ("lmb: consider EFI memory map"), the first DRAM bank indicates <4GB address, so whole >4GB memory is marked as EFI_BOOT_SERVICES_DATA and it results that U-Boot can not access >4GB memory. Since 64-bits DRAM address is fully available on the SynQuacer Developerbox, let's set the installed DIMM information to gd->ram_top and gd->ram_size. Signed-off-by: Masahisa Kojima <masahisa.kojima@linaro.org> Acked-by: Jassi Brar <jaswinder.singh@linaro.org>
| * input: avoid NULL dereferenceHeinrich Schuchardt2023-10-111-10/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before using the result of env_get("stdin") we must check if it is NULL. Avoid #if. This resolves the -Wunused-but-set-variable issue and we don't need a dummy assignment in the else branch. Anyway this warning is disabled in the Makefile. For sake of readability use an early return after the configuration check. Checking CONFIG_SPL_BUILD is incorrect as env_get() is only defined if CONFIG_$(SPL_TPL)ENV_SUPPORT=y. Fixes: 985ca3945fa3 ("spl: input: Allow input in SPL and TPL") Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by: Simon Glass <sjg@chromium.org> Reviewed-by: Tom Rini <trini@konsulko.com>
| * mkimage: allow internalization of data-positionLars Feyaerts2023-10-112-5/+40
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Make it possible for data that was externalized using a static external position (-p) to be internalized. Enables the ability to convert existing FIT images built with -p to be converted to a FIT image where the data is internal, to be converted to a FIT image where the data is external relative to the end of the FIT (-E) or change the initial static external position to a different static external position (-p). Removing the original external-data-related properties ensures that they're not present after conversion. Without this, they would still be present in the resulting FIT even if the FIT has been, for example, internalized. Signed-off-by: Lars Feyaerts <lars@bitbiz.be> Reviewed-by: Simon Glass <sjg@chromium.org>
| * checkpatch: skip fdtdec_* check for toolsLars Feyaerts2023-10-111-2/+2
|/ | | | | | | | Have checkpatch.pl skip warnings for use of fdtdec_* functions in ooling; livetree isn't used there. Signed-off-by: Lars Feyaerts <lars@bitbiz.be> Reviewed-by: Simon Glass <sjg@chromium.org>
* Merge tag 'fsl-qoirq-2023-10-10' of ↵Tom Rini2023-10-1186-6098/+130
|\ | | | | | | | | | | | | | | https://source.denx.de/u-boot/custodians/u-boot-fsl-qoriq Drop legacy PPA secure FW support support for MC reserved memory reset the FLSHxCR1 registers for nxp_fspi
| * spi: nxp_fspi: reset the FLSHxCR1 registersHan Xu2023-10-101-0/+7
| | | | | | | | | | | | | | | | Reset the FLSHxCR1 registers to default value. ROM may set the register value and it affects the SPI NAND normal functions. Signed-off-by: Han Xu <han.xu@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * board: freescale: ls1088a: declare MC reserved regionsLaurentiu Tudor2023-10-101-0/+1
| | | | | | | | | | | | | | Populate the device tree with the MC reserved memory regions. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * board: freescale: ls2080a: declare MC reserved regionsLaurentiu Tudor2023-10-102-0/+2
| | | | | | | | | | | | | | Populate the device tree with the MC reserved memory regions. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * drivers: net: fsl-mc: add support for MC reserved memoryLaurentiu Tudor2023-10-103-0/+112
| | | | | | | | | | | | | | | | | | | | | | | | Add support for declaring in device tree the reserved memory ranges required for MC. Since the MC firmware acts as any DMA master present in the SoC, the reserved memory ranges need also be identity mapped in the SMMU, so create the required 'iommu-addresses' property in the reserved memory nodes. For now this support is used only on LX2160A SoCs. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * armv8: fsl-layerscape: make some functions staticLaurentiu Tudor2023-10-101-6/+6
| | | | | | | | | | | | | | Some functions are not used outside this file, so make them static. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * fsl-layerscape: drop obsolete PPA secure firmware supportLaurentiu Tudor2023-10-1031-627/+2
| | | | | | | | | | | | | | | | | | PPA was a secure firmware developed in-house which is no longer supported and replaced by TF-A quite some years ago. Drop support for it. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> Signed-off-by: Peng Fan <peng.fan@nxp.com>
| * configs: layerscape: delete defconfigs using legacy PPA secure FWLaurentiu Tudor2023-10-1050-5465/+0
| | | | | | | | | | | | | | | | | | | | PPA was a secure firmware developed in-house which is no longer supported and replaced by TF-A quite some years ago. This makes the defconfigs that make use of PPA obsolete, so remove them. Signed-off-by: Laurentiu Tudor <laurentiu.tudor@nxp.com> [Merged part 1 and part 2] Signed-off-by: Peng Fan <peng.fan@nxp.com>