Eric Lee / smarc-uboot

08 Sep, 2017

2 commits

26 Jul, 2017

1 commit

  • 2be296538   Convert CONFIG_ENV_IS_IN_MMC/NAND/UBI and NOWHERE to Kconfig ... Browse Code »
    20

    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
     

16 May, 2017

1 commit

15 May, 2017

1 commit

31 Jan, 2017

1 commit

  • 54925327f   mmc: move CONFIG_GENERIC_MMC to Kconfig ... Browse Code »
    40

    Now, CONFIG_GENERIC_MMC seems equivalent to CONFIG_MMC.

    Let's create an entry for "config GENERIC_MMC" with "default MMC",
    then convert all macro defines in headers to Kconfig. Almost all
    of the defines will go away.

    I see only two exceptions:
    configs/blanche_defconfig
    configs/sandbox_noblk_defconfig

    They define CONFIG_GENERIC_MMC, but not CONFIG_MMC. Something
    might be wrong with these two boards, so should be checked later.

    Anyway, this is the output of the moveconfig tool.

    This commit was created as follows:

    [1] create a config entry in drivers/mmc/Kconfig

    [2] tools/moveconfig.py -r HEAD GENERIC_MMC

    [3] manual clean-up of garbage comments in doc/README.* and
    include/configs/*.h

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

    Masahiro Yamada
     

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
     

30 Dec, 2016

1 commit

  • c27269953   mmc: complete unfinished move of CONFIG_MMC ... Browse Code »
    26

    Commit 7a777f6d6f35 ("mmc: Add generic Kconfig option") created
    a Kconfig entry for this option without any actual moves, then
    commit 44c798799f66 ("sunxi: Use Kconfig CONFIG_MMC") moved
    instances only for SUNXI.

    We generally do not like such partial moves. This kind of work
    is automated by tools/moveconfig.py, so it is pretty easy to
    complete this move.

    I am adding "default ARM || PPC || SANDBOX" (suggested by Tom).
    This shortens the configs and will ease new board porting.

    This commit was created as follows:

    [1] Edit Kconfig (remove the "depends on", add the "default",
    copy the prompt and help message from Linux)

    [2] Run 'tools/moveconfig.py -y -s -r HEAD MMC'

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

    Masahiro Yamada
     

10 Sep, 2016

1 commit

26 Apr, 2016

2 commits

19 Feb, 2016

1 commit

25 Nov, 2015

1 commit

13 Nov, 2015

1 commit

  • d6bf06c0c   ARM: tegra: simplify GPU setup ... Browse Code »

    Enable the GPU node in the system-wide ft_system_setup() hook instead of
    the board-specific ft_board_hook(). This allows us to enable GPU per SoC
    generation instead of per-board as we did initially.

    Reported-by: Stephen Warren
    Signed-off-by: Alexandre Courbot
    Signed-off-by: Tom Warren

    Alexandre Courbot
     

17 Sep, 2015

3 commits

  • f8007235a   p2571: Remove hard-coded counter frequency ... Browse Code »

    The counter frequency is derived from clk_m on Tegra, but that clock can
    be configured by the primary bootloader to run at the same frequency as
    the oscillator (38.4 MHz on Tegra210) or a divided down frequency (most
    typically 19.2 MHz). Remove the hard-coded frequency and allow the timer
    setup code to query the correct value at runtime.

    Signed-off-by: Thierry Reding
    Signed-off-by: Tom Warren

    Thierry Reding
     
  • b9f269f60   ARM: tegra: replace V_PROMPT define with kconfig ... Browse Code »

    Commit 181bd9dc61d2 "kconfig: add config option for shell prompt" replaced
    define V_PROMPT with Kconfig option SYS_PROMPT. This crossed with patches
    adding Tegra T210 boards. Migrate the boards to the new scheme.

    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     
  • bfac08472   ARM: tegra: fix COUNTER_FREQUENCY for T210 ... Browse Code »

    While T210 boards all have 38.4MHz crystals, per the TRM, the only
    supported configuration is to divide the crystal frequency by 2 to
    generate clk_m, which is what feeds the ARM generic timers amongst other
    things. Fix the value of COUNTER_FREQUENCY to reflect this divide-by-2.

    When I queried the 19.2 value in Tom's original T210 patches, I wasn't
    aware of this extra divide-by-2, and didn't notice any effect from the
    incorrect value, since its only used if U-Boot is booted in EL3, whereas
    I'm booting it in EL2.

    Reported-by: Thierry Reding
    Signed-off-by: Stephen Warren
    Signed-off-by: Tom Warren

    Stephen Warren
     

07 Aug, 2015

2 commits

  • 04037c877   ARM: tegra: p2571: remove another unused define ... Browse Code »

    CONFIG_MAX77620_POWER isn't used anywhere. Don't define it in p2571.h.

    Signed-off-by: Stephen Warren
    Reviewed-by: Simon Glass
    Signed-off-by: Tom Warren

    Stephen Warren
     
  • a38a3c4af   ARM: tegra: enable GPU DT node when appropriate ... Browse Code »

    T124/210 requires some specific configuration (VPR setup) to
    be performed by the bootloader before the GPU can be used.
    For this reason, the GPU node in the device tree is disabled
    by default. This patch enables the node if U-boot has performed
    VPR configuration.

    Boards enabled by this patch are T124's Jetson TK1 and Venice2
    and T210's P2571.

    Signed-off-by: Alexandre Courbot
    Cc: Stephen Warren
    Cc: Tom Warren
    Signed-off-by: Tom Warren

    Alexandre Courbot
     

06 Aug, 2015

3 commits

29 Jul, 2015

1 commit