June 2016 - U-Boot

[U-Boot] [PATCH] Drivers: SPI: spi_slave struct has no member called bus nor cs.
by Ahmed Samir Khalil 17 Jun '16

17 Jun '16

In case of Driver Model, spi_slave structure (in spi.c) doesn't have member called bus or cs. Compiler error will be reported when using the new Driver Model while assigning bus & cs to non-members. This compiler error becomes obvious while applying the step-by-step documented in spi-howto.txt Signed-off-by: Ahmed Samir Khalil <engkhalil86(a)gmail.com> --- drivers/spi/spi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c index 7d81fbd..b02c7ab 100644 --- a/drivers/spi/spi.c +++ b/drivers/spi/spi.c @@ -31,8 +31,10 @@ void *spi_do_alloc_slave(int offset, int size, unsigned int bus, if (ptr) { memset(ptr, '\0', size); slave = (struct spi_slave *)(ptr + offset); +#ifndef CONFIG_DM_SPI slave->bus = bus; slave->cs = cs; +#endif slave->wordlen = SPI_DEFAULT_WORDLEN; } -- 2.7.4

2 1

[U-Boot] U-Boot Minnowboard Max USB3.0 port not powering up
by vinoth eswaran 17 Jun '16

17 Jun '16

Hello Bin, I am using the latest U-Boot version : u-boot-2016.07-rc1 I am seeing that after the bootup the USB port 3.0 -- the bottom one in the board is not powering up. I compared the dmesg logs with UEFI and with u-boot. I understood that with u-boot EHCI driver is being used and with UEFI XHCI driver is used 00:1d.0 USB controller: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB EHCI (rev 11) In the U-boot , minnowmax.dts in the fsp section I include the 'fsp,enable-xhci;' and now I am seeing that the XHCI driver is being used but still the USB port is not powered up. So I am assuming it to be other issue might be wrong pad up or it's not getting probed. Can you please look into the issue. Mit Freundlichen Grüßen VinothKumar +49 1798909072

2 1

[U-Boot] [PATCH 1/3] pci: Remove CONFIG_ALWAYS_LOAD_OPROM
by Bin Meng 17 Jun '16

17 Jun '16

