April 2019 - U-Boot

Re: [U-Boot] [U-Boot, 3/4] rockchip: rk3399: Add Orangepi RK3399 support
by Jagan Teki 22 Apr '19

22 Apr '19

Hi Steven, On Mon, Apr 22, 2019 at 2:51 PM zhaoyifan <zhao_steven(a)263.net> wrote: > > Hi friend, > > > > Could you please advice the the problem with RK3399 in detail? Sorry, couldn't get which issue are you talking about? Mainline u-boot work well on OrangePI, if you want to look refer the doc patch[1] or wiki[2] for more information. [1] https://patchwork.ozlabs.org/patch/1086231/ [2] https://wiki.amarulasolutions.com/bsp/rockchip/rk3399/orangepi.html

1 0

[U-Boot] [PATCH v2] board_r: Detect ifc-nor flash at run-time
by Pankit Garg 22 Apr '19

22 Apr '19

CONFIG_MTD_NOR_FLASH flag needs to be enable for all boot sources,as all flash drivers need to compile in TFA Boot.Probe ifc nor flash only when there is nor flash available on board.So needs to detect ifc-nor flash at run-time for probing. Signed-off-by: Pankit Garg <pankit.garg(a)nxp.com> --- changes for v2: - change commit id subject common/board_r.c | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/common/board_r.c b/common/board_r.c index 472987d..681379c 100644 --- a/common/board_r.c +++ b/common/board_r.c @@ -327,11 +327,19 @@ static int initr_manual_reloc_cmdtable(void) #endif #if defined(CONFIG_MTD_NOR_FLASH) +__weak int is_flash_available(void) +{ + return 1; +} + static int initr_flash(void) { ulong flash_size = 0; bd_t *bd = gd->bd; + if (!is_flash_available()) + return 0; + puts("Flash: "); if (board_flash_wp_on()) -- 1.9.1

1 0

[U-Boot] [PATCH] at91: corvus_defconfig: get rid of build warnings
by Heiko Schocher 22 Apr '19

22 Apr '19

fix CONFIG_OF_EMBED and add CONFIG_DM_USB build warnings. Signed-off-by: Heiko Schocher <hs(a)denx.de> --- tree builds fine on travis, see: https://travis-ci.org/hsdenx/u-boot/builds/520165307 configs/corvus_defconfig | 6 ++++-- include/configs/corvus.h | 1 + 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/configs/corvus_defconfig b/configs/corvus_defconfig index a1af2f1342..af159ecb47 100644 --- a/configs/corvus_defconfig +++ b/configs/corvus_defconfig @@ -18,6 +18,7 @@ CONFIG_USE_BOOTARGS=y CONFIG_BOOTARGS="console=ttyS0,115200 earlyprintk mtdparts=atmel_nand:256k(bootstrap)ro,512k(uboot)ro,256k(env),256k(env_redundant),256k(spare),512k(dtb),6M(kernel)ro,-(rootfs) root=/dev/mtdblock7 rw rootfstype=jffs2" # CONFIG_DISPLAY_BOARDINFO is not set CONFIG_BOARD_EARLY_INIT_F=y +CONFIG_SPL_SYS_MALLOC_SIMPLE=y CONFIG_SPL_NAND_SUPPORT=y CONFIG_HUSH_PARSER=y CONFIG_SYS_PROMPT="U-Boot> " @@ -34,10 +35,11 @@ CONFIG_CMD_USB=y CONFIG_CMD_DHCP=y CONFIG_CMD_PING=y CONFIG_CMD_MTDPARTS=y +CONFIG_DOS_PARTITION=y CONFIG_OF_CONTROL=y -CONFIG_OF_EMBED=y CONFIG_DEFAULT_DEVICE_TREE="at91sam9g45-corvus" CONFIG_ENV_IS_IN_NAND=y +CONFIG_BLK=y CONFIG_CLK=y CONFIG_CLK_AT91=y CONFIG_DFU_NAND=y @@ -47,8 +49,8 @@ CONFIG_NAND_ATMEL=y CONFIG_PHYLIB=y CONFIG_ATMEL_USART=y CONFIG_USB=y +CONFIG_DM_USB=y CONFIG_USB_EHCI_HCD=y -CONFIG_USB_STORAGE=y CONFIG_USB_GADGET=y CONFIG_USB_GADGET_MANUFACTURER="Siemens AG" CONFIG_USB_GADGET_VENDOR_NUM=0x0908 diff --git a/include/configs/corvus.h b/include/configs/corvus.h index 749a67d4b0..e85f684e32 100644 --- a/include/configs/corvus.h +++ b/include/configs/corvus.h @@ -72,6 +72,7 @@ #define CONFIG_SYS_NAND_MASK_CLE (1 << 22) #define CONFIG_SYS_NAND_ENABLE_PIN AT91_PIN_PC14 #define CONFIG_SYS_NAND_READY_PIN AT91_PIN_PC8 +#define CONFIG_SYS_NAND_DRIVER_ECC_LAYOUT #endif /* Ethernet */ -- 2.17.2

