Enable eSDHC device module for P5040DS board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Enable eSDHC device module for P4080DS board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Enable eSDHC device module for P3041DS board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Enable eSDHC device module for P2041RDB board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Enable eSDHC device module for P2020RDB board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Enable eSDHC device module for P1020RDB board
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Use block layer to read from mmc
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Reviewed-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to t4240 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to t104x dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to t102x dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p5040 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p4080 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p3041 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p2041 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p2020 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

Add eSDHC node to p1020 dts
Signed-off-by: NYinbo Zhu <yinbo.zhu@nxp.com>
Signed-off-by: NPriyanka Jain <priyanka.jain@nxp.com>

- Clean vid/pid in Kconfig and add fastboot for rk3399
- add 'u-boot, spl-fifo-mode' for mmc
- Use FIT generator for rk3229 optee and rk3368 ATF
- fan53555: add support for Silergy SYR82X and SYR83X

- More travis job splits
- Assorted build clean-ups
- Correct optimization flags for some ARMv6 platforms

In GCC 9 support for the Armv5 and Armv5E architectures (which have no
known implementations) has been removed, cf.
https://gcc.gnu.org/gcc-9/changes.html

ARM11 is an armv6 implementation. So change the architecture flag for the
compiler to armv6 for ARM11.
Suggested-by: NFabio Estevam <festevam@gmail.com>
Signed-off-by: NHeinrich Schuchardt <xypron.glpk@gmx.de>
Reviewed-by: NFabio Estevam <festevam@gmail.com>

Now that we have buildman telling genboards.cfg to use an output
directory we need to ensure that it exists.

Cc: Bin Meng <bmeng.cn@gmail.com>
Cc: Simon Glass <sjg@chromium.org>
Fixes: bc750bca ("tools: buildman: Honor output directory when generating boards.cfg")
Signed-off-by: NTom Rini <trini@konsulko.com>
Reviewed-by: NBin Meng <bmeng.cn@gmail.com>

Add __pycache__ to ignored files and extend the rule for _libfdt to also
include generated shared objects (e.g. _libfdt.cpython-37m-x86_64-linux-gnu.so).
Signed-off-by: NBartosz Golaszewski <bgolaszewski@baylibre.com>

With the move to using Python 3 for real, we encounter two different
issues.  First, the file include/video_font_data.h includes at least one
UTF-16 character.  Given that it does not include any CONFIG symbols it
is easiest to just ignore this file.  Next, we encounter similar
problems with some dts/dtsi files that come from Linux.  In this case
it's easiest to simply ignore all dts/dtsi files as there will not be
CONFIG symbols for us to migrate in them.

Cc: Masahiro Yamada <yamada.masahiro@socionext.com>
Signed-off-by: NTom Rini <trini@konsulko.com>

As part of loading trustedfirmware, the SPL is required to place portions
of code into the socs sram but the mmc controllers can only do dma
transfers into the regular memory, not sram.

The results of this are not directly visible in u-boot itself, but
manifest as security-relate cpu aborts during boot of for example Linux.

There were a number of attempts to solve this elegantly but so far
discussion is still ongoing, so to make the board at least boot correctly
put both mmc controllers into fifo-mode, which also circumvents the
issue for now.
Signed-off-by: NHeiko Stuebner <heiko.stuebner@theobroma-systems.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>

Rockchips dwmmc controllers can't do dma to non-ddr addresses,
like for example the soc-internal sram but during boot parts of
TrustedFirmware need to be placed there from the read FIT image.

So add handling for a u-boot,spl-fifo-mode to not put the mmc
controllers into fifo mode for all time.

The regular fifo-mode property still takes precedent and only
if not set do we check for the spl-specific property.
Suggested-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
Signed-off-by: NHeiko Stuebner <heiko.stuebner@theobroma-systems.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
Signed-off-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>
Reviewed-by: NPhilipp Tomsich <philipp.tomsich@theobroma-systems.com>

Enable DWC3 core, gadget for rock960 board.

This would help to use fastboot by default.
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Setup dwc3_device structure for non-dm gadgets, which is used
in rk3399 platforms.

dwc3_device would have basic regbase, dr_mode, high speed
and 16-bit UTMI+ etc.

