October 2013 - U-Boot

[U-Boot] [UBOOT][PATCHv4 0/6] Add TI qspi controller with memory mapped support
by Sourav Poddar 06 Oct '13

06 Oct '13

This patch series add support for TI qspi controller and in the process also add support for quad read and memory mapped read in mtd spi framework. Testing details: Did a boot from qspi mode on DRA7xx. Testing details present in the last patch of the series. Currently, TI qpsi controller supports only 16MB access. Access for higher MB area will be added later. v3->v4: 1. Remove quad support for now 2. Rebase to master-probe barnach, where qspi framework has changed. 3. Adapt my qspi driver according to the new format suggested by Jagan.. Patches are available at: git://gitorious.org/u-boot-shared/u-boot-qspi.git qspi_v4 Matt Porter (3): omap5: add qspi support spi: add TI QSPI driver dra7xx_evm: add SPL API, QSPI, and serial flash support Sourav Poddar (3): armv7: hw_data: change clock divider setting. driver: mtd: spi: Add memory mapped read support README: qspi usecase and testing documentation. arch/arm/cpu/armv7/omap5/hw_data.c | 10 +- arch/arm/cpu/armv7/omap5/prcm-regs.c | 1 + arch/arm/include/asm/arch-omap5/omap.h | 3 + arch/arm/include/asm/arch-omap5/spl.h | 1 + arch/arm/include/asm/omap_common.h | 1 + board/ti/dra7xx/mux_data.h | 10 + doc/README.ti_qspi_dra_test | 38 ++++ doc/README.ti_qspi_flash | 47 +++++ drivers/mtd/spi/sf_ops.c | 2 + drivers/mtd/spi/sf_probe.c | 1 + drivers/spi/Makefile | 1 + drivers/spi/ti_qspi.c | 328 ++++++++++++++++++++++++++++++++ include/configs/dra7xx_evm.h | 19 ++ include/spi.h | 3 + 14 files changed, 464 insertions(+), 1 deletions(-) create mode 100644 doc/README.ti_qspi_dra_test create mode 100644 doc/README.ti_qspi_flash create mode 100644 drivers/spi/ti_qspi.c

3 26

[U-Boot] [PATCH 1/4] powerpc/p1010rdb: remove unused cpld_show
by Shengzhou Liu 05 Oct '13

05 Oct '13

