24 Feb, 2018

1 commit

  • This converts the following to Kconfig:
    CONFIG_BOOTP_BOOTPATH
    CONFIG_BOOTP_DNS
    CONFIG_BOOTP_GATEWAY
    CONFIG_BOOTP_HOSTNAME
    CONFIG_BOOTP_PXE
    CONFIG_BOOTP_SUBNETMASK
    CONFIG_CMDLINE_EDITING
    CONFIG_AUTO_COMPLETE
    CONFIG_SYS_LONGHELP
    CONFIG_SUPPORT_RAW_INITRD
    CONFIG_ENV_VARS_UBOOT_CONFIG

    Signed-off-by: Adam Ford
    [trini: Re-run the migration]
    Signed-off-by: Tom Rini

    Adam Ford
     

11 Feb, 2018

1 commit

  • On the NIOS2 and Xtensa architectures, we do not have
    CONFIG_SYS_TEXT_BASE set. This is a strict migration of the current
    values into the defconfig and removing them from the headers.

    I did not attempt to add more default values in and for now will leave
    that to maintainers.

    Signed-off-by: Tom Rini

    Tom Rini
     

06 Nov, 2017

1 commit


21 Oct, 2017

1 commit

  • 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


14 Aug, 2017

1 commit


12 Aug, 2017

3 commits


10 Aug, 2017

1 commit


09 Aug, 2017

1 commit


01 Aug, 2017

1 commit

  • Migrate all remaining instances of CMD_NAND, CMD_NAND_TRIMFFS
    CMD_NAND_LOCK_UNLOCK and CMD_NAND_TORTURE from the headers into the
    defconfig files.

    Tested-by: Adam Ford
    Signed-off-by: Tom Rini
    Reviewed-by: Bin Meng

    Tom Rini
     

26 Jul, 2017

1 commit

  • 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
     

04 Jun, 2017

1 commit

  • Now that these symbols are in Kconfig, migrate all users. Use imply on
    a number of platforms that default to having this enabled. As part of
    this we must migrate some straglers for CMD_FAT and DOS_PARTITION.

    Signed-off-by: Tom Rini

    Tom Rini
     

23 May, 2017

1 commit


15 May, 2017

1 commit


12 Oct, 2016

2 commits


17 Sep, 2016

1 commit


26 Apr, 2016

3 commits


19 Nov, 2015

1 commit


13 Aug, 2015

1 commit


26 Jun, 2015

1 commit


05 Mar, 2015

1 commit

  • Currently in some cases SDRAM init requires global_data to be available
    and soon this will not be available prior to board_init_f(). Adjust the
    code paths in these cases to be correct. In some cases we had the SPL
    stack be in DDR as we might have large stacks (due to Falcon Mode +
    Environment). In these cases switch to CONFIG_SPL_STACK_R. In other
    cases we had simply been setting CONFIG_SPL_STACK into SRAM. In these
    cases we no longer need to (CONFIG_SYS_INIT_SP_ADDR is used and is also
    in SRAM) so drop those lines.

    Signed-off-by: Simon Glass
    Tested on Beagleboard, Beagleboard xM
    Tested-by: Matt Porter
    Tested on Beaglebone Black, AM43xx GP EVM, OMAP5 uEVM, OMAP4 Pandaboard
    Tested-by: Tom Rini
    Signed-off-by: Tom Rini
    Reviewed-by: Simon Glass

    Simon Glass
     

14 Jan, 2015

2 commits


06 Jan, 2015

1 commit


05 Dec, 2014

1 commit


27 Oct, 2014

1 commit


31 Aug, 2014

1 commit


31 Jul, 2014

1 commit


30 Jul, 2014

1 commit

  • We are about to switch to Kconfig in the next commit.
    But there are something to get done beforehand.

    In Kconfig, include/generated/autoconf.h defines boolean
    CONFIG macros as 1.

    CONFIG_SPL and CONFIG_TPL, if defined, must be set to 1.
    Otherwise, when switching to Kconfig, the build log
    would be sprinkled with warning messages like this:
    warning: "CONFIG_SPL" redefined [enabled by default]

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

    Masahiro Yamada
     

26 Jul, 2014

1 commit

  • 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
     

07 Jun, 2014

1 commit

  • 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
     

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
     

25 Nov, 2013

1 commit


22 Nov, 2013

1 commit

  • 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
     

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