u-boot.git/configs/spring_defconfig, branch v2017.05

configs: Re-sync

2017-03-13T17:52:33Z

Signed-off-by: Tom Rini

ARM: Default to using optimized memset and memcpy routines

2017-01-20T20:38:01Z

We have long had available optimized versions of the memset and memcpy functions that are borrowed from the Linux kernel. We should use these in normal conditions as the speed wins in many workflows outweigh the relatively minor size increase. However, we have a number of places where we're simply too close to size limits in SPL and must be able to make the size vs performance trade-off in those cases. Cc: Philippe Reynes Cc: Eric Jarrige Cc: Heiko Schocher Cc: Magnus Lilja Cc: Lokesh Vutla Cc: Chander Kashyap Cc: Akshay Saraswat Cc: Simon Glass Cc: Stefan Roese Signed-off-by: Tom Rini Acked-by: Stefan Roese Reviewed-by: Simon Glass

Merge git://git.denx.de/u-boot-samsung

2017-01-18T12:21:12Z

exynos: video: Enable stdout env var backward compatibility for LCD

2017-01-18T05:28:46Z

Commit bb5930d5c97f ("exynos: video: Convert several boards to driver model for video") converted the Exynos Chromebooks machines to use DM for video, but this breaks backward compatibility with the stdout env var since now stdout is expected to be "vidconsole" instead of "lcd". This causes display to not work when updating u-boot on these boards if the old stdout env var is used. Since these are consumer devices, there's no easy way to have a serial console so users may be confused thinking that u-boot failed to boot, or in the best case will need to update the stdout env var blindly to make the display to work again. There's a CONFIG_VIDCONSOLE_AS_LCD config option to workaround this, so enable it in the Chromebooks' default configuration files to allow users to change their stdout env var before the workaround is removed. Suggested-by: Simon Glass Signed-off-by: Javier Martinez Canillas Signed-off-by: Minkyu Kang

exynos: Enable XHCI on exynos5250 boards

2017-01-18T05:28:36Z

Once upon a time u-boot didn't support building with two usb host controller types, these days it does. Enable XHCI in addition to the existing EHCI support so user can plug usb devices in all available ports regardless of the controller type. Signed-off-by: Sjoerd Simons Reviewed-by: Javier Martinez Canillas Reviewed-by: Jaehoon Chung Signed-off-by: Minkyu Kang

mmc: move CONFIG_DWMMC to Kconfig, renaming to CONFIG_MMC_DW

2017-01-11T10:40:14Z

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

mmc: move some SDHCI related options to Kconfig

2016-12-29T18:08:16Z

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

mmc: move CONFIG_SDHCI to Kconfig, renaming to CONFIG_MMC_SDHCI

2016-12-29T18:08:12Z

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

Sync defconfig files by savedefconfig

2016-12-29T18:07:33Z

Generated by "tools/moveconfig -s". This will make config moves easier. Signed-off-by: Masahiro Yamada

Enable DISTRO_DEFAULT on platforms that missed it before

2016-12-03T18:21:24Z

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