05 May, 2014

2 commits


08 Apr, 2014

1 commit


29 Mar, 2014

1 commit


13 Mar, 2014

1 commit

  • When using the am335x_evm_nor target one is generally expecting to be
    used in an environment when you want to program the NOR and not a
    "deployment" type target. In addition this only supports the Beaglebone
    White with the memory cape and NOR module installed, which precludes the
    presence of SPI flash. Drop SPI as we were getting close to the binary
    limit in some cases and slightly over with other toolchains.

    Signed-off-by: Tom Rini

    Tom Rini
     

11 Mar, 2014

1 commit


05 Mar, 2014

1 commit

  • OMAP NAND driver can detect Page-size and OOB-size of NAND device from ONFI
    params or nand_id[] table. And based on that it defines ECC layout.
    This patch
    1) removes following board configs used for defining NAND ECC layout
    - GPMC_NAND_ECC_LP_x16_LAYOUT (for large page x16 NAND)
    - GPMC_NAND_ECC_LP_x8_LAYOUT (for large page x8 NAND)
    - GPMC_NAND_ECC_SP_x16_LAYOUT (for small page x16 NAND)
    - GPMC_NAND_ECC_SP_x8_LAYOUT (for small page x8 NAND)

    2) removes unused #defines in common omap_gpmc.h depending on above configs

    Build tested using: ./MAKEALL -s am33xx -s omap3 -s omap4 -s omap5

    Signed-off-by: Pekon Gupta

    pekon gupta
     

04 Mar, 2014

1 commit


22 Feb, 2014

2 commits

  • Signed-off-by: Tom Rini

    Tom Rini
     
  • This patch add support for the Silica Pengwyn board [1]
    The board is based on a TI AM3354 CPU [2]
    All jumpers removed it will boot from the SDcard, the console is on
    UART1 accessible via the FDTI -> USB. The on board NAND flash is
    supported and can act as boot medium, depending on jumper settings.
    USB Host, USB Device and Ethernet are also provided but untested.

    [1]
    http://www.silica.com/product/silica-pengwyn-board.html
    [2]
    http://www.ti.com/product/am3354

    Signed-off-by: Lothar Felten
    [trini: Move CONFIG_BOARD_LATE_INIT into am335x_evm.h, drop unused
    spi0_pin_mux from Pengwyn support]
    Signed-off-by: Tom Rini

    Lothar Felten
     

13 Dec, 2013

1 commit


11 Dec, 2013

1 commit


05 Dec, 2013

1 commit


25 Nov, 2013

1 commit


22 Nov, 2013

2 commits

  • This patch adds new CONFIG_NAND_OMAP_ECCSCHEME, replacing other distributed
    CONFIG_xx used for selecting NAND ecc-schemes.
    This patch aims at solving following issues.

    1) Currently ecc-scheme is tied to SoC platform, which prevents user to select
    other ecc-schemes also supported in hardware. like;
    - most of OMAP3 SoC platforms use only 1-bit Hamming ecc-scheme, inspite
    the fact that they can use higher ecc-schemes like 8-bit ecc-schemes with
    software based error detection (OMAP_ECC_BCH4_CODE_HW_DETECTION_SW).
    - most of AM33xx SoC plaforms use 8-bit BCH ecc-scheme for now, but hardware
    supports BCH16 ecc-scheme also.

    2) Different platforms use different CONFIG_xx to select ecc-schemes, which
    adds confusion for user while migrating platforms.
    - *CONFIG_NAND_OMAP_ELM* which enables ELM hardware engine, selects only
    8-bit BCH ecc-scheme with h/w based error-correction (OMAP_ECC_BCH8_CODE_HW)
    whereas ELM hardware engine supports other ecc-schemes also like; BCH4,
    and BCH16 (in future).
    - *CONFIG_NAND_OMAP_BCH8* selects 8-bit BCH ecc-scheme with s/w based error
    correction (OMAP_ECC_BCH8_CODE_HW_DETECTION_SW).
    - *CONFIG_SPL_NAND_SOFTECC* selects 1-bit Hamming ecc-scheme using s/w library

    Thus adding new *CONFIG_NAND_OMAP_ECCSCHEME* de-couples ecc-scheme dependency
    on SoC platform and NAND driver. And user can select ecc-scheme independently
    foreach board.
    However, selection some hardware based ecc-schemes (OMAP_ECC_BCHx_CODE_HW) still
    depends on presence of ELM hardware engine on SoC. (Refer doc/README.nand)

    Signed-off-by: Pekon Gupta

    pekon gupta
     
  • ELM hardware engine which is used for ECC error detection, is present on all
    latest OMAP SoC (like OMAP4xxx, OMAP5xxx, DRA7xxx, AM33xx, AM43xx). Thus ELM
    driver should be moved to common drivers/mtd/nand/ folder so that all SoC
    having on-chip ELM hardware engine can re-use it.
    This patch has following changes:
    - mv arch/arm/include/asm/arch-am33xx/elm.h arch/arm/include/asm/omap_elm.h
    - mv arch/arm/cpu/armv7/am33xx/elm.c drivers/mtd/nand/omap_elm.c
    - update Makefiles
    - update #include
    - add CONFIG_NAND_OMAP_ELM to compile driver/mtd/nand/omap_elm.c
    and include in all board configs using AM33xx SoC platform.

    Signed-off-by: Pekon Gupta

    pekon gupta
     

