- 03 5月, 2019 13 次提交
-
-
由 Heiko Schocher 提交于
- at91sam9g20-taurus.dts: use labels - cleanup taurus port to compile clean with current mainline again. SPL has no serial output anymore, so it fits into SRAM. Signed-off-by: NHeiko Schocher <hs@denx.de>
-
由 Andrew F. Davis 提交于
TI-SCI firmware will only respond to messages when the TI_SCI_FLAG_REQ_ACK_ON_PROCESSED flag is set. Most messages already do this, set this for the ones that do not. Signed-off-by: NAndrew F. Davis <afd@ti.com> Tested-by: NAlejandro Hernandez <ajhernandez@ti.com> Acked-by: NNishanth Menon <nm@ti.com>
-
由 Heiko Schocher 提交于
commit 95f4bbd5 ("lib: fdt: Allow LZO and GZIP DT compression in U-Boot") introduced Kconfig option for gzip in U-Boot, but help text says gzip for SPL, which is wrong. Fix this. Signed-off-by: NHeiko Schocher <hs@denx.de> Acked-by: NMarek Vasut <marex@denx.de>
-
由 Heinrich Schuchardt 提交于
common.h already includes uuid.h Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Marek Behún 提交于
Other filesystem drivers don't do this. Signed-off-by: NMarek Behún <marek.behun@nic.cz>
-
由 Heinrich Schuchardt 提交于
The existing comments where confusing read and write. The comment for fs_write() had: "@addr: The address to read into" So let's rework the comments and format them in Sphinx style. Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Andreas Dannenberg 提交于
Switch from using the high priority DMSC transmit message queue used by the secure R5 MCU island boot context to the low priority message queue. While the change in priority is irrelevant for the current boot architecture it however gives us access to a deeper message queue that will allow us to buffer more messages. This is an important aspect when sending several messages without requesting and waiting for a response in a row which is a communication scheme used during core shutdown for example. See AM654 TISCI User Guide for additional details. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Paul Barker 提交于
In commit ad6054f1 where support for the Sancloud BeagleBone Enhanced (BBE) was added, new conditional configuration of either MII pin muxing or RGMII pin muxing is done depending on the board type. However, the old call to set up MII pin muxing was not removed. This may result in misconfiguration of the pin muxing for the BBE or duplicate configuration for other boards and so we remove this obsolete call. Signed-off-by: NPaul Barker <paul.barker@sancloud.co.uk>
-
由 Patrice Chotard 提交于
Restart operation never exists and reset operation never makes the watchdog expire immediately but expire_now operation does. Signed-off-by: NPatrice Chotard <patrice.chotard@st.com> Reviewed-by: NStefan Roese <sr@denx.de>
-
由 Peter Ujfalusi 提交于
Upcoming sysfw (2019.03) will not open the channelized firewalls during init, it only going to do so in response to the channel configuration message. Remove the channel state checks done before the channel configuration and move it after the configuration for warning purposes. Signed-off-by: NPeter Ujfalusi <peter.ujfalusi@ti.com> Signed-off-by: NVignesh Raghavendra <vigneshr@ti.com> Reviewed-by: NGrygorii Strashko <grygorii.strashko@ti.com>
-
由 Andreas Dannenberg 提交于
An earlier commit converted the TISCI receive timeouts to be specified in ms rather than us however it failed to take this change into account when passing the actual timeout to be used when invoking the mailbox receive API. This leads to the actual timeout to be 1,000 times shorter than expected and as a result certain TISCI operations would fail. Fix the issue by converting the timeout declared in ms to us on the fly as expected by the respective API. Fixes: fd6b40b1 ("firmware: ti_sci: Add support for NAVSS resource management") Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Peng Fan 提交于
Update the mmc maintainer from Jaehoon to me. Cc: Jaehoon Chung <jh80.chung@samsung.com> Signed-off-by: NPeng Fan <peng.fan@nxp.com> Acked-by: NMarek Vasut <marex@denx.de>
-
由 Keerthy 提交于
Currently packet data is wrongly extracted when metadata is NULL. Fix it and negate the if check. Signed-off-by: NKeerthy <j-keerthy@ti.com> Reviewed-by: NGrygorii Strashko <grygorii.strashko@ti.com> Reviewed-by: NPeter Ujfalusi <peter.ujfalusi@ti.com>
-
- 01 5月, 2019 1 次提交
-
-
git://git.denx.de/u-boot-imx由 Tom Rini 提交于
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
-
- 30 4月, 2019 3 次提交
-
-
由 Tom Rini 提交于
Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Simon Goldschmidt 提交于
Moved CONFIG_SPL_TEXT_BASE to common/spl/Kconfig and migrate existing values. Signed-off-by: NSimon Goldschmidt <simon.k.r.goldschmidt@gmail.com> [trini: Re-run migration] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Rsync all defconfig files using moveconfig.py Signed-off-by: NTom Rini <trini@konsulko.com>
-
- 27 4月, 2019 23 次提交
-
-
由 Tom Rini 提交于
- Various vexpress, taurus, da850evm, lpc32xx, brxre1 fixes/updates - btrfs fixes - Add AM65x HS EVM - Other small fixes
-
由 Igor Opaniuk 提交于
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/2699Reviewed-by: NSimon Glass <sjg@chromium.org> Reviewed-by: NSam Protsenko <semen.protsenko@linaro.org> Signed-off-by: NIgor Opaniuk <igor.opaniuk@gmail.com>
-
由 Heinrich Schuchardt 提交于
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: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Patrick Delaunay 提交于
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: NPatrick Delaunay <patrick.delaunay@st.com>
-
由 Robert P. J. Day 提交于
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 提交于
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: NBaruch Siach <baruch@tkos.co.il> Reviewed-by: NFabio Estevam <festevam@gmail.com>
-
由 Adam Ford 提交于
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: NAdam Ford <aford173@gmail.com>
-
由 Adam Ford 提交于
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: NAdam Ford <aford173@gmail.com>
-
由 Björn Stenberg 提交于
addr0 is being freed twice, leading to segmentation fault Signed-off-by: NBjörn Stenberg <bjorn@haxx.se>
-
由 Gregory CLEMENT 提交于
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: NGregory CLEMENT <gregory.clement@bootlin.com>
-
由 Gregory CLEMENT 提交于
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: NGregory CLEMENT <gregory.clement@bootlin.com>
-
由 Gregory CLEMENT 提交于
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: NMiquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: NGregory CLEMENT <gregory.clement@bootlin.com> Tested-by: NEugen Hristev <eugen.hristev@microchip.com>
-
由 Heiko Schocher 提交于
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: NHeiko Schocher <hs@denx.de>
-
由 Pierre Bourdon 提交于
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: NPierre Bourdon <delroth@gmail.com> Cc: Marek Behun <marek.behun@nic.cz>
-
由 Ismael Luceno Cortes 提交于
Signed-off-by: NIsmael Luceno <ismael.luceno@silicon-gears.com>
-
由 Pierre Bourdon 提交于
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: NPierre Bourdon <delroth@gmail.com> Cc: Marek Behun <marek.behun@nic.cz>
-
由 Andrew F. Davis 提交于
Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andrew F. Davis 提交于
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: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andrew F. Davis 提交于
K3 HS devices require signed binaries for boot, use the SECDEV tools to sign the boot artifacts during build. Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andrew F. Davis 提交于
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: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andrew F. Davis 提交于
SYSFW version 2019.01 introduces a slightly modified version of this API, add support for it here. Signed-off-by: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andrew F. Davis 提交于
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: NAndrew F. Davis <afd@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com> Reviewed-by: NAndreas Dannenberg <dannenberg@ti.com>