Eric Lee / smarc-uboot

19 Apr, 2015

2 commits

  • 0adb5b761   net: cosmetic: Name ethaddr variables consistently ... Browse Code »

    Use "_ethaddr" at the end of variables and drop CamelCase.
    Make constant values actually 'const'.

    Signed-off-by: Joe Hershberger
    Acked-by: Simon Glass

    Joe Hershberger
     
  • 58d423b88   dm: select CONFIG_DM* options ... Browse Code »

    As mentioned in the previous commit, adding default values in each
    Kconfig causes problems because it does not co-exist with the
    "depends on" syntax. (Please note this is not a bug of Kconfig.)
    We should not do so unless we have a special reason. Actually,
    for CONFIG_DM*, we have no good reason to do so.

    Generally, CONFIG_DM is not a user-configurable option. Once we
    convert a driver into Driver Model, the board only works with Driver
    Model, i.e. CONFIG_DM must be always enabled for that board.
    So, using "select DM" is more suitable rather than allowing users to
    modify it. Another good thing is, Kconfig warns unmet dependencies
    for "select" syntax, so we easily notice bugs.

    Actually, CONFIG_DM and other related options have been added
    without consistency: some into arch/*/Kconfig, some into
    board/*/Kconfig, and some into configs/*_defconfig.

    This commit prefers "select" and cleans up the following issues.

    [1] Never use "CONFIG_DM=n" in defconfig files

    It is really rare to add "CONFIG_FOO=n" to disable CONFIG options.
    It is more common to use "# CONFIG_FOO is not set". But here, we
    do not even have to do it.
    Less than half of OMAP3 boards have been converted to Driver Model.
    Adding the default values to arch/arm/cpu/armv7/omap3/Kconfig is
    weird. Instead, add "select DM" only to appropriate boards, which
    eventually eliminates "CONFIG_DM=n", etc.

    [2] Delete redundant CONFIGs

    Sandbox sets CONFIG_DM in arch/sandbox/Kconfig and defines it again
    in configs/sandbox_defconfig.
    Likewise, OMAP3 sets CONFIG_DM arch/arm/cpu/armv7/omap3/Kconfig and
    defines it also in omap3_beagle_defconfig and devkit8000_defconfig.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

25 Feb, 2015

1 commit

13 Feb, 2015

1 commit

30 Jan, 2015

1 commit

  • f3b4bc458   OMAP3: igep00x0: Fix boot hang and add support for status LED. ... Browse Code »
    44

    Use the STATUS_LED APIs for indicating a boot progress instead of
    show_boot_progress.

    This patch also fixes a problem introduced with commit b3f4ca1135 (dm: omap3:
    Move to driver model for GPIO and serial). After that commit the board doesn't
    boot. Looks like the problem is the gpio_request call inside the function
    show_boot_progress.

    Signed-off-by: Enric Balletbo i Serra

    Enric Balletbo i Serra
     

05 Dec, 2014

1 commit

  • aac5450ea   omap_hsmmc: Board-specific TWL4030 MMC power initializations ... Browse Code »

    Boards using the TWL4030 regulator may not all use the LDOs the same way
    (e.g. MMC2 power can be controlled by another LDO than VMMC2).
    This delegates TWL4030 MMC power initializations to board-specific functions,
    that may still call twl4030_power_mmc_init for the default behavior.

    Signed-off-by: Paul Kocialkowski
    Reviewed-by: Tom Rini
    [trini: Fix omap3_evm warning, add twl4030.h]
    Signed-off-by: Tom Rini

    Paul Kocialkowski
     

29 Oct, 2014

1 commit

  • 2e07c249a   kconfig: arm: introduce symbol for ARM CPUs ... Browse Code »
    220

    This commit introduces a Kconfig symbol for each ARM CPU:
    CPU_ARM720T, CPU_ARM920T, CPU_ARM926EJS, CPU_ARM946ES, CPU_ARM1136,
    CPU_ARM1176, CPU_V7, CPU_PXA, CPU_SA1100.
    Also, it adds the CPU feature Kconfig symbol HAS_VBAR which is selected
    for CPU_ARM1176 and CPU_V7.

    For each target, the corresponding CPU is selected and the definition of
    SYS_CPU in the corresponding Kconfig file is removed.

    Also, it removes redundant "string" type in some Kconfig files.

    Signed-off-by: Georges Savoundararadj
    Acked-by: Albert ARIBAUD
    Cc: Masahiro Yamada

    Georges Savoundararadj
     

24 Oct, 2014

1 commit

25 Sep, 2014

1 commit

  • 535aad29f   MAINTAINERS: comment out blank M: field ... Browse Code »

    Since commit ddaf5c8f3030050fcd356a1e49e3ee8f8f52c6d4
    (patman: RunPipe() should not pipe stdout/stderr unless asked),
    Patman spits lots of "Invalid MAINTAINERS address: '-'"
    error messages for patches with global changes.
    It takes too long for Patman to process them.

    Anyway, "M: -" does not carry any important information.
    Rather, it is just like a place holder in case of assigning
    a new board maintainer. Let's comment out.

    This commit can be reproduced by the following command:

    find . -name MAINTAINERS | xargs sed -i -e '/^M:[[:blank:]]*-$/s/^/#/'

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

14 Sep, 2014

1 commit

  • 461be2f96   kconfig: remove redundant "string" type in arch and board Kconfigs ... Browse Code »
    44

    Now the types of CONFIG_SYS_{ARCH, CPU, SOC, VENDOR, BOARD, CONFIG_NAME}
    are specified in arch/Kconfig.

    We can delete the ones in arch and board Kconfig files.

    This commit can be easily reproduced by the following command:

    find . -name Kconfig -a ! -path ./arch/Kconfig | xargs sed -i -e '
    /config[[:space:]]SYS_\(ARCH\|CPU\|SOC\|\VENDOR\|BOARD\|CONFIG_NAME\)/ {
    N
    s/\n[[:space:]]*string//
    }
    '

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

31 Aug, 2014

1 commit

30 Jul, 2014

2 commits

  • 93d4334f7   Add board MAINTAINERS files ... Browse Code »

    We have switched to Kconfig and the boards.cfg file is going to
    be removed. We have to retrieve the board status and maintainers
    information from it.

    The MAINTAINERS format as in Linux Kernel would be nice
    because we can crib the scripts/get_maintainer.pl script.

    After some discussion, we chose to put a MAINTAINERS file under each
    board directory, not the top-level one because we want to collect
    relevant information for a board into a single place.

    TODO:
    Modify get_maintainer.pl to scan multiple MAINTAINERS files.

    Signed-off-by: Masahiro Yamada
    Suggested-by: Tom Rini
    Acked-by: Simon Glass

    Masahiro Yamada
     
  • dd84058d2   kconfig: add board Kconfig and defconfig files ... Browse Code »

    This commit adds:
    - arch/${ARCH}/Kconfig
    provide a menu to select target boards
    - board/${VENDOR}/${BOARD}/Kconfig or board/${BOARD}/Kconfig
    set CONFIG macros to the appropriate values for each board
    - configs/${TARGET_BOARD}_defconfig
    default setting of each board

    (This commit was automatically generated by a conversion script
    based on boards.cfg)

    In Linux Kernel, defconfig files are located under
    arch/${ARCH}/configs/ directory.
    It works in Linux Kernel since ARCH is always given from the
    command line for cross compile.

    But in U-Boot, ARCH is not given from the command line.
    Which means we cannot know ARCH until the board configuration is done.
    That is why all the "*_defconfig" files should be gathered into a
    single directory ./configs/.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass

    Masahiro Yamada
     

11 Mar, 2014

1 commit

05 Mar, 2014

1 commit

04 Mar, 2014

1 commit

19 Dec, 2013

1 commit

  • 965de8b91   ARM: AM33xx+: Update ioregs to pass different values ... Browse Code »

    Currently same value is programmed for all ioregs. This is not
    the case for all SoC's like AM4372. So adding a structure for ioregs
    and updating in all board files. And also return from config_cmd_ctrl()
    and config_ddr_data() functions if data is not passed.

    Signed-off-by: Lokesh Vutla
    [trini: Fixup dxr2, cm_t335, adapt pcm051 rev3]
    Signed-off-by: Tom Rini

    Lokesh Vutla
     

04 Dec, 2013

1 commit

  • 39245c869   am33xx: Stop modifying certain EMIF4D registers ... Browse Code »

    Based on the definitive guide to EMIF configuration[1] certain registers
    that we have been modifying (and are documented registers) should be
    left in their reset values rather than modified. This has been tested
    on AM335x GP EVM and Beaglebone White.

    [1]: http://processors.wiki.ti.com/index.php/AM335x_EMIF_Configuration_tips
    Cc: Enric Balletbo i Serra
    Cc: Javier Martinez Canillas
    Cc: Heiko Schocher
    Cc: Lars Poeschel
    Signed-off-by: Tom Rini
    Tested-by: Matt Porter

    Tom Rini
     

01 Nov, 2013

1 commit

15 Oct, 2013

1 commit

07 Oct, 2013

2 commits

28 Aug, 2013

1 commit

16 Aug, 2013

2 commits

  • 73feefdc1   am33xx: Stop using PHYS_DRAM_1 define ... Browse Code »

    We defined PHYS_DRAM_1 to 0x80000000 (start of DRAM) and then used this
    for CONFIG_SYS_SDRAM_BASE. But then we kept on referencing PHYS_DRAM_1
    in other places. Change to directly setting CONFIG_SYS_DRAM_BASE and
    then using that name in code.

    Signed-off-by: Tom Rini

    Tom Rini
     
  • a2fa28bc9   OMAP3: igep00x0: allow booting with a FDT from MMC ... Browse Code »

    IGEP boards now have Device Tree support in the mainline
    kernel. To boot an IGEP board using a DT, a uEnv.txt plain
    text file could be used to define a custom uenvcmd that will
    be run by the default boot command.

    It is more convenient to change the default boot command to
    allow loading a FDT if it is stored in the boot dir of the
    rootfs uSD/MMC partition.

    If no FDT is found then the defaul command tries to boot a
    zImage without a DT using legacy boot.

    Signed-off-by: Javier Martinez Canillas

    Javier Martinez Canillas
     

15 Aug, 2013

4 commits

24 Jul, 2013

1 commit

18 Jun, 2013

2 commits

05 Jun, 2013

1 commit

  • 4596dcc1d   am33xx/omap: Move save_omap_boot_params to omap-common/boot-common.c ... Browse Code »

    We need to call the save_omap_boot_params function on am33xx/ti81xx and
    other newer TI SoCs, so move the function to boot-common. Only OMAP4+
    has the omap_hw_init_context function so add ifdefs to not call it on
    am33xx/ti81xx. Call save_omap_boot_params from s_init on am33xx/ti81xx
    boards.

    Reviewed-by: R Sricharan
    Signed-off-by: Tom Rini

    Tom Rini
     

10 May, 2013

1 commit

  • 5f5c1d13d   ARM: Add support for IGEP COM AQUILA/CYGNUS ... Browse Code »

    The IGEP COM AQUILA and CYGNUS are industrial processors modules with
    following highlights:

    o AM3352/AM3354 Texas Instruments processor
    o Cortex-A8 ARM CPU
    o 3.3 volts Inputs / Outputs use industrial
    o 256 MB DDR3 SDRAM / 128 Megabytes FLASH
    o MicroSD card reader on-board
    o Ethernet controller on-board
    o JTAG debug connector available
    o Designed for industrial range purposes

    Signed-off-by: Enric Balletbo i Serra

    Enric Balletbo i Serra
     

08 Apr, 2013

1 commit

  • 5bf299bc4   asm/omap_gpmc.h: consolidate common defines ... Browse Code »

    arch/arm/include/asm/arch-am33xx/omap_gpmc.h and
    arch/arm/include/asm/arch-omap3/omap_gpmc.h are almost the same, consolidate
    the common parts into a new header.

    Introduce a new asm/omap_gpmc.h which defines the command part and pulls in
    the architecture specific one.

    Signed-off-by: Andreas Bießmann
    Cc: Tom Rini
    Reviewed-by: Tom Rini

    Andreas Bießmann
     

09 Mar, 2013

2 commits

19 Feb, 2013

2 commits

07 Feb, 2013

1 commit