08 Jan, 2019

1 commit


03 Dec, 2018

1 commit

  • The most generic way of having a stable boot behavior is to rely on
    UUID instead of device names for root partition, so the order of
    probing does not cause issues with booting.

    This enables the `CMD_FS_UUID` for following defconfig files:

    - rpi_0_w_defconfig
    - rpi_2_defconfig
    - rpi_3_32b_defconfig
    - rpi_3_defconfig
    - rpi_defconfig

    Signed-off-by: Otavio Salvador
    Signed-off-by: Fabio Berton
    Signed-off-by: Alexander Graf

    Otavio Salvador
     

04 Sep, 2018

1 commit


18 Aug, 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
     

09 Apr, 2018

1 commit


08 Apr, 2018

1 commit


05 Apr, 2018

1 commit


11 Feb, 2018

2 commits


06 Feb, 2018

1 commit

  • cmd/Makefile has:

    ifdef CONFIG_FPGA
    obj-$(CONFIG_CMD_FPGA) += fpga.o
    endif

    which means that if CONFIG_FPGA is not set, CONFIG_CMD_FPGA silently
    does nothing. Let's remove that Makefile conditional and instead express
    this equivalent dependency in Kconfig, so a lot of redundant

    # CONFIG_CMD_FPGA is not set

    can be removed from board defconfigs that don't actually have an FPGA.

    Signed-off-by: Tuomas Tynkkynen

    Tuomas Tynkkynen
     

29 Jan, 2018

1 commit

  • The bcm283x family of SoCs have a GPIO controller that also acts as
    pinctrl controller.

    This patch introduces a new pinctrl driver that can actually properly mux
    devices into their device tree defined pin states and is now the primary
    owner of the gpio device. The previous GPIO driver gets moved into a
    subdevice of the pinctrl driver, bound to the same OF node.

    That way whenever a device asks for pinctrl support, it gets it
    automatically from the pinctrl driver and GPIO support is still available
    in the normal command line phase.

    Signed-off-by: Alexander Graf

    Alexander Graf
     

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
     

27 Sep, 2017

1 commit


08 Sep, 2017

3 commits


07 Sep, 2017

1 commit

  • This reverts commit 25877d4e4c45451c5398aec3de50e0d5befe0e9f.

    This is a workaround for Raspberry Pi boot failures seen when passing on
    the device tree provided by the Raspberry Pi firmware at boot. Without
    CONFIG_OF_EMBED, we just get stuck at "Starting kernel ..." when we try
    to boot Linux with this device tree.

    Signed-off-by: Paul Barker
    Cc: Simon Glass
    Tested-by: Jonathan Gray
    Reviewed-by: Simon Glass

    Paul Barker
     

02 Sep, 2017

1 commit

  • 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


27 Aug, 2017

1 commit


15 Aug, 2017

1 commit


31 Jul, 2017

1 commit


11 Jul, 2017

1 commit


10 Jul, 2017

1 commit


07 Jul, 2017

1 commit


10 May, 2017

5 commits


01 May, 2017

1 commit


30 Dec, 2016

2 commits

  • While I moved the options, I also renamed them so that they are all
    prefixed with MMC_SDHCI_.

    This commit was created in the following steps.

    [1] Rename with the following command
    find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \
    -type f -print | xargs sed -i -e '
    s/CONFIG_MMC_SDMA/CONFIG_MMC_SDHCI_SDMA/g
    s/CONFIG_BCM2835_SDHCI/CONFIG_MMC_SDHCI_BCM2835/g
    s/CONFIG_KONA_SDHCI/CONFIG_MMC_SDHCI_KONA/g
    s/CONFIG_MV_SDHCI/CONFIG_MMC_SDHCI_MV/g
    s/CONFIG_S5P_SDHCI/CONFIG_MMC_SDHCI_S5P/g
    s/CONFIG_SPEAR_SDHCI/CONFIG_MMC_SDHCI_SPEAR/g
    '

    [2] create the Kconfig entries in drivers/mmc/Kconfig

    [3] Move the options by the following command
    tools/moveconfig.py -y MMC_SDHCI_SDMA MMC_SDHCI_BCM2835 \
    MMC_SDHCI_KONA MMC_SDHCI_MV MMC_SDHCI_S5P MMC_SDHCI_SPEAR

    [4] Sort drivers/mmc/Makefile for readability

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

    Masahiro Yamada
     
  • Move CONFIG_SDHCI to Kconfig and rename it to CONFIG_MMC_SDHCI.
    My motivation for the rename is, ultimately, to make all the MMC
    options prefixed with MMC_ and SDHCI options with MMC_SDHCI_,
    like Linux.

    This commit was created as follows:

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

    [2] create the entry for MMC_SDHCI in drivers/mmc/Kconfig

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

    [4] add "depends on MMC_SDHCI" to existing SDHCI driver entries

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

    Masahiro Yamada
     

04 Dec, 2016

1 commit

  • A number of platforms had been using the distro default feature before
    it was moved to Kconfig but did not enable the new Kconfig option when
    it was enabled. This caused a regression in terms of features and this
    introduces breakage when more things move to Kconfig.

    Signed-off-by: Tom Rini

    Tom Rini
     

29 Nov, 2016

1 commit


24 Oct, 2016

3 commits


12 Oct, 2016

1 commit