Eric Lee / smarc-uboot

06 Nov, 2017

1 commit

21 Oct, 2017

2 commits

  • 8daec2d9d   net: Add SMC911X driver to Kconfig, convert ... Browse Code »

    We add the various SMC91XX symbols to drivers/net/Kconfig and then this
    converts the following to Kconfig:
    CONFIG_SMC911X
    CONFIG_SMC911X_BASE
    CONFIG_SMC911X_16_BIT
    CONFIG_SMC911X_32_BIT

    Signed-off-by: Adam Ford
    [trini: Apply to the rest of the tree, re-squash old and new patch]
    Signed-off-by: Tom Rini

    Adam Ford
     
  • 0a9ef4515   Convert CONFIG_NAND_OMAP_GPMC et al and CONFIG_NAND_MXC to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_NAND_MXC
    CONFIG_NAND_OMAP_GPMC
    CONFIG_NAND_OMAP_GPMC_PREFETCH
    CONFIG_NAND_OMAP_ELM
    CONFIG_SPL_NAND_AM33XX_BCH
    CONFIG_SPL_NAND_SIMPLE
    CONFIG_SYS_NAND_BUSWIDTH_16BIT

    Signed-off-by: Adam Ford
    Reviewed-by: Heiko Schocher
    [trini: Finish migration of CONFIG_SPL_NAND_SIMPLE, fix some build issues,
    add CONFIG_NAND_MXC so we can do CONFIG_SYS_NAND_BUSWIDTH_16BIT]
    Signed-off-by: Tom Rini

    Adam Ford
     

13 Sep, 2017

1 commit

02 Sep, 2017

1 commit

12 Aug, 2017

3 commits

10 Aug, 2017

1 commit

09 Aug, 2017

1 commit

29 Jul, 2017

1 commit

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    This converts the following to Kconfig:
    CONFIG_ENV_IS_IN_MMC
    CONFIG_ENV_IS_IN_NAND
    CONFIG_ENV_IS_IN_UBI
    CONFIG_ENV_IS_NOWHERE

    In fact this already exists for sunxi as a 'choice' config. However not
    all the choices are available in Kconfig yet so we cannot use that. It
    would lead to more than one option being set.

    In addition, one purpose of this series is to allow the environment to be
    stored in more than one place. So the existing choice is converted to a
    normal config allowing each option to be set independently.

    There are not many opportunities for Kconfig updates to reduce the size of
    this patch. This was tested with

    ./tools/moveconfig.py -i CONFIG_ENV_IS_IN_MMC

    And then manual updates. This is because for CHAIN_OF_TRUST boards they
    can only have ENV_IS_NOWHERE set, so we enforce that via Kconfig logic
    now.

    Signed-off-by: Simon Glass
    Signed-off-by: Tom Rini

    Simon Glass
     

25 Jul, 2017

1 commit

16 May, 2017

2 commits

15 May, 2017

2 commits

  • 8850c5d57   Kconfig: USB: Migrate CONFIG_USB_EHCI to CONFIG_USB_EHCI_HCD ... Browse Code »

    In order to be able to migrate the various SoC EHCI CONFIG options we
    first need to finish the switch from CONFIG_USB_EHCI to
    CONFIG_USB_EHCI_HCD.

    Cc: Marek Vasut
    Signed-off-by: Tom Rini
    Reviewed-by: Marek Vasut

    Tom Rini
     
  • 68ccab519   omap3: Migrate CONFIG_OMAP3_GPIO_X to Kconfig ... Browse Code »

    The symbols CONFIG_OMAP3_GPIO_X control if we enable the clocks for a
    given GPIO bank in U-Boot. select the required banks for each target.
    In some cases we need to also migrate from CONFIG_USB_EHCI (deprecated,
    in include/configs/) to CONFIG_USB_EHCI_HCD as we only require the GPIO
    bank to be enabled if USB is also enabled.

    Signed-off-by: Tom Rini

    Tom Rini
     

12 Oct, 2016

2 commits

27 Sep, 2016

1 commit

10 Sep, 2016

1 commit

07 Sep, 2016

