July 2015 - U-Boot

[U-Boot] [PATCH] keystone2: net: add mcast function to keyston2 Ethernet driver
by Vitaly Andrianov 28 Jul '15

28 Jul '15

The MCAST_TFTP support requires that network drivers has mcast functon implemented. This commit adds dummy keystone2_eth_bcast_addr() to meet the requirement. As far as the driver doesn't use ALE and doesn't filter any incoming packets, the function is empty. Signed-off-by: Vitaly Andrianov <vitalya(a)ti.com> --- drivers/net/keystone_net.c | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/drivers/net/keystone_net.c b/drivers/net/keystone_net.c index e2adb67..b3ab13d 100644 --- a/drivers/net/keystone_net.c +++ b/drivers/net/keystone_net.c @@ -511,6 +511,13 @@ static int keystone2_eth_rcv_packet(struct eth_device *dev) return pkt_size; } +#ifdef CONFIG_MCAST_TFTP +static int keystone2_eth_bcast_addr(struct eth_device *dev, u32 ip, u8 set) +{ + return 0; +} +#endif + /* * This function initializes the EMAC hardware. */ @@ -536,6 +543,9 @@ int keystone2_emac_initialize(struct eth_priv_t *eth_priv) dev->halt = keystone2_eth_close; dev->send = keystone2_eth_send_packet; dev->recv = keystone2_eth_rcv_packet; +#ifdef CONFIG_MCAST_TFTP + dev->mcast = keystone2_eth_bcast_addr; +#endif eth_register(dev); -- 1.9.1

3 3

[U-Boot] [PATCH] keystone2: add wfi in to the core_spin loop
by Vitaly Andrianov 28 Jul '15

28 Jul '15

