Eric Lee / smarc-uboot

22 Feb, 2018

1 commit

23 Jan, 2018

1 commit

02 Sep, 2017

1 commit

  • ecad7051b   configs: Migrate all of the existing USB symbols, except fastboot ... Browse Code »
    20

    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
     

10 Jun, 2017

1 commit

  • 06cc85a29   tegra: Enable CP15 init ... Browse Code »

    At present CP15 init is disabled on tegra. Use the correct option so that
    this init is performed on boot. This enables the instruction cache, for
    example, which is critical to the machine running at full speed.

    Signed-off-by: Simon Glass

    Simon Glass
     

04 Jun, 2017

1 commit

  • 91d27a17c   Kconfig: Migrate FS_FAT / FAT_WRITE ... Browse Code »

    Now that these symbols are in Kconfig, migrate all users. Use imply on
    a number of platforms that default to having this enabled. As part of
    this we must migrate some straglers for CMD_FAT and DOS_PARTITION.

    Signed-off-by: Tom Rini

    Tom Rini
     

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
     

28 Jan, 2017

3 commits

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

17 Feb, 2016

1 commit

11 Nov, 2015

1 commit

12 Sep, 2015

2 commits

  • f69d72ee2   ARM: tegra: tweak DFU buffer sizes ... Browse Code »

    CONFIG_SYS_DFU_DATA_BUF_SIZE defines the size of chunks transferred
    across USB. This doesn't need to be particularly large, since it doesn't
    limit the overall transfer size.

    CONFIG_SYS_DFU_MAX_FILE_SIZE is used to buffer an entire file before
    writing it to a filesystem. This define limits the maximum file size that
    may be transferred. Bump this up to 32MiB in order to support large
    uncompressed kernel images.

    Both of these buffers are dynamically allocated, and so the size of both
    needs to be taken into account when calculating the required malloc
    region size.

    Signed-off-by: Stephen Warren

    Stephen Warren
     
  • 99d969612   ARM: tegra: fix malloc region sizing ... Browse Code »

    Commit 52a7c98a1772 "tegra-common: increase malloc pool len by dfu mmc
    file buffer size" updated the definition of CONFIG_SYS_MALLOC_LEN for
    Tegra to take account of the DFU buffer size. However, this change had
    no effect, since typical Tegra board config headers don't set the DFU-
    related defines until after tegra-common.h is included. Fix this by
    moving the affected conditional code to tegra-common-post.h, which is
    included last. Also move the definition of SYS_NONCACHED_MEMORY since
    it's a related and adjacent definition.

    Fix the condition to test for the DFU feature, rather than specifically
    MMC DFU support, so it applies in all cases.

    Signed-off-by: Stephen Warren

    Stephen Warren
     

29 Jul, 2015

1 commit

10 Jun, 2015

2 commits

14 May, 2015

2 commits

  • 48cfca240   ARM: tegra: CONFIG_{SYS_, }LOAD{_, }ADDR rationalization ... Browse Code »

    As best I can tell, CONFIG_SYS_LOAD_ADDR and CONFIG_LOADADDR/$loadaddr
    serve essentially the same purpose. Roughly, if a command takes a load
    address, then CONFIG_SYS_LOAD_ADDR or $loadaddr (or both) are the default
    if the command-line does not specify the address. Different U-Boot
    commands are inconsistent re: which of the two default values they use.
    As such, set the two to the same value, and move the logic that does this
    into tegra-common-post.h so it's not duplicated. A number of other non-
    Tegra boards do this too.

    The values chosen for these macros are no longer consistent with anything
    in MEM_LAYOUT_ENV_SETTINGS. Regain consistency by setting $kernel_addr_r
    to CONFIG_LOADADDR. Older scripts tend to use $loadaddr for the default
    kernel load address, whereas newer scripts and features tend to use
    $kernel_addr_r, along with other variables for other purposes such as
    DTBs and initrds. Hence, it's logical they should share the same value.

    I had originally thought to make the $kernel_addr_r and CONFIG_LOADADDR
    have different values. This would guarantee no interference if a script
    used the two variables for different purposes. However, that scenario is
    unlikely given the semantic meaning associated with the two variables.
    The lowest available value is 0x90200000; see comments for
    MEM_LAYOUT_ENV_SETTINGS in tegra30-common-post.h for details. However,
    that value would be problematic for a script that loaded a raw zImage to
    $loadaddr, since it's more than 128MB beyond the start of SDRAM, which
    would interfere with the kernel's CONFIG_AUTO_ZRELADDR. So, let's not do
    that.

    The only potential fallout I could foresee from this patch is if someone
    has a script that loads the kernel to $loadaddr, but some other file
    (DTB, initrd) to a hard-coded address that the new value of $loadaddr
    interferes with. This seems unlikely. A user should not do that; they
    should either hard-code all load addresses, or use U-Boot-supplied
    variables for all load addresses. Equally, any fallout due to this change
    is trivial to fix; simply modify the load addresses in that script.

    Cc: Paul Walmsley
    Signed-off-by: Stephen Warren
    Reviewed-by: Paul Walmsley
    Reviewed-by: Simon Glass
    Signed-off-by: Tom Warren

    Stephen Warren
     
  • ec022efb8   tegra: config: Use CONFIG_LCD to detect LCD presence ... Browse Code »

    Instead of CONFIG_VIDEO_TEGRA, use CONFIG_LCD to determine whether an LCD
    is present. Tegra124 uses a different driver.

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

    Simon Glass
     

24 Oct, 2014

1 commit

23 Oct, 2014

