26 Jul, 2017

2 commits

  • Updates the default u-boot environment variables to support FIT image
    loading.

    Signed-off-by: Andrew F. Davis
    Reviewed-by: Tom Rini

    Andrew F. Davis
     
  • 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

  • Not all TI Keystone2 EVMs want environment in NAND flash.
    K2G EVM which has an MMC/SD slot, keep environment in a
    FAT partition on SD card.

    Since ti_armv7_keystone2.h defines environment is in NAND,
    boards which do not follow that have to #undef'ine that
    configuration. This leads to ugly ordering issues around
    where exactly the include of ti_armv7_keystone2.h can come
    in within the k2*_evm.h files.

    Move environment location to config file of each board.
    This should make it easy to change it for any one board
    without affecting all other boards.

    Signed-off-by: Sekhar Nori

    Sekhar Nori
     

08 Apr, 2017

1 commit

  • SPI U-Boot image for K2 boards have now exceeded 512K partition
    allocated to it and no longer fit the partitions defined in kernel DTS
    file. Therefore, pass an updated MTD partition table from U-Boot as
    kernel command line arguments to avoid kernel from accidentally
    modifying boot loader image that has overflowed to next user partition.

    To do is, introduce a common environment file for declaring SPI
    partition so that each individual boards need not repeat the same.
    Choose appropriate SPI bus from board config file and pass it as command
    line argument to kernel.

    Signed-off-by: Vignesh R

    Vignesh R
     

29 Nov, 2016

1 commit

  • The config option TARGET_K2x_EVM is set by the k2x defconfigs to pick
    a board target, but the header configs also set K2x_EVM. This config
    is redundant, remove it and use TARGET_K2x_EVM everywhere in its place.

    Signed-off-by: Andrew F. Davis
    Reviewed-by: Lokesh Vutla

    Andrew F. Davis
     

02 Oct, 2016

1 commit

  • As boot monitor contains a mkimage header, it can be loaded at any location.
    So, have a common addr_mon address across all keystone2 SoCs. And also
    making sure that boot monitor is installed early during default boot to
    avoid any overlapping with other images.

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Lokesh Vutla
     

07 Jun, 2016

1 commit


16 Mar, 2016

2 commits

  • For k2l, k2e and k2hk, ubi is set to default boot in uboot
    environment settings; while for k2g, mmc should be the
    default boot. This patch is to set mmc as default for k2g-evm

    Signed-off-by: Yan Liu
    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Yan Liu
     
  • This patch updates the env script to include a initramfs with firmware
    loaded and provided to kernel through second argument of bootz command
    during boot. Defined DEFAULT_FW_INITRAMFS_BOOT_ENV to have all of the
    required env variables and use it in evm specific config file.

    The K2 linux drivers for PCIe and NetCP (1G, 10G) requires serdes
    firmwares. These requires firmware to be available early through the boot
    process in some cases to satisfy firmware requests from driver. Hence use
    a small initramfs to provide the same and update boot env to accommodate
    this in the boot flow. This method is used when rootfs is nfs and ubifs.
    This fs contains just lib/firmware folder with all required firmware.

    When rootfs is on initramfs, then the filesystem has the firmware under
    lib/firmware and this early initramfs is not required and is not used.

    Signed-off-by: Murali Karicheri
    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Murali Karicheri
     

15 Mar, 2016

1 commit

  • This commit replaces hard-coded EMIF and PHY DDR3 configurations for
    predefined SODIMMs to a calculated configuration. The SODIMM parameters
    are read from SODIMM's SPD and used to calculated the configuration.

    The current commit supports calculation for DDR3 with 1600MHz and 1333MHz
    only.

    Signed-off-by: Vitaly Andrianov
    Signed-off-by: Lokesh Vutla
    Signed-off-by: Nishanth Menon
    Reviewed-by: Tom Rini

    Vitaly Andrianov
     

28 Jul, 2015

4 commits


09 Jul, 2015

1 commit


07 Nov, 2014

2 commits

  • The Multicore Software Development Kit (MCSDK) provides foundational
    software for TI KeyStone II device platforms. It's supposed to be used
    with uboot, and it's convenient to have the same names for images, so
    correct environment image names according to the last MCSDK3.

    Signed-off-by: Ivan Khoronzhuk
    Reviewed-by: Tom Rini

    Khoronzhuk, Ivan
     
  • Currently to customize env for various ks2 boards, individual
    variables such as NAME_FS etc are defined and included in the
    common config.h to define CONFIG_EXTRA_ENV_SETTINGS. This
    doesn't scale well if a variable is not applicable on a
    specific board. Using this scheme, we have to define variables
    with empty value and it's ugly. Instead, to allow board specific
    customization of default env variable, define a common
    CONFIG_EXTRA_ENV_KS2_SETTINGS for all common variables and define
    board specific variables in individual board specific config.h
    using CONFIG_EXTRA_ENV_KS2_BOARD_SETTINGS. Use the common and board
    specific variables to define CONFIG_EXTRA_ENV_SETTINGS. This way
    more variables can be added in future for individual boards
    without affecting the other config.h files.

    Signed-off-by: Murali Karicheri
    Signed-off-by: Ivan Khoronzhuk
    Reviewed-by: Tom Rini

    Murali Karicheri
     

06 Nov, 2014

2 commits


23 Oct, 2014

2 commits


26 Jul, 2014

1 commit