- May 03, 2019
-
-
Horatiu Vultur authored
In Serval SoC family there are 2 different pcb, both of them have the same phy, but with different version. Therefore implement board_phy_config and set all the phys in the same way. Signed-off-by:
Horatiu Vultur <horatiu.vultur@microchip.com>
-
Horatiu Vultur authored
Add network driver for Microsemi Ethernet switch. It is present on Serval SoCs. Signed-off-by:
Horatiu Vultur <horatiu.vultur@microchip.com> Reviewed-by:
Daniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
Horatiu Vultur authored
When detecting the board, it was reading a register in the GPIO page of the phy and based on that value it was making a decision. The bug was that after the GPIO page for the first phy was set it was not reseted back. Signed-off-by:
Horatiu Vultur <horatiu.vultur@microchip.com>
-
Horatiu Vultur authored
In case the ddr training was failing, it couldn't reset, it was just hanging. Therefore reimplement it, so when ddr training is failing it would call _machine_restart, which power downs the DDR and does a force reset. Signed-off-by:
Horatiu Vultur <horatiu.vultur@microchip.com>
-
- May 01, 2019
-
-
git://git.denx.de/u-boot-imxTom Rini authored
Porting to DM and i.MX8 ------------------------ - warp7 to DM - kp_imx53 to DM - Warnings in DT - MX8QM support - colibri-imx6ull to DM - imx7d-pico to DM - ocotp for MX8
-
- Apr 30, 2019
-
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Simon Goldschmidt authored
Moved CONFIG_SPL_TEXT_BASE to common/spl/Kconfig and migrate existing values. Signed-off-by:
Simon Goldschmidt <simon.k.r.goldschmidt@gmail.com> [trini: Re-run migration] Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
Rsync all defconfig files using moveconfig.py Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Apr 27, 2019
-
-
Tom Rini authored
Per Pierre this change shouldn't have been applied as it was superseded by "fs: btrfs: fix btrfs_search_tree invalid results" which is also applied now as 1627e5e5. This reverts commit 633967f9. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
- Various vexpress, taurus, da850evm, lpc32xx, brxre1 fixes/updates - btrfs fixes - Add AM65x HS EVM - Other small fixes
-
- Apr 26, 2019
-
-
Igor Opaniuk authored
AVB 2.0 spec. revision 1.1 introduces support for named persistent values that must be tamper evident and allows AVB to store arbitrary key-value pairs [1]. Introduce implementation of two additional AVB operations read_persistent_value()/write_persistent_value() for retrieving/storing named persistent values. Correspondent pull request in the OP-TEE OS project repo [2]. [1]: https://android.googlesource.com/platform/external/avb/+/android-9.0.0_r22 [2]: https://github.com/OP-TEE/optee_os/pull/2699 Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Sam Protsenko <semen.protsenko@linaro.org> Signed-off-by:
Igor Opaniuk <igor.opaniuk@gmail.com>
-
Heinrich Schuchardt authored
Add the device trees for * vexpress_ca5x2_defconfig * vexpress_ca9x4_defconfig * vexpress_ca15_tc2_defconfig as available in Linux 5.1 rc5. We are using the vexpress_ca15_tc2_defconfig and vexpress_ca9x4_defconfig for Travis testing via QEMU. The UEFI base Embedded Base Boot Requirements Specification (EBBR) requires that an embedded board either provides a device tree or an ACPI table. All block devices are meant to be moved to the driver model. On ARM this requires a device tree. Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Patrick Delaunay authored
The sysreset of 'POWER' type is a PMIC reset defined as 'remove and restore power'. So normally only COLD/WARN is supported by sysreset_syscon. This modification allows to use the function sysreset_walk(SYSRESET_POWER) when it is supported by PMIC driver (see example in stpmic1). Signed-off-by:
Patrick Delaunay <patrick.delaunay@st.com>
-
Robert P. J. Day authored
As far back as 2011, "_armboot_start" was being described as "no longer defined": commit 297f18ac Author: Greg Ungerer <greg.ungerer@opengear.com> Date: Fri Sep 9 22:23:34 2011 +1000 CM4000: fix broken flash base for OpenGear boards Use _bss_start_ofs as the size of the boot loader code+data that we want to protect in the flash. This replaces use of the no longer defined _armboot_start.
-
Baruch Siach authored
The generated flash.log file that mach-imx uses for MKIMAGEOUTPUT is not covered by any other ignore pattern. Ignore all *.log files. Signed-off-by:
Baruch Siach <baruch@tkos.co.il> Reviewed-by:
Fabio Estevam <festevam@gmail.com>
-
Adam Ford authored
The da850evm include environment/ti/mmc.h and places DEFAULT_MMC_TI_ARGS, defined int that file, in CONFIG_EXTRA_ENV_SETTINGS. This has been broken for some time since neither CMD_PART nor CMD_UUID are available, so manually changing the environmental variables was always required before booting from MMC. With this patch, these scripts should work again, and by default they point to mmc 0, partition 2, and the dtb file exists in a /boot directory on partition 2. Signed-off-by:
Adam Ford <aford173@gmail.com>
-
Adam Ford authored
A previous patch converted a bunch of settings for CONFIG_SF_DEFAULT but it broke the SPI Flash which now prevents booting. This patch now correctly sets CONFIG_SF_DEFAULT_SPEED=30000000 to match what it was before the conversion. Fixes: 14453fbf ("Convert CONFIG_SF_DEFAULT_* to Kconfig") Signed-off-by:
Adam Ford <aford173@gmail.com>
-
Björn Stenberg authored
addr0 is being freed twice, leading to segmentation fault Signed-off-by:
Björn Stenberg <bjorn@haxx.se>
-
Gregory CLEMENT authored
The match controller register is not cleared during initialization. However, some bits of this register may reset the TC if tnMRx match it. As we can't make any assumption about how U-Boot is launched by the first stage bootloader (such as S1L) clearing this register ensure that the timers work as expected. Signed-off-by:
Gregory CLEMENT <gregory.clement@bootlin.com>
-
Gregory CLEMENT authored
Since the introduction of the driver, some memory in IRAM is reserved for the TX buffers. However there are not used but instead of it, it is the buffer provided by the net stack which is used. As stated in the comment of the driver, not using the IRAM buffer could cause cache issue and lower the throughput. For the second argument it is less the case for transmitting buffers because the throughput gain in IRAM is mitigated by the time to copy the data from RAM to IRAM, but the first argument is still valid and indeed this patch fixes issue seen with Ethernet on some boards Signed-off-by:
Gregory CLEMENT <gregory.clement@bootlin.com>
-
Gregory CLEMENT authored
The purpose of "mtd: nand: raw: allow to disable unneeded ECC layouts" was to allow disabling the default ECC layouts if a driver is known to provide its own ECC layout. However, this commit did the opposite and disabled the default layout when it was _not_ selected. It breaks all the NAND drivers not providing their own ECC layout this patch fix this situation. It was tested with the lpc32xx_nand_slc driver. Fixes: a38c3af8 ("mtd: nand: raw: allow to disable unneeded ECC layouts") Reviewed-by:
Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by:
Gregory CLEMENT <gregory.clement@bootlin.com> Tested-by:
Eugen Hristev <eugen.hristev@microchip.com>
-
Heiko Schocher authored
generate define for an alias only if the struct is not created already. This prevents compilerwarning: PLAT spl/dts/dt-platdata.o spl/dts/dt-platdata.c:11:46: error: missing braces around initializer [-Werror=missing-braces] static const struct dtd_simple_bus dtv_ahb = { ^ spl/dts/dt-platdata.c:20:46: error: missing braces around initializer [-Werror=missing-braces] static const struct dtd_simple_bus dtv_apb = { ^ cc1: all warnings being treated as errors on the at91 based taurus board. Reason is in at91sam9260.dtsi is defined: ahb { compatible = "simple-bus"; ranges; and later: pinctrl: pinctrl@fffff400 { compatible = "atmel,at91rm9200-pinctrl", "simple-bus"; ranges = <0xfffff400 0xfffff400 0x600>; without this patch dtoc generates: struct dtd_atmel_at91rm9200_pinctrl { fdt32_t atmel_mux_mask[6]; fdt32_t ranges[3]; fdt32_t reg[6]; }; struct dtd_simple_bus { bool ranges; }; "#define dtd_simple_bus dtd_atmel_at91rm9200_pinctrl" and the line with "define dtd_simple_bus..." introduces the warning. This define is not needed. Signed-off-by:
Heiko Schocher <hs@denx.de>
-
Pierre Bourdon authored
btrfs_search_tree should return the first item in the tree that is greater or equal to the searched item. The search algorithm did not properly handle the edge case where the searched item is higher than the last item of the node but lower than the first item of the next node. Instead of properly returning the first item of the next node, it was returning an invalid path pointer (pointing to a non-existent item after the last item of the node + 1). This fixes two issues in the btrfs driver: - Looking for a ROOT_ITEM could fail if it was the first item of its leaf node. - Iterating through DIR_INDEX entries (for readdir) could fail if the first DIR_INDEX entry was the first item of a leaf node. Signed-off-by:
Pierre Bourdon <delroth@gmail.com> Cc: Marek Behun <marek.behun@nic.cz>
-
Ismael Luceno Cortes authored
Signed-off-by:
Ismael Luceno <ismael.luceno@silicon-gears.com>
-
Pierre Bourdon authored
ROOT_ITEMs in btrfs are referenced without knowing their actual "offset" value. To perform these searches using only two items from the key, the btrfs driver uses a special "btrfs_search_tree_key_type" function. The algorithm used by that function to transform a 3-tuple search into a 2-tuple search was subtly broken, leading to items not being found if they were the first in their tree node. This commit fixes btrfs_search_tree_key_type to properly behave in these situations. Signed-off-by:
Pierre Bourdon <delroth@gmail.com> Cc: Marek Behun <marek.behun@nic.cz>
-
Andrew F. Davis authored
Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
Add new defconfig files for the AM65x High Security EVM. This defconfigs are the same as for the non-secure part, except for: CONFIG_TI_SECURE_DEVICE option set to 'y' CONFIG_FIT_IMAGE_POST_PROCESS option set to 'y' CONFIG_SPL_FIT_IMAGE_POST_PROCESS option set to 'y' Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
K3 HS devices require signed binaries for boot, use the SECDEV tools to sign the boot artifacts during build. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
K3 devices have High Security (HS) variants along with the non-HS already supported. Like the previous generation devices (OMAP/Keystone2) K3 supports boot chain-of-trust by authenticating and optionally decrypting images as they are unpacked from FIT images. Add support for this here. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
SYSFW version 2019.01 introduces a slightly modified version of this API, add support for it here. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
TI-SCI message protocol provides support for controlling the firewall configurations available in SoC. Introduce support for the set of TI-SCI message protocol APIs that provide us with this capability of controlling firewalls. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com>
-
Andrew F. Davis authored
On HS devices the 512b region of reset isolated memory called MCU_PSRAM0 is firewalled by default. Until SYSFW is loaded we cannot use this memory. It is only used to store a single value left at the end of SRAM by ROM that will be needed later. Save that value to a global variable stored in the .data section. This section is used as .bss will be cleared between saving this value and using it. Signed-off-by:
Andrew F. Davis <afd@ti.com> Reviewed-by:
Andreas Dannenberg <dannenberg@ti.com> Reviewed-by:
Lokesh Vutla <lokeshvutla@ti.com>
-
Heiko Schocher authored
adding a new bootstage ID: BOOTSTAGE_ID_ENTER_CLI_LOOP Signed-off-by:
Heiko Schocher <hs@denx.de>
-
Patrice Chotard authored
The objective is to provide a simple way to retrieve a BMP file, and display it as splashscreen, from extlinux.conf file input. For this, we take example on https://www.syslinux.org/wiki/ index.php?title=Menu#The_advanced_menu_system and more particularly on MENU BACKGROUND chapter. For this, add "menu background" support in pxe command. As example, extlinux.conf content will look like: # Generic Distro Configuration file generated by OpenEmbedded menu title Select the boot mode TIMEOUT 20 menu background ../splash.bmp DEFAULT stm32mp157c-ev1-sdcard LABEL stm32mp157c-ev1-sdcard KERNEL /uImage FDT /stm32mp157c-ev1.dtb APPEND root=/dev/mmcblk0p6 rootwait rw earlyprintk console=ttySTM0,115200 Signed-off-by:
Patrice Chotard <patrice.chotard@st.com>
-
Pierre Bourdon authored
Fixes building mkimage on systems where OpenSSL header files do not live in the standard include path. Signed-off-by:
Pierre Bourdon <delroth@gmail.com>
-
Heinrich Schuchardt authored
%g/rathen then/rather than/ Signed-off-by:
Heinrich Schuchardt <xypron.glpk@gmx.de>
-
Hannes Schmelzer authored
The handling of regarding bootmode and early setup has been moved to central location 'common/br_resetc.c', so use this on brxre1 board. Signed-off-by:
Hannes Schmelzer <hannes.schmelzer@br-automation.com>
-
Hannes Schmelzer authored
- fixup coding style - drop unused 'PUSH_KEY' define Signed-off-by:
Hannes Schmelzer <hannes.schmelzer@br-automation.com>
-
Hannes Schmelzer authored
On many B&R boards we have a reset-controller, responsible for very early board-bringup (voltages, clocks, ...) and bootmode selection. To be ready for adding more B&R boards to source tree while avoiding duplicate code, we add the resetcontroller implementation to the common part of B&R boards. Signed-off-by:
Hannes Schmelzer <hannes.schmelzer@br-automation.com>
-
Hannes Schmelzer authored
Many B&R boards are equipped with an I2C-EEPROM where various information can be stored. Today there is only a single byte for 'board_id' used. We write this 'board_id' into environment for later use during boot. If the value != 0xFF, meaning the byte is programmed, we modify the "brdefaultip" environment variable for setting an IP-Address based on board_id. Signed-off-by:
Hannes Schmelzer <hannes.schmelzer@br-automation.com>
-