15 Feb, 2018

1 commit

  • Migrate the option CONFIG_SPL_FRAMEWORK and make this gate most of the
    current set of options we have in Kconfig. We will need to have some
    options available for SPL and !SPL_FRAMEWORK so this is important. In a
    few cases we re-order existing options so that we have less escapes from
    the SPL_FRAMEWORK guard.

    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

02 Feb, 2018

1 commit


11 Oct, 2017

1 commit

  • Having this as a 'default y' is rather annoying because it doesn't
    actually compile unless other options are defined in the board header:

    ../cmd/bootm.c: In function 'do_imls_nor':
    ../cmd/bootm.c:330:7: error: 'CONFIG_SYS_MAX_FLASH_BANKS' undeclared (first use in this function); did you mean 'CONFIG_SYS_MAX_FLASH_SECT'?
    i < CONFIG_SYS_MAX_FLASH_BANKS; ++i, ++info) {

    Make it 'default n' so people who develop new boards that start from a
    blank defconfig have one less compilation failure to debug.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

04 Oct, 2017

2 commits

  • Fastboot need a bunch of options to be operating properly, such as the
    g_dnl gadget, the fastboot command, and some options that make sense. Since
    fastboot is now part of Kconfig, make sure we have them right.

    That will also reduce the boilerplate in the defconfigs.

    Reviewed-by: Łukasz Majewski
    Reviewed-by: Simon Glass
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     
  • The g_dnl USB settings for the vendor ID, product ID and manufacturer are
    actually common settings that can and should be shared by all the gadgets.

    Make them common by renaming them, and convert all the users.

    Reviewed-by: Simon Glass
    Reviewed-by: Lukasz Majewski
    Signed-off-by: Maxime Ripard

    Maxime Ripard
     

08 Sep, 2017

2 commits


02 Sep, 2017

2 commits

  • - Move ANDROID_IMAGE_SUPPORT to top level Kconfig under images as it's
    not strictly part of fastboot.
    - Add some defaults for the fastboot buffer location and size
    - Migrate all options listed in cmd/fastboot/Kconfig
    - Cleanup the README

    Signed-off-by: Tom Rini

    Tom Rini
     
  • This syncs all of the currently Kconfig'd symbols out of the headers and
    into the defconfig files. This has two exceptions, first am335x_evm
    needs to be converted to DM in SPL and then it can stop undef'ing
    CONFIG_DM_USB. Leaving this as-is results in a build failure, and
    without work, run time failure. The other case is am43xx_evm.h and in
    turn am43xx_evm_usbhost_boot. The problem here is that we need DWC3 USB
    host mode in SPL, but still desire to have gadget mode in U-Boot proper.

    Signed-off-by: Tom Rini

    Tom Rini
     

28 Aug, 2017

1 commit


15 Aug, 2017

1 commit


01 Aug, 2017

1 commit


27 Jul, 2017

3 commits


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
     

11 Jul, 2017

2 commits


28 Apr, 2017

1 commit

  • This originally started out as
    "pinctrl: Kconfig: reorder to keep Rockchip options together"
    and tried to keep the Rockchip-related config options together.

    However, we now rewrite all chip-specific driver selections to start
    with CONFIG_PINCTRL_ (with the inadvertent changes to related
    Makefiles) and sort those alphabetically. And as this already means
    touching most of the file, we also reformat the help text to not exceed
    80 characters (but make full use of those 80 characters).

    Signed-off-by: Philipp Tomsich
    Acked-by: Simon Glass

    Philipp Tomsich
     

28 Jan, 2017

4 commits


24 Jan, 2017

1 commit


22 Jan, 2017

1 commit


11 Jan, 2017

2 commits

  • This commit was created as follows:

    [1] Rename the option with the following command:
    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e 's/CONFIG_DWMMC/CONFIG_MMC_DW/g'

    [2] create the entry for MMC_DW in drivers/mmc/Kconfig
    (the prompt and help were copied from Linux)

    [3] run "tools/moveconfig.py -y MMC_DW"

    [4] add "depends on MMC_DW" to the MMC_DW_ROCKCHIP entry

    [5] Clean-up doc/README.socfpga by hand

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

    Masahiro Yamada
     
  • I am trying to make all DesignWare-based driver options prefixed
    with CONFIG_MMC_DW_.

    This commit was generated as follows:

    find . -name .git -prune -o -type f -print | \
    xargs sed -i -e 's/ROCKCHIP_DWMMC/MMC_DW_ROCKCHIP/g'

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

    Masahiro Yamada
     

30 Dec, 2016

1 commit


26 Nov, 2016

2 commits


12 Oct, 2016

1 commit


09 Sep, 2016

1 commit


26 Jul, 2016

1 commit


17 Jun, 2016

1 commit


10 Jun, 2016

1 commit


27 May, 2016

1 commit

  • The current reset API implements a method to reset the entire system.
    In the near future, I'd like to introduce code that implements the device
    tree reset bindings; i.e. the equivalent of the Linux kernel's reset API.
    This controls resets to individual HW blocks or external chips with reset
    signals. It doesn't make sense to merge the two APIs into one since they
    have different semantic purposes. Resolve the naming conflict by renaming
    the existing reset API to sysreset instead, so the new reset API can be
    called just reset.

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

    Stephen Warren
     

26 Apr, 2016

3 commits