1 commit

  • fa2f81b06   TI: Rework SRAM definitions and maximums ... Browse Code »

    On all TI platforms the ROM defines a "downloaded image" area at or near
    the start of SRAM which is followed by a reserved area. As it is at
    best bad form and at worst possibly harmful in corner cases to write in
    this reserved area, we stop doing that by adding in the define
    NON_SECURE_SRAM_IMG_END to say where the end of the downloaded image
    area is and make SRAM_SCRATCH_SPACE_ADDR be one kilobyte before this.
    At current we define the end of scratch space at 0x228 bytes past the
    start of scratch space this this gives us a lot of room to grow. As
    these scratch uses are non-optional today, all targets are modified to
    respect this boundary.

    Tested on OMAP4 Pandaboard, OMAP3 Beagle xM

    Cc: Albert Aribaud
    Cc: Nagendra T S
    Cc: Vaibhav Hiremath
    Cc: Lokesh Vutla
    Cc: Felipe Balbi
    Cc: Igor Grinberg
    Cc: Nikita Kiryanov
    Cc: Paul Kocialkowski
    Cc: Enric Balletbo i Serra
    Cc: Adam Ford
    Cc: Steve Sakoman
    Cc: Stefan Roese
    Cc: Thomas Weber
    Cc: Hannes Schmelzer
    Cc: Thomas Chou
    Cc: Masahiro Yamada
    Cc: Simon Glass
    Cc: Joe Hershberger
    Cc: Sam Protsenko
    Cc: Heiko Schocher
    Cc: Samuel Egli
    Cc: Michal Simek
    Cc: Wolfgang Denk
    Cc: Mateusz Kulikowski
    Cc: Ben Whitten
    Cc: Stefano Babic
    Cc: Bin Meng
    Cc: Sekhar Nori
    Cc: Mugunthan V N
    Cc: "B, Ravi"
    Cc: "Matwey V. Kornilov"
    Cc: Ladislav Michl
    Cc: Ash Charles
    Cc: "Kipisz, Steven"
    Cc: Daniel Allred
    Signed-off-by: Tom Rini
    Tested-by: Lokesh Vutla
    Acked-by: Lokesh Vutla
    Tested-by: Ladislav Michl

    Tom Rini
     

27 Aug, 2016

1 commit

  • 067716bac   ARM: Move SYS_CACHELINE_SIZE over to Kconfig ... Browse Code »

    This series moves the CONFIG_SYS_CACHELINE_SIZE. First, in nearly all
    cases we are mirroring the values used by the Linux Kernel here. Also,
    so long as (and in this case, it is true) we implement flushes in hunks
    that are no larger than the smallest implementation (and given that we
    mirror the Linux Kernel, again we are fine) it is OK to align higher.
    The biggest changes here are that we always use 64 bytes for CPU_V7 even
    if for example the underlying core is only 32 bytes (this mirrors
    Linux). Second, we say ARM64 uses 64 bytes not 128 (as found in the
    Linux Kernel) as we do not need multi-platform support (to this degree)
    and only the Cavium ThunderX 88xx series has a use for such large
    alignment.

    Cc: Albert Aribaud
    Cc: Marek Vasut
    Cc: Stefano Babic
    Cc: Prafulla Wadaskar
    Cc: Luka Perkov
    Cc: Stefan Roese
    Cc: Nagendra T S
    Cc: Vaibhav Hiremath
    Acked-by: Lokesh Vutla
    Cc: Steve Rae
    Cc: Igor Grinberg
    Cc: Nikita Kiryanov
    Cc: Stefan Agner
    Acked-by: Heiko Schocher
    Cc: Mateusz Kulikowski
    Cc: Peter Griffin
    Acked-by: Paul Kocialkowski
    Cc: Anatolij Gustschin
    Acked-by: "Pali Rohár"
    Cc: Adam Ford
    Cc: Steve Sakoman
    Cc: Grazvydas Ignotas
    Cc: Nishanth Menon
    Cc: Stephen Warren
    Cc: Robert Baldyga
    Cc: Minkyu Kang
    Cc: Thomas Weber
    Cc: Masahiro Yamada
    Cc: David Feng
    Cc: Alison Wang
    Cc: Michal Simek
    Cc: Simon Glass
    Cc: York Sun
    Cc: Shengzhou Liu
    Cc: Mingkai Hu
    Cc: Prabhakar Kushwaha
    Cc: Aneesh Bansal
    Cc: Saksham Jain
    Cc: Qianyu Gong
    Cc: Wang Dongsheng
    Cc: Alex Porosanu
    Cc: Hongbo Zhang
    Cc: tang yuantian
    Cc: Rajesh Bhagat
    Cc: Josh Wu
    Cc: Bo Shen
    Cc: Viresh Kumar
    Cc: Hannes Schmelzer
    Cc: Thomas Chou
    Cc: Joe Hershberger
    Cc: Sam Protsenko
    Cc: Bin Meng
    Cc: Christophe Ricard
    Cc: Anand Moon
    Cc: Beniamino Galvani
    Cc: Carlo Caione
    Cc: huang lin
    Cc: Sjoerd Simons
    Cc: Xu Ziyuan
    Cc: "jk.kernel@gmail.com"
    Cc: "Ariel D'Alessandro"
    Cc: Kever Yang
    Cc: Samuel Egli
    Cc: Chin Liang See
    Cc: Dinh Nguyen
    Cc: Hans de Goede
    Cc: Ian Campbell
    Cc: Siarhei Siamashka
    Cc: Boris Brezillon
    Cc: Andre Przywara
    Cc: Bernhard Nortmann
    Cc: Wolfgang Denk
    Cc: Ben Whitten
    Cc: Tom Warren
    Cc: Alexander Graf
    Cc: Sekhar Nori
    Cc: Vitaly Andrianov
    Cc: "Andrew F. Davis"
    Cc: Murali Karicheri
    Cc: Carlos Hernandez
    Cc: Ladislav Michl
    Cc: Ash Charles
    Cc: Mugunthan V N
    Cc: Daniel Allred
    Cc: Gong Qianyu
    Signed-off-by: Tom Rini
    Acked-by: Masahiro Yamada
    Acked-by: Chin Liang See
    Tested-by: Stephen Warren
    Acked-by: Paul Kocialkowski

    Tom Rini
     