2 1

[U-Boot] [PATCH 1/4] rockchip: dts: rk3399: Sync rk3399-opp from Linux
by Jagan Teki 22 Apr '19

22 Apr '19

Sync rk3399-opp.dtsi from Linux. Linux commit details about the rk3399-opp.dtsi sync: "arm64: dts: rockchip: use SPDX-License-Identifier" (sha1: 4ee99cebd486238ac433da823b95cc5f8d8a6905) Signed-off-by: Jagan Teki <jagan(a)amarulasolutions.com> --- arch/arm/dts/rk3399-opp.dtsi | 133 +++++++++++++++++++++++++++++++++++ 1 file changed, 133 insertions(+) create mode 100644 arch/arm/dts/rk3399-opp.dtsi diff --git a/arch/arm/dts/rk3399-opp.dtsi b/arch/arm/dts/rk3399-opp.dtsi new file mode 100644 index 0000000000..d6f1095abb --- /dev/null +++ b/arch/arm/dts/rk3399-opp.dtsi @@ -0,0 +1,133 @@ +// SPDX-License-Identifier: (GPL-2.0+ OR MIT) +/* + * Copyright (c) 2016-2017 Fuzhou Rockchip Electronics Co., Ltd + */ + +/ { + cluster0_opp: opp-table0 { + compatible = "operating-points-v2"; + opp-shared; + + opp00 { + opp-hz = /bits/ 64 <408000000>; + opp-microvolt = <800000>; + clock-latency-ns = <40000>; + }; + opp01 { + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <800000>; + }; + opp02 { + opp-hz = /bits/ 64 <816000000>; + opp-microvolt = <850000>; + }; + opp03 { + opp-hz = /bits/ 64 <1008000000>; + opp-microvolt = <925000>; + }; + opp04 { + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt = <1000000>; + }; + opp05 { + opp-hz = /bits/ 64 <1416000000>; + opp-microvolt = <1125000>; + }; + }; + + cluster1_opp: opp-table1 { + compatible = "operating-points-v2"; + opp-shared; + + opp00 { + opp-hz = /bits/ 64 <408000000>; + opp-microvolt = <800000>; + clock-latency-ns = <40000>; + }; + opp01 { + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <800000>; + }; + opp02 { + opp-hz = /bits/ 64 <816000000>; + opp-microvolt = <825000>; + }; + opp03 { + opp-hz = /bits/ 64 <1008000000>; + opp-microvolt = <875000>; + }; + opp04 { + opp-hz = /bits/ 64 <1200000000>; + opp-microvolt = <950000>; + }; + opp05 { + opp-hz = /bits/ 64 <1416000000>; + opp-microvolt = <1025000>; + }; + opp06 { + opp-hz = /bits/ 64 <1608000000>; + opp-microvolt = <1100000>; + }; + opp07 { + opp-hz = /bits/ 64 <1800000000>; + opp-microvolt = <1200000>; + }; + }; + + gpu_opp_table: opp-table2 { + compatible = "operating-points-v2"; + + opp00 { + opp-hz = /bits/ 64 <200000000>; + opp-microvolt = <800000>; + }; + opp01 { + opp-hz = /bits/ 64 <297000000>; + opp-microvolt = <800000>; + }; + opp02 { + opp-hz = /bits/ 64 <400000000>; + opp-microvolt = <825000>; + }; + opp03 { + opp-hz = /bits/ 64 <500000000>; + opp-microvolt = <875000>; + }; + opp04 { + opp-hz = /bits/ 64 <600000000>; + opp-microvolt = <925000>; + }; + opp05 { + opp-hz = /bits/ 64 <800000000>; + opp-microvolt = <1100000>; + }; + }; +}; + +&cpu_l0 { + operating-points-v2 = <&cluster0_opp>; +}; + +&cpu_l1 { + operating-points-v2 = <&cluster0_opp>; +}; + +&cpu_l2 { + operating-points-v2 = <&cluster0_opp>; +}; + +&cpu_l3 { + operating-points-v2 = <&cluster0_opp>; +}; + +&cpu_b0 { + operating-points-v2 = <&cluster1_opp>; +}; + +&cpu_b1 { + operating-points-v2 = <&cluster1_opp>; +}; + +&gpu { + operating-points-v2 = <&gpu_opp_table>; +}; -- 2.18.0.321.gffc6fa0e3

