25 Sep, 2014

1 commit

  • 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

  • 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

  • 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
     
  • 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

  • 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

  • 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

  • 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
     
  • 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

  • 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

  • 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

  • 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

3 commits

  • commit b689cd5 OMAP3: use a single board file for IGEP devices

    introduced the following build warning:

    igep00x0.h:168:24: warning: backslash-newline at end of file [enabled
    by default]

    This patch fixes the issue.

    Signed-off-by: Javier Martinez Canillas

    Javier Martinez Canillas
     
  • This patch adds an GPIO LED boot status for IGEP boards.

    The GPIO LED used is the red LED0 while the Linux kernel
    uses the green LED0 as the boot status.

    By using different GPIO LEDs, the user can know in which
    step of the boot process the board currently is.

    Signed-off-by: Javier Martinez Canillas
    Acked-by: Igor Grinberg

    Javier Martinez Canillas
     
  • Even when the IGEPv2 board and the IGEP Computer-on-Module
    are different from a form factor point of view, they are
    very similar in the fact that share many components and how
    they are wired.

    So, it is possible (and better) to have a single board file
    for both devices and just use the CONFIG_MACH_TYPE to make
    a differentiation between each board when needed.

    This change avoids code duplication by removing 298 lines of
    code and makes future maintenance easier.

    Signed-off-by: Javier Martinez Canillas
    Acked-by: Igor Grinberg

    Javier Martinez Canillas
     

10 Dec, 2012

1 commit


01 Sep, 2012

3 commits


15 May, 2012

2 commits

  • This is rework on config files of IGEP-based boards with the aim to remove
    duplicated code to be more maintainable. Basically this patch creates a
    common configuration file for both boards and only sets the specific option
    in the board config file.

    On board files the hardcored mach type was replaced in favour of using the
    CONFIG_MACH_TYPE option.

    More than 200 duplicated lines have been deleted.

    Signed-off-by: Enric Balletbo i Serra

    Enric Balletbò i Serra
     
  • Add parameters to the OMAP MMC initialization function so the board can
    mask host capabilities and set the maximum clock frequency. While the
    OMAP supports a certain set of MMC host capabilities, individual boards
    may be more restricted and the OMAP may need to be configured to match
    the board. The PRG_SDMMC1_SPEEDCTRL bit in the OMAP3 is an example.

    Signed-off-by: Jonathan Solnit

    Jonathan Solnit