28 Apr, 2016

1 commit

  • 2489a7e9f   omap3: Reduce logic/overo SPL max image size ... Browse Code »

    While the OMAP3 has 64KiB of SRAM, per the TRM the download area is only
    from 0x40200000 to 0x4020F000 and exceeding that will cause failure to
    boot. Further, we need to make sure that we don't run into
    SRAM_SCRATCH_SPACE_ADDR as once SPL is running we will write values
    there and would corrupt our running image.

    Cc: Adam Ford
    Cc: Steve Sakoman
    Signed-off-by: Tom Rini

    Tom Rini
     

26 Apr, 2016

2 commits

28 Sep, 2015

1 commit

  • e0bed6b67   configs: remove remnants of CONFIG_SYS_NAND_QUIET_TEST ... Browse Code »

    The config option has been removed by one of the syncs with the Linux
    mainline MTD subsystem:
    ff94bc40af (mtd, ubi, ubifs: resync with Linux-3.14)
    It has been left inside the config files. Currently does not look to
    serve any purpose, so remove it now from all the configs.

    Signed-off-by: Igor Grinberg
    Cc: Matthias Fuchs
    Cc: Stefan Roese
    Cc: "Albert ARIBAUD (3ADEV)"
    Cc: Peter Barada
    Cc: Steve Sakoman
    Cc: Peter Tyser
    Cc: Joe Hershberger
    Cc: Simon Glass
    Acked-by: Stefan Roese

    Igor Grinberg
     

13 Aug, 2015

