13 Dec, 2017

2 commits


08 Sep, 2017

2 commits


12 Aug, 2017

1 commit


29 Jul, 2017

1 commit


26 Jul, 2017

1 commit

  • 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
     

12 Jul, 2017

1 commit


06 Jun, 2017

1 commit

  • The problems with the current DFU layout are:
    MMC: The space allocated for u-boot is too small for the latest u-boot
    (>750KB). We need to increase it. eMMC uses a much bigger area (2MB).
    eMMC: region "u-boot.img.raw" overlaps the environment area and the region
    "spl-os-image.raw".
    both: region "spl-os-image.raw" is quite small and can't handle android
    kernels

    Fixing this requires growing some regions and moving others.
    Care has been taken to leave some room for further growth of
    "spl-os-args.raw".
    Also the "env" now appears in the dfu so that it's apparent that the
    region is not free space that can be used to grow "u-boot.img.raw".
    The MLO region is 0x100 sectors wide but the 0x100 are unused in case the
    MLO comes too overflow this areas.
    The total space allocated for those raw binaries is 16MB, of which 13+MB
    are reserved for the kernel image.

    Signed-off-by: Jean-Jacques Hiblot
    Reviewed-by: Tom Rini
    Reviewed-by: Sam Protsenko

    Jean-Jacques Hiblot
     

16 May, 2017

2 commits


15 May, 2017

2 commits

  • In order to be able to migrate the various SoC EHCI CONFIG options we
    first need to finish the switch from CONFIG_USB_EHCI to
    CONFIG_USB_EHCI_HCD.

    Cc: Marek Vasut
    Signed-off-by: Tom Rini
    Reviewed-by: Marek Vasut

    Tom Rini
     
  • While in theory this value could be used in places outside of "omap5"
    (such as OMAP4), we only make use of it today in OMAP5, so place the
    Kconfig entry there. Given that Kconfig lets us provide a default, we
    drop CONFIG_DEFAULT_OMAP_RESET_TIME_MAX_USEC entirely. The contents of
    doc/README.omap-reset-time make a good help entry, so adjust them
    slightly and delete the file. Move the comment about range to where we
    use the value now, and have Kconfig enforce the upper bound.

    Signed-off-by: Tom Rini

    Tom Rini
     

20 Mar, 2017

1 commit


28 Jan, 2017

2 commits


03 Dec, 2016

1 commit

  • Introduce include/environment/ti/dfu.h that
    consolidates environment variable definitions
    for various TI boards that support DFU today.

    Tested on AM335x EVM, AM437x SK EVM and DRA74x
    EVM by using DFU to write to SD card.

    Signed-off-by: Sekhar Nori
    Reviewed-by: Tom Rini

    Sekhar Nori
     

27 Sep, 2016

1 commit

  • Introduce a hidden USB_FUNCTION_DFU Kconfig option and select it for
    CMD_DFU (as we must have the DFU command enabled to do anything DFU).
    Make all of the entries in drivers/dfu/Kconfig depend on CMD_DFU and add
    options for all of the back end choices that DFU can make use of.

    Cc: Lukasz Majewski
    Signed-off-by: Tom Rini
    Acked-by: Lukasz Majewski

    Tom Rini
     

10 Sep, 2016

1 commit


08 Aug, 2016

1 commit

  • The meaning of CONFIG_USB in U-Boot is different from that in Linux.

    As you see in drivers/usb/Kconfig of Linux, CONFIG_USB enables the
    USB host controller support, while CONFIG_USB_SUPPORT is used to
    enable the whole of the USB sub-system.

    When I added CONFIG_USB into Kconfig by commit 6e7e9294d321 ("usb:
    add basic USB configs in Kconfig"), I planned to follow the Linux's
    convention, i.e. CONFIG_USB to enable/disable the USB host support.

    Then, commit 68f7c5db2d1e ("usb: Generic USB Kconfig option, that
    fits both host and gadget and comments") changed the logic of the
    CONFIG_USB to point to the whole of the USB sub-system. As a result,
    currently we do not have an option for USB host.

    This commit adds CONFIG_USB_HOST, which will be useful to compile
    in the USB host support code.

    CONFIG_USB_HOST is not referenced at all, but strangely some boards
    define it in board headers. I removed them because USB_HOST will be
    selected in Kconfig going forward.

    Signed-off-by: Masahiro Yamada

    Masahiro Yamada
     

17 May, 2016

1 commit


26 Apr, 2016

2 commits


20 Apr, 2016

7 commits


26 Mar, 2016

1 commit

  • The description was borrowed from kernel. "tristate" type was changed
    to "bool" (I believe we don't support modules for u-boot yet, right?).
    CONFIG_USB_GADGET requires CONFIG_USB to be defined too, so add it along
    as well.

    Definitions were added to defconfig files in a way that
    "make savedefconfig" generates exactly the same file as used defconfig.

    Signed-off-by: Sam Protsenko
    [trini: Add zynq_zc702 conversion]
    Signed-off-by: Tom Rini

    Sam Protsenko
     

12 Sep, 2015

1 commit


26 Jun, 2015

1 commit


15 Jun, 2015

1 commit


01 Jun, 2015

1 commit


06 Jan, 2015

1 commit


05 Dec, 2014

1 commit


10 Oct, 2014

1 commit


18 Apr, 2014

1 commit


18 Feb, 2014

1 commit