2 8

[U-Boot] [PATCH v1] common: command: Add command execution tracer.
by Christoph Muellner 22 Apr '19

22 Apr '19

When using boot scripts it can become quite hard to understand which commands are actually executed during bootup (e.g. where is a kernel image loaded from or which DTB is in use). Shell scripts suffer from a similar problem and many shells address this problem with a command execution tracer (e.g. BASH has xtrace, which can be enabled by "set -x"). This patch introduces a command tracer for U-Boot, which prints every command with its arguments before it is executed. Signed-off-by: Christoph Muellner <christoph.muellner(a)theobroma-systems.com> --- cmd/Kconfig | 11 +++++++++++ common/command.c | 14 ++++++++++++++ 2 files changed, 25 insertions(+) diff --git a/cmd/Kconfig b/cmd/Kconfig index 0b07b3b9d77..eeadc3827cb 100644 --- a/cmd/Kconfig +++ b/cmd/Kconfig @@ -53,6 +53,17 @@ config SYS_PROMPT This string is displayed in the command line to the left of the cursor. +config SYS_XTRACE + string "Command execution tracer" + depends on CMDLINE + default y if CMDLINE + help + This option enables the possiblity to print all commands before + executing them and after all variables are evaluated (similar + to Bash's xtrace/'set -x' feature). + To enable the tracer a variable "xtrace" needs to be defined in + the environment. + menu "Autoboot options" config AUTOBOOT diff --git a/common/command.c b/common/command.c index e14d1fa1d6b..e192bb2a619 100644 --- a/common/command.c +++ b/common/command.c @@ -574,6 +574,20 @@ enum command_ret_t cmd_process(int flag, int argc, char * const argv[], enum command_ret_t rc = CMD_RET_SUCCESS; cmd_tbl_t *cmdtp; +#if defined(CONFIG_SYS_XTRACE) + char *xtrace; + + xtrace = env_get("xtrace"); + if (xtrace) { + puts("+"); + for (int i = 0; i < argc; i++) { + puts(" "); + puts(argv[i]); + } + puts("\n"); + } +#endif + /* Look up command in command table */ cmdtp = find_cmd(argv[0]); if (cmdtp == NULL) { -- 2.11.0

3 2

[U-Boot] [PATCH v2 00/13] sandbox: Tidy up initcall and tracing
by Simon Glass 22 Apr '19

22 Apr '19

This series started from a patch to make sandbox show a useful address when an initcall failed (an address that can be looked up in u-boot.map). Since then various other problems with addresses have been found, so this series now includes fixes for those also, as well as some clean-ups. Changes in v2: - Adjust code to allow it to work before relocation also - Update commit message to take account of initcall.h being in a header - Add documentation to README.sandbox - Add a new patch to Correct maths in allocation routines - Add a new patch to drop the printf() in setup_ram_buf() - Add new patch to move pre-console buffer out of the way of tracing - Add new patch to allow calling bootstage_mark() before bootstage_init() - Add new patch to increase the early-trace-buffer size for sandbox - Add new patch to drop use of header files in initcall.h - Add new patch to use kernel types in div64 - Add new patch to avoid instrumenting the division function - Add new patch to tidy up error returns in trace.c - Add new patch to enable the 'trace' command on sandbox when needed Simon Glass (13): sandbox: Improve debugging in initcall_run_list() sandbox: Correct maths in allocation routines sandbox: Drop the printf() in setup_ram_buf() sandbox: Move pre-console buffer out of the way of tracing bootstage: Allow calling bootstage_mark() before bootstage_init() sandbox: Increase the early-trace-buffer size initcall: Drop use of header files div64: Use kernel types div64: Don't instrument the division function trace: Tidy up error returns Convert CONFIG_TRACE to Kconfig Convert CONFIG_TRACE_BUFFER_SIZE et al to Kconfig sandbox: Enable the 'trace' command when tracing is used arch/sandbox/cpu/os.c | 59 ++++++++++++++++++---- arch/sandbox/cpu/start.c | 16 ++++-- arch/sandbox/include/asm/global_data.h | 1 + board/sandbox/README.sandbox | 46 +++++++++++++++++ cmd/Kconfig | 2 +- common/board_f.c | 2 +- common/bootstage.c | 7 +++ configs/sandbox_defconfig | 2 +- include/configs/sandbox.h | 4 +- include/div64.h | 70 +++++++++++++------------- include/initcall.h | 19 ++++--- include/os.h | 11 ++++ lib/Kconfig | 57 +++++++++++++++++++++ lib/div64.c | 20 +++++--- lib/trace.c | 17 ++++--- scripts/config_whitelist.txt | 5 -- 16 files changed, 258 insertions(+), 80 deletions(-) -- 2.21.0.392.gf8f6787159e-goog

2 26

[U-Boot] [PATCH] dm: core: Change platform specific translation-offset handling
by Stefan Roese 22 Apr '19

22 Apr '19

Testing has shown that the current DM implementation of a platform / board specific translation offset, as its needed for the SPL on MVEBU platforms is buggy. The translation offset is confingured too late, after the driver bind functions are run. This may result in incorrect address translations. With the current implementation its not possible to configure the offset earlier, as the DM code has not run at all. This patch now removed the set_/get_translation_offset() calls and moves the translation offset into the GD variable translation_offset. This variable will get used when CONFIG_TRANSLATION_OFFSET is enabled. This option is enabled only for MVEBU on ARM32 platforms, where its currenty needed and configured in the SPL. Signed-off-by: Stefan Roese <sr(a)denx.de> Cc: Pierre Bourdon <delroth(a)gmail.com> Cc: Baruch Siach <baruch(a)tkos.co.il> Cc: Simon Glass <sjg(a)chromium.org> Cc: Heiko Schocher <hs(a)denx.de> Cc: Tom Rini <trini(a)konsulko.com> --- arch/arm/mach-mvebu/Kconfig | 1 + arch/arm/mach-mvebu/spl.c | 12 +++++++++--- drivers/core/Kconfig | 9 +++++++++ drivers/core/fdtaddr.c | 9 ++++++--- drivers/core/root.c | 21 --------------------- include/asm-generic/global_data.h | 4 ++++ include/dm/fdtaddr.h | 21 --------------------- 7 files changed, 29 insertions(+), 48 deletions(-) diff --git a/arch/arm/mach-mvebu/Kconfig b/arch/arm/mach-mvebu/Kconfig index 7dda04e0e3..6d3429b6b1 100644 --- a/arch/arm/mach-mvebu/Kconfig +++ b/arch/arm/mach-mvebu/Kconfig @@ -14,6 +14,7 @@ config ARMADA_32BIT select SPL_OF_CONTROL select SPL_SIMPLE_BUS select SUPPORT_SPL + select TRANSLATION_OFFSET config ARMADA_64BIT bool diff --git a/arch/arm/mach-mvebu/spl.c b/arch/arm/mach-mvebu/spl.c index 9dd7c84b68..530b98c1aa 100644 --- a/arch/arm/mach-mvebu/spl.c +++ b/arch/arm/mach-mvebu/spl.c @@ -93,15 +93,21 @@ void board_init_f(ulong dummy) */ #endif + /* + * Use special translation offset for SPL. This needs to be + * configured *before* spl_init() is called as this function + * calls dm_init() which calls the bind functions of the + * device drivers. Here the base address needs to be configured + * (translated) correctly. + */ + gd->translation_offset = 0xd0000000 - 0xf1000000; + ret = spl_init(); if (ret) { debug("spl_init() failed: %d\n", ret); hang(); } - /* Use special translation offset for SPL */ - dm_set_translation_offset(0xd0000000 - 0xf1000000); - preloader_console_init(); timer_init(); diff --git a/drivers/core/Kconfig b/drivers/core/Kconfig index ddf2fb3fb8..2d195ae35e 100644 --- a/drivers/core/Kconfig +++ b/drivers/core/Kconfig @@ -225,6 +225,15 @@ config SPL_OF_TRANSLATE used for the address translation. This function is faster and smaller in size than fdt_translate_address(). +config TRANSLATION_OFFSET + bool "Platforms specific translation offset" + depends on DM && OF_CONTROL + help + Some platforms need a special address translation. Those + platforms (e.g. mvebu in SPL) can configure a translation + offset by enabling this option and setting the translation_offset + variable in the GD in their platform- / board-specific code. + config OF_ISA_BUS bool depends on OF_TRANSLATE diff --git a/drivers/core/fdtaddr.c b/drivers/core/fdtaddr.c index e113f1dd39..c2873861da 100644 --- a/drivers/core/fdtaddr.c +++ b/drivers/core/fdtaddr.c @@ -74,13 +74,16 @@ fdt_addr_t devfdt_get_addr_index(struct udevice *dev, int index) } } +#if defined(CONFIG_TRANSLATION_OFFSET) /* * Some platforms need a special address translation. Those * platforms (e.g. mvebu in SPL) can configure a translation - * offset in the DM by calling dm_set_translation_offset() that - * will get added to all addresses returned by devfdt_get_addr(). + * offset by setting this value in the GD and enaling this + * feature via CONFIG_TRANSLATION_OFFSET. This value will + * get added to all addresses returned by devfdt_get_addr(). */ - addr += dm_get_translation_offset(); + addr += gd->translation_offset; +#endif return addr; #else diff --git a/drivers/core/root.c b/drivers/core/root.c index e6ec7faf37..8fa096648e 100644 --- a/drivers/core/root.c +++ b/drivers/core/root.c @@ -25,10 +25,6 @@ DECLARE_GLOBAL_DATA_PTR; -struct root_priv { - fdt_addr_t translation_offset; /* optional translation offset */ -}; - static const struct driver_info root_info = { .name = "root_driver", }; @@ -52,22 +48,6 @@ void dm_fixup_for_gd_move(struct global_data *new_gd) } } -fdt_addr_t dm_get_translation_offset(void) -{ - struct udevice *root = dm_root(); - struct root_priv *priv = dev_get_priv(root); - - return priv->translation_offset; -} - -void dm_set_translation_offset(fdt_addr_t offs) -{ - struct udevice *root = dm_root(); - struct root_priv *priv = dev_get_priv(root); - - priv->translation_offset = offs; -} - #if defined(CONFIG_NEEDS_MANUAL_RELOC) void fix_drivers(void) { @@ -420,7 +400,6 @@ int dm_init_and_scan(bool pre_reloc_only) U_BOOT_DRIVER(root_driver) = { .name = "root_driver", .id = UCLASS_ROOT, - .priv_auto_alloc_size = sizeof(struct root_priv), }; /* This is the root uclass */ diff --git a/include/asm-generic/global_data.h b/include/asm-generic/global_data.h index 78dcf40bff..65ee3e5d5a 100644 --- a/include/asm-generic/global_data.h +++ b/include/asm-generic/global_data.h @@ -20,6 +20,7 @@ */ #ifndef __ASSEMBLY__ +#include <fdtdec.h> #include <membuff.h> #include <linux/list.h> @@ -133,6 +134,9 @@ typedef struct global_data { struct spl_handoff *spl_handoff; # endif #endif +#if defined(CONFIG_TRANSLATION_OFFSET) + fdt_addr_t translation_offset; /* optional translation offset */ +#endif } gd_t; #endif diff --git a/include/dm/fdtaddr.h b/include/dm/fdtaddr.h index c171d9bc2f..3bc2599b6c 100644 --- a/include/dm/fdtaddr.h +++ b/include/dm/fdtaddr.h @@ -120,25 +120,4 @@ fdt_addr_t devfdt_get_addr_size_index(struct udevice *dev, int index, */ fdt_addr_t devfdt_get_addr_name(struct udevice *dev, const char *name); -/** - * dm_set_translation_offset() - Set translation offset - * @offs: Translation offset - * - * Some platforms need a special address translation. Those - * platforms (e.g. mvebu in SPL) can configure a translation - * offset in the DM by calling this function. It will be - * added to all addresses returned in devfdt_get_addr(). - */ -void dm_set_translation_offset(fdt_addr_t offs); - -/** - * dm_get_translation_offset() - Get translation offset - * - * This function returns the translation offset that can - * be configured by calling dm_set_translation_offset(). - * - * @return translation offset for the device address (0 as default). - */ -fdt_addr_t dm_get_translation_offset(void); - #endif -- 2.21.0

4 3

[U-Boot] [PATCH] ARM: rmobile: Always select pin control drivers on Gen3
by Marek Vasut 22 Apr '19

22 Apr '19

To assure the pins on R-Car Gen3 SoCs are configured correctly, always select pin control drivers on Gen3 SoCs. Signed-off-by: Marek Vasut <marek.vasut+renesas(a)gmail.com> Cc: Nobuhiro Iwamatsu <iwamatsu(a)nigauri.org> --- arch/arm/mach-rmobile/Kconfig | 3 +++ 1 file changed, 3 insertions(+) diff --git a/arch/arm/mach-rmobile/Kconfig b/arch/arm/mach-rmobile/Kconfig index 5b5d96e665..38d7300dc7 100644 --- a/arch/arm/mach-rmobile/Kconfig +++ b/arch/arm/mach-rmobile/Kconfig @@ -14,6 +14,9 @@ config RCAR_GEN3 select PHY select CMD_CACHE select SUPPORT_SPL + select PINCTRL + select PINCONF + select PINCTRL_PFC imply CMD_FS_UUID imply CMD_GPT imply CMD_UUID -- 2.20.1

1 0

[U-Boot] [PATCH] pinctrl: renesas: Fix linker error when PINCTRL_PFC=n
by Eugeniu Rosca 22 Apr '19

22 Apr '19

With CONFIG_PINCTRL_PFC=n, aarch64-linux-gnu-ld reports: -----8<----- LD u-boot drivers/gpio/built-in.o: In function `rcar_gpio_request': drivers/gpio/gpio-rcar.c:128: undefined reference to `sh_pfc_config_mux_for_gpio' -----8<----- Fix it in the least intrusive way and *avoid* ifdefs in the *.c code. Some recent Linux commits sharing the same approach: - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… ("acpi, nfit: Add function to look up nvdimm device and provide SMBIOS handle") - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… ("spi: make OF helper available for others") - https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?… ("IB/uverbs: Add UVERBS_ATTR_FLAGS_IN to the specs language") Fixes: f6e545a73f88 ("pfc: rmobile: Add hook to configure pin as GPIO") Reported-by: Dirk Behme <dirk.behme(a)de.bosch.com> Signed-off-by: Eugeniu Rosca <erosca(a)de.adit-jv.com> --- drivers/pinctrl/renesas/sh_pfc.h | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/drivers/pinctrl/renesas/sh_pfc.h b/drivers/pinctrl/renesas/sh_pfc.h index b98c2f185d26..3d95d3c725cf 100644 --- a/drivers/pinctrl/renesas/sh_pfc.h +++ b/drivers/pinctrl/renesas/sh_pfc.h @@ -261,7 +261,15 @@ void sh_pfc_write(struct sh_pfc *pfc, u32 reg, u32 data); const struct pinmux_bias_reg * sh_pfc_pin_to_bias_reg(const struct sh_pfc *pfc, unsigned int pin, unsigned int *bit); +#if IS_ENABLED(CONFIG_PINCTRL_PFC) int sh_pfc_config_mux_for_gpio(struct udevice *dev, unsigned pin_selector); +#else +static inline +int sh_pfc_config_mux_for_gpio(struct udevice *dev, unsigned pin_selector) +{ + return -ENODEV; +} +#endif extern const struct sh_pfc_soc_info r8a7790_pinmux_info; extern const struct sh_pfc_soc_info r8a7791_pinmux_info; -- 2.21.0

4 14

[U-Boot] [PATCH 1/1] efi_loader: disable EFI_LOADER on vexpress_ca15_tc2 and ca9x4
by Heinrich Schuchardt 22 Apr '19

22 Apr '19

vexpress_ca15_tc2_defconfig and vexpress_ca9x4_defconfig do not provide device trees (as $fdtcontroladdr) as needed to pass our Travis CI tests. As we are on the move to requiring block devices to be based on the driver model these boards either will have to be converted to use device trees or will be kicked out of U-Boot. So let's disable CONFIG_EFI_LOADER on these boards until the device tree issue is resolved. Signed-off-by: Heinrich Schuchardt <xypron.glpk(a)gmx.de> --- configs/vexpress_ca15_tc2_defconfig | 1 + configs/vexpress_ca9x4_defconfig | 1 + 2 files changed, 2 insertions(+) diff --git a/configs/vexpress_ca15_tc2_defconfig b/configs/vexpress_ca15_tc2_defconfig index cabc0c4577..9bcbca5f24 100644 --- a/configs/vexpress_ca15_tc2_defconfig +++ b/configs/vexpress_ca15_tc2_defconfig @@ -32,3 +32,4 @@ CONFIG_SMC911X_32_BIT=y CONFIG_BAUDRATE=38400 CONFIG_CONS_INDEX=0 CONFIG_OF_LIBFDT=y +# CONFIG_EFI_LOADER is not set diff --git a/configs/vexpress_ca9x4_defconfig b/configs/vexpress_ca9x4_defconfig index 9390cf61d1..3350c88b20 100644 --- a/configs/vexpress_ca9x4_defconfig +++ b/configs/vexpress_ca9x4_defconfig @@ -31,3 +31,4 @@ CONFIG_SMC911X_32_BIT=y CONFIG_BAUDRATE=38400 CONFIG_CONS_INDEX=0 CONFIG_OF_LIBFDT=y +# CONFIG_EFI_LOADER is not set -- 2.20.1

1 0