Cc: Marek Vasut <marex@denx.de>
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>
(Fix to use CONFIG_USB_DWC3_GADGET instead of CONFIG_USB_DWC3)
Signed-off-by: NKever Yang <kever.yang@rock-chips.com>

The 'debug' and 'printf' functions were previously added to the list of
logFunctions in commit 0cab4211 ("checkpatch.pl: Add 'debug' to
the list of logFunctions") and commit 397bfd46 ("checkpatch.pl:
Add 'printf' to logFunctions") but these additions were lost when newer
versions of checkpatch were pulled in from the upstream Linux
kernel version.

This restores them so that you don't end up in a situation where
checkpatch will give a warning for "quoted string split across lines"
which you cannot fix without getting a warning for "line over 80
characters" instead.
Signed-off-by: NJames Byrne <james.byrne@origamienergy.com>

remove from NXP arm32 all layerscape boards and
build them instead in already existing layerscape
jobs (which now not only build aarch64 boards)
Signed-off-by: NHeiko Schocher <hs@denx.de>

move orangepi builds into a new job, and exclude
orangepi builds from sunxi and rockchip jobs.
Signed-off-by: NHeiko Schocher <hs@denx.de>
Reviewed-by: NTom Rini <trini@konsulko.com>

Pull request for UEFI sub-system for efi-2020-01-rc4 (2)

Use CONFIG_EFI_LOADER=n for ARM11 except for the Raspberry Pi and the
Raspberry Pi Zero.

Add 0x330c for rk3399 gadget product number.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

U-Boot has two different variants of dwc3 initializations,
- with dm variant gadget, so the respective dm driver would
  call the dwc3_init in core.
- with non-dm variant gadget, so the usage board file would
  call dwc3_uboot_init in core.

The driver probe would handle all respective gadget properties
including phy interface via phy_type property and then trigger
dwc3_init for dm-variant gadgets.

So, to support the phy interface for non-dm variant gadgets,
the better option is dwc3_uboot_init since there is no
dedicated controller for non-dm variant gadgets.

This patch support for adding phy interface like 8/16-bit UTMI+
code for dwc3_uboot.

This change used Linux phy.h enum list, to make proper code
compatibility.

Cc: Marek Vasut <marex@denx.de>
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NMarek Vasut <marex@denx.de>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Technically the default mmc device for fastboot would
use eMMC if the board support for it.

Rockchip platform access device 0 for eMMC so, use the
same device number for rk3328.
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Select CONFIG_FASTBOOT_FLASH, CONFIG_FASTBOOT_FLASH_MMC_DEV
for rockchip SoC plaforms in fastboot Kconfig file instead
of defined it in board defconfig.

This eventually drop the explicit configs defined in
supporting board defconfig files.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Add 0x310c for rk3128 gadget product number.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Rockchip support differnet or common gadget product number
between Rockchip SoCs like,

0x310a - rk3036
0x320a - rk3229, rk3288
0x330a - rk3328

So, select them on Kconfig based on platform specific
config defined.
   
This eventually drop the explicit configs defined in
supporting board defconfig files.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Gadget vendor number, 0x2207 is common across all platfroms
supported in Rockchip SoC.

So, select the same number globally, if ARCH_ROCKCHIP.

This eventually drop the explicit configs defined in supported
board defconfig files.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

Select the gadget manufacturer as 'Rockchip' for
all rockchip platform SoC's.

This eventually drop the explicit defined added
on supported board defconfig files.
Tested-by: NLevin Du <djw@t-chip.com.cn>
Signed-off-by: NJagan Teki <jagan@amarulasolutions.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

fan53555_regulator_set_value() passes its own dev to pmic_clrsetbits()
instead of its parent (pmic). As result u-boot crashes when you try to
set voltage on fan53555 regulator
Signed-off-by: NVasily Khoruzhick <anarsoul@gmail.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>

That's not correct and it breaks SMBUS-style reads and and writes for
some chips (e.g. SYR82X/SYR83X).

Stop bit should be sent only after the last message.
Signed-off-by: NVasily Khoruzhick <anarsoul@gmail.com>
Reviewed-by: NKever Yang <kever.yang@rock-chips.com>