- Mar 02, 2024
-
-
This file is no longer used, the PFC pin controller driver is superseded by drivers/pinctrl/renesas/pfc-r8a7790.c which includes all the details of the hardware. Remove this file. No functional change. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org> Reviewed-by:
Paul Barker <paul.barker.ct@bp.renesas.com>
-
This file is no longer used, the MMCIF controller driver is superseded by drivers/mmc/sh_mmcif.c which includes all the details of the hardware. Remove this file include from all board files and remove the file itself. No functional change. Signed-off-by:
-
This file is no longer used, the SDHI controller driver is long superseded by drivers/mmc/renesas-sdhi.c which includes all the details of the hardware. Remove this file include from all board files and remove the file itself. No functional change. Signed-off-by:
-
Last board with this SoC has been removed in commit 0fb054b3 ("arm: Remove armadillo-800eva board") in August 2022. Drop the rest of unused code. Signed-off-by:
-
- Feb 24, 2024
-
-
https://source.denx.de/u-boot/custodians/u-boot-imxTom Rini authored
- Enable the thermal driver for the imx8m phycore boards. - Convert imx53-qsb to watchdog driver to fix the 'reset' command. - Remove multiline string from imx6dl-sielaff. - Add SPI boot support for imxrt1050-evk. - Convert opos6uldev to watchdog driver to fix the 'reset' command.
-
Commit 68dcbdd5 ("ARM: imx: Add weak default reset_cpu()") caused the 'reset' command in U-Boot to not cause a board reset. Fix it by switching to the watchdog driver model via sysreset, which is the preferred method for implementing the watchdog reset. Signed-off-by:
Sébastien Szymanski <sebastien.szymanski@armadeus.com> Reviewed-by:
Fabio Estevam <festevam@gmail.com>
-
Commit 68dcbdd5 ("ARM: imx: Add weak default reset_cpu()") caused the 'reset' command in U-Boot to not cause a board reset. Fix it by switching to the watchdog driver model via sysreset, which is the preferred method for implementing the watchdog reset. Signed-off-by:
-
Enable the imx thermal driver to prevent booting when the system is too hot. Signed-off-by:Benjamin Hahn <B.Hahn@phytec.de>
-
Enable the imx thermal driver to prevent booting when the system is too hot. Signed-off-by: -
Enable the imx thermal driver to prevent booting when the system is too hot. Signed-off-by: -
Enable the `fastboot` command. Signed-off-by:Mathieu Othacehe <othacehe@gnu.org>
-
Enable the `usb` command and some USB drivers. Signed-off-by: -
Enable both usbotg1 and usbotg2 ports. Signed-off-by: -
Copied from: https://lore.kernel.org/linux-devicetree/20240131114324.3722428-6-xu.yang_2@nxp.com/ Signed-off-by:
-
Remove the malformed multiline string and fix the checkpatch warning. Reported-by:
Dan Carpenter <dan.carpenter@linaro.org> Signed-off-by:
Frieder Schrempf <frieder.schrempf@kontron.de>
-
Add documentation for SPI boot. Signed-off-by:Jesse Taube <Mr.Bossman075@gmail.com>
-
Add support for booting the imxrt1050-evk from spi. Add imximage config and the ability for SPL to boot from NOR. Enable binman in Kconfig and device tree for imxrt* as it is used to prepend fspi_header.bin to SPL and u-boot.img. Signed-off-by:
-
- Feb 23, 2024
-
-
Tom Rini authored
Merge tag 'u-boot-amlogic-fixes-20240223' of https://source.denx.de/u-boot/custodians/u-boot-amlogic - fix AVB oom error for Khadas VIM3 Android configs
-
When booting Android with AVB enabled, an OOM is observed: => avb init ${mmcdev} => avb verify _a ## Android Verified Boot 2.0 version 1.1.0 read_is_device_unlocked not supported yet read_rollback_index not supported yet avb_util.c:182: ERROR: Failed to allocate memory. OOM error occurred during verification A custom malloc length of 128MB is required as documented in commit 285a83b1 ("configs: meson64_android: increase SYS_MALLOC_LEN to 128M for AVB") However, this 128M custom malloc length was not ported to Kconfig in commit 7cfbba36 ("Convert CONFIG_SYS_MALLOC_LEN to Kconfig") Add it back to fix AVB verification on VIM3/VIM3L. Fixes: 7cfbba36 ("Convert CONFIG_SYS_MALLOC_LEN to Kconfig") Co-developed-by:Guillaume La Roque <glaroque@baylibre.com> Signed-off-by:
Mattijs Korpershoek <mkorpershoek@baylibre.com> Reviewed-by:
Neil Armstrong <neil.armstrong@linaro.org> Reviewed-by:
Igor Opaniuk <igor.opaniuk@gmail.com> Link: https://lore.kernel.org/r/20240209-vim3-avb-malloc-v1-1-91427d8c19ab@baylibre.com Signed-off-by:
-
- Feb 22, 2024
-
-
https://gitlab.denx.de/u-boot/custodians/u-boot-snapdragonTom Rini authored
- Two fixes for the qcom-pmic button driver
-
- Feb 20, 2024
-
-
Tom Rini authored
Nishanth Menon <nm@ti.com> says: This is a wide cleanup to switch to setting fdtfile using env_set instead of scripted magic. 'fdtfile' is expected to be set by default. This allows the stdboot triggered efi loaders to find the correct OS device tree file even if regular boot process is interrupted by user intervention.
-
We shouldn't need finfdt anymore. Drop the env script. Reviewed-by:
Jonathan Humphreys <j-humphreys@ti.com> Reviewed-by:
Roger Quadros <rogerq@kernel.org> Signed-off-by:
Nishanth Menon <nm@ti.com>
-
Stop using the findfdt script and switch to setting the fdtfile from C code. Reviewed-by:
-
Stop using the findfdt script and switch to setting the fdtfile from C code. Reviewed-by:
-
We now can provide a map and have the standard fdtfile variable set from code itself. This allows for bootstd to "just work". While at this, replace findfdt in environment with a warning as it is no longer needed. Reviewed-by:
-
We now can provide a map and have the standard fdtfile variable set from code itself. This allows for bootstd to "just work". While at this, replace findfdt in environment with a warning as it is no longer needed. Reviewed-by:
-
We now can provide a map and have the standard fdtfile variable set from code itself. This allows for bootstd to "just work". While at this, replace findfdt in environment with a warning as it is no longer needed. Reviewed-by:
-
We now can provide a map and have the standard fdtfile variable set from code itself. This allows for bootstd to "just work". While at this, replace findfdt in environment with a warning as it is no longer needed. Reviewed-by:
-
Stop using the findfdt script and switch to setting the fdtfile from C code. While at this, replace findfdt in environment with a warning as it is no longer needed Reviewed-by:
-
Stop using the findfdt script and switch to setting the fdtfile from C code. While at this, replace findfdt in environment with a warning as it is no longer needed Reviewed-by:
-
Introduce a common fdt operations library for basic device tree operations that are common between various boards. The first library to introduce here is the capability to set up fdtfile as a standard variable as part of board identification rather than depend on scripted ifdeffery. Reviewed-by:
-
Add missing board/ti/common/Kconfig references for the platforms that missed it. The intent is for the common Kconfig to be usable across TI reference boards as required. Reported-by:
Tom Rini <trini@konsulko.com> Signed-off-by:
-
-
-
- Feb 19, 2024
-
-
i.MX93 uses the same USB IP as i.MX8MM. It can then reuse the ehci-mx6 driver. Reviewed-by:
Marek Vasut <marex@denx.de> Signed-off-by:
-
Additional testing of the changes introduced in commit 33e06dcb "common: usb-hub: Reset hub port before scanning") revealed that some USB 2.0 and 3.0 flash drives didn't work in U-Boot on some Allwinner SoCs that support USB 2.0 interfaces only. More precisely, some of the tested USB 2.0 and 3.0 flash drives failed to be detected and work on an OrangePi Zero 3, based on the Allwinner H616 SoC that supports USB 2.0 only, while the same USB flash drives worked just fine on a Pine64 H64, based on the Allwinner H6 SoC that supports both USB 2.0 and USB 3.0 interfaces. The USB ID of the above-mentioned USB 3.0 flash drive that failed to work is 1f75:0917 (Innostor Technology Corporation IS917 Mass storage), it is 32 GB in size and sold under the PNY brand. The mentioned USB 2.0 drive is some inexpensive no-name drive with an invalid USB ID. Resetting USB 3.0 hubs only, which this patch introduces to the USB hub resets, has been tested to work as expected, resolving the identified issues on the Allwinner H616, while not introducing any new issues on other tested Allwinner SoCs. Thus, let's fix it that way. According to the USB 3.0 specification, resetting a USB 3.0 port is required when an attached USB device transitions between different states, such as when it resumes from suspend. Though, the Linux kernel performs additional USB 3.0 port resets upon initial USB device attachment, as visible in commit 07194ab7be63 ("USB: Reset USB 3.0 devices on (re)discovery") in the kernel source, to ensure proper state of the USB 3.0 hub port and proper USB mode negotiation during the initial USB device attachment and enumeration. These additional types of USB port resets don't exist for USB 2.0 hubs, according the USB 2.0 specification. The resets seem to be added to the USB 3.0 specification as part of the port and device mode negotiation. The Linux kernel resets USB 3.0 (i.e. SuperSpeed) hubs only, as visible in commit 10d674a82e55 ("USB: When hot reset for USB3 fails, try warm reset.") in the kernel source. The check for SuperSpeed hubs is performed in a way that also applies to newer SuperSpeed Plus (USB 3.1 or 3.2) hubs as well, which hopefully makes it future proof. Fixes: 33e06dcb ("common: usb-hub: Reset hub port before scanning") Link: https://lore.kernel.org/u-boot/20240207102327.35125-1-i@shantur.com/T/#u Link: https://lore.kernel.org/u-boot/20240201164604.13315fa6@donnerap.manchester.arm.com/T/#u Signed-off-by:
Shantur Rathore <i@shantur.com> Helped-by:
Dragan Simic <dsimic@manjaro.org> Tested-by:
Andre Przywara <andre.przywara@arm.com> Reviewed-by:
-
https://gitlab.denx.de/u-boot/custodians/u-boot-imxTom Rini authored
CI: https://source.denx.de/u-boot/custodians/u-boot-imx/-/pipelines/19683 - Convert msc_sm2s_imx8mp to DM_SERIAL. - Make Ethernel functional on msc_sm2s_imx8mp. - General improvements for msc_sm2s_imx8mp. - Add suport for the Sielaff i.MX6 Solo board. - Update GE HealthCare maitainers' e-mail addresses.
-
Describe how to build and boot for the Sielaff i.MX6 Solo board. Signed-off-by: -
The Sielaff i.MX6 Solo board is a control and HMI board for vending machines. Add support for this board. The devicetree files are taken from pending changes in the Linux kernel that are available from linux-next and will likely be part of Linux v6.9. Signed-off-by: -
The datasheet can be found here: https://www.esmt.com.tw/upload/pdf/ESMT/datasheets/EN25Q80B_Ver.E.pdf Signed-off-by:
-
