summaryrefslogtreecommitdiffstats
Commit message (Collapse)AuthorAgeFilesLines
* ARM: rmobile: Ignore U-Boot env when started via JTAG on PorterMarek Vasut2018-04-171-0/+16
| | | | | | | | When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* ARM: rmobile: Ignore U-Boot env when started via JTAG on StoutMarek Vasut2018-04-171-0/+15
| | | | | | | | When U-Boot is started via JTAG, ignore the installed environment as it may interfere with the recovery of the board. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* ARM: rmobile: Enable fitImage support on Gen3Marek Vasut2018-04-177-0/+7
| | | | | | | Enable fitImage support to be on the right side of the millenium. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* ARM: rmobile: Disable SDHI on R8A77970 V3M EagleMarek Vasut2018-04-171-6/+2
| | | | | | | The SDHI is not routed to a slot on the Eagle, so disable it. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* ARM: rmobile: Enable RPC QSPI on R8A77970 V3M EagleMarek Vasut2018-04-173-0/+35
| | | | | | | | Enable the RPC QSPI driver on R8A77970 V3M Eagle and configure the environment layout to match that used by old U-Boot. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* ARM: rmobile: Add Renesas RPC HF/QSPI DT nodesMarek Vasut2018-04-175-0/+40
| | | | | | | Add device tree nodes for the Renesas RPC HF/QSPI controller. Signed-off-by: Marek Vasut <marek.vasut+renesas@gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu@nigauri.org>
* Prepare v2018.05-rc2Tom Rini2018-04-161-1/+1
| | | | Signed-off-by: Tom Rini <trini@konsulko.com>
* serial: Remove duplicated line in MakefilePatrice Chotard2018-04-161-1/+0
| | | | | | | | | | | The line "-obj-$(CONFIG_STM32_SERIAL) += serial_stm32.o" is found twice in Makefile. Fixes: ae74de0dfd45 ("serial: stm32: Rename serial_stm32x7.c to serial_stm32.c" Signed-off-by: Patrice Chotard <patrice.chotard@st.com> Acked-by: Vikas Manocha <vikas.manocha@st.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* doc: Update git-mailrc entry for lukma (lukma@denx.de)Lukasz Majewski2018-04-161-1/+1
| | | | Signed-off-by: Lukasz Majewski <lukma@denx.de>
* env: mmc/fat/ext4: undefined reference to `mmc_initialize'Heinrich Schuchardt2018-04-162-0/+4
| | | | | | | | | | For CONFIG_ENV_FAT_INTERFACE != 'mmc' a link error env/fat.c:93: undefined reference to `mmc_initialize' occurs if CONFIG_MMC_SUPPORT is not enabled. Fixes: 26862b4a40c3 ("env: mmc/fat/ext4: make sure that the MMC sub-system is initialized before using it") Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
* env: Relocate env drivers if manual reloc is requiredSiva Durga Prasad Paladugu2018-04-163-0/+27
| | | | | | | | | | Relocate env drivers if manual relocation is enabled. This patch fixes the issue of u-boot hang incase if env is present in any of the flash devices. Signed-off-by: Siva Durga Prasad Paladugu <sivadur@xilinx.com> Signed-off-by: Michal Simek <michal.simek@xilinx.com> Reviewed-by: Simon Glass <sjg@chromium.org>
* Kconfig: Enlarge default SYS_MALLOC_F_LEN for AM33XXSjoerd Simons2018-04-161-0/+1
| | | | | | | | | | | | | Since commit 8e14ba7bd524 ("gpio: omap_gpio: Add DM_FLAG_PRE_RELOC flag") omap GPIO gets bound before relocation. Unfortunately due to this, on at least the beaglebone black, the pre-relocation memory pool gets exhausted before probing the serial port. This then causes u-boot to panic as CONFIG_REQUIRE_SERIAL_CONSOLE is set... Resolve this by resizing the default size of the pre-relocation malloc pool for AM335X platforms. Signed-off-by: Sjoerd Simons <sjoerd.simons@collabora.co.uk>
* part: Disable CONFIG_SPL_ISO_PARTITION by defaultAlexander Graf2018-04-16179-179/+0
| | | | | | | | | | | | | | | | We enabled CONFIG_ISO_PARTITION by default for distro boot, so that U-Boot could load distro images that usually get shipped as iso images. These images usually come with a board agnostic boot environment. However, there is very little point in having ISO support enabled (for anyone really) in SPL, as the whole idea of SPL is to load U-Boot proper which again is board specific. So the fact that we enable ISO support in U-Boot proper does not mean at all that we want ISO support in U-Boot SPL. Hence, let's remove the Kconfig dependency. Along the way, let's also clean up all those default configs that disabled SPL ISO support. Signed-off-by: Alexander Graf <agraf@suse.de>
* Merge git://git.denx.de/u-boot-x86Tom Rini2018-04-1626-298/+465
|\
| * x86: Rename coreboot-x86 to corebootSimon Glass2018-04-163-2/+2
| | | | | | | | | | | | | | | | | | We only use coreboot as a target on x86 platforms, since on ARM platforms U-Boot always runs as the primary boot loader. Rename the coreboot-x86 platform to reflect this. Signed-off-by: Simon Glass <sjg@chromium.org> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * doc: vxworks: Update x86 specific instructionsBin Meng2018-04-161-2/+19
| | | | | | | | | | | | | | This updates the doc of booting VxWorks, like loading an x64 kernel, and how to make VxWorks graphics console driver work. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
| * bootvx: x86: Assign bootaddr based on kernel memory baseBin Meng2018-04-162-41/+49
| | | | | | | | | | | | | | | | On VxWorks x86 its bootline address is at a pre-defined offset @ 0x1200. If 'bootaddr' is not passed via environment variable, we assign its value based on the kernel memory base address. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
| * bootvx: Exit if bootline address is not specifiedBin Meng2018-04-161-56/+53
| | | | | | | | | | | | Exit the 'bootvx' command if bootline address is not specified. Signed-off-by: Bin Meng <bmeng.cn@gmail.com>
| * bootvx: Refactor the bootline copy codes a little bitBin Meng2018-04-161-10/+5
| | | | | | | | | | | | | | | | There is a small duplication in do_bootvx() that does the bootline copy. Refactor this a little bit to make it simpler. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * bootvx: x86: Make VxWorks EFI console driver happyBin Meng2018-04-162-0/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When booting from EFI BIOS, VxWorks bootloader stores the EFI GOP framebuffer info at a pre-defined offset @ 0x6100. When VxWorks kernel boots up, its EFI console driver tries to find such a block and if the signature matches, the framebuffer information will be used to initialize the driver. However it is not necessary to prepare an EFI environment for VxWorks's EFI console driver to function (eg: EFI loader in U-Boot). If U-Boot has already initialized the graphics card and set it to a VESA mode that is compatible with EFI GOP, we can simply prepare such a block for VxWorks. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * pci: video: Only print out when everything is OKBin Meng2018-04-161-3/+1
| | | | | | | | | | | | | | | | | | If video initialization fails, the "Video:" output message will be mixed with the next console log. Change to print out such message only when everything is OK, which improves the boot log readability. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * x86: Change default FRAMEBUFFER_VESA_MODE of some boardsBin Meng2018-04-166-6/+6
| | | | | | | | | | | | | | | | This changes some boards' default FRAMEBUFFER_VESA_MODE to use 32-bit pixel format for better VxWorks compatibility. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * video: vesa: Change default FRAMEBUFFER_VESA_MODEBin Meng2018-04-161-1/+1
| | | | | | | | | | | | | | | | This changes the default FRAMEBUFFER_VESA_MODE to use 32-bit pixel format for better VxWorks compatibility. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * bios: vesa: Guard setting vesa mode with CONFIG_FRAMEBUFFER_SET_VESA_MODEBin Meng2018-04-162-0/+8
| | | | | | | | | | | | | | | | | | If CONFIG_FRAMEBUFFER_SET_VESA_MODE is not set, don't switch graphics card to VESA mode. This applies to both native mode and emulator mode of running the VGA BIOS. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * elf: Add a very simple ELF64 loaderBin Meng2018-04-161-1/+43
| | | | | | | | | | | | | | | | This adds a very simple ELF64 loader via program headers, similar to load_elf_image_phdr() that we already have. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * elf: Add ELF64 related structure definesBin Meng2018-04-161-0/+43
| | | | | | | | | | | | | | | | This adds ELF header, program header and section header structure defines for the 64-bit ELF image. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * elf: Clean up the ELF header fileBin Meng2018-04-161-146/+138
| | | | | | | | | | | | | | | | | | | | | | | | Fix various style violations in elf.h - use correct comment format if the comment fits in just one line - remove the ending period for the one-line comment - use tab for the indention instead of space - put the opening brace at the same line of a typedef/union - remove <name> in a 'typedef struct' for consistency Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * x86: Rename e820entry to e820_entryBin Meng2018-04-169-13/+13
| | | | | | | | | | | | | | | | This changes 'struct e820entry' to 'struct e820_entry' to conform with the coding style. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * x86: Use 'unsigned int' in install_e820_map() functionsBin Meng2018-04-166-11/+17
| | | | | | | | | | | | | | | | | | This fixes the following checkpatch warning: warning: Prefer 'unsigned int' to bare use of 'unsigned' Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * vxworks: x86: Rename e820info to e820_infoBin Meng2018-04-162-4/+4
| | | | | | | | | | | | | | | | This changes 'struct e820info' to 'struct e820_info' to conform with the coding style. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * bootvx: x86: Explicitly clear the bootloader image sizeBin Meng2018-04-162-0/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | VxWorks bootloader stores its size at a pre-defined offset @ 0x5004. Later when VxWorks kernel boots up and system memory information is retrieved from the E820 table, the bootloader size will be subtracted from the total system memory size to calculate the size of available memory for the OS. Explicitly clear the bootloader image size otherwise if memory at this offset happens to contain some garbage data, the final available memory size for the kernel is insane. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Simon Glass <sjg@chromium.org>
| * bootvx: x86: Prepare e820 related stuff from the given kernel memory base ↵Bin Meng2018-04-163-27/+23
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | address At present two environment variables 'e820data'/'e820info' are required to boot a VxWorks x86 kernel, but this is superfluous. The offset of these two tables are actually at a fixed offset from the kernel memory base address and we can provide the kernel memory base address to U-Boot via only one variable 'vx_phys_mem_base'. Note as it name indicates, the physical address should be provided. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * doc: vxworks: Minor update for clarityBin Meng2018-04-161-5/+5
| | | | | | | | | | | | | | This corrects a typo and updates several places for clarity. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Reviewed-by: Christian Gmeiner <christian.gmeiner@gmail.com>
| * x86: Update the io.h file to use {out|in}_{be|le}X macrosLukasz Majewski2018-04-161-17/+17
| | | | | | | | | | | | | | | | | | | | | | | | | | The commit 3f70a6f57734 ("x86: Add clr/setbits functions") introduced the {read|write}_ macros to manipulate data. Those macros are not used by any code in the u-boot project (despite the io.h itself). Other architectures use io.h with {in|out}_* macros. This commit brings some unification across u-boot supported architectures. Signed-off-by: Lukasz Majewski <lukma@denx.de> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
| * x86: Add 64-bit memory-mapped I/O functionsIvan Gorinov2018-04-161-0/+4
| | | | | | | | | | | | | | | | | | | | | | Add readq() and writeq() definitions for x86. Please note: in 32-bit code readq/writeq will generate two 32-bit memory access instructions instead of one atomic 64-bit operation. Signed-off-by: Ivan Gorinov <ivan.gorinov@intel.com> Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com> Reviewed-by: Bin Meng <bmeng.cn@gmail.com>
* | Merge git://git.denx.de/u-boot-cfi-flashTom Rini2018-04-161-10/+11
|\ \ | |/ |/|
| * mtd: cfi_flash: Make live-tree compatibleMario Six2018-04-161-10/+11
|/ | | | | | | Make the cfi_flash driver compatible with a live device tree. Signed-off-by: Mario Six <mario.six@gdsys.cc> Signed-off-by: Stefan Roese <sr@denx.de>
* Merge git://git.denx.de/u-boot-imxTom Rini2018-04-1569-1329/+1439
|\ | | | | | | Signed-off-by: Tom Rini <trini@konsulko.com>
| * mx6cuboxi: Fix some memory configuration errorsJon Nettleton2018-04-151-2/+1
| | | | | | | | | | | | | | | | These changes bring mainline back into line with the configurations that were originally set in our stable BSP. Signed-off-by: Jon Nettleton <jon@solid-run.com> Signed-off-by: Fabio Estevam <fabio.estevam@nxp.com>
| * imx: Create distinct pre-processed mkimage config filesTrent Piepho2018-04-151-7/+8
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Each imx image is created by a separate sub-make and during this process the mkimage config file is run though cpp. The cpp output is to the same file no matter what imx image is being created. This means if two imx images are generated in parallel they will attempt to independently produce the same pre-processed mkimage config file at the same time. Avoid the problem by making the pre-processed config file name unique based on the imx image it will be used in. This way each image will create a unique config file and they won't clobber each other when run in parallel. This should fixed the build bug referenced in b5b0e4e3 ("imximage: Remove failure when no IVT offset is found"). Cc: Breno Lima <breno.lima@nxp.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Trent Piepho <tpiepho@impinj.com> Tested-by: Fabio Estevam <fabio.estevam@nxp.com>
| * mx31ads: DeleteTom Rini2018-04-159-687/+0
| | | | | | | | | | | | This platform has been marked as orphaned since September 2013, remove. Signed-off-by: Tom Rini <trini@konsulko.com>
| * imx31_phycore: DeleteTom Rini2018-04-1512-568/+0
| | | | | | | | | | | | This platform has been marked as orphaned since September 2013, remove. Signed-off-by: Tom Rini <trini@konsulko.com>
| * pico-imx7d: Replace fatload commandVanessa Maegima2018-04-152-2/+3
| | | | | | | | | | | | | | Replace fatload with the fs generic loading interface ('load' command). Signed-off-by: Vanessa Maegima <vanessa.maegima@nxp.com> Reviewed-by: Fabio Estevam <fabio.estevam@nxp.com>
| * imx: mx7: snvs: Add an SNVS init routineBryan O'Donoghue2018-04-154-1/+26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Working with HAB on the i.MX7 we've encountered a case where a board that successfully authenticates u-boot when booting Linux via OPTEE subsequently fails to properly bring up the RTC. The RTC registers live in the low-power block of the Secure Non-Volatile Storage (SNVS) block. The root cause of the error has been traced to the HAB handing off the SNVS-RTC in a state where HPCOMR::NPSWA_EN = 0 in other words where the Non-Privileged Software Access Enable bit is zero. In ordinary circumstances this is OK since we typically do not run in TZ mode, however when we boot via HAB and enablng TrustZone, it is required to set HPCOMR::NPSWA_EN = 1 in order for the upstream Linux driver to have sufficient permissions to manipulate the SNVS-LP block. On our reference board it is the difference between Linux doing this: root@imx7s-warp-mbl:~# dmesg | grep rtc snvs_rtc_enable read 0x00000000 from SNVS_LPLR @ 0x00000034 snvs_rtc_enable read 0x00000021 from SNVS_LPCR @ 0x00000038 snvs_rtc_enable read 0x00000000 from SNVS_HPLR @ 0x00000000 snvs_rtc_enable read 0x80002100 from SNVS_HPCOMR @ 0x00000004 snvs_rtc 30370000.snvs:snvs-rtc-lp: rtc core: registered 30370000.snvs:snvs-rtc-lp as rtc0 snvs_rtc 30370000.snvs:snvs-rtc-lp: setting system clock to2018-04-01 00:51:04 UTC (1522543864) and doing this: root@imx7s-warp-mbl:~# dmesg | grep rtc snvs_rtc_enable read 0x00000000 from SNVS_LPLR @ 0x00000034 snvs_rtc_enable read 0x00000020 from SNVS_LPCR @ 0x00000038 snvs_rtc_enable read 0x00000001 from SNVS_HPLR @ 0x00000000 snvs_rtc_enable read 0x00002020 from SNVS_HPCOMR @ 0x00000004 snvs_rtc 30370000.snvs:snvs-rtc-lp: failed to enable rtc -110 snvs_rtc: probe of 30370000.snvs:snvs-rtc-lp failed with error -110 hctosys: unable to open rtc device (rtc0) Note bit 1 of LPCR is not set in the second case and is set in the first case and that bit 31 of HPCOMR is set in the second case but not in the first. Setting NPSWA_EN in HPCOMR allows us to boot through enabling TrustZone and continue onto the kernel. The kernel then has the necessary permissions to set LPCR::SRTC_ENV (RTC enable in the LP command register) whereas in contrast - in the failing case the non-privileged kernel cannot do so. This patch adds a simple init_snvs() call which sets the permission-bit called from soc.c for the i.MX7. It may be possible, safe and desirable to perform this on other i.MX processors but for now this is only tested on i.MX7 as working. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
| * boot: script: The boot.scr file for K+P's boardsLukasz Majewski2018-04-151-0/+96
| | | | | | | | | | | | | | | | | | | | | | By using this file one can avoid cluttering <board>.h file with u-boot HUSH commands necessary for booting target device. With such approach the commands are stored only in one place and can be reused if needed. Signed-off-by: Lukasz Majewski <lukma@denx.de> Reviewed-by: Stefano Babic <sbabic@denx.de>
| * imx: board: Add support for the K+P's kp_imx6q_tpc boardLukasz Majewski2018-04-158-0/+863
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit provides support for Kieback & Peter GmbH IMX6Q based TPC board. U-boot console output: U-Boot SPL 2018.05-rc1-00005-g631e2d01fd (Apr 04 2018 - 21:16:24 +0200) Trying to boot from MMC1 U-Boot 2018.05-rc1-00005-g631e2d01fd (Apr 04 2018 - 21:16:24 +0200) CPU: Freescale i.MX6Q rev1.5 996 MHz (running at 792 MHz) CPU: Extended Commercial temperature grade (-20C to 105C) at 37C Reset cause: POR Board: K+P KP_IMX6Q_TPC i.MX6Q Watchdog enabled I2C: ready DRAM: 2 GiB MMC: FSL_SDHC: 0, FSL_SDHC: 1 Loading Environment from MMC... OK In: serial Out: serial Err: serial Net: FEC [PRIME] Autoboot in 3 seconds
| * board: ge: bx50v3: enable backlight on demandIan Ray2018-04-152-17/+29
| | | | | | | | | | | | | | | | | | Enable display backlight only if a message needs to be displayed. The kernel re-initializes the backlight, which results in some unwanted artifacts. Signed-off-by: Ian Ray <ian.ray@ge.com> Signed-off-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
| * arm: imx: Add Winbond SPI-NOR support for Advantech DMS-BA16 boardKen Lin2018-04-152-0/+2
| | | | | | | | | | | | Windbond's been in the AVL list and need to enable the support Signed-off-by: Ken Lin <yungching0725@gmail.com>
| * imx: hab: Provide hab_auth_img_or_fail commandBryan O'Donoghue2018-04-151-0/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch adds hab_auth_img_or_fail() a command line function that encapsulates a common usage of authenticate and failover, namely if authenticate image fails, then drop to BootROM USB recovery mode. For secure-boot systems, this type of locked down behavior is important to ensure no unsigned images can be run. It's possible to script this logic but, when done over and over again the environment starts get very complex and repetitive, reducing that script repetition down to a command line function makes sense. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Cc: Utkarsh Gupta <utkarsh.gupta@nxp.com> Cc: Breno Lima <breno.lima@nxp.com> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Tested-by: Breno Lima <breno.lima@nxp.com>
| * imximage: Encase majority of header in __ASSEMBLY__ declarationBryan O'Donoghue2018-04-151-0/+2
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Subsequent patches will want to include imageimage.h but in doing so include it on an assembly compile path causing a range of compile errors. Fix the errors pre-emptively by encasing the majority of the declarations in imximage.h inside an ifdef __ASSEMBLY__ block. Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Cc: Utkarsh Gupta <utkarsh.gupta@nxp.com> Cc: Breno Lima <breno.lima@nxp.com> Cc: Fabio Estevam <fabio.estevam@nxp.com> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org> Tested-by: Breno Lima <breno.lima@nxp.com>
generated by cgit (git 2.34.1) at 2024-09-13 16:57:28 +0000