When core A turning of core B, via tetris DPSC it places the core B DPSC into transitional state. The core B has to execute wfi instruction to move its DPSC to the OFF state. This patch add such instruction. Signed-off-by: Vitaly Andrianov <vitalya(a)ti.com> --- arch/arm/mach-keystone/cmd_mon.c | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/arch/arm/mach-keystone/cmd_mon.c b/arch/arm/mach-keystone/cmd_mon.c index f9f58a3..73ceb83 100644 --- a/arch/arm/mach-keystone/cmd_mon.c +++ b/arch/arm/mach-keystone/cmd_mon.c @@ -55,8 +55,13 @@ U_BOOT_CMD(mon_install, 2, 0, do_mon_install, static void core_spin(void) { - while (1) - ; /* forever */; + while (1) { + asm volatile ( + "dsb\n" + "isb\n" + "wfi\n" + ); + } } int mon_power_on(int core_id, void *ep) -- 1.9.1

2 2

[U-Boot] [PATCH] misc: led: pca9551_led: Fix problem with multiple blink frequencies
by Stefan Roese 28 Jul '15

28 Jul '15

Only 2 frequencies are supported. The current driver implementation does not always use the 2 last configured blink frequencies. This patch fixes this problem. So that the last two entered frequencies are active. Signed-off-by: Stefan Roese <sr(a)denx.de> Cc: Fabio Estevam <fabio.estevam(a)freescale.com> Cc: Tom Rini <trini(a)konsulko.com> --- drivers/misc/pca9551_led.c | 32 ++++++++++++++++++++++---------- 1 file changed, 22 insertions(+), 10 deletions(-) diff --git a/drivers/misc/pca9551_led.c b/drivers/misc/pca9551_led.c index 79b1e20..d4034f6 100644 --- a/drivers/misc/pca9551_led.c +++ b/drivers/misc/pca9551_led.c @@ -32,7 +32,10 @@ struct pca9551_blink_rate { u8 pwm; /* Pulse width modulation, see PCA9551_7.pdf p. 6 */ }; -static int freq0, freq1; +static int freq_last = -1; +static int mask_last = -1; +static int idx_last = -1; +static int mode_last; static int pca9551_led_get_state(int led, int *state) { @@ -135,21 +138,30 @@ void __led_blink(led_id_t mask, int freq) { struct pca9551_blink_rate rate; int mode; - int blink; + int idx; - if ((freq0 == 0) || (freq == freq0)) { - blink = 0; - mode = PCA9551_LED_STATE_BLINK0; - freq0 = freq; + if ((freq == freq_last) || (mask == mask_last)) { + idx = idx_last; + mode = mode_last; } else { - blink = 1; - mode = PCA9551_LED_STATE_BLINK1; - freq1 = freq; + /* Toggle blink index */ + if (idx_last == 0) { + idx = 1; + mode = PCA9551_LED_STATE_BLINK1; + } else { + idx = 0; + mode = PCA9551_LED_STATE_BLINK0; + } + + idx_last = idx; + mode_last = mode; } + freq_last = freq; + mask_last = mask; rate.psc = ((freq * 38) / 1000) - 1; rate.pwm = 128; /* 50% duty cycle */ - pca9551_led_set_blink_rate(blink, rate); + pca9551_led_set_blink_rate(idx, rate); pca9551_led_set_state(mask, mode); } -- 2.4.5

2 1

[U-Boot] [PATCH 1/1] stm32f429-discovery: Use ttyS0 as the console device
by Kamil Lulko 28 Jul '15

28 Jul '15

Mainline kernel will be using this device name as well. Signed-off-by: Kamil Lulko <rev13(a)wp.pl> --- include/configs/stm32f429-discovery.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/configs/stm32f429-discovery.h b/include/configs/stm32f429-discovery.h index 46869dd..7406788 100644 --- a/include/configs/stm32f429-discovery.h +++ b/include/configs/stm32f429-discovery.h @@ -80,7 +80,7 @@ #define CONFIG_BAUDRATE 115200 #define CONFIG_BOOTARGS \ - "console=ttystm0,115200 earlyprintk consoleblank=0 ignore_loglevel" + "console=ttyS0,115200 earlyprintk consoleblank=0 ignore_loglevel" #define CONFIG_BOOTCOMMAND \ "run bootcmd_romfs" -- 2.3.1.167.g7f4ba4b

2 1

[U-Boot] [PATCH 0/4] kbuild & kconfig: sync with Linux 4.1
by Masahiro Yamada 28 Jul '15

28 Jul '15

These change sets have been imported from Linux. This series should not change any boards. Masahiro Yamada (4): kconfig: sync with Linux 4.1 kbuild: sync with Linux 4.1 kbuild: do not add $((generic-)offsets-file) to targets kbuild: use relative path more to include Makefile Kbuild | 3 +- Makefile | 33 ++++-------- scripts/Kbuild.include | 25 +++++++-- scripts/Makefile.build | 5 +- scripts/Makefile.clean | 29 ++++------ scripts/Makefile.lib | 25 +++++---- scripts/kconfig/Makefile | 80 ++++++++++++++-------------- scripts/kconfig/conf.c | 8 ++- scripts/kconfig/confdata.c | 6 +++ scripts/kconfig/expr.c | 22 ++++---- scripts/kconfig/expr.h | 5 -- scripts/kconfig/gconf.c | 29 ++-------- scripts/kconfig/list.h | 6 +-- scripts/kconfig/lkc.h | 14 ----- scripts/kconfig/lkc_proto.h | 85 ++++++++++++++---------------- scripts/kconfig/lxdialog/check-lxdialog.sh | 6 ++- scripts/kconfig/mconf.c | 35 +++++++----- scripts/kconfig/menu.c | 4 +- scripts/kconfig/merge_config.sh | 30 +++++++---- scripts/kconfig/nconf.c | 5 ++ scripts/kconfig/qconf.cc | 5 +- scripts/kconfig/symbol.c | 42 +++++++-------- scripts/kconfig/util.c | 10 ---- 23 files changed, 244 insertions(+), 268 deletions(-) -- 1.9.1

2 8

[U-Boot] [PATCH] config: ti_omap5_common: Palmas power support in SPL
by Paul Kocialkowski 28 Jul '15

28 Jul '15

Palmas power support is required for OMAP5 devices such as the OMAP5 uEVM, that need to e.g. enable MMC power at SPL stage. This is especially important when booting from a peripheral (such as USB, UART), where the bootrom will not enable power for the MMC device that will hold the main U-Boot. Signed-off-by: Paul Kocialkowski <contact(a)paulk.fr> --- include/configs/ti_armv7_common.h | 1 + include/configs/ti_omap5_common.h | 2 -- 2 files changed, 1 insertion(+), 2 deletions(-) diff --git a/include/configs/ti_armv7_common.h b/include/configs/ti_armv7_common.h index 0aea7d1..34756de 100644 --- a/include/configs/ti_armv7_common.h +++ b/include/configs/ti_armv7_common.h @@ -261,6 +261,7 @@ #define CONFIG_SPL_LIBCOMMON_SUPPORT #define CONFIG_SPL_LIBGENERIC_SUPPORT #define CONFIG_SPL_SERIAL_SUPPORT +#define CONFIG_SPL_POWER_SUPPORT #define CONFIG_SPL_GPIO_SUPPORT #define CONFIG_SPL_BOARD_INIT diff --git a/include/configs/ti_omap5_common.h b/include/configs/ti_omap5_common.h index 4179a57..b33feb6 100644 --- a/include/configs/ti_omap5_common.h +++ b/include/configs/ti_omap5_common.h @@ -40,9 +40,7 @@ #define CONFIG_SYS_DEFAULT_LPDDR2_TIMINGS #endif -#ifndef CONFIG_SPL_BUILD #define CONFIG_PALMAS_POWER -#endif #include <asm/arch/cpu.h> #include <asm/arch/omap.h> -- 1.9.1

2 4

[U-Boot] Does FIT support a Bootloader along with kernel, fdt and ramfs
by harsha kiran 28 Jul '15

28 Jul '15

Hi ! we have a two stage booting system with 2 bootloaders. (1st stage (MLO, U-boot.img) and 2nd stage(u-Boot.bin) for upgrade purposes). With the current implementation is it possible to upgrade my bootloader with a FIT image? 1st stage loads FIT ---------> 2nd stage should run from FIT and load all kernel, fdt and ramfs . Thanks, Harsha -- View this message in context: http://u-boot.10912.n7.nabble.com/Does-FIT-support-a-Bootloader-along-with-… Sent from the U-Boot mailing list archive at Nabble.com.

1 0

[U-Boot] Framework to boot multicore CPU
by bharat gohil 28 Jul '15

28 Jul '15

Hi All, I want suggestion on, How to boot multicore CPU from u-boot? Modern SoC contain dual or qaud core same CPU core.Heterogeneous SoC contain ARM cortexAx+M3/4 or CortexAx+Renesas SH4 and many other combination. As of now,I have two code to boot muticore CPU. 1)OMAP5 based SOC(DRA7 Dual core CortexA15) boot into AMP mode.Core0 boot u-boot and linux kernel.Core0 load RTOS/Baremetal to Core1 and start Core1. 2)Renesas R-CAR E2(CortexA7+SH4).Core0(CortexA7) boot u-boot and linux kernel.Core0(CortexA7) load RTOS to Core1(SH4) and start Core1(SH4). Can we have common code or generic framework to boot other core from u-boot? I have created framework for same but before submit it,I want your expert suggestion. Similarly common framework to boot CPU in hypervisor mode.(I will disscuss in separate thread) -- Regards, Bharat Gohil Sr.Software Engineer bharat.gohil(a)harman.com +919427054633

1 0

[U-Boot] i.MX6 LVDS clock with u-boot splash screen spport
by Andreas Geisreiter 28 Jul '15

28 Jul '15

Hi, we are working with self-developed i.MX6 board. Now we have enabled U-Boot splash screen support. It is working well, but we have problems with LVDS interface. If we configure LVDS we always get 56MHz LVDS clock although we configured 30MHz for LVDS clock via displays structure in the board file: .bus = 0, .addr = 0, .pixfmt = IPU_PIX_FMT_RGB24, .detect = NULL, .enable = enable_lvds, .mode = { .name = "wvga-lvds", .refresh = 57, .xres = 800, .yres = 480, .pixclock = 33000, .left_margin = 40, .right_margin = 40, .upper_margin = 3, .lower_margin = 80, .hsync_len = 10, .vsync_len = 10, .sync = FB_SYNC_EXT, .vmode = FB_VMODE_NONINTERLACED Changing the pixclock value doesn't affect the lvds clock output. We always get 56MHz. Currently we are using u-boot version 2013.10. Has anyone an idea what's going wrong? Best regards, Andreas

1 0

[U-Boot] MPC8308RDB Development
by sudheer A 28 Jul '15

28 Jul '15

Hi, I am new to the U-boot development. I have MPC8308RDB with loaded u-boot-2009.11-rc1 version. Now how to trace that source code to implement or changes as per my application. And also please let me know the loading procedure(U-boot and custom application in windows) to that MPC8308RDB. Thanks in Advance, Sudheer A. -- View this message in context: http://u-boot.10912.n7.nabble.com/MPC8308RDB-Development-tp221336.html Sent from the U-Boot mailing list archive at Nabble.com.

1 0