2 commits

  • fda6fac39   dm: tegra: spi: Convert to driver model ... Browse Code »

    This converts the Tegra SPI drivers to use driver model. This is tested
    on:

    - Tegra20 - trimslice
    - Tegra30 - beaver
    - Tegra124 - dalmore

    (not tested on Tegra124)

    Reviewed-by: Jagannadha Sutradharudu Teki
    Signed-off-by: Simon Glass

    Simon Glass
     
  • 4dab5549a   tegra: clean-up useless define ... Browse Code »

    Wondering what exactly that one should bring (;-p). Looks like a remnant of the last commit

    783e6a72b8278d59854ced41a4696c9a14abbb0b
    kconfig: move CONFIG_OF_* to Kconfig

    Signed-off-by: Marcel Ziswiler
    Acked-by: Simon Glass
    Signed-off-by: Tom Warren

    Marcel Ziswiler
     

25 Sep, 2014

1 commit

  • 783e6a72b   kconfig: move CONFIG_OF_* to Kconfig ... Browse Code »
    43

    This commit moves:
    CONFIG_OF_CONTROL
    CONFIG_OF_SEPARATE
    CONFIG_OF_EMBED
    CONFIG_OF_HOSTFILE

    Because these options are currently not supported for SPL,
    the "Device Tree Control" menu does not appear in the SPL
    configuration.

    Note:
    zynq-common.h should be adjusted so as not to change the
    default value of CONFIG_SPL_FAT_LOAD_PAYLOAD_NAME.

    Signed-off-by: Masahiro Yamada
    Acked-by: Simon Glass
    Cc: Stephen Warren
    Cc: Minkyu Kang
    Acked-by: Michal Simek

    Masahiro Yamada
     

09 Aug, 2014

1 commit

20 Jun, 2014

2 commits

  • fe7b7cd26   ARM: tegra: set initrd_high so boot scripts work ... Browse Code »

    During bootm/z, U-Boot relocates the DTB and initrd to high memory so
    they are out of the way of the kernel. On ARM at least, some parts of
    high memory are "highmem" and can't be accessed at early boot. To solve
    this, we need to restrict this relocation process to use lower parts of
    RAM that area accessible.

    For the DTB, an earlier patch of mine set CONFIG_SYS_BOOTMAPSZ. However,
    since some platforms have different restrictions on DTB and initrd
    location, that config option doesn't affect the initrd. We need to set
    the initrd_high environment variable to control the initrd relocation.

    Since we have carefully chosen the load addresses for the DTB and
    initrd (see comments in include/configs/tegraNNN-common.h re: values in
    MEM_LAYOUT_ENV_SETTINGS), we don't actually need any DTB or initrd
    relocation at all. Skipping relocation removes some redundant work.
    Hence, set both fdt_high and initrd_high to ffffffff which completely
    disables relocation.

    If the user does something unusual, such as using custom locations for
    the DTB/initrd load address or wanting to use DTB/initrd relocation for
    some reason, they can simply set these variables to custom values to
    override these environment defaults.

    With this change, cmd_sysboot works correctly for a filesystem created
    by the Fedora installer.

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

    Stephen Warren
     
  • 72638b02f   ARM: tegra: fix extlinux.conf search location ... Browse Code »

    extlinux.conf is stored in /boot/extlinux/extlinux.conf rather than
    /boot/extlinux.conf. Adjust Tegra's default boot scripts to use the
    correct location. This change aligns Tegra's boot scripts with rpi_b.h
    and also the location that the Fedora installer actually puts the file.

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

    Stephen Warren
     

06 Mar, 2014

2 commits

  • f940c72e1   ARM: tegra: implement bootcmd_pxe ... Browse Code »

    This retrieves a PXE config file over the network, and executes it. This
    allows an extlinux config file to be retrieved over the network and
    executed, whereas the existing bootcmd_dhcp retrieves a U-Boot script.

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

    Stephen Warren
     
  • 4d7d2e570   ARM: tegra: rework boot scripts ... Browse Code »

    Update the common Tegra boot scripts in the default environment to

    a) Make use of the new "test -e" shell command to avoid some error
    messages.

    b) Allow booting using the sysboot command and extlinux.conf. This
    allows easy creation of boot menus, and provides a simple interface
    for distros to parameterize/configure the boot process.

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

    Stephen Warren
     

04 Feb, 2014

2 commits

  • 09266b270   ARM: tegra: clear $usb_need_init each boot ... Browse Code »

    $usb_need_init prevents "usb start" from being run multiple times for
    each boot attempt, i.e. once for USB storage, another for PXE, and
    another for DHCP. However, the flag that's used to determine when to run
    "usb start" is never cleared, so a subsequent "boot" command will never
    probe for a freshly plugged in USB device. Fix this so that new USB
    devices will be probed once per boot attempt.

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

    Stephen Warren
     
  • b9b53a60a   ARM: tegra: set env vars to indicate Cardhu A04 support ... Browse Code »

    The U-Boot "cardhu" build supports only revision 4 of the Cardhu board
    and later compatible revisions. Hence, set $board_name in the default
    environment to "cardhu-a04" rather than just "cardhu".

    The Linux kernel has separate DTs for Cardhu A02 and A04, although the
    former isn't really supported any more. Consequently, the kernel DT file
    that matches the U-Boot cardhu build is "tegra30-cardhu-a04.dtb" rather
    than "tegra30-cardhu.dtb". Set the $fdtfile default environment variable
    to reflect this.

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

    Stephen Warren
     

24 Jul, 2013

2 commits

23 Jul, 2013

1 commit

29 May, 2013

1 commit