- 18 7月, 2019 12 次提交
-
-
由 Tom Rini 提交于
- Bring in the first three series that we need in order to enhance the TI AM65x series support and then later introduce J721E support.
-
由 Tom Rini 提交于
This brings in a small update to our Travis-CI config file and introduces a GitLab CI file. Currently they have the same functionality and the plan currently is to migrate away from Travis-CI.
-
由 Tom Rini 提交于
We need this for building some 64bit ARM platforms, not for test.py runs. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
To better allow for parallelization of the world build job split things into 32bit ARM (687 boards), 64bit ARM (215), PowerPC (311 boards) and everything else (167 boards). While the 32bit ARM job is heavier than I would like, there is not a natural split that would reduce it in half or so without requiring the sort of hard to maintain splits we have to do in Travis CI. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
In order to mirror current Travis CI support we need to install this package via pip. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Bring us back into line with current Travis tests. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
Migrate all of the logic in our current .travis.yml file to a GitLab CI config file. Notable changes are that this will run the jobs on runners with the "all" tag. The timeout for a job needs to be configured higher than normal as we no longer split building the world up into a large number of small jobs but instead perform one big build job. We make use of stages so that we build and run all of the QEMU + test.py tests first in order to increase the chance that any problems will be found before starting the final big build. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Tom Rini 提交于
In order to save a little space in SPL, do not use the asm versions of memcpy/memset. Signed-off-by: NTom Rini <trini@konsulko.com>
-
由 Joel Stanley 提交于
In order to boot u-boot in the aspeed machine we need to run at least qemu 3059c2f5a813 (v4.0.0-1592-g3059c2f5a813), which is not in a released tag. This should be changed to v4.1.0 when it is released. Signed-off-by: NJoel Stanley <joel@jms.id.au>
-
由 Joel Stanley 提交于
Signed-off-by: NJoel Stanley <joel@jms.id.au>
-
由 Joel Stanley 提交于
Tests in test/py/tests/test_env.py like this fail without CONFIG_HUSH_PARSER: => => printenv test_env_0 ## Error: "test_env_0" not defined => .=> setenv test_env_0 => => echo $test_env_0 $test_env_0 => F We also want a mac address so the ethernet device works in qemu. Signed-off-by: NJoel Stanley <joel@jms.id.au>
-
由 Joel Stanley 提交于
The aspeed board does not have an upstream MMC driver. As CONFIG_MMC defaults on, the board would fail to build due to the CONFIG_DM_MMC migration: ===================== WARNING ====================== This board does not use CONFIG_DM_MMC. Please update the board to use CONFIG_DM_MMC before the v2019.04 release. Failure to update by the deadline may result in board removal. See doc/driver-model/MIGRATION.txt for more info. ==================================================== Change the defconfig to disable MMC until a driver is submitted. Signed-off-by: NJoel Stanley <joel@jms.id.au>
-
- 17 7月, 2019 28 次提交
-
-
由 Andreas Dannenberg 提交于
This will allow for downloading and applying overlays from an MMC/SD boot media based on the overlay_files ENV variable containing a list of overlay files. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
This will allow for downloading and applying overlays from an MMC/SD boot media based on the overlay_files ENV variable containing a list of overlay files. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The TI AM654x EVM base board and the associated daughtercards have on- board I2C-based EEPROMs containing board configuration data. Use the board detection infrastructure introduced earlier to do the following: 1) Parse the AM654x EVM base board EEPROM and populate items like board name and MAC addresses into the TI common EEPROM data structure residing in SRAM scratch space 2) Check for presence of daughter card(s) by probing the associated presence signals via an I2C-based GPIO expander. Then, if such a card is found, parse the data such as additional Ethernet MAC addresses from its on-board EEPROM and populate into U-Boot accordingly 3) Dynamically create an U-Boot ENV variable called overlay_files containing a list of daugherboard-specific DTB overlays based on daughercards found. This patch adds support for the AM654x base board ("AM6-COMPROCEVM") as well as for the IDK ("AM6-IDKAPPEVM"), OLDI LCD ("OLDI-LCD1EVM") PCIe/USB3.0 ("SER-PCIEUSBEVM"), 2 Lane PCIe/USB2.0 ("SER-PCIE2LEVM"), and general purpuse ("AM6-GPAPPEVM") daughtercards. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The AM654x EVM based on the TI K3 family of SoCs has an updated board detection EEPROM structure that contains a TLV record of dedicated MAC addresses rather than a range of MAC addresses as it was used on earlier platforms such as DRA7. Add a basic function that allows us setting up Ethernet MAC addresses into the U-Boot environment based on the MAC address record contained in the common TI EEPROM structure. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The AM654x EVM based on the TI K3 family of SoCs have an updated board detection EEPROM structure, now comprising variable-sized TLV-type records, containing a superset of what is already being provided on earlier platforms such as DRA7. Add basic support for parsing the new data structures contained on the base board into the common TI EEPROM structure while also providing infrastructure that can be used later on to parse data from additional EEPROMs such as the ones that are used on daughtercards for this platform. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The board detection scheme employed on various TI EVMs makes use of SRAM scratch space to share data read from an on-board EEPROM between the different bootloading stages. Map the associated definition that's used to locate this data into the SRAM scratch space we use on AM654x. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The malloc pool used before relocation is getting tight leading to out of memory errors doing certain DM-related calls. Since we are running the A53 SPL out of DDR let's just go ahead and bump its size as used in U-Boot proper as well as SPL (via Kconfig default value) from 8KB to 32KB. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com> Acked-by: NAndrew F. Davis <afd@ti.com>
-
由 Andreas Dannenberg 提交于
The malloc pool used before relocation is getting tight leading to out of memory errors doing certain DM-related calls. Since we are running the A53 SPL out of DDR let's just go ahead and bump its size as used in U-Boot proper as well as SPL (via Kconfig default value) from 8KB to 32KB. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
Enable GPIO driver for PCA953X-compatible I2C-based I/O expander which includes support for the TCA9554/PCA9554-type expander found on the AM654 EVM base board. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com> Acked-by: NAndrew F. Davis <afd@ti.com>
-
由 Andreas Dannenberg 提交于
Enable GPIO driver for PCA953X-compatible I2C-based I/O expander which includes support for the TCA9554/PCA9554-type expander found on the AM654 EVM base board. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The AM654 base board has a TCA9554/PCA9554-type GPIO expander on the wkup_i2c0 bus at address 0x38 that is used to detect the presence of daughter cards. Add a respective DTS description of this expander to enable its use. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
Enable I2C via driver model as well as the associated set of U-Boot commands to allow us interacting with various I2C slave devices. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com> Acked-by: NAndrew F. Davis <afd@ti.com>
-
由 Andreas Dannenberg 提交于
Enable I2C via driver model as well as the associated set of U-Boot commands to allow us interacting with various I2C slave devices. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
To enable the use of an EEPROM-based board detection scheme we need to be able to access the I2C bus associated with the EEPROMs across all 3 stages of U-Boot: R5 SPL, A53 SPL, and A53 U-Boot (proper). So go ahead and add/update the wkup_i2c0 peripheral module DTS definitions and its associated pinmux node accordingly. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
Add I2C DT nodes Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
Only U-Boot specifc DT properties or overrides, must be in -u-boot.dtsi. Pinctrl nodes does not belong here. Now that pinctrl nodes are in kernel DT, there is no reason to be keep these in -u-boot.dtsi. Move them to proper places so that it would ease copying DT entries from kernel DT. Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vignesh R 提交于
There is no need for to include this header here, so drop it. Signed-off-by: NVignesh R <vigneshr@ti.com> Reviewed-by: NHeiko Schocher <hs@denx.de> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Vignesh R 提交于
K3 devices have I2C IP that is same as OMAP2+ family. Allow driver to be compiled for ARCH_K3. Signed-off-by: NVignesh R <vigneshr@ti.com> Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NHeiko Schocher <hs@denx.de> Reviewed-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Faiz Abbas 提交于
Add instructions for flashing boot images to the eMMC with a layout of the address where each image needs to be flashed. Also add instructions to flash filesystem partition in user partition and boot kernel from the rootfs. Signed-off-by: NFaiz Abbas <faiz_abbas@ti.com>
-
由 Andreas Dannenberg 提交于
Add configs to support RAW boot mode in eMMC. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Faiz Abbas 提交于
Add configs to support RAW boot mode in eMMC. Signed-off-by: NFaiz Abbas <faiz_abbas@ti.com> Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andreas Dannenberg 提交于
Enable all the relevant configs that enables support for loading sysfw via MMC. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NSimon Glass <sjg@chromium.org>
-
由 Andreas Dannenberg 提交于
Enable all the relevant configs that enables support for loading sysfw via MMC. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andreas Dannenberg 提交于
Use the System Firmware (SYSFW) loader framework to load and start the SYSFW as part of the AM654 early initialization sequence. While at it also initialize the WKUP_UART0 pinmux as it is used by SYSFW to print diagnostic messages. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andreas Dannenberg 提交于
Switch to using the full malloc scheme in post-relocation SPL to allow better utilization of available memory for example by allowing memory to get freed. Initially allocate a 16MB-sized region in DDR starting at address 0x84000000 for this purpose. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andreas Dannenberg 提交于
In order to be able to use more advanced driver functionality which often relies on having BSS initialized during early boot prior to relocation several things need to be in place: 1) Memory needs to be available for BSS to use. For this, we locate BSS at the top of the MCU SRAM area, with the stack starting right below it, 2) We need to move the initialization of BSS prior to entering board_init_f(). We will do this with a separate commit by turning on the respective CONFIG option. In this commit we also clean up the assignment of the initial SP address as part of the refactoring, taking into account the pre-decrement post- increment nature in which the SP is used on ARM. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com>
-
由 Andreas Dannenberg 提交于
Introduce a framework that allows loading the System Firmware (SYSFW) binary as well as the associated configuration data from an image tree blob named "sysfw.itb" from an FS-based MMC boot media or from an MMC RAW mode partition or sector. To simplify the handling of and loading from the different boot media we tap into the existing U-Boot SPL framework usually used for loading U-Boot by building on an earlier commit that exposes some of that functionality. Note that this initial implementation only supports FS and RAW-based eMMC/SD card boot. Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Signed-off-by: NLokesh Vutla <lokeshvutla@ti.com>
-
由 Andreas Dannenberg 提交于
The current U-Boot SPL image loader infrastructure is very powerful, able to initialize and load from a variety of boot media however it is strongly geared towards loading specific types of images in a very specific way. To address the need being able to use this infrastructure to load arbitrary image files go ahead and refactor it as follows: - Refactor existing spl_mmc_load_image function into superset function, accepting additional arguments such as filenames and media load offset (same concept can also be applied toother spl_XXX_load_image functions) - Extend the loader function to "remember" their peripheral initialization status so that the init is only done once during the boot process, - Extend the FIT image loading function to allow skipping the parsing/ processing of the FIT contents (so that this can be done separately in a more customized fashion) - Populate the SPL_LOAD_IMAGE_METHOD() list with a trampoline function, invoking the newly refactored superset functions in a way to maintain compatibility with the existing behavior This refactoring initially covers MMC/SD card loading (RAW and FS-based). Signed-off-by: NAndreas Dannenberg <dannenberg@ti.com> Reviewed-by: NTom Rini <trini@konsulko.com>
-