08 Sep, 2017

2 commits


12 Aug, 2017

1 commit


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
     

16 May, 2017

1 commit


15 May, 2017

1 commit


30 Apr, 2017

2 commits


31 Jan, 2017

1 commit

  • Now, CONFIG_GENERIC_MMC seems equivalent to CONFIG_MMC.

    Let's create an entry for "config GENERIC_MMC" with "default MMC",
    then convert all macro defines in headers to Kconfig. Almost all
    of the defines will go away.

    I see only two exceptions:
    configs/blanche_defconfig
    configs/sandbox_noblk_defconfig

    They define CONFIG_GENERIC_MMC, but not CONFIG_MMC. Something
    might be wrong with these two boards, so should be checked later.

    Anyway, this is the output of the moveconfig tool.

    This commit was created as follows:

    [1] create a config entry in drivers/mmc/Kconfig

    [2] tools/moveconfig.py -r HEAD GENERIC_MMC

    [3] manual clean-up of garbage comments in doc/README.* and
    include/configs/*.h

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Tom Rini

    Masahiro Yamada
     

11 Jan, 2017

1 commit

  • Move (and rename) the following CONFIG options to Kconfig:

    CONFIG_DAVINCI_MMC (renamed to CONFIG_MMC_DAVINCI)
    CONFIG_OMAP_HSMMC (renamed to CONFIG_MMC_OMAP_HS)
    CONFIG_MXC_MMC (renamed to CONFIG_MMC_MXC)
    CONFIG_MXS_MMC (renamed to CONFIG_MMC_MXS)
    CONFIG_TEGRA_MMC (renamed to CONFIG_MMC_SDHCI_TEGRA)
    CONFIG_SUNXI_MMC (renamed to CONFIG_MMC_SUNXI)

    They are the same option names as used in Linux.

    This commit was created as follows:

    [1] Rename the options with the following command:

    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e '
    s/CONFIG_DAVINCI_MMC/CONFIG_MMC_DAVINCI/g
    s/CONFIG_OMAP_HSMMC/CONFIG_MMC_OMAP_HS/g
    s/CONFIG_MXC_MMC/CONFIG_MMC_MXC/g
    s/CONFIG_MXS_MMC/CONFIG_MMC_MXS/g
    s/CONFIG_TEGRA_MMC/CONFIG_MMC_SDHCI_TEGRA/g
    s/CONFIG_SUNXI_MMC/CONFIG_MMC_SUNXI/g
    '

    [2] Commit the changes

    [3] Create entries in driver/mmc/Kconfig.
    (copied from Linux)

    [4] Move the options with the following command
    tools/moveconfig.py -y -r HEAD \
    MMC_DAVINCI MMC_OMAP_HS MMC_MXC MMC_MXS MMC_SDHCI_TEGRA MMC_SUNXI

    [5] Sort and align drivers/mmc/Makefile for readability

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Marek Vasut

    Masahiro Yamada
     

30 Dec, 2016

1 commit

  • Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("sunxi: Use Kconfig CONFIG_MMC") moved
    instances only for SUNXI.

    We generally do not like such partial moves. This kind of work
    is automated by tools/moveconfig.py, so it is pretty easy to
    complete this move.

    I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
    This shortens the configs and will ease new board porting.

    This commit was created as follows:

    [1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

    [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

    Signed-off-by: Masahiro Yamada
    Reviewed-by: Jaehoon Chung

    Masahiro Yamada
     

28 Oct, 2016

2 commits


10 Sep, 2016

1 commit


07 Sep, 2016

2 commits

  • Move this option to Kconfig and set its default value to 4; this
    increases the number of supported CPUs for some boards.

    It consumes 1KB memory per CPU for PSCI stack, but it should not
    be a big deal, given the amount of memory used for the modern OSes.

    Reviewed-by: Alexander Graf
    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     
  • Add ARCH_SUPPORT_PSCI as a non-configurable option that platforms
    can select. Then, move CONFIG_ARMV7_PSCI, which is automatically
    enabled if both ARMV7_NONSEC and ARCH_SUPPORT_PSCI are enabled.

    Reviewed-by: Alexander Graf
    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

15 Jul, 2016

1 commit


26 Apr, 2016

2 commits


23 Mar, 2016

1 commit


19 Feb, 2016

1 commit


01 Dec, 2015

2 commits


25 Nov, 2015

1 commit


13 Nov, 2015

1 commit

  • Enable the GPU node in the system-wide ft_system_setup() hook instead of
    the board-specific ft_board_hook(). This allows us to enable GPU per SoC
    generation instead of per-board as we did initially.

    Reported-by: Stephen Warren
    Signed-off-by: Alexandre Courbot
    Signed-off-by: Tom Warren

    Alexandre Courbot
     

13 Aug, 2015

1 commit

  • 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
     

07 Aug, 2015

1 commit

  • T124/210 requires some specific configuration (VPR setup) to
    be performed by the bootloader before the GPU can be used.
    For this reason, the GPU node in the device tree is disabled
    by default. This patch enables the node if U-boot has performed
    VPR configuration.

    Boards enabled by this patch are T124's Jetson TK1 and Venice2
    and T210's P2571.

    Signed-off-by: Alexandre Courbot
    Cc: Stephen Warren
    Cc: Tom Warren
    Signed-off-by: Tom Warren

    Alexandre Courbot
     

06 Aug, 2015

2 commits


26 Jun, 2015

1 commit

  • Some archs/boards specify their own default by pre-defining the config
    which causes the Kconfig system to mix up the order of the configs in
    the defconfigs... This will cause merge pain if allowed to proliferate.

    Remove the configs that behave this way from the archs.

    A few configs still remain, but that is because they only exist as
    defaults and do not have a proper Kconfig entry. Those appear to be:

    SPIFLASH
    DISPLAY_BOARDINFO

    Signed-off-by: Joe Hershberger
    [trini: rastaban, am43xx_evm_usbhost_boot, am43xx_evm_ethboot updates,
    drop DM_USB from MSI_Primo81 as USB_MUSB_SUNXI isn't converted yet to DM]
    Signed-off-by: Tom Rini

    Joe Hershberger
     

01 Jun, 2015

1 commit


14 May, 2015

1 commit

  • The secure world code is relocated to the MB just below the top of 4G, we
    reserve it in the FDT (by setting CONFIG_ARMV7_SECURE_RESERVE_SIZE) but it is
    not protected in h/w.

    Signed-off-by: Ian Campbell
    Signed-off-by: Jan Kiszka
    Reviewed-by: Tom Rini
    Reviewed-by: Thierry Reding
    Tested-by: Thierry Reding
    Tested-by: Ian Campbell
    Signed-off-by: Tom Warren

    Ian Campbell
     

05 Mar, 2015

1 commit

  • All boards need CONFIG_BOARD_EARLY_INIT_F, and many actively need
    CONFIG_BOARD_LATE_INIT. Move both of these into tegra-common.h so that
    board config headers don't need to repeatedly define them.

    Later commits will add new code in board_late_init() which applies to
    all boards, so CONFIG_BOARD_LATE_INIT should be enabled for all Tegra
    boards.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     

19 Dec, 2014

1 commit

  • The Jetson TK1 has an ethernet NIC connected to the PCIe bus and routes
    the second root port to a miniPCIe slot. Enable the PCIe controller and
    the network driver to allow the device to boot over the network.

    Signed-off-by: Thierry Reding
    Signed-off-by: Simon Glass
    Signed-off-by: Tom Warren

    Thierry Reding
     

12 Dec, 2014

1 commit

  • This converts all Tegra boards over to use driver model for I2C. The driver
    is adjusted to use driver model and the following obsolete CONFIGs are
    removed:

    - CONFIG_SYS_I2C_INIT_BOARD
    - CONFIG_I2C_MULTI_BUS
    - CONFIG_SYS_MAX_I2C_BUS
    - CONFIG_SYS_I2C_SPEED
    - CONFIG_SYS_I2C

    This has been tested on:
    - trimslice (no I2C)
    - beaver
    - Jetson-TK1

    It has not been tested on Tegra 114 as I don't have that board.

    Acked-by: Heiko Schocher
    Signed-off-by: Simon Glass

    Simon Glass
     

25 Sep, 2014

2 commits

  • This option specifies the default Device Tree used for the run-time
    configuration of U-Boot.

    Signed-off-by: Masahiro Yamada
    Cc: Simon Glass
    Cc: Stephen Warren
    Cc: Minkyu Kang
    Cc: Michal Simek

    Masahiro Yamada
     
  • This commit moves:
    CONFIG_OF_CONTROL
    CONFIG_OF_SEPARATE
    CONFIG_OF_EMBED
    CONFIG_OF_HOSTFILE

    Because these options are currently not supported for SPL,
    the "Device Tree Control" menu does not appear in the SPL
    configuration.

    Note:
    zynq-common.h should be adjusted so as not to change the
    default value of CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass
    Cc: Stephen Warren
    Cc: Minkyu Kang
    Acked-by: Michal Simek

    Masahiro Yamada
     

19 Aug, 2014

1 commit

  • Enable DFU protocol support (via the "dfu" command) on Tegra boards where
    USB device/gadget mode is enabled.

    Note that for DFU to operate correctly on Tegra, we still need some DFU
    fixes/enhancements that are going through the DFU -> USB trees. However,
    the code builds just fine without those changes, and applying this patch
    now will allow both sets of patches to meet in the main U-Boot tree much
    more quickly.

    In order to run test/dfu/dfu_gadget_test.sh, you would need to add the
    following to the board configuration:

    CONFIG_EXT4_WRITE
    CONFIG_CMD_EXT4_WRITE

    However, I haven't enabled those here, since I believe the main use-case
    for DFU on Tegra is raw flash writing, rather than filesystem access, so
    we don't need the additional code-size hit. However, I could be persuaded
    otherwise! We should probably add a separate test script for raw flash
    access.

    Signed-off-by: Stephen Warren
    Acked-by: Simon Glass
    Signed-off-by: Tom Warren

    Stephen Warren
     

06 Jun, 2014

1 commit

  • For each of Jetson TK1, Venice2, and Beaver:

    - Enable the first USB controller in DT, and describe its configuration.

    - Enable USB device/gadget support. This allows the user to type e.g.
    "ums 0 mmc 0" at the command-line to cause U-Boot to act a USB device
    implementing the USB Mass Storage protocol, and expose MMC device 0
    that way.

    This allows a host PC to mount the Tegra device's MMC, partition it, and
    install a filesystem on it.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     

17 Apr, 2014

1 commit