summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Merge git://www.denx.de/git/u-boot-imxTom Rini2017-11-2797-1027/+2162
|\ | | | | | | Signed-off-by: Tom Rini <trini@konsulko.com>
| * configs: icore-rqs: Enable falcon modeJagan Teki2017-11-271-0/+1
| | | | | | | | Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * engicam: imx6q: Return mmc dev 0 for icoreJagan Teki2017-11-271-1/+2
| | | | | | | | | | | | | | icorem6 has sd on usdhci1 which is devno 0 so return proper devno from board_mmc_get_env_dev for icorem6 and icorem_6rqs Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * i.MX6: engicam: Add imx6q/imx6ul boards for existing boardsJagan Teki2017-11-2730-311/+89
| | | | | | | | | | | | | | | | Add new board names for existing board support imx6q - icore and icore_rqs boards imx6ul - geam6ul and isiot boards Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * board: icore-rqs: Fix mmc get env deviceJagan Teki2017-11-272-1/+6
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As per USDHC boot eFUSE descriptions: USDHC3 => devno 2 USDHC4 => devno 3 Linux will detect mmc0, mmc1, mmc2 based on the status "okay" on usdhc so imx6qdl-icore-rqs.dtsi has enabled usdhc1, usdhc3 and usdhc4.But U-Boot can detect based on the aliases so add mmc1, mmc2 for usdhc3 and usdhc4 respectively and return the board_mmc_get_env_dev by subtracting -1 Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * i.MX6UL: icore: Add SPL_OF_CONTROL supportJagan Teki2017-11-2711-195/+26
| | | | | | | | | | | | Add OF_CONTROL support for SPL code. Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * pinctrl: imx6ul: Fix pinctrl data overlapped with DT areaJagan Teki2017-11-271-1/+6
| | | | | | | | | | | | | | | | | | | | | | before relocation pinctrl data BSS is overlapping DT area, when .data is using uninitialized global variable, imx6_pinctrl_soc_info. So assign them flags ZERO_OFFSET_VALID to prevent BSS overlap Suggested-by: Lokesh Vutla <lokeshvutla@ti.com> Reported-by: Jagan Teki <jagan@amarulasolutions.com> Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * i.MX6Q: icore: Add SPL_OF_CONTROL supportJagan Teki2017-11-279-187/+31
| | | | | | | | | | | | Add OF_CONTROL support for SPL code. Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * i.MX6Q: icorem6: Move spl load fit to common/splJagan Teki2017-11-273-24/+16
| | | | | | | | | | | | Move spl load fit code into common/spl Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * i.MX6: engicam: Move set_fdt_file to commonJagan Teki2017-11-276-34/+24
| | | | | | | | | | | | | | setenv_fdt_file to common code and set dtb based on CONFIG_DEFAULT_DEVICE_TREE and cpu_type. Signed-off-by: Jagan Teki <jagan@amarulasolutions.com>
| * mx6sxsabresd: Use PARTUUID to specify the rootfs locationFabio Estevam2017-11-272-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | mx6sxsabresd can run different kernel versions, such as NXP 4.1 or mainline. Currently the rootfs location is passed via mmcblk number and the problem with this approach is that the mmcblk number for the SD card changes depending on the kernel version. In order to avoid such issue, use the UUID method to specify the rootfs location. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: Stefano Babic <sbabic@denx.de> Reviewed-by: Lukasz Majewski <lukma@denx.de>
| * imx: Remove boolean parameter from wdog powerdown functionFabio Estevam2017-11-274-8/+8
| | | | | | | | | | | | | | | | | | | | | | | | imx_set_wdog_powerdown() is always used to disable the power down enable bit, so remove the boolean parameter of the function. It is also a bit strange to write a boolean value into registers, so this new version makes explicit that we are writing 0. While at it, rename it to imx_wdog_disable_powerdown(). Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * imx: Also clear powerdown enable bit for WDOG3 on i.MX6ULLFabio Estevam2017-11-271-1/+1
| | | | | | | | | | | | | | | | | | | | Clear powerdown enable bit for WDOG3 on i.MX6ULL to avoid unwanted kernel reboots. Suggested-by: Ye Li <ye.li@nxp.com> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: Peng Fan <peng.fan@nxp.com> Reviewed-by: Stefano Babic <sbabic@denx.de>
| * mx6ull: Fix WDOG3 base addressFabio Estevam2017-11-271-1/+1
| | | | | | | | | | | | | | | | | | i.MX6ULL has the same WDOG3 base address as i.MX6UL, so take this into account in the base address definition. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com> Reviewed-by: Peng Fan <peng.fan@nxp.com> Reviewed-by: Stefano Babic <sbabic@denx.de>
| * mx6sabreauto: Remove unneeded SPL selectionFabio Estevam2017-11-201-1/+1
| | | | | | | | | | | | | | SPL option is already selected via Kconfig, so remove it from the CONFIG_SYS_EXTRA_OPTIONS line. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * mx6: Select MX6QDL option via KconfigFabio Estevam2017-11-2015-14/+25
| | | | | | | | | | | | | | Currently the MX6QDL option is selected via CONFIG_SYS_EXTRA_OPTIONS, but it is better to select it directly via Kconfig. Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * mx53: Add Board support for GE PPDPeter Senna Tschudin2017-11-2010-0/+1105
| | | | | | | | | | | | | | | | | | | | | | | | | | Create board support for GE PPD, based on mx53loco. Use mx53ppd_defconfig make target to configure for this board. Signed-off-by: Peter Senna Tschudin <peter.senna@collabora.com> Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Cc: Stefano Babic <sbabic@denx.de> Acked-by: Stefano Babic <sbabic@denx.de>
| * board: ge: make VPD code commonMartyn Welch2017-11-206-241/+209
| | | | | | | | | | | | | | | | The VPD data is used on a number of GE products. Move the parsing code to a common location so that we can share this code. Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Acked-by: Stefano Babic <sbabic@denx.de>
| * rtc: add support for s35392aNandor Han2017-11-204-0/+375
| | | | | | | | | | | | | | | | | | Add support for S35392A RTC. The driver supports both U-Boot driver models. Signed-off-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Cc: Heiko Schocher <hs@denx.de>
| * bootcount: add support for bootcounter on EXT filesystemIan Ray2017-11-205-0/+130
| | | | | | | | | | | | | | | | Add support for bootcounter on an EXT filesystem. Sync configuration whitelist. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk>
| * arm: mx5: Add more register definitionsMartyn Welch2017-11-202-0/+41
| | | | | | | | | | | | | | | | | | | | Add register definitions require for video configuration. Signed-off-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Reviewed-by: Stefano Babic <sbabic@denx.de> Cc: Stefano Babic <sbabic@denx.de> Reviewed-by: Stefano Babic <sbabic@denx.de>
| * pwm: imx: Enable PWM support on i.MX53Martyn Welch2017-11-202-0/+19
| | | | | | | | | | | | | | | | | | Add missing parts for i.MX53 PWM support Acked-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Cc: Stefano Babic <sbabic@denx.de> Acked-by: Stefano Babic <sbabic@denx.de>
| * ext4: recover from filesystem corruption when readingIan Ray2017-11-202-1/+19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Some fixes when reading EXT files and directory entries were identified after using e2fuzz to corrupt an EXT3 filesystem: - Stop reading directory entries if the offset becomes badly aligned. - Avoid overwriting memory by clamping the length used to zero the buffer in ext4fs_read_file. Also sanity check blocksize. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Reviewed-by: Stefano Babic <sbabic@denx.de>
| * imx: mxc_i2c: tweak the i2c transfer methodNandor Han2017-11-201-10/+15
| | | | | | | | | | | | | | | | | | | | | | Tweak the i2c transfer to work for devices that want to read data without addressing a register. Signed-off-by: Nandor Han <nandor.han@ge.com> Signed-off-by: Martyn Welch <martyn.welch@collabora.co.uk> Acked-by: Heiko Schocher <hs@denx.de> Cc: Heiko Schocher <hs@denx.de> Cc: Stefano Babic <sbabic@denx.de>
| * Revert "wandboard: Remove unnecessary delay"Fabio Estevam2017-11-201-0/+2
| | | | | | | | | | | | | | | | | | | | | | This reverts commit b8b9790e23a7d6eec08d66192853ecb61bcae095. Some wandboard variants no longer boot after this commit, so keep the original delay to avoid the boot regression. Reported-by: Varga Zsolt <vazso@vazso.hu> Tested-by: Varga Zsolt <vazso@vazso.hu> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * pico-imx6ul: Use FS_GENERIC load commandFabio Berton2017-11-201-2/+2
| | | | | | | | | | Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
| * pico-imx6ul: Add function to create gpt partitionsFabio Berton2017-11-202-0/+2
| | | | | | | | | | | | | | | | Command run setup_emmc will create gpt partitions for mmc 0 device based on patitions variable. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
| * pico-imx6ul: Define partition layout in the environmentFabio Berton2017-11-201-0/+3
| | | | | | | | | | | | | | | | | | Create layout with a boot 16MiB partition and rootfs with remain space. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * pico-imx6ul: Add boot and rootfs dfu_alt_infoFabio Berton2017-11-201-1/+5
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Change dfu_alt_info variable to use the following altsetting: uboot: To flash raw U-Boot /zImage: boot: To copy kernel image /imx6ul-pico-hobbit.dtb: To copy dtb file rootfs: To copy rootfs List the currently attached DFU capable USB devices running: sudo dfu-util -l Flash U-Boot: sudo dfu-util -D u-boot.imx -a uboot Copy boot files: sudo dfu-util -D zImage -a /zImage sudo dfu-util -D imx6ul-pico-hobbit.dtb -a /imx6ul-pico-hobbit.dtb Flash rootfs: sudo dfu-util -D rootfs.ext4 -a rootfs To copy boot files you need to have a formated mmc 0:1 partition. To format with ext4 filesystem you can use ums. Run on target: ums 0 mmc 0 and on host: sudo mkfs.ext4 /dev/sdx1 Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br>
| * pico-imx6ul: Use PARTUUID to specify the rootfs locationFabio Berton2017-11-202-3/+4
| | | | | | | | | | | | | | | | | | | | | | Currently the rootfs location is passed via mmcblk number and using the UUID method to specify the rootfs location is a better approach working even if mmcblk number for the eMMC changes depending on the kernel versions. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * pico-imx6ul: Move dfu_alt_info to CONFIG_DFU_ENV_SETTINGS variableFabio Berton2017-11-201-1/+4
| | | | | | | | | | | | | | | | | | Create CONFIG_DFU_ENV_SETTINGS to set dfu environment settings to improve human readable code. Signed-off-by: Fabio Berton <fabio.berton@ossystems.com.br> Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Reviewed-by: Lukasz Majewski <lukma@denx.de>
| * ARM: imx6: Adjust DDR DRAM settings on DHCOM i.MX6 PDKMarek Vasut2017-11-161-20/+20
| | | | | | | | | | | | | | | | | | | | The board uses T-topology for the four x16 DRAM chips, so remove the write-leveling from the SPL as that is only usefly on fly-by topology and can be harmful on T-topology. Also update the DRAM timing with values from calibration on multiple boards. Signed-off-by: Marek Vasut <marex@denx.de> Cc: Stefano Babic <sbabic@denx.de>
* | Merge git://git.denx.de/u-boot-rockchipTom Rini2017-11-2621-87/+379
|\ \
| * | rockchip: defconfig: puma-rk3399: bypass ADC-based boot_mode checkPhilipp Tomsich2017-11-261-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The boot (and fallback/emergency boot) concept for the RK3399-Q7 differs from Rockchip's reference platforms. On the RK3399-Q7, some of this functionality is present in the bootloader itself (and configurable); some is backed in hardware by the Qseven BIOS_DISABLE signal to invoke the final stages of fallbacks (i.e. either an external boot bypassing on-module memories or falling back to the BROM for USB recovery). In summary: the ADC-based boot_mode check does not apply for the RK3399-Q7 and we therefore disable it (in this commit) by setting CONFIG_BOOT_MODE_REG to 0. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
| * | rockchip: fix turning off boot-mode via KconfigPhilipp Tomsich2017-11-262-2/+15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ROCKCHIP_BOOT_MODE_REG option defaults to a hex value, so 0 will show as 0x0 if a default is provided and changed via Kconfig. However, it still will show as 0, if no default is given. Consequently, the "is set to something other than 0" test in a Makefile is cumbersome. Instead this check can easily be performed in the C-code. This removes the ifeq-check from mach-rockchip/Makefile, adds a matching #if-check to boot_mode.c and fixes resulting link issues (if boot_mode.o was not included due to the Makefile check) by defining a stub function (in case the functionality is not built in) for setup_boot_mode in boot_mode.c. Fixes: e306779 (rockchip: make boot_mode related codes reused across all platforms) Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
| * | rockchip: pinctrl: rk3399: add support for I2C8Philipp Tomsich2017-11-263-1/+28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The RK3399 has a total of 9 I2C controllers. To support these, the enum in periph.h is extended and the mapping from the IRQ numbers to the peripheral-ids is extended to ensure that pinctrl requests are passed through to the function configuring the I2C pins. For I2C8, the pinctrl is implemented and tested (on a RK3399-Q7) using communication with the FAN53555 connected on I2C8. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Tested-by: Klaus Goger <klaus.goger@theobroma-systems.com>
| * | rockchip: clk: rk3399: change extract_bits to bitfield_extractPhilipp Tomsich2017-11-261-6/+2
| | | | | | | | | | | | | | | | | | | | | | | | The RK3399 clk driver still has a left-over use of extract_bits, which can be replaced by using bitfield_extract from include/bitfield.h. This rewrites the invocation to use the shared function. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
| * | spl: fit: add SPL_FIT_IMAGE_TINY config to reduce code-sizePhilipp Tomsich2017-11-263-5/+33
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | A minor code-size increase from the changes for tracking the os-type of FIT images and from infrastructure for recording the loadables into the the loaded FDT, broke the builds for sun50i and some OMAP2+ devices. This change adds a new config option (enabled by default for MACH_SUN50I, MACH_SUN50I_H5 and ARCH_OMAP2PLUS) that does skips these processing steps (bringing code size down to below the limit again). The os-type is not evaluated, but assumed to be IH_OS_UBOOT (i.e. taking the code-paths intended for backward-compatibility). Note that enabling this config option precludes any useful downstream processing, such as utilising a special calling convention for ATF or OPTEE, based on the os-type of the loadables. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com>
| * | rockchip: defconfig: lion-rk3368: sync up with SPL changes for ATFPhilipp Tomsich2017-11-261-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This tracks the SPL changes for ATF for the RK3368-uQ7: * renames ATF_SUPPORT to ATF * drops CONFIG_SPL_ATF_TEXT_BASE (now dynamically retrieved from the .itb file) Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | rockchip: defconfig: puma-rk3399: sync up with SPL changes for ATFPhilipp Tomsich2017-11-261-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This defconfig update makes use of the new features: * CONFIG_ROCKCHIP_SPL_RESERVE_IRAM is now set to 0, as there is no overlap between the M0 firmware and the ATF (we load this to DRAM and relocate it to its final location within the ATF) * tracks the ATF_SUPPORT -> ATF renaming Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | rockchip: board: lion-rk3368: update .its filePhilipp Tomsich2017-11-261-2/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | For the RK3368-uQ7, we can now update the .its file to mark the Trusted Firmware as out 'firmware' bootable and annotate both ATF and U-Boot with an OS-type. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | rockchip: board: puma-rk3399: update .its file to use new featuresPhilipp Tomsich2017-11-261-5/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit updates the .its file for the RK3399-Q7 to use the new features and demonstrates how to use those: * it marks the ATF as the 'firmware' * it tracks the OS-type for U-Boot and ATF * it loads the PMU (M0) firmware to DRAM and records the location to /fit-images (where our ATF reads it from) With the handoff of the next-stage FDT to ATF in place, we can now use this to pass information about the load addresses and names of each loadables to ATF: now we can load the M0 firmware into DRAM and avoid overwriting parts of the SPL stage. This is achieved by changing our .its-file to use an available area of DRAM as the load-address. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | rockchip: defconfig: firefly-rk3399: sync up with SPL changes for ATFPhilipp Tomsich2017-11-261-2/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | This tracks the SPL changes for ATF for the Firefly: * renames ATF_SUPPORT to ATF * drops CONFIG_SPL_ATF_TEXT_BASE Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: atf: drop the SPL_ATF_TEXT_BASE configuration itemPhilipp Tomsich2017-11-261-6/+0
| | | | | | | | | | | | | | | | | | | | | | | | The SPL_ATF_TEXT_BASE configuration item has become obsolete. Remove it from Kconfig. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: rename config item SPL_ATF_SUPPORT to SPL_ATFPhilipp Tomsich2017-11-262-2/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | Having CONFIG_SPL_ATF seems more natural. Rename it, while it it is easy and there's few boards that use it (only RK3399 and RK3368 boards). Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: atf: introduce spl_invoke_atf and make bl31_entry privatePhilipp Tomsich2017-11-262-13/+82
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This adds a new interface spl_invoke_atf() that takes a spl_image_info argument and then derives the necessary parameters for the ATF entry. Based on the additional information recorded (into /fit-images) from the FIT loadables, we can now easily locate the next boot stage. We now pass a pointer to a FDT as the platform-specific parameter pointer to ATF (so we don't run into the future headache of every board/platform defining their own proprietary tag-structure), as FDT access is already available in ATF. With the necessary infrastructure in place, we can now update the support for the ARM Trusted Firmware to dispatch into the spl_invoke_atf function only if a IH_OS_ARM_TRUSTED_FIRMWARE image is loaded. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: fit: implement recording of loadables into /fit-imagesPhilipp Tomsich2017-11-261-14/+81
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | If a FDT was loaded (e.g. to append it to U-Boot image), we store it's address and record information for all loadables into this FDT. This allows us to easily keep track of images for multiple privilege levels (e.g. with ATF) or of firmware images preloaded into temporary locations (e.g. PMU firmware that may overlap the SPL stage). Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: fit: implement fdt_record_loadablePhilipp Tomsich2017-11-262-0/+59
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During the loading of more complex FIT images (e.g. when the invoked next stage needs to find additional firmware for a power-management core... or if there are multiple images for different privilege levels started in parallel), it is helpful to create a record of what images are loaded where: if a FDT is loaded for one of the next stages, it can be used to convey the status and location of loadables. This adds a fdt_record_loadable() function that can be invoked to record the status of each loadable below the /fit-images path. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: fit: simplify logic for FDT loading for non-OS bootsPhilipp Tomsich2017-11-261-30/+56
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | To better support bootin through an ATF or OPTEE, we need to streamline some of the logic for when the FDT is appended to an image: depending on the image type, we'd like to append the FDT not at all (the case for the OS boot), to the 'firmware' image (if it is a U-Boot) or to one of the loadables (if the 'firmware' is an ATF, an OPTEE, or some other image-type and U-Boot is listed in the loadabled). To achieve this goal, we drop the os_boot flag and track the type of image loaded. If it is of type IH_OS_U_BOOT, we append the FDT. Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Acked-by: York Sun <york.sun@nxp.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * | spl: change load_addr and entry_point to uintptr_tPhilipp Tomsich2017-11-261-3/+6
| | | | | | | | | | | | | | | | | | | | | | | | Mainly a stylistic change: convert the load_addr and entry_point fields of struct spl_image_info to uintptr_t (from ulong). Signed-off-by: Philipp Tomsich <philipp.tomsich@theobroma-systems.com> Reviewed-by: Simon Glass <sjg@chromium.org>
View Lorry Controller Status