This option is defined at nowhere. Remove it. Signed-off-by: Bin Meng <bmeng.cn(a)gmail.com> --- drivers/pci/pci_rom.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/pci/pci_rom.c b/drivers/pci/pci_rom.c index 9eb605b..3ae9231 100644 --- a/drivers/pci/pci_rom.c +++ b/drivers/pci/pci_rom.c @@ -41,8 +41,6 @@ __weak bool board_should_run_oprom(struct udevice *dev) static bool should_load_oprom(struct udevice *dev) { - if (IS_ENABLED(CONFIG_ALWAYS_LOAD_OPROM)) - return 1; if (board_should_run_oprom(dev)) return 1; -- 2.7.4

2 8

[U-Boot] [PATCH v3 00/12] Convert davinci_spi to DM
by Vignesh R 17 Jun '16

17 Jun '16

This series converts davinci_spi driver to adapt to driver model framework. And enables the driver on k2l, k2e, k2hk evms. Also, added support for davinci_spi on k2g evm. Tested on k2l, k2e, k2hk and k2g evms. Rebased on top of v2016.05-rc3 Vignesh R (12): dm: core: implement dev_map_phsymem() spi: davinci_spi: Convert to driver to adapt to DM keystone2: spi: do not define DM_SPI and DM_SPI_FLASH for SPL build ARM: dts: keystone2: add SPI aliases for davinci SPI nodes ARM: dts: k2hk: Enable Davinci SPI controller defconfig: k2hk_evm_defconfig: enable SPI driver model ARM: dts: k2e: Enable Davinci SPI controller defconfig: k2e_evm_defconfig: enable SPI driver model ARM: dts: k2l: Enable Davinci SPI controller defconfig: k2l_evm_defconfig: enable SPI driver model ARM: dts: k2g: add support for Davinci SPI controller defconfig: k2g_evm_defconfig: enable SPI driver model arch/arm/dts/k2e-evm.dts | 3 +- arch/arm/dts/k2g-evm.dts | 24 +++ arch/arm/dts/k2g.dtsi | 47 +++++ arch/arm/dts/k2hk-evm.dts | 3 +- arch/arm/dts/k2l-evm.dts | 3 +- arch/arm/dts/keystone.dtsi | 3 + configs/k2e_evm_defconfig | 2 + configs/k2g_evm_defconfig | 2 + configs/k2hk_evm_defconfig | 2 + configs/k2l_evm_defconfig | 2 + drivers/core/device.c | 6 + drivers/spi/davinci_spi.c | 327 +++++++++++++++++++++++++---------- include/configs/ti_armv7_keystone2.h | 4 + include/dm/device.h | 9 + 14 files changed, 344 insertions(+), 93 deletions(-) -- 2.8.2

5 33

[U-Boot] [PATCH] ARM: AM437x: Sync defconfig between GP and HS EVM
by Madan Srinivas 16 Jun '16

16 Jun '16

Adds missing NAND option to CONFIG_SYS_EXTRA_OPTIONS for AM437x HS EVMs. This syncs up the config options between GP and HS EVMs. Signed-off-by: Madan Srinivas <madans(a)ti.com> --- configs/am437x_hs_evm_defconfig | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configs/am437x_hs_evm_defconfig b/configs/am437x_hs_evm_defconfig index 1d7fabc..35e1fa2 100644 --- a/configs/am437x_hs_evm_defconfig +++ b/configs/am437x_hs_evm_defconfig @@ -10,7 +10,7 @@ CONFIG_DEFAULT_DEVICE_TREE="am437x-gp-evm" CONFIG_SPL=y CONFIG_ISW_ENTRY_ADDR=0x40302ae0 CONFIG_SPL_STACK_R=y -CONFIG_SYS_EXTRA_OPTIONS="CONS_INDEX=1" +CONFIG_SYS_EXTRA_OPTIONS="CONS_INDEX=1,NAND" CONFIG_FIT=y CONFIG_SPL_LOAD_FIT=y CONFIG_HUSH_PARSER=y -- 1.9.1

3 4

[U-Boot] [PATCH] arm: lib: Fix fix push/pop-section directives
by Marek Vasut 16 Jun '16

16 Jun '16

Repair typos in the previous "arm: lib: fix push/pop-section directives" patch, which prevented VCMA9 board from building. Signed-off-by: Marek Vasut <marex(a)denx.de> Fixes: b2f1858455e9 ("arm: lib: fix push/pop-section directives") Cc: Tom Warren <twarren(a)nvidia.com> Cc: Simon Glass <sjg(a)chromium.org> Cc: Masahiro Yamada <yamada.masahiro(a)socionext.com> Cc: Stephen Warren <swarren(a)nvidia.com> --- arch/arm/lib/lib1funcs.S | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/arch/arm/lib/lib1funcs.S b/arch/arm/lib/lib1funcs.S index 9bf93ce..76968ce 100644 --- a/arch/arm/lib/lib1funcs.S +++ b/arch/arm/lib/lib1funcs.S @@ -367,9 +367,9 @@ UNWIND(.fnend) ENDPROC(Ldiv0) .popsection -.pushsection .text.__gnu_thumb1_case_sqi, "ax" /* Thumb-1 specialities */ #if defined(CONFIG_SYS_THUMB_BUILD) && !defined(CONFIG_HAS_THUMB2) +.pushsection .text.__gnu_thumb1_case_sqi, "ax" ENTRY(__gnu_thumb1_case_sqi) push {r1} mov r1, lr @@ -383,7 +383,7 @@ ENTRY(__gnu_thumb1_case_sqi) ENDPROC(__gnu_thumb1_case_sqi) .popsection -_.pushsection .text.__gnu_thumb1_case_uqi, "ax" +.pushsection .text.__gnu_thumb1_case_uqi, "ax" ENTRY(__gnu_thumb1_case_uqi) push {r1} mov r1, lr -- 2.7.0

3 2

[U-Boot] [PATCH v1 00/12] am335x: add support for the am335x based bosch shc board
by Heiko Schocher 16 Jun '16

16 Jun '16

6 30

Re: [U-Boot] [PATCH] ARM: board: cm-fx6: fix mmc for old revisions of utilite
by Christopher Spinrath 16 Jun '16

16 Jun '16

Hi Igor, On 06/16/2016 11:05 AM, Igor Grinberg wrote: > Hi Christopher, > > On 06/15/2016 06:38 PM, Christopher Spinrath wrote: >> Hi Nikita, >> >> On 06/15/2016 05:15 PM, Nikita Kiryanov wrote: >>> Hi CHristopher, >>> >>> On Wed, Jun 08, 2016 at 09:02:36PM +0200, Christopher Spinrath wrote: >>>> Old revisions of Utilite (based on cmfx6) do not have a dedicated >>>> card detect pin. But the card is removable by the user and card >>>> detection can be realized with polling (e.g. supported by Linux). >>>> >>>> Add the broken-cd property to the mmc device tree instead of the >>>> non-removable property to make card detection possible if polling >>>> is supported. >>> >>> Acked-by: Nikita Kiryanov <nikita(a)compulab.co.il> >> >> How is this patch (and, in general, patches for Utilite/cm-fx6) supposed >> to be merged? > > Well, you've done this almost correctly. You just need to add > Stefano Babic <sbabic(a)denx.de> > (who is the maintainer of imx) to "cc" or "to" list. > Added now. > Thanks! >> Due to get_maintainers your are (the only) maintainer >> related to the cm-fx6 board. > > That is a separate discussion (e.g. how boards of a specific vendor, but > different architectures/platforms should be listed in the MAINTAINERS files). > I expected the output of get_maintainers to be complete. But ok, now I know it's not. >> Do you want me to resend the patch (without >> the Fixes: tag)? >> >>> One nit-pick below: >>> >>>> >>>> Fixes: 41855186afd3 ("arm: mx6: cm-fx6: modify device tree for old revisions of utilite") >>> >>> This isn't technically a fix; you're enabling new functionality. The >>> original behavior wasn't buggy, it just lacked the card detect feature. >>> >> Well, the card is clearly removable. So IMHO adding the non-removable >> property is wrong and this patch corrects/fixes it. But I'm fine either way. > > Just a little explanation... > Mechanically the card _is_ removable, but for revisions < 1.3, it will > result in errors on the bus as no removal event will be sent to the > subsystem. Moreover, if I'm not mistaken, you have the PRO model, right? > In PRO model, you have internal storage (e.g. SSD) which makes the SD card > an additional and sensibly removable device... > There are additional Utilite models which have the SD card as the only > storage device and those models have the rootfs on the SD card. > In such case, IMO, it is much more appropriate to state that it should be > non-removable. > With the broken-cd property the driver/subsystem knows that the card may have been removed and checks that if an (false positive) error occurs. Indeed, I have the Pro model but even for the other models there are use cases where the card may be removed. For instance, you can use netboot (think of thin clients) or boot from usb storage. So IMO the broken-cd property is a better choice for all models. Cheers, Christopher

2 1

[U-Boot] u-boot for Galileo board
by Liu, Changcheng 16 Jun '16

16 Jun '16

Hi all, I have some questions about the u-boot for Galileo2 board. 1. Code: https://github.com/LeMaker/u-boot (it's for Galileo board which could be ported for Galileo2 board) 2. Confusing at the building process. a. objcopy --gap-fill=0xff -O binary -R .start16 -R .resetvec u-boot u-boot.bin Question: Why the ".resetvec" section should be removed since it's placed at "0xffffffff0" section according to arch/x86/cpu/u-boot.lds? b. cat u-boot.bin dts/dt.dtb > u-boot-dtb.bin Question: I think ROM is layout at the top of the physical address and quark x1000 SoC will fetch instruction from FFFF_FFF0H after being power on. If dts/dt.dtb is appended after u-boot.bin, how could the content is effective at FFFF_FFF0H? B.R. Changcheng

1 0

[U-Boot] what is Flash Address Table why we can use(Board/---/flash.c)?
by Rama Chandra 16 Jun '16

16 Jun '16

Hai sir, I am using S29JL064H Spansion FLASH Memory, In this case 4 Banks used. For U-Boot i am taken OCOTEA Reference Board i am taken only 3 banks initialized in (Board/ocotea/flash.c) flash.c file Flash Address table why we are using and same addresses for starting thing -- Thanks & Regards, RamaChandra PC +918892147159.

1 0