13 Nov, 2013

1 commit

  • - add omap24xx driver to new multibus/multiadpater support
    - adapted all config files, which uses this driver

    Tested on the am335x based siemens boards rut, dxr2 and pxm2
    posted here:
    http://patchwork.ozlabs.org/patch/263211/

    Signed-off-by: Heiko Schocher
    Tested-by: Tom Rini
    Cc: Lars Poeschel
    Cc: Steve Sakoman
    Cc: Thomas Weber
    Cc: Tom Rix
    Cc: Grazvydas Ignotas
    Cc: Enric Balletbo i Serra
    Cc: Luca Ceresoli
    Cc: Igor Grinberg
    Cc: Ilya Yanok
    Cc: Stefano Babic
    Cc: Nishanth Menon
    Cc: Pali Rohár
    Cc: Peter Barada
    Cc: Nagendra T S
    Cc: Michael Jones
    Cc: Raphael Assenat
    Acked-by: Igor Grinberg
    Acked-by: Stefano Babic

    Heiko Schocher
     

12 Nov, 2013

1 commit


15 Oct, 2013

1 commit


08 Oct, 2013

2 commits


07 Oct, 2013

1 commit


02 Oct, 2013

1 commit


24 Sep, 2013

1 commit

  • Enable DFU for RAM, provide example dfu_alt_info

    Signed-off-by: Afzal Mohammed
    Cc: Heiko Schocher
    Cc: Tom Rini
    Cc: Marek Vasut
    Cc: Lukasz Majewski
    Cc: Pantelis Antoniou
    Reviewed-by: Lukasz Majewski

    Afzal Mohammed
     

21 Sep, 2013

2 commits

  • If, in CONFIG_BOOTCOMMAND, the environment switches both the mmcdev
    and bootpart variables to refer to MMC device 1, it would make sense
    that the mmcroot env variable should switch to that device as well.

    Signed-off-by: Robert P. J. Day

    Robert P. J. Day
     
  • Add a am33xx_spl_board_init (and enable the PMICs) that we may see,
    depending on the board we are running on. In all cases, we see if we
    can rely on the efuse_sma register to tell us the maximum speed. In the
    case of Beaglebone White, we need to make sure we are on AC power, and
    are on later than rev A1, and then we can ramp up to the PG1.0 maximum
    of 720Mhz. In the case of Beaglebone Black, we are either on PG2.0 that
    supports 1GHz or PG2.1. As PG2.0 may or may not have efuse_sma set, we
    cannot rely on this probe. In the case of the GP EVM, EVM SK and IDK we
    need to rely on the efuse_sma if we are on PG2.1, and the defaults for
    PG1.0/2.0.

    Signed-off-by: Tom Rini

    Tom Rini
     

07 Sep, 2013

1 commit


06 Sep, 2013

1 commit


28 Aug, 2013

3 commits


16 Aug, 2013

3 commits


15 Aug, 2013

1 commit


30 Jul, 2013

5 commits

  • Some boards, such as the BeagleBone Black, have an eMMC chip intstead
    of NAND. We can use the eMMC boot partition to store the environment,
    since it isn't used for anything else. This allows us to have a
    configurable environment on those boards.

    Signed-off-by: Justin Waters

    Justin Waters
     
  • The BeagleBone Black can boot from either the MMC card
    or eMMC chip on board. We should try both interfaces.

    This modification also allows a graceful fallback if
    a device exists but boot images are not present on it.

    Changes for v2:

    * Fix boot partition - it should always show up as mmcblk0p2
    * Fix missing FDT load

    Signed-off-by: Justin Waters

    Justin Waters
     
  • Many modern U-Boot ports enable command line editing and
    a history buffer. The am335x_evm configuration is fairly
    comprehensive as it is, so a few extra kb should not be
    noticable, and it adds a very convenient feature.

    Signed-off-by: Justin Waters

    Justin Waters
     
  • Give the user the ability to disable NAND support by defining
    CONFIG_NO_NAND. This will allow custom hardware to easily support
    this configuration.

    Signed-off-by: Justin Waters
    [trini: Make apply on top of other series]
    Signed-off-by: Tom Rini

    Justin Waters
     
  • NOR requires that s_init be within the first 4KiB of the image so that
    we can perform the rest of the required pinmuxing to talk with the rest
    of NOR that we are found on. When NOR_BOOT is set we save our
    environment in NOR at 512KiB and a redundant copy at 768KiB. We avoid
    using SPL for this case and u-boot.bin is written directly to the start
    of NOR.

    We enclose the DMM-related parts of arch/arm/cpu/armv7/am33xx/emif4.c
    with TI81xx checks as at this time U-Boot does not discard unused
    sections in the main build and this code relies on functions specific to
    (and only provided in) ti81xx-related code.

    Cc: Albert ARIBAUD
    Signed-off-by: Steve Kipisz
    Signed-off-by: Tom Rini

    Steve Kipisz