2 commits

  • 181bd9dc6   kconfig: add config option for shell prompt ... Browse Code »
    102

    Add option to set shell prompt string from menuconfig and migrate
    boards globally.

    The migration is done as follows:
    - Boards that explicitly and unconditionally set CONFIG_SYS_PROMPT had the
    entry moved to their defconfig files.
    - Boards that defined some kind of #ifdef logic which selects the
    CONFIG_SYS_PROMPT (for example qemu-mips) got an #undef CONFIG_SYS_PROMPT
    right before the #ifdef logic and were left alone.
    - This change forces CONFIG_SYS_PROMPT to be a per board decision, and thus
    CONFIG_SYS_PROMPT was removed from all _common.h and _common.h
    files. This results in a streamlined default value across platforms, and
    includes the following files: spear-common, sunxi-common, mv-common,
    ti_armv7_common, tegra-common, at91-sama5_common, and zynq-common.
    - Boards that relied on _common.h values of CONFIG_SYS_PROMPT were
    not updated in their respective defconfig files under the assumption that
    since they did not explicitly define a value, they're fine with whatever
    the default is.
    - On the other hand, boards that relied on a value defined in some
    _common.h file such as woodburn_common, rpi-common,
    bur_am335x_common, ls2085a_common, siemens_am33x_common, and
    omap3_evm_common, had their values moved to the respective defconfig files.
    - The define V_PROMPT was removed, since it is not used anywhere except for
    assigning a value for CONFIG_SYS_PROMPT.

    Cc: Tom Rini
    Cc: Masahiro Yamada
    Cc: Stefano Babic
    Cc: Igor Grinberg
    Signed-off-by: Nikita Kiryanov
    [trini: Add spring, sniper, smartweb to conversion]
    Signed-off-by: Tom Rini

    Nikita Kiryanov
     
  • 55f1b39f7   ti: drop value from CONFIG_SYS_NAND_BUSWIDTH_16BIT ... Browse Code »

    Signed-off-by: Stefano Babic
    Reviewed-by: Tom Rini

    Stefano Babic
     

28 Jul, 2015

1 commit

26 Jun, 2015

1 commit

10 May, 2015

2 commits

  • 88d89668b   omap3: overo: Allow boot with kernel in UBI rootfs ... Browse Code »

    If regular NAND booting fails to find a valid uImage in the
    kernel partition in NAND, try to boot using a zImage and dtb found
    in a UBI volume in the rootfs partition. This is the NAND analog
    of mmc zImage booting for device-tree based kernels.

    Signed-off-by: Ash Charles
    Signed-off-by: Arun Bharadwaj

    Ash Charles
     
  • ce170a1c3   omap3: overo: Use software BCH8 ECC for NAND ... Browse Code »

    Overo COMs have NAND flash that requires 4-bit ECC or better except for
    the first sector which can use 1-bit ECC. The boot ROM expects to load
    a payload from NAND written using 1-bit hardware-based ECC. In short,
    write SPL to NAND something like this (4 times for redundancy):
    #> nandecc hw
    #> nand write ${loadaddr} 0x0 ${filesize}
    #> nand write ${loadaddr} 0x20000 ${filesize}
    #> nand write ${loadaddr} 0x40000 ${filesize}
    #> nand write ${loadaddr} 0x60000 ${filesize}

    Then, switch back to software-based BCH8 for everything else:
    #> nandecc sw bch8

    After [1], enlarge the max size of the SPL so the BCH code can fit.

    [1] https://www.mail-archive.com/u-boot@lists.denx.de/msg163912.html

    Signed-off-by: Ash Charles

    Ash Charles
     

23 Oct, 2014

2 commits

10 Oct, 2014

1 commit

  • 115e71f7d   omap3: overo: Fix fdtfile test ... Browse Code »

    Commit 12cc54376768461533b55ada1b0b6d4979f40579 'omap3: overo: Select
    fdtfile for expansion board' wrongly missed the operator in the fdtfile
    test. Update the test to only overwrite an empty fdtfile environment
    variable.

    Signed-off-by: Stefan Herbrechtsmeier

    Stefan Herbrechtsmeier
     

26 Jul, 2014

