27 Oct, 2017

1 commit


15 May, 2017

1 commit


30 Apr, 2017

1 commit


20 Mar, 2017

1 commit

  • To keep a consistent MMC device mapping in SPL and in u-boot, let's
    register the MMC controllers the same way in u-boot and in the SPL.
    In terms of boot time, it doesn't hurt to register more controllers than
    needed because the MMC device is initialized only prior being accessed for
    the first time.
    Having the same device mapping in SPL and u-boot allows us to use the
    environment in SPL whatever the MMC boot device.

    Signed-off-by: Jean-Jacques Hiblot

    Jean-Jacques Hiblot
     

16 Mar, 2016

2 commits


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
     

24 Jan, 2014

1 commit


01 Nov, 2013

1 commit


28 Aug, 2013

2 commits


24 Jul, 2013

1 commit


10 Jun, 2013

1 commit


09 Mar, 2013

2 commits


07 Jul, 2012

1 commit


15 May, 2012

2 commits

  • TPS SET0/SET1 register is selected by a GPIO pin on OMAP4460 platforms.
    Currently we control this pin with a mux configuration as part of
    boot sequence.
    Current configuration results in the following voltage waveform:
    |---------------| (SET1 default 1.4V)
    | --------(programmed voltage)
    | |
    timing violation for a duration Tx close to few milliseconds.
    Problem 2) voltage of MPU goes beyond spec for even the highest of MPU OPP.

    By using GPIO as recommended as standard procedure by TI, the sequence
    changes to:
    -------- (programmed voltage)
    vdd_mpu(TPS) ------------/ (Opp boot voltage)
    --------- (programmed voltage)
    vdd_core(TWL6030) -------------/ (OPP boot voltage)

    NOTE: This does not attempt to address OMAP5 - Aneesh please confirm

    Reported-by: Isabelle Gros
    Reported-by: Jerome Angeloni
    Signed-off-by: Nishanth Menon

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

07 Dec, 2011

1 commit

  • TPS power IC is controlled using a GPIO (gpio_wk7).
    This GPIO should be maintained at logic 1 always. As
    such an internal pull-up on this pin will do the job,
    driving the GPIO outuput is not needed. This will avoid
    the need of using GPIO library in SPL and also may
    save some power.

    Signed-off-by: Aneesh V

    Aneesh V
     

16 Nov, 2011

2 commits

  • Configuration header(CH) is 512 byte header attached to an OMAP
    boot image that will help ROM code to initialize clocks, SDRAM
    etc and copy U-Boot directly into SDRAM. CH can help us in
    by-passing SPL and directly boot U-boot, hence it's an alternative
    for SPL. However, we intend to support both CH and SPL for OMAP4/5.

    Initialization done through CH is limited and is not equivalent
    to that done by SPL. So U-Boot has to distinguish between the
    two cases and handle them accordingly. This patch takes care
    of doing this.

    Signed-off-by: sricharan
    Signed-off-by: Sandeep Paulraj

    Sricharan
     
  • This patch adds the minimal support for OMAP5. The platform and machine
    specific headers and sources updated for OMAP5430.

    OMAP5430 is Texas Instrument's SOC based on ARM Cortex-A15 SMP architecture.
    It's a dual core SOC with GIC used for interrupt handling and SCU for cache
    coherency.

    Also moved some part of code from the basic platform support that can be made
    common for OMAP4/5. Rest is kept out seperately. The same approach is followed
    for clocks and emif support in the subsequent patches.

    Signed-off-by: sricharan
    Signed-off-by: Sandeep Paulraj

    Sricharan
     

16 Oct, 2011

1 commit

  • The top level Makefile does not do any recursion into subdirs when
    cleaning, so these clean/distclean targets in random arch/board dirs
    never get used. Punt them all.

    MAKEALL didn't report any errors related to this that I could see.

    Signed-off-by: Mike Frysinger

    Mike Frysinger
     

13 Sep, 2011

1 commit


03 Aug, 2011

2 commits

  • - Provide alternate implementations of board_init_f()
    board_init_r() for OMAP spl.
    - Provide linker script
    - Initialize global data
    - Add serial console support
    - Update CONFIG_SYS_TEXT_BASE to allow for SPL's bss and move
    it to board config header from config.mk

    Signed-off-by: Aneesh V
    Signed-off-by: Sandeep Paulraj

    Aneesh V
     
  • - separate mux settings into essential and non essential parts
    - essential part is board independent as of now(so move it
    to SoC directory). Will help in having single SPL for all
    boards.
    - Non-essential part(the pins not essential for u-boot to function)
    need to be phased out eventually.
    - Correct mux data by aligning to the latest settings in x-loader

    Signed-off-by: Aneesh V
    Signed-off-by: Sandeep Paulraj

    Aneesh V
     

11 Dec, 2010

1 commit


18 Nov, 2010

1 commit

  • Before this commit, weak symbols were not overridden by non-weak symbols
    found in archive libraries when linking with recent versions of
    binutils. As stated in the System V ABI, "the link editor does not
    extract archive members to resolve undefined weak symbols".

    This commit changes all Makefiles to use partial linking (ld -r) instead
    of creating library archives, which forces all symbols to participate in
    linking, allowing non-weak symbols to override weak symbols as intended.
    This approach is also used by Linux, from which the gmake function
    cmd_link_o_target (defined in config.mk and used in all Makefiles) is
    inspired.

    The name of each former library archive is preserved except for
    extensions which change from ".a" to ".o". This commit updates
    references accordingly where needed, in particular in some linker
    scripts.

    This commit reveals board configurations that exclude some features but
    include source files that depend these disabled features in the build,
    resulting in undefined symbols. Known such cases include:
    - disabling CMD_NET but not CMD_NFS;
    - enabling CONFIG_OF_LIBFDT but not CONFIG_QE.

    Signed-off-by: Sebastien Carlier

    Sebastien Carlier
     

19 Oct, 2010

1 commit

  • The change is currently needed to be able to remove the board
    configuration scripting from the top level Makefile and replace it by
    a simple, table driven script.

    Moving this configuration setting into the "CONFIG_*" name space is
    also desirable because it is needed if we ever should move forward to
    a Kconfig driven configuration system.

    Signed-off-by: Wolfgang Denk

    Wolfgang Denk
     

18 Oct, 2010

2 commits


10 Sep, 2010

1 commit


05 Aug, 2010

1 commit


16 Jul, 2010

1 commit


06 Jul, 2010

1 commit

  • OMAP4430 SDP is a reference board based on OMAP4430, an ARMV7 Cortex A9 CPU

    This patch adds basic support for booting the board. It includes i2c and mmc
    support. It assumes U-boot is loaded to SDRAM with the help of another small
    bootloader (x-load) running from SRAM. U-boot currently relies on x-load for
    clock, mux, and SDRAM initialization

    Signed-off-by: Aneesh V
    Signed-off-by: Steve Sakoman
    Signed-off-by: Sandeep Paulraj

    Steve Sakoman