- Jul 06, 2023
-
-
As the serial devices are configured in the device tree, enable DM_SERIAL in the ls1043ardb defconfigs. Signed-off-by:
Camelia Groza <camelia.groza@nxp.com> Signed-off-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com>
-
Make sure the serial driver is initialized before relocation by tagging the serial nodes with "bootph-all". In order to keep the serial nodes in sync with their representation in the Linux dts, add these u-boot specific properties to *-u-boot.dtsi files. Signed-off-by:
Camelia Groza <camelia.groza@nxp.com> Signed-off-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com>
-
Pick up the serial node descriptions from Linux v6.3 for the ls1043ardb board and its dependencies. Including the fsl,qoriq-clockgen.h and arm-gic.h headers forces us to change the include directives to explicitly go through the C preprocessor for all boards in the ls1043a SoC family. Signed-off-by:
Camelia Groza <camelia.groza@nxp.com> Signed-off-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com>
-
- Jul 05, 2023
-
-
Tom Rini authored
Prepare v2023.07-rc6
-
- Jul 04, 2023
-
-
The regulator core can return different codes which are not considered a real error for this function. Return success in such cases. Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Patrice Chotard <patrice.chotard@foss.st.com>
-
Simplify the subsystem by renaming `dev_pdata` to just `plat`. No functional change, just trivial renaming. Suggested-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Patrice Chotard <patrice.chotard@foss.st.com>
-
Some devices share a regulator supply, when the first one will request regulator disable, the second device will have it's supply cut off before graciously shutting down. Hence there will be timeouts and other failed operations. Implement a reference counter mechanism similar with what is done in Linux, to keep track of enable and disable requests, and only disable the regulator when the last of the consumers has requested shutdown. Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Patrice Chotard <patrice.chotard@foss.st.com>
- Jul 03, 2023
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Currently, spl_end points to the __bss_end address, which is an external RAM address instead of the end of the SPL text section in the internal RAM. This causes boot failures on imx6-colibri, for example: ``` Trying to boot from MMC1 SPL: Image overlaps SPL resetting ... ``` Fix this problem by assigning spl_end to _image_binary_end, as this symbol properly represents the end of the SPL text section. From u-boot-spl.map: .end *(.__end) 0x00000000009121a4 _image_binary_end = . Fixes: 77aed22b ("spl: spl_legacy: Add extra address checks") Reported-by:
Francesco Dolcini <francesco.dolcini@toradex.com> Signed-off-by:
Fabio Estevam <festevam@denx.de> Tested-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Marek Vasut <marex@denx.de> Tested-by: Marek Vasut <marex@denx.de> # DH i.MX6Q DHCOM PDK2
-
Pass _image_binary_end to make a standard way to indicate the end of the text section in SPL. The motivation for this is to have a uniform way to handle the SPL boundary checks. Signed-off-by:
Fabio Estevam <festevam@denx.de> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Pass _image_binary_end to make a standard way to indicate the end of the text section in SPL. The motivation for this is to have a uniform way to handle the SPL boundary checks. Signed-off-by:
Fabio Estevam <festevam@denx.de> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Fix two occurrences where 'signing' is misspelled. Signed-off-by:
Fabio Estevam <festevam@denx.de> Reviewed-by:
Tim Harvey <tharvey@gateworks.com>
-
Use of CONFIG_SPL_FIT_SIGNATURE=y cause CONFIG_LEGACY_IMAGE_FORMAT=n as default, this prevent boot scripts in legacy image format from working and was an unintended change in the listed fixes commits: Wrong image format for "source" command Add CONFIG_LEGACY_IMAGE_FORMAT=y to defconfig for affected boards to restore support for boot scripts in legacy image format. Fixes: 3bf8e408 ("board: rockchip: add Radxa ROCK5B Rk3588 board") Fixes: cf777572 ("rockchip: rockpro64: Use SDMA to boost eMMC performance") Fixes: 6e2b8344 ("rockchip: rock-pi-4: Use SDMA to boost eMMC performance") Fixes: 1bf49d5a ("rockchip: rk3566-radxa-cm3-io: Update defconfig") Fixes: 703c170b ("rockchip: rk3568-evb: Update defconfig") Fixes: 68000f75 ("rockchip: rk3568-rock-3a: Update defconfig") Fixes: 6fb02589 ("rockchip: rk3588-evb: Update defconfig") Signed-off-by:
Jonas Karlman <jonas@kwiboo.se>
-
- Jul 01, 2023
-
-
https://source.denx.de/u-boot/custodians/u-boot-efiTom Rini authored
Pull request efi-2023-07-rc6 Documentation: * man-pages for the loads and saves commands UEFI: * fix implementation of allow_unaligned() for armv7 and arm11
-
Rename current assembler implementation of allow_unaligned() to arm11_arch_cp15_allow_unaligned() and add it into arm11.h header, then add C wrapper of allow_unaligned(). This fixes misbehavior when linking U-Boot, where the CPU specific allow_unaligned() implementation was ignored and instead the __weak allow_unaligned() implementation from lib/efi_loader/efi_setup.c was used, which led to "data abort" just before booting Linux via tftp, in efi_dp_from_file() -> path_to_uefi() -> utf16_put() . The problem is triggerd by c7c0ca37 ("efi_loader: fix efi_dp_from_file()") . Adding the wrapper fixes the problem. Fixes: d47a7746 ("arm: arm11: allow unaligned memory access") Signed-off-by:
Marek Vasut <marex@denx.de>
-
Rename current assembler implementation of allow_unaligned() to v7_arch_cp15_allow_unaligned() and add it into armv7.h header, then add C wrapper of allow_unaligned(). This fixes misbehavior when linking U-Boot on ARMv7a i.MX6Q, where the CPU specific allow_unaligned() implementation was ignored and instead the __weak allow_unaligned() implementation from lib/efi_loader/efi_setup.c was used, which led to "data abort" just before booting Linux via tftp, in efi_dp_from_file() -> path_to_uefi() -> utf16_put() . The problem is triggerd by c7c0ca37 ("efi_loader: fix efi_dp_from_file()") . Adding the wrapper fixes the problem. Fixes: 78f90aae ("arm: armv7: allow unaligned memory access") Signed-off-by:
Marek Vasut <marex@denx.de>
-
Heinrich Schuchardt authored
%s/loady/loadb/ Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Heinrich Schuchardt authored
Provide a man-page for the saves command. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Heinrich Schuchardt authored
Provide a man-page for the loads command. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
-
- Jun 29, 2023
-
-
board_mmc_get_env_part() is not called as the default implementation of mmc_get_env_part() is used. Fix this problem by directly calling mmc_get_env_part() instead. Signed-off-by:
Eduard Strehlau <eduard@lionizers.com> Signed-off-by:
Fabio Estevam <festevam@denx.de>
-
Tom Rini authored
Currently the PowerPC build job in Azure will hit the maximum time limit for a build and stop. Looking at the job, the easiest path to reducing it is to move Keymile vendor boards to their own job and exclude them from the PowerPC one (and while at this, the ls102 job). Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Heiko Schocher <hs@denx.de>
-
Currently, the imx93_evk is configured with CONFIG_ENV_IS_IN_MMC and the chosen environment offset in the config is 0x400000. Unless the user programs the associated fuses, this offset is the default secondary boot image offset used by the i.MX 93 ROM bootloader. With certain combinations of environmental variables, the CRC and beginning of the environment can potentially falsely appear as a valid boot image container header. If the expected "sw_version" offset within this mistaken boot image container is greater than the primary's, the ROM bootloader can skip booting of the primary image altogether and attempt to boot with the content of the environment data. This will then hang the system. To fix this, move the environment from 0x400000 to 0x700000 reserving up to 3 MB at 0x400000 for any actual secondary user image container. Signed-off-by:
Ken Sloat <ken.s@variscite.com> Reviewed-by:
Peng Fan <peng.fan@nxp.com> Reviewed-by:
Fabio Estevam <festevam@denx.de>
-
https://source.denx.de/u-boot/custodians/u-boot-rockchipTom Rini authored
- rockchip inno phy fix; - pinctrl driver in SPL arort in specific case; - fix IO port voltage for rock5b-rk3588 board;
-
Update description with correct specifications Fixes: 3bf8e408 ("board: rockchip: add Radxa ROCK5B Rk3588 board") Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by:
Kever Yang <kever.yang@rock-chips.com>
-
Using CONFIG_ARMV8_SPL_EXCEPTION_VECTORS=y and CONFIG_OF_LIVE=y triggers a Data Abort exception from unaligned memory access when the pinctrl driver iterate node properties, e.g. for UART2 on RK3568. setting mux of GPIO0-24 to 1 setting mux of GPIO0-24 to 1 "Synchronous Abort" handler, esr 0x96000021 elr: 000000000000e554 lr : 000000000000e54c x 0: 0000000000000a5c x 1: 0000000000000a5c x 2: 0000000000000007 x 3: 0000000000000065 x 4: 0000000000000007 x 5: 0000000000022d4e x 6: 0000000000000a7c x 7: 00000000000227a4 x 8: 0000000000021cf0 x 9: 0000000000000a7c x10: 0000000000021cf0 x11: 0000000000021cf0 x12: 00000000003fda1c x13: 0000000000000007 x14: 00000000003fd9ec x15: 000000000001c0ff x16: 0000000007000000 x17: 00000000fdccd028 x18: 00000000003fde20 x19: 0000000000000018 x20: 0000000000020670 x21: 0000000000000000 x22: 00000000003fdb00 x23: 00000000003fef90 x24: 0000000000020688 x25: 0000000000000000 x26: 0000000000000001 x27: 00000000003ffc50 x28: 0000000000000000 x29: 00000000003fda60 Code: b94083e1 97ffd508 93407c01 37f81260 (f9401038) Resetting CPU ... Fix this by replacing the loop to access node properties with use of ofnode_for_each_prop instead of the current ifdef. Also continue to next prop instead of aborting at first sign of an unknown property. This fixes the Data Abort exception and also pinconf of e.g. pull and drive in SPL, e.g. for UART2 on RK3568. setting mux of GPIO0-24 to 1 setting mux of GPIO0-24 to 1 setting pull of GPIO0-24 to 5 setting mux of GPIO0-25 to 1 setting mux of GPIO0-25 to 1 setting pull of GPIO0-25 to 5 Fixes: e7ae4cf2 ("pinctrl: rockchip: Add common rockchip pinctrl driver") Signed-off-by:
Jonas Karlman <jonas@kwiboo.se> Reviewed-by:
Kever Yang <kever.yang@rock-chips.com>
-
This fixes access to camera sensor over I2C during probe time in the kernel. (Kernel will fix I/0 port voltage by itself, but the timing depends on probe order of the drivers, so the fix can come after the camera sensor driver already failed to probe.) Signed-off-by:
Ondrej Jirman <megi@xff.cz> Cc: Kever Yang <kever.yang@rock-chips.com> Reviewed-by:
Kever Yang <kever.yang@rock-chips.com> Reviewed-by:
Peter Robinson <pbrobinson@gmail.com> Tested-by:
Peter Robinson <pbrobinson@gmail.com>
-
The support for #address-cells=2 has a loophole: if the reg is actually 0, but the #address-cells is actually 1, like in such case below: syscon { #address-cells = <1>; phy { reg = <0 0x10>; }; }; then the second u32 of the 'reg' is the size, not the address. The code should check for the parent's #address-cells value, and not assume that if the first u32 is 0, then the #address-cells is 2, and the reg property is something like reg = <0 0xff00 0x10>; Fixed this by looking for the #address-cells value and retrieving the reg address only if this is ==2. To avoid breaking anything I also kept the check `if reg==0` as some DT's may have a wrong #address-cells as parent and even if this commit is correct, it might break the existing wrong device-trees. Fixes: d538efb9 ("phy: rockchip: inno-usb2: Add support #address_cells = 2") Signed-off-by:
Eugen Hristev <eugen.hristev@collabora.com> Reviewed-by:
Kever Yang <kever.yang@rock-chips.com>
-
- Jun 28, 2023
-
-
Tom Rini authored
Merge tag 'u-boot-amlogic-next-20230628' of https://source.denx.de/u-boot/custodians/u-boot-amlogic into next - add support for Amlogic A1 SoC and ad401 board - add support for Videostrong KII Pro - introduce secure power domain for A1 SoC
-
This patch adds Power controller driver support for Amlogic A1 family using secure monitor calls. The power domains register only can access in secure world. Signed-off-by:
Alexey Romanov <avromanov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230531093156.29240-4-avromanov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
We can use them in secure pwrc driver. Signed-off-by:
Alexey Romanov <avromanov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230531093156.29240-3-avromanov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
This commit adds functions to manage secure power domain for Amlogic SoC's using smc functionality. Signed-off-by:
Alexey Romanov <avromanov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230531093156.29240-2-avromanov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Add build instructions for the KII Pro set-top box. Signed-off-by:
Ferass El Hafidi <vitali64pmemail@protonmail.com> Link: https://lore.kernel.org/r/20230507124109.31778-4-vitali64pmemail@protonmail.com Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Add configurations for the Videostrong KII Pro set-top box. This defconfig is cloned from the WeTek Play2's. Signed-off-by:
Ferass El Hafidi <vitali64pmemail@protonmail.com> Link: https://lore.kernel.org/r/20230507124109.31778-3-vitali64pmemail@protonmail.com Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Import the device tree from mainline linux (v6.4-rc1) and add the old PHY reset bindings in the PHY node, else U-Boot and linux won't be able to use the PHY. Signed-off-by:
Ferass El Hafidi <vitali64pmemail@protonmail.com> Link: https://lore.kernel.org/r/20230507124109.31778-2-vitali64pmemail@protonmail.com Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
The AD401 board is the Amlogic A1 SoC reference board Signed-off-by:
Igor Prusov <ivprusov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230505125639.3605-6-ivprusov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Based on Linux kernel commit: dabad1ff85611 (pinctrl: meson: add pinctrl driver support for Meson-A1 SoC) Signed-off-by:
Igor Prusov <ivprusov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230505125639.3605-5-ivprusov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Add support for Amlogic A1 SoC family. Signed-off-by:
Igor Prusov <ivprusov@sberdevices.ru> Signed-off-by:
Evgeny Bachinin <eabachinin@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230505125639.3605-4-ivprusov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Add meson-a1-ad401.dts file from Linux 6.3-rc7 Signed-off-by:
Igor Prusov <ivprusov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230505125639.3605-3-ivprusov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-
Import Linux 6.3-rc7 Device tree and necessary bindings for Amlogic A1 board from 6a8f57ae2eb0 ("Linux 6.3-rc7"). Signed-off-by:
Igor Prusov <ivprusov@sberdevices.ru> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Link: https://lore.kernel.org/r/20230505125639.3605-2-ivprusov@sberdevices.ru Signed-off-by:
Neil Armstrong <neil.armstrong@linaro.org>
-