Eric Lee / smarc-uboot

05 Mar, 2018

1 commit

31 Jan, 2018

1 commit

21 Oct, 2017

1 commit

  • 0a9ef4515   Convert CONFIG_NAND_OMAP_GPMC et al and CONFIG_NAND_MXC to Kconfig ... Browse Code »

    This converts the following to Kconfig:
    CONFIG_NAND_MXC
    CONFIG_NAND_OMAP_GPMC
    CONFIG_NAND_OMAP_GPMC_PREFETCH
    CONFIG_NAND_OMAP_ELM
    CONFIG_SPL_NAND_AM33XX_BCH
    CONFIG_SPL_NAND_SIMPLE
    CONFIG_SYS_NAND_BUSWIDTH_16BIT

    Signed-off-by: Adam Ford
    Reviewed-by: Heiko Schocher
    [trini: Finish migration of CONFIG_SPL_NAND_SIMPLE, fix some build issues,
    add CONFIG_NAND_MXC so we can do CONFIG_SYS_NAND_BUSWIDTH_16BIT]
    Signed-off-by: Tom Rini

    Adam Ford
     

14 Aug, 2017

1 commit

10 Aug, 2017

1 commit

01 Aug, 2017

1 commit

  • 8f1a80e99   configs: Migrate CMD_NAND* ... Browse Code »

    Migrate all remaining instances of CMD_NAND, CMD_NAND_TRIMFFS
    CMD_NAND_LOCK_UNLOCK and CMD_NAND_TORTURE from the headers into the
    defconfig files.

    Tested-by: Adam Ford
    Signed-off-by: Tom Rini
    Reviewed-by: Bin Meng

    Tom Rini
     

15 May, 2017

2 commits

  • 29cb2b3b9   gpio: Move OMAP_GPIO to Kconfig ... Browse Code »

    This driver is used often enough such that we want to have this enabled
    by default on any ARCH_OMAP2PLUS board, and this only compiles on
    ARCH_OMAP2PLUS due to required defines, so mark that as the depends.

    Signed-off-by: Tom Rini

    Tom Rini
     
  • 89024ddc9   TI: Drop 'CONFIG_OMAP' ... Browse Code »

    In the two cases in the code where we use CONFIG_OMAP as a useful test
    currently we can make use of CONFIG_ARCH_OMAP2PLUS instead. With that
    changed we can drop all defines of CONFIG_OMAP. While in here,
    CONFIG_OMAP3430 is only defined and then never used, so drop.

    Signed-off-by: Tom Rini

    Tom Rini
     

11 Jan, 2017

1 commit

  • 1d2c0506d   mmc: move more driver config options to Kconfig ... Browse Code »

    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
    Reviewed-by: Marek Vasut

    Masahiro Yamada
     

22 Nov, 2016

1 commit

28 Jul, 2015

1 commit

  • 9a0f4004c   configs: split ti_armv7_common into a omap generic header ... Browse Code »

    TI armv7 based SoCs are based on two architectures - one based on OMAP
    generation architecture and others based on Keystone architecture.

    Many of the options are architecture specific, however a lot are common
    with v7 architecture. So, step 1 will be to move out OMAP specific stuff
    from ti_armv7_common into a ti_armv7_omap.h header which is then used
    by all the relevant architecture headers.

    Reviewed-by: Tom Rini
    Signed-off-by: Nishanth Menon

    Nishanth Menon