26 Mar, 2019

1 commit

  • This converts the following to Kconfig:
    CONFIG_SF_DEFAULT_BUS
    CONFIG_SF_DEFAULT_CS
    CONFIG_SF_DEFAULT_MODE
    CONFIG_SF_DEFAULT_SPEED

    I use moveconfig script and then manual check on generated u-boot.cfg
    to solve the remaining issue.

    Signed-off-by: Patrick Delaunay

    Patrick Delaunay
     

01 Feb, 2019

2 commits


08 Jan, 2019

1 commit


04 Sep, 2018

1 commit


17 Aug, 2018

1 commit

  • We have the following cases:
    - CONFIG_NR_DRAM_BANKS was defined, migrate normally
    - CONFIG_NR_DRAM_BANKS_MAX was defined and then used for
    CONFIG_NR_DRAM_BANKS after a check, just migrate it over now.
    - CONFIG_NR_DRAM_BANKS was very oddly defined on p2771-0000-* (to 1024 +
    2), set this to 8.

    Signed-off-by: Tom Rini

    Tom Rini
     

21 Jul, 2018

1 commit

  • Currently the fdtfile environment variable is set to
    CONFIG_DEFAULT_DEVICE_TREE which is іnternally used as U-Boot devicetree
    source. The OS can use a different filename and Kconfig gives us the
    ability to select a default devicetree via CONFIG_DEFAULT_FDT_FILE.
    This also gives user configuring U-Boot via menuconfig the behaviour
    someone would expect.

    Signed-off-by: Klaus Goger
    Tested-By: Vagrant Cascadian
    Reviewed-by: Philipp Tomsich
    Acked-by: Philipp Tomsich

    Klaus Goger
     

04 Jun, 2018

1 commit


28 Apr, 2018

1 commit


26 Apr, 2018

2 commits


09 Apr, 2018

1 commit


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
     

18 Dec, 2017

1 commit


07 Nov, 2017

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
     

08 Sep, 2017

2 commits


28 Aug, 2017

1 commit


08 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
     

19 Jun, 2017

1 commit


11 May, 2017

3 commits


01 May, 2017

1 commit


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
     

16 Apr, 2017

2 commits


05 Apr, 2017

1 commit

  • This commit adds the baseline defconfig for the RK3399-Q7 (Puma) SoM
    (under the name 'puma-rk3399_defconfig') featuring the Rockchip RK3399
    in a Qseven compatible module.

    This subsumes the following changes:
    * defconfig: rk3399: migrate CONFIG_SPL_LIBCOMMON_SUPPORT/CONFIG_SPL_LIBGENERIC_SUPPORT
    * defconfig: rk3399-puma: add CONFIG_MMC_DW_ROCKCHIP
    * defconfig: rk3399-puma: disable CONFIG_SPL_OF_PLATDATA
    * defconfig: rk3399-puma: don't USE_TINY_PRINTF
    * defconfig: rk3399-puma: set up CONFIG_SYS_BOARD for the RK3399-Q7
    * defconfig: rk3399-puma: enable the multi-image loading via CONFIG_SPL_FIT
    * defconfig: rk3399-puma: SPL should be able to boot from MMC/SD card
    * defconfig: rk3399-puma: enable GMAC support
    * defconfig: rk3399-puma: enable support for SPI and Winbond SPI flash
    * defconfig: rk3399-puma: enable SPI as a boot-source in SPL
    * defconfig: rk3399-puma: disallow non-FIT images from being loaded
    * defconfig: rk3399-puma: rename to puma-rk3399
    * rockchip: config: rk3399: update defconfigs and rk3399_common

    For the RK3399-Q7, we want a default boot-order of SPI -> MMC -> uSD.
    This both follows how the BootROM probes devices and is a sane default
    for customers in device-personalisation (e.g. it allows for quick and
    easy factory programming of unpersonalised devices using an SD card)
    and field usage (with customer devices expected to have their firmware
    either in SPI or MMC).

    However, when probing multiple interfaces (according to the result
    from the board_boot_order function), we need to ensure that only valid
    FIT images are considered and disable the fallback to assuming that a
    raw (binary-only) U-Boot image is loaded (to avoid hangs/crashes from
    jumping to random content loaded from devices that are probed, but
    don't contain valid image content).

    By disabling the SPL_RAW_IMAGE_SUPPORT and SPL_LEGACY_IMAGE_SUPPORT
    options, we ensure that raw images (indistinguishable from random
    data) are not considered for booting.

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

    Philipp Tomsich
     

20 Mar, 2017

1 commit


17 Mar, 2017

1 commit


14 Mar, 2017

1 commit


31 Jan, 2017

1 commit


28 Jan, 2017

3 commits


12 Jan, 2017

1 commit

  • This is the only RK3399 device without DHCP. Enable it so that we
    can use a common BOOT_TARGET_DEVICES setting. It is likely useful to be
    able to use USB networking, at least. Full networking can be enabled when
    a suitable platform needs it.

    Signed-off-by: Simon Glass

    Simon Glass
     

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