Function cpld_show() was for debug and not called, so clean it. Signed-off-by: Shengzhou Liu <Shengzhou.Liu(a)freescale.com> --- board/freescale/p1010rdb/p1010rdb.c | 35 ----------------------------------- 1 file changed, 35 deletions(-) diff --git a/board/freescale/p1010rdb/p1010rdb.c b/board/freescale/p1010rdb/p1010rdb.c index 06aa800..42153e6 100644 --- a/board/freescale/p1010rdb/p1010rdb.c +++ b/board/freescale/p1010rdb/p1010rdb.c @@ -52,41 +52,6 @@ struct cpld_data { u8 por2; /* POR Options */ u8 por3; /* POR Options */ }; - -void cpld_show(void) -{ - struct cpld_data *cpld_data = (void *)(CONFIG_SYS_CPLD_BASE); - - printf("CPLD: V%x.%x PCBA: V%x.0\n", - in_8(&cpld_data->cpld_ver) & 0xF0, - in_8(&cpld_data->cpld_ver) & 0x0F, - in_8(&cpld_data->pcba_ver) & 0x0F); - -#ifdef CONFIG_DEBUG - printf("twindie_ddr =%x\n", - in_8(&cpld_data->twindie_ddr3)); - printf("bank_sel =%x\n", - in_8(&cpld_data->bank_sel)); - printf("usb2_sel =%x\n", - in_8(&cpld_data->usb2_sel)); - printf("porsw_sel =%x\n", - in_8(&cpld_data->porsw_sel)); - printf("tdm_can_sel =%x\n", - in_8(&cpld_data->tdm_can_sel)); - printf("tdm_can_sel =%x\n", - in_8(&cpld_data->tdm_can_sel)); - printf("spi_cs0_sel =%x\n", - in_8(&cpld_data->spi_cs0_sel)); - printf("bcsr0 =%x\n", - in_8(&cpld_data->bcsr0)); - printf("bcsr1 =%x\n", - in_8(&cpld_data->bcsr1)); - printf("bcsr2 =%x\n", - in_8(&cpld_data->bcsr2)); - printf("bcsr3 =%x\n", - in_8(&cpld_data->bcsr3)); -#endif -} #endif int board_early_init_f(void) -- 1.8.0

6 11

[U-Boot] [PATCH] config.mk: Add -Wundef to CFLAGS
by Masahiro Yamada 05 Oct '13

05 Oct '13

In U-boot source, some '#if' directives evaluate undefined identifiers. To find and fix them, this commit adds -Wundef to CFLAGS. Signed-off-by: Masahiro Yamada <yamada.m(a)jp.panasonic.com> --- config.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config.mk b/config.mk index f71e145..7a92ae3 100644 --- a/config.mk +++ b/config.mk @@ -259,7 +259,7 @@ CPPFLAGS += -I$(TOPDIR)/include CPPFLAGS += -fno-builtin -ffreestanding -nostdinc \ -isystem $(gccincdir) -pipe $(PLATFORM_CPPFLAGS) -CFLAGS := $(CPPFLAGS) -Wall -Wstrict-prototypes +CFLAGS := $(CPPFLAGS) -Wall -Wstrict-prototypes -Wundef ifdef BUILD_TAG CFLAGS += -DBUILD_TAG='"$(BUILD_TAG)"' -- 1.8.1.2

3 7

Re: [U-Boot] [RFC PATCH 4/3] i.MX6DQ/DLS: remove unused pad declarations
by Eric Nelson 05 Oct '13

05 Oct '13

Hi all, I'm just following up on this patch. On 09/18/2013 12:18 PM, Eric Nelson wrote: > Hi Otavio, > > On 09/18/2013 11:27 AM, Otavio Salvador wrote: >> On Wed, Sep 18, 2013 at 3:14 PM, Eric Nelson >> <eric.nelson(a)boundarydevices.com> wrote: >>> That's not a typo. I really did intend this to be an add-on to the >>> series described here: >>> >>> http://lists.denx.de/pipermail/u-boot/2013-September/#162774 >>> >>> This patch assumes that the answer about what to do with pads that >>> aren't in the Linux tree is to delete them from U-Boot. >>> >>> No boards are currently referring to them, and the names are still >>> a jumble of mis-matched abbreviations. >>> >>> After applying this patch, there are still over 200 differences in >>> pad declarations between the i.MX6D/Q and the i.MX6DL/S header files, >>> but the differences may all be meaningful. >>> >>> Specifically: >>> >>> 142 have names referring to IPU2 on i.MX6D/Q and LCDIF on i.MX6DL/S >>> It's not clear to me whether these can be used in the same >>> manner >>> on both variants. >>> 50 refer to the EPDC signals only available on i.MX6DL/S >>> 8 refer to ACLK_FREERUN, and it's not clear from the >>> documentation >>> whether this exists on i.MX6 D/Q >>> 15 refer to the ECSPI5 component, only available on i.MX6 D/Q >>> 8 refer to the I2C4 component, only available on i.MX6 DL/S >>> >>> These pad declarations seem to have made it into the Linux kernel >>> for i.MX6DL and should be added to i.MX6DQ: >>> >>> 38 refer to IPU1_CSI1, which is available on both variants and >>> should be added to the i.MX6D/Q declarations in Linux and >>> U-Boot >>> 4 refer to USBOH3 functions that should be added to i.MX6 D/Q >>> in Linux and U-Boot >>> >>> Signed-off-by: Eric Nelson <eric.nelson(a)boundarydevices.com> >> >> Personally I think this is the way to go. >> > > I guess I didn't really weigh in, but I'm in favor of 'ding now, > add later if needed'. > I don't think Stefano, Shawn, or Fabio ever weighed in on whether to - remove them all, or - review and remove or consolidate names, or - leave them alone Tapani requested that the MMDC_DRAM pads be kept, but I don't see a response to the comment that these are likely to be configured in DCD data at least for some boards, so the structs won't be useful and #defines would do the trick. Please let me know your thoughts. Regards, Eric

1 0

[U-Boot] Pull request: u-boot-arm/master
by Albert ARIBAUD 04 Oct '13

04 Oct '13

Hello Tom, The following changes since commit f04c53762962280365005c9db12ab561a18f2692: Merge branch 'u-boot-imx/master' into 'u-boot-arm/master' (2013-10-02 14:53:27 +0200) are available in the git repository at: git://git.denx.De/u-boot-arm master for you to fetch changes up to e261c83aa04ce0396d57aaecf8dfe0970ffac03e: ARM: VExpress: enable ARMv7 virt support for VExpress A15 (2013-10-03 21:28:57 +0200) ---------------------------------------------------------------- Andre Przywara (8): ARM: prepare armv7.h to be included from assembly source ARM: add secure monitor handler to switch to non-secure state ARM: add assembly routine to switch to non-secure state ARM: add C function to switch to non-secure state ARM: trigger non-secure state switch during bootm execution ARM: add SMP support for non-secure switch ARM: extend non-secure switch to also go into HYP mode ARM: VExpress: enable ARMv7 virt support for VExpress A15 arch/arm/cpu/armv7/Makefile | 5 + arch/arm/cpu/armv7/nonsec_virt.S | 208 ++++++++++++++++++++++++++++++++ arch/arm/cpu/armv7/virt-v7.c | 173 ++++++++++++++++++++++++++ arch/arm/include/asm/armv7.h | 33 ++++- arch/arm/include/asm/gic.h | 19 +++ arch/arm/lib/bootm.c | 18 +++ board/armltd/vexpress/vexpress_common.c | 15 +++ include/common.h | 2 + include/configs/vexpress_ca15_tc2.h | 5 +- 9 files changed, 476 insertions(+), 2 deletions(-) create mode 100644 arch/arm/cpu/armv7/nonsec_virt.S create mode 100644 arch/arm/cpu/armv7/virt-v7.c create mode 100644 arch/arm/include/asm/gic.h Amicalement, -- Albert.

2 1

[U-Boot] DDR setting, p1020 registers read
by Avinash Vijayvargia 04 Oct '13

04 Oct '13

Hi I have got a P1020 board similar to Freescale P1020 eval board RDB. If I put the DDR size as 512 uboot works fine. But if I make it as 1G which is the real size on the board then the uboot hangs. Also is there any cli in uboot to read p1020 registers? I want to read GUTS_PORBMSR to check if HW has bootstrapping correctly done for booting two cores. Thanks Avinash

1 0

[U-Boot] [PATCH v3 0/6] Second step towards Kbuild: Descend down like Kbuild
by Masahiro Yamada 04 Oct '13

04 Oct '13

Note: Update for v3 is the only patch subjects. The patch body is the same as v2. I have been just wondering why the U-Boot top Makefile is so dirty. It is sprinkled with SoC-specific code as follows: ifneq ($(CONFIG_OMAP_COMMON),) LIBS-y += $(CPUDIR)/omap-common/libomap-common.o endif ifneq (,$(filter $(SOC), mx25 mx27 mx5 mx6 mx31 mx35 mxs vf610)) LIBS-y += arch/$(ARCH)/imx-common/libimx-common.o endif ifeq ($(SOC),s5pc1xx) LIBS-y += $(CPUDIR)/s5p-common/libs5p-common.o endif ifeq ($(SOC),exynos) LIBS-y += $(CPUDIR)/s5p-common/libs5p-common.o endif ifneq ($(CONFIG_TEGRA),) LIBS-y += arch/$(ARCH)/cpu/$(SOC)-common/lib$(SOC)-common.o LIBS-y += arch/$(ARCH)/cpu/tegra-common/libcputegra-common.o LIBS-y += $(CPUDIR)/tegra-common/libtegra-common.o endif And it describes drivers not right under the top directory, which should be essentially cared by drivers/Makefile. LIBS-y += drivers/bios_emulator/libatibiosemu.o LIBS-y += drivers/block/libblock.o LIBS-$(CONFIG_BOOTCOUNT_LIMIT) += drivers/bootcount/libbootcount.o LIBS-y += drivers/crypto/libcrypto.o LIBS-y += drivers/dma/libdma.o ... This series adds the directory descending feature like Kbuild. 1/6 tweaks scripts/Makefile.build to support 'obj-y += foo/' syntax. If the build system finds 'foo/' (trailed by a slash), it visits foo directory. 2/6-6/6 demonstarate how we can refactor makefiles with this syntax. 2/6: Move some drivers LIBS from top Makefile to drivers/Makefile 3/6: Move some fs LIBS from top Makefile to fs/Makefile 4/6: Move Tegra specific lines from top Makefile under arch/arm/ 5/6: Move OMAP specific lines from top Makefile under arch/arm/ 6/6: Move Samsung SoC specific lines from top Makefile under arch/arm/ Note: This series uses [PATCH v2]First step towards Kbuild: Use Kbuild-style makefiles (19 patch files). as a prerequisite. Please apply those patches first. I believe no boards are broken by this refactoring. In order to confirm my claim, I compiled all boards except nds32 and nios2 architrecutures. (I could not get an appropriate prebuilt cross compilers for those two arch.) For arm, avr32, sandbox, x86, I could perfectly compile all boards without any warnings. For the other architectures, I could compile some boards and I could not the others. But the SUMMARY result is still the same after applying this series. In addition I compared all the error and warning messages for all boards and they are the same. This means these patches do not introduce any additional errors, warnings. Cc: Simon Glass <sjg(a)chromium.org> Cc: Tom Rini <trini(a)ti.com> Changes for v3: 1/6 - 3/6: No change 4/6 - 6/6: Fix mesleading patch subject (No change in body) Changes for v2: 1/6: No change 2/6: additionally refactor drivers/pcmcia drivers/rtc too 3/6, 4/6: No change 5/6: rebase on the master 6/6: No change Masahiro Yamada (6): Makefile: support descending down to subdirectories drivers: move some drivers to drivers/Makefile fs: move some file system to fs/Makefile ARM: tegra: delete Tegra specific code from toplevel Makefile ARM: omap: delete OMAP specific code from toplevel Makefile ARM: s5pc, exynos: delete Samsung ARM SoC specific code from toplevel Makefile Makefile | 44 +++---------------------------------------- arch/arm/cpu/Makefile | 2 ++ arch/arm/cpu/arm720t/Makefile | 2 ++ arch/arm/cpu/armv7/Makefile | 9 +++++++++ board/LEOX/elpt860/u-boot.lds | 1 - board/tqc/tqm8xx/u-boot.lds | 4 ++-- drivers/Makefile | 15 +++++++++++++++ fs/Makefile | 11 +++++++++++ scripts/Makefile.build | 15 +++++++++++++++ spl/Makefile | 14 +------------- 10 files changed, 60 insertions(+), 57 deletions(-) create mode 100644 arch/arm/cpu/Makefile create mode 100644 drivers/Makefile -- 1.8.1.2

2 9

[U-Boot] : Discussion on Serial Flash Discoverable Parameters (SFDP): JESD216A
by Jagan Teki 04 Oct '13

04 Oct '13

Hi All, As all we know that the spi_flash is a day-by-day developing hardware where each vendor has followed their own standard to get the best to come out. I see SFDP looks like a common standard where most of the vendors were following to get the flash parameter information at runtime. I have couple of questions, added few flash vendors on cc - request for all try to give some inputs 1. Does all vendors follow this standard at-least from the latest parts? 2. Any idea who are not following SFDP 3. Does the format of getting data from SFDP is varies from vendor to vendor or same? 4. Command to get the SFDP is same for all vendors? 5. What type of information we can get any list? Request for your comments, this will really help to shape the spi_flash code more dynamic. -- Thanks, Jagan. -------- Jagannadha Sutradharudu Teki, E: jagannadh.teki(a)gmail.com, P: +91-9676773388 Engineer - System Software Hacker U-boot - SPI Custodian and Zynq APSOC Ln: http://www.linkedin.com/in/jaganteki

1 1

[U-Boot] Lots of SPDX-License Identifer have a trailing space
by Masahiro Yamada 04 Oct '13

04 Oct '13

Hello Wolfgang, I noticed many of SPDX-License blocks have a trailing space after "GPL-2.0+". For example, arch/arm/cpu/arm1136/start.S * * SPDX-License-Identifier: GPL-2.0+[A Trailing Space] */ Is this space the one intentinally added? (If not, I can send a patch to fix it.) I am not sure whether I should precisely copy and paste SPDX indentifier or drop a trailing space when I add a new source file. Best Regards Masahiro Yamada

2 2

[U-Boot] [PATCH 0/6] SMDK5420: Add S2MPS11 pmic support to SMDK5420
by Leela Krishna Amudala 04 Oct '13

04 Oct '13

This patchset adds support for S2MPS11 pmic on SMDK5420 This patchset has dependency on Rajeshwari's base patchset: [V4] EXYNOS5420: Add SMDK5420 board support http://comments.gmane.org/gmane.comp.boot-loaders.u-boot/170582 Also, for testing we need Naveen's i2c patchset as well: i2c: improve s3c24x0 with High-speed and new SYS_I2C framework support http://www.mail-archive.com/u-boot@lists.denx.de/msg122679.html Leela Krishna Amudala (6): exynos: Use common pmic_reg_update() definition power: Explicitly select pmic device's bus FDT: Exynos5420: Add compatible srings for PMIC SMDK5420: S2MPS11: Adds the register settings for S2MPS11 exynos: Add a common DT based PMIC driver initialization config: SMDK5420: Enable S2MPS11 pmic board/samsung/common/board.c | 40 ++++++----- drivers/power/pmic/Makefile | 1 + drivers/power/pmic/pmic_common.c | 97 +++++++++++++++++++++++++ drivers/power/power_core.c | 14 ++++ drivers/power/power_i2c.c | 81 +++++++++++++++++++-- include/configs/smdk5420.h | 4 ++ include/fdtdec.h | 1 + include/power/pmic.h | 35 +++++++++ include/power/s2mps11_pmic.h | 144 ++++++++++++++++++++++++++++++++++++++ lib/fdtdec.c | 1 + 10 files changed, 394 insertions(+), 24 deletions(-) create mode 100644 drivers/power/pmic/pmic_common.c create mode 100644 include/power/s2mps11_pmic.h -- 1.7.10.4

4 17