- Jan 11, 2017
-
-
Masahiro Yamada authored
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 <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Masahiro Yamada authored
This CONFIG is not referenced from anywhere. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Masahiro Yamada authored
Move (and rename) the following CONFIG options to Kconfig: CONFIG_EXYNOS_DWMMC (renamed to CONFIG_MMC_DW_EXYNOS) CONFIG_HIKEY_DWMMC (renamed to CONFIG_MMC_DW_K3) CONFIG_SOCFPGA_DWMMC (renamed to CONFIG_MMC_DW_SOCFPGA) The "HIKEY" is a board name, so it is not suitable for the MMC controller name. I am following the name used in Linux. This commit was generated as follows: [1] Rename the config options with the following command: find . -name .git -prune -o ! -path ./scripts/config_whitelist.txt \ -type f -print | xargs sed -i -e ' s/CONFIG_EXYNOS_DWMMC/CONFIG_MMC_DW_EXYNOS/g s/CONFIG_HIKEY_DWMMC/CONFIG_MMC_DW_K3/g s/CONFIG_SOCFPGA_DWMMC/CONFIG_MMC_DW_SOCFPGA/g ' [2] Commit the changes [3] Create the entries in drivers/mmc/Kconfig (with default y for EXYNOS and SOCFPGA) [4] Run the following: tools/moveconfig.py -y -r HEAD MMC_DW_EXYNOS MMC_DW_K3 MMC_DW_SOCFPGA [5] Sort and align drivers/mmc/Makefile for readability [6] Clean-up doc/README.socfpga by hand Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Masahiro Yamada authored
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 <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Masahiro Yamada authored
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 <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Masahiro Yamada authored
CONFIG_SOCFPGA_DWMMC_FIFO_DEPTH is defined in the socfpga_common.h, but not referenced at all. Remove. Also, clean-up the README.socfpga. CONFIG_MMC should not be defined in the header since it was moved to Kconfig by commit c2726995 ("mmc: complete unfinished move of CONFIG_MMC"). I see no grep hit for the others. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com> Reviewed-by:
Marek Vasut <marex@denx.de>
-
Jaehoon Chung authored
'-1' is absolutely meaningless value. This patch changed from meaningless value to error number. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Masahiro Yamada authored
Some MMC drivers describe operations with the DM_MMC_OPS form, but there are still several drivers with older implementation. We can not compile drivers from different groups at the same time because the core framework is shared with #ifdef CONFIG_DM_MMC_OPS. Every driver should have "depends on DM_MMC_OPS" (or !DM_MMC_OPS) explicitly to express which framework it is based on. This will avoid enabling drivers with incompatible interface at the same time. It is incorrect to make a driver "select DM_MMC_OPS". While we are here, add "depends on OF_CONTROL" as well because this driver can be configured only by Device Tree. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Masahiro Yamada authored
Add a driver for the Cadence SD4HC SD/SDIO/eMMC Controller. Signed-off-by:
Masahiro Yamada <yamada.masahiro@socionext.com>
-
Jaehoon Chung authored
It doesn't need to seperate the condition. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
Ther is no usage anywhere. It doesn't need to maintain this bit. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
The using the bitops is too easy controlling than now. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
callback function should be moved into sdhci_ops struct. Other controller can use these ops for controlling clock or their own specific register. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
Add the s5p_set_clock function. It's not good that "set_mmc_clk" is assigned directly. In future, it should be changed to use the clock framework. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
To maintain consistency, set_ios type of legacy mmc_ops changed to int. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
This quirk doesn't need anymore. It's replaced to get_cd callback function. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
This code is used for only pic32_sdhci controller. To remove the "#ifdef", moves to pic32_sdhci.c. And use the get_cd callback function. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
This code is dead code..There is no usage anywhere. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
Some SoCs can have their own card dect scheme. Then they may use this get_cd callback function after implementing init in their drivers. Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
Jaehoon Chung authored
Buswidth is depeneded on Hardware schematic. Evne though host can support the 8bit buswidth, if hardware doesn't support 8bit mode, it doesn't work fine. So the buswidth mode selection leaves a matter in each SoC drivers. On the contrary to this, hardware supports 8bit mode, but host doesn't support it. then controller has to disable the MMC_MODE_8BIT. (Host can check whether 8bit mode is supported or not, since V3.0) Signed-off-by:
Jaehoon Chung <jh80.chung@samsung.com>
-
- Jan 10, 2017
-
-
git://git.denx.de/u-boot-dmTom Rini authored
-
Tom Rini authored
MIPS no longer needs to have its own version of this macro now. Fixes: 2a6713b0 ("move UL() macro from armv8/mmu.h into common.h") Signed-off-by:
Tom Rini <trini@konsulko.com>
-
git://git.denx.de/u-boot-sunxiTom Rini authored
-
- Jan 09, 2017
-
-
Michal Simek authored
New scan should unbind all block devices not to be listed again. Without this patch if scsi reset or scan is called new block devices are created which point to the same id and lun. For example: ZynqMP> scsi scan scsi_scan: if_type=2, devnum=0: sdhci@ff170000.blk, 6, 0 scsi_scan: if_type=2, devnum=0: ahci@fd0c0000.id1lun0, 2, 0 scsi_scan: if_type=2, devnum=0: ahci@fd0c0000.id1lun0, 2, 1 scsi_scan: if_type=2, devnum=0: ahci@fd0c0000.id1lun0, 2, 2 scsi_scan: if_type=2, devnum=0: ahci@fd0c0000.id1lun0, 2, 3 scsi_scan: if_type=2, devnum=0: ahci@fd0c0000.id1lun0, 2, 4 scanning bus for devices... Device 0: (1:0) Vendor: ATA Prod.: KINGSTON SVP200S Rev: 501A Type: Hard Disk Capacity: 57241.8 MB = 55.9 GB (117231408 x 512) Reported-by:
Ken Ma <make@marvell.com> Signed-off-by:
Michal Simek <michal.simek@xilinx.com> Acked-by:
Simon Glass <sjg@chromium.org>
-
Mugunthan V N authored
enable usb driver model for am335x bbb as musb supports driver model Signed-off-by:
Mugunthan V N <mugunthanvnm@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Mugunthan V N authored
Since usb ether gadget have support for driver model, so enable usb ether gadget. Signed-off-by:
Mugunthan V N <mugunthanvnm@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Mugunthan V N authored
Add usb ether gadget device with usb_ether_init() when CONFIG_DM_ETH and CONFIG_USB_ETHER are defined. Signed-off-by:
Mugunthan V N <mugunthanvnm@ti.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Mugunthan V N authored
Adopt usb ether gadget and rndis driver to adopt driver model Signed-off-by:
Mugunthan V N <mugunthanvnm@ti.com>
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Ladislav Michl authored
Signed-off-by:
Ladislav Michl <ladis@linux-mips.org>
-
Tom Rini authored
Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Jan 08, 2017
-
-
Jagan Teki authored
Add 'Peng Fan' as MAINTAINERS of configs/mx6ull_14x14_evk_plugin_defconfig which is missing in below commit "imx: mx6ull_14x14_evk: add plugin defconfig" (sha1: b90ebf49) Cc: Stefano Babic <sbabic@denx.de> Reviewed-by:
Peng Fan <peng.fan@nxp.com> Signed-off-by:
Jagan Teki <jagan@openedev.com>
-
Andrew F. Davis authored
The SPL load address changes based on boot type in HS devices, ISW_ENTRY_ADDR is used to set this address for AM43xx based SoCs for similar reasons. Add this same logic for AM33xx devices. Also make the default value for ISW_ENTRY_ADDR correct for GP devices based on SoC, HS devices already pick the correct value in their defconfig. Signed-off-by:
Andrew F. Davis <afd@ti.com>
-
Andrew F. Davis authored
When TI_SECURE_DEV_PKG is not defined we warn that the file '*_HS' was not generated but generate an unsigned one anyway, first fix this warning to say that it was generated but not secured. When the user then exports TI_SECURE_DEV_PKG after getting this warning, and tries to re-build, 'make' will detect the build artifacts as unchanged and so assume they do not need to be re-generated. This causes it to fail to sign the files and it will pack unsigned files into the final image, even though TI_SECURE_DEV_PKG is now correctly defined and working. Fix this by using FORCE on the targets causes them to be re-run even if the dependent files have not changed. This then causes another issue. We currently rename the signed dtb files to overwrite the non-signed ones. We do this so the 'mkimage' tool gives the packaged dtb sections the correct name. If we do not rename the files then SPL will not find them during boot. Fix this by renaming the dtb files by appending _HS to the end of the filename, after the ".dtb", this causes them to still be named correctly in the FIT blob. Signed-off-by:
Andrew F. Davis <afd@ti.com>
-
- Jan 05, 2017
-
-
git://git.denx.de/u-boot-tegraTom Rini authored
-
git://git.denx.de/u-boot-spiTom Rini authored
-
York Sun authored
Use Kconfig option SYS_PPC64 instead. Signed-off-by:
York Sun <york.sun@nxp.com>
-
York Sun authored
Use Kconfig option to select chassis version. Signed-off-by:
York Sun <york.sun@nxp.com>
-
York Sun authored
Use Kconfig option E6500 and clean up existing usage. Signed-off-by:
York Sun <york.sun@nxp.com>
-
York Sun authored
After most config options are moved to Kconfig, the unused ifdef or elif can be removed. Signed-off-by:
York Sun <york.sun@nxp.com>
-