- 24 4月, 2019 28 次提交
-
-
由 Tom Rini 提交于
- Add and enable brcmnand driver on a number of relevant platforms. Also add and enable LED drivers on more bcm platforms. - Various ARMv8 fixes/improvements, including extending PSCI functionality. - fs_loader improvments - Various FIT/SPL improvements - PCI bugfixes - Poplar platform ethernet support - MediaTek MMC improvements - Android boot improvements
-
由 Eugeniu Rosca 提交于
Fix below CP warning triggered by the 'iminfo' output in another patch: WARNING: 'addrress' may be misspelled - perhaps 'address'? Fixes: 4f1318b2 ("common: image: minimal android image iminfo support") Signed-off-by: NEugeniu Rosca <erosca@de.adit-jv.com> Acked-by: NMarek Vasut <marek.vasut@gmail.com>
-
由 Eugeniu Rosca 提交于
According to Android image format [1], kernel image resides at 1 page offset from the boot image address. Grab the magic number from there and allow U-Boot to handle LZ4-compressed KNL binaries instead of hardcoding compression type to IH_COMP_NONE. Other compression types, if needed, can be added later. Tested on H3ULCB-KF using the image detailed in [2]. [1] Excerpt from include/android_image.h +-----------------+ | boot header | 1 page +-----------------+ | kernel | n pages +-----------------+ | ramdisk | m pages +-----------------+ | second stage | o pages +-----------------+ [2] => iminfo 4c000000 ## Checking Image at 4c000000 ... Android image found kernel size: 85b9d1 kernel address: 48080000 ramdisk size: 54ddbc ramdisk addrress: 4a180000 second size: 0 second address: 48000800 tags address: 48000100 page size: 800 os_version: 1200012a (ver: 0.9.0, level: 2018.10) name: cmdline: buildvariant=userdebug Signed-off-by: NEugeniu Rosca <erosca@de.adit-jv.com>
-
由 Heinrich Schuchardt 提交于
If CONFIG_UNIT_TEST is enabled we should enable the individual tests by default to ensure good test coverage. Reviewed-by: NSimon Glass <sjg@chromium.org> Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
-
由 Lars Povlsen 提交于
This fixes relaction isses with the PSCI_TABLE entries in the psci_32_table and psci_64_table. When using 32-bit adress pointers relocation was not being applied to the tables, causing PSCI handlers to point to the un-relocated code area. By using 64-bit data relocation is properly applied. The handlers are thus in the "secure data" area, which is protected by /memreserve/ in the FDT. Signed-off-by: NLars Povlsen <lars.povlsen@microchip.com>
-
由 Trent Piepho 提交于
The cache flush of the kernel load area needs to be aligned outward to the DMA cache alignment. The operations are simpler if we think of this as aligning the start down, ALIGN_DOWN(load, ARCH_DMA_MINALIGN), and aligning the end up, ALIGN(load_end, ARCH_DMA_MINALIGN), and then find the length of the flushed region by subtracting the former from the latter. Cc: Tom Rini <trini@konsulko.com> Cc: Simon Glass <sjg@chromium.org> Cc: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by: NTrent Piepho <tpiepho@impinj.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Andreas Dannenberg 提交于
When using memalign() in a scenario where U-Boot is configured for full malloc support with simple malloc not explicitly enabled and before the full malloc support is initialized, a memory block is being allocated and returned without the alignment parameter getting honored. Fix this issue by replacing the existing memalign pre-full malloc init logic with a call to memalign_simple() this way ensuring proper alignment of the returned memory block. Fixes: ee038c58 ("malloc: Use malloc simple before malloc is fully initialized in memalign()") Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Stefan Roese 提交于
This patch adds a short message to the SPL NAND loader, which displays the source and destinations addresses including the size of the loaded image, like this: U-Boot SPL 2019.04-rc3-00113-g486efd8aaf (Mar 15 2019 - 14:18:02 +0100) Trying to boot from NAND Loading U-Boot from 0x00040000 (size 0x000a0000) to 0x22900000 I find this message quite helpful - hopefully others do so as well. Signed-off-by: NStefan Roese <sr@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Tom Rini <trini@konsulko.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Fabien Parent 提交于
Add support for MediaTek MT8516 SoC. This include the file that will initialize the SoC after boot and its device tree. Signed-off-by: NFabien Parent <fparent@baylibre.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Fabien Parent 提交于
Add Pinctrl driver for MediaTek MT8516 SoC. Signed-off-by: NFabien Parent <fparent@baylibre.com> Acked-by: NRyder Lee <ryder.lee@mediatek.com>
-
由 Fabien Parent 提交于
Add clock driver for MediaTek MT8516 SoC. Signed-off-by: NFabien Parent <fparent@baylibre.com> Acked-by: NRyder Lee <ryder.lee@mediatek.com> [trini: Redo whitespace] Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Fabien Parent 提交于
Add the implementation for the CLK_GATE_SETCLR_INV and CLK_GATE_NO_SETCLR flags. Signed-off-by: NFabien Parent <fparent@baylibre.com> Acked-by: NRyder Lee <ryder.lee@mediatek.com>
-
由 Fabien Parent 提交于
We either need to use IS_ENABLED(CONFIG_FOO) or CONFIG_IS_ENABLED(FOO). IS_ENABLE(FOO) will always return false. This commit fixes the comparison by using the CONFIG_IS_ENABLED(FOO) syntax. Signed-off-by: NFabien Parent <fparent@baylibre.com>
-
由 Fabien Parent 提交于
Add config for handling MT8516 SoC. Signed-off-by: NFabien Parent <fparent@baylibre.com> Acked-by: NRyder Lee <ryder.lee@mediatek.com>
-
由 Fabien Parent 提交于
Some MediaTek SoC need an additional clock "source_cg". Enable this new clock. We reuse the same clock name as in the kernel. Signed-off-by: NFabien Parent <fparent@baylibre.com> Acked-by: NRyder Lee <ryder.lee@mediatek.com>
-
由 Shawn Guo 提交于
The 'phy' reset of gmac device in kernel device tree is not generic enough for u-boot to use, so we need to overwrite the 'resets' property as needed. With this device tree fixup and poplar_defconfig changes, Ethernet starts working on Poplar board. Signed-off-by: NShawn Guo <shawn.guo@linaro.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Shawn Guo 提交于
It adds the driver for HIGMACV300 Ethernet controller found on HiSilicon SoCs like Hi3798CV200. It's based on a downstream U-Boot driver, but quite a lot of code gets rewritten and cleaned up to adopt driver model and PHY API. Signed-off-by: NShawn Guo <shawn.guo@linaro.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Shawn Guo 提交于
It adds a Driver Model compatible reset driver for HiSlicon platform. The driver implements a custom .of_xlate function, and uses .data field as reset register offset and .id field as bit shift. Signed-off-by: NShawn Guo <shawn.guo@linaro.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Shawn Guo 提交于
Some reset controllers support different polarities for reset operation, so let's add a polarity field into struct reset_ctl. Signed-off-by: NShawn Guo <shawn.guo@linaro.org> Acked-by: NJoe Hershberger <joe.hershberger@ni.com>
-
由 Thierry Reding 提交于
If a platform defines CONFIG_NR_DRAM_BANKS, each DRAM bank will be added as a PCI region. The number of MAX_PCI_REGIONS therefore needs to scale with the number of DRAM banks, otherwise we will end up with too little space in the hose->regions array to store all system memory regions. Signed-off-by: NThierry Reding <treding@nvidia.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Thierry Reding 提交于
Make sure that we don't overflow the hose->regions array, otherwise we would end up overwriting the hose->region_count field and cause mayhem to ensue. Also print an error message when we'd be overflowing because it indicates that there aren't enough regions available and the number needs to be increased. Signed-off-by: NThierry Reding <treding@nvidia.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Adam Ford 提交于
With the migration to DM in SPL and the DT support, the old legacy code is no longer neaded, so this patch removes it Signed-off-by: NAdam Ford <aford173@gmail.com>
-
由 Philippe Reynes 提交于
Enable the led support in the configuration of the board bcm963158. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the led controller in the device tree of the board bcm963158. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Add the led controller in the bcm63158 device tree. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Allow the led bcm6858 driver to be used on bcm63158. They have the same led controller. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the led support in the configuration of the board bcm968580xref. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
Enable the led controller in the device tree of the board bcm968580xref. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
- 23 4月, 2019 12 次提交
-
-
由 Philippe Reynes 提交于
Add the led controller in the bcm6858 device tree. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com>
-
由 Philippe Reynes 提交于
The driver add the support of the led IP on bcm6858. This led IP can drive up to 32 leds, and can handle blinking. Signed-off-by: NPhilippe Reynes <philippe.reynes@softathome.com> Reviewed-by: NDaniel Schwierzeck <daniel.schwierzeck@gmail.com>
-
由 Ibai Erkiaga 提交于
Current relocation code is limited to 21bit PC-relative addressing which might not be enough for bigger code sizes. The following patch increases the addressing to 32bit PC-relative. This feature is specially interesting if U-Boot is build without optimiation (-O0) as the text section is increased significativelly. Signed-off-by: NIbai Erkiaga <ibai.erkiaga-elorza@xilinx.com>
-
由 Marek Vasut 提交于
At least MIPS Boston currently uses srec_cat tool to fiddle with srecords. There will be other platforms coming, so install the tool to prevent build problems. Signed-off-by: NMarek Vasut <marek.vasut+renesas@gmail.com> Cc: Daniel Schwierzeck <daniel.schwierzeck@gmail.com> Cc: Michal Simek <michal.simek@xilinx.com> Cc: Tom Rini <trini@konsulko.com>
-
由 Stefano Babic 提交于
The initial environment is linked to the u-boot binary. Modifying the environment from User Space with the env tools requires that the tools are always built together with the bootloader to be sure that they contain the initial environment in case no environment is stored into persistent storage or when a board boots with just the default environment. This makes difficult for distros to provide a general package to access the environment. A simpler way is if the tools are generic for all boards and a configuration file is given to provide the initial environment. The patch just generates the initial environment by extracting it from the compiled object. This file can then be used for tools in user space to initialize the environment. Signed-off-by: NStefano Babic <sbabic@denx.de>
-
由 Marek Vasut 提交于
Add support for loading fully featured fitImages over YModem in SPL. This is useful when various advanced features of full fitImages are needed in SPL. Signed-off-by: NMarek Vasut <marex@denx.de> Cc: Tom Rini <trini@konsulko.com>
-
由 Peter Ujfalusi 提交于
Currently only the first fdt is loaded from the extra configuration of FIT image. If the configuration have multiple fdt, load them all as well. Signed-off-by: NPeter Ujfalusi <peter.ujfalusi@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Tien Fong Chee 提交于
In previously label which will be expanded to the node's full path was used, and now replacing label with most commonly used DT phandle. The codes were changed accordingly to the use of DT phandle and supporting multiple instances. Signed-off-by: NTien Fong Chee <tien.fong.chee@intel.com>
-
由 Ibai Erkiaga 提交于
HVC call makes use of 6 mandatory arguments rather than 7 in the same way as SMC calls. The 7th argument is optional (Client ID) for both HVC and SMC but is implemented as 16-bit parameter and register R7 or W7. The aim of this patch is just fix compilation error due to an invalid asm code in the HVC call so that's why the 7th argument is removed. The issue does not report any error in a normal build as hvc_call is not used at all and is optimized by the compiler. Using -O0 triggers the error so the patch is intended to fix issues on a ongoing effor to build U-Boot with -O0. Signed-off-by: NIbai Erkiaga <ibai.erkiaga-elorza@xilinx.com>
-
由 Shawn Guo 提交于
It works perfectly fine to boot an Android boot.img with bootm command followed by an explicit address argument that holds the image. But if we have boot.img downloaded into default 'loadaddr', and then boot it using bootm command without the address argument, we will run into problem, because U-Boot fails to find ramdisk and fdt (second area) in boot.img. The current Android image support assumes there is always an address argument on bootm command. However just like booting any other images, 'loadaddr' should be used when address argument is missing from bootm command. It patches boot_get_ramdisk() and boot_get_fdt() a bit to support this quite common usage of bootm command for Android image. Signed-off-by: NShawn Guo <shawn.guo@linaro.org> Reviewed-by: NTom Rini <trini@konsulko.com>
-
由 Tien Fong Chee 提交于
This function supports getting both data address and length for existing FIT subimage and FIT external data. Signed-off-by: NTien Fong Chee <tien.fong.chee@intel.com>
-
由 Ang, Chee Hong 提交于
When PSCI is enabled, we are expecting U-Boot which now act as EL3 software will handle all the PSCI calls. We won't need fwcall as no further HVC or SMC are needed. Signed-off-by: NAng, Chee Hong <chee.hong.ang@intel.com>
-