2 commits

  • 434f2cfca   ARM: omap: move board specific NAND configs out from ti_armv7_common.h ... Browse Code »

    This patch moves some board specific NAND configs:
    - FROM: generic config file 'ti_armv7_common.h'
    - TO: individual board config files using these configs.
    So that each board can independently set the value as per its design.

    Following configs are affected in this patch:
    CONFIG_SYS_NAND_U_BOOT_OFFS:
    CONFIG_CMD_SPL_NAND_OFS:
    CONFIG_SYS_NAND_SPL_KERNEL_OFFS:
    CONFIG_CMD_SPL_WRITE_SIZE:

    This patch also updates documentation for few of above NAND configs.

    Signed-off-by: Pekon Gupta

    pekon gupta
     
  • 222a3113b   ARM: omap: clean redundant PISMO_xx macros used in OMAP3 ... Browse Code »

    PISMO_xx macros were used to define 'Platform Independent Storage MOdule'
    related GPMC configurations. This patch
    - Replaces these OMAP3 specific macros with generic CONFIG_xx macros as provided
    by current u-boot infrastructure.
    - Removes unused redundant macros, which are no longer required after
    merging of common platform code in following commit
    commit a0a37183bd75e74608bc78c8d0e2a34454f95a91
    ARM: omap: merge GPMC initialization code for all platform

    +-----------------+-----------------------------------------------------------+
    | Macro | Reason for removal |
    +-----------------+-----------------------------------------------------------+
    | PISMO1_NOR_BASE | duplicate of CONFIG_SYS_FLASH_BASE |
    +-----------------+-----------------------------------------------------------+
    | PISMO1_NAND_BASE| duplicate of CONFIG_SYS_NAND_BASE |
    +-----------------+-----------------------------------------------------------+
    | PISMO1_ONEN_BASE| duplicate of CONFIG_SYS_ONENAND_BASE |
    +-----------------+-----------------------------------------------------------+
    | PISMO1_NAND_SIZE| GPMC accesses NAND device via I/O mapped registers so |
    | | configuring GPMC chip-select for smallest allowable |
    | | segment (GPMC_SIZE_16M) is enough. |
    +-----------------+-----------------------------------------------------------+
    | PISMO1_ONEN_SIZE| OneNAND uses a fixed GPMC chip-select address-space of |
    | | 128MB (GPMC_SIZE_128M) |
    +-----------------+-----------------------------------------------------------+
    +-----------------+-----------------------------------------------------------+
    | PISMO1_NOR | Unused Macros |
    | PISMO1_NAND | |
    | PISMO2_CS0 | |
    | PISMO2_CS1 | |
    | PISMO1_ONENAND | |
    | PISMO2_NAND_CS0 | |
    | PISMO2_NAND_CS1 | |
    | PISMO1_NOR_BASE | |
    | PISMO1_NAND_BASE| |
    | PISMO2_CS0_BASE | |
    +-----------------+-----------------------------------------------------------+

    Signed-off-by: Pekon Gupta

    pekon gupta
     

20 Jun, 2014

1 commit

  • 12cc54376   omap3: overo: Select fdtfile for expansion board ... Browse Code »
    43

    The u-boot Overo board actually supports both Overo (OMAP35xx)
    and Overo Storm (AM/DM37xx) COMs with a range of different expansion
    boards. This provides a mechanism to select the an appropriate device
    tree file based on the processor version and, if available, the
    expansion board ID written on the expansion board EEPROM. To match the
    3.15+ kernels, fdtfile names have this format:
    "omap3-overo[-storm]-.dtb"

    By default, we use "omap3-overo-storm-tobi.dtb".

    Signed-off-by: Ash Charles

    Conflicts:
    include/configs/omap3_overo.h

    Ash Charles
     

07 Jun, 2014

1 commit

  • b80a66033   mtd: nand: omap: add CONFIG_SYS_NAND_BUSWIDTH_16BIT to indicate NAND device bus-width ... Browse Code »

    GPMC controller needs to be configured based on bus-width of the NAND device
    connected to it. Also, dynamic detection of NAND bus-width from on-chip ONFI
    parameters is not possible in following situations:
    SPL: SPL NAND drivers does not support ONFI parameter reading.
    U-boot: GPMC controller iniitalization is done in omap_gpmc.c:board_nand_init()
    which is called before probing for devices, hence any ONFI parameter
    information is not available during GPMC initialization.

    Thus, OMAP NAND driver expected board developers to explicitely write GPMC
    configurations specific to NAND device attached on board in board files itself.
    But this was troublesome for board manufacturers as they need to dive into
    lengthy platform & SoC documents to find details of GPMC registers and
    appropriate configurations to get NAND device working.

    This patch instead adds existing CONFIG_SYS_NAND_BUSWIDTH_16BIT to board config
    hich indicates that connected NAND device has x16 bus-width. And then based on
    this config GPMC driver itself initializes itself based on NAND bus-width. This
    keeps board developers free from knowing GPMC controller specific internals.

    Signed-off-by: Pekon Gupta

    pekon gupta