22 Nov, 2016

14 commits

  • Support was already implemented, but not hooked up. This fixes several
    fails in the test cases.

    Signed-off-by: Stefan Brüns
    Acked-by: Stephen Warren

    Stefan Brüns
     
  • A sparse file may have regions not mapped by any extents, at the start
    or at the end of the file, or anywhere between, thus not finding a
    matching extent region is never an error.

    Found by python filesystem tests.

    Signed-off-by: Stefan Brüns

    Stefan Brüns
     
  • If a test uses a fixture which is expensive to setup, the fixture can
    possibly created with session or module scope. As u_boot_console has
    function scope, it can not be used in this case.

    Signed-off-by: Stefan Brüns
    Acked-by: Stephen Warren

    Stefan Brüns
     
  • The IP supports two ports, A and B, each providing up to 32 gpios.
    The driver already creates a 2nd gpio bank by reading the 2nd node
    from DT, so this is quite a simple change to support the 2nd bank.

    Signed-off-by: Phil Edworthy
    Acked-by: Marek Vasut
    Reviewed-by: Simon Glass

    Phil Edworthy
     
  • Make Android partition table the same as for AM57x EVM.

    1. Make "bootloader" partition start from 0x300 sectors offset, so
    DRA7 is bootable in Android mode (see
    CONFIG_SYS_MMCSD_RAW_MODE_U_BOOT_SECTOR option).
    2. Increase "bootloader" partition size, because size of u-boot.img is
    about 632 KiB (when building DT defconfig, with FIT image enabled).
    3. Specify "reserved" partition explicitly, rather than specifying
    "efs" partition start. Reserved area will be used to store U-Boot
    environment on eMMC. It's convenient to have it exposed explicitly
    so we can read/write U-Boot environment.
    4. Keep all Android partitions locations intact, by reducing
    "reserved" partition size. CONFIG_ENV_SIZE is considered.

    Signed-off-by: Sam Protsenko

    Semen Protsenko
     
  • Signed-off-by: Sam Protsenko

    Semen Protsenko
     
  • "fastboot oem format" command reuses "gpt write" command, which in turn
    requires correct partitions defined in $partitions variable. This patch
    adds such definition of Android partitions for DRA7XX EVM board.

    By default $partitions variable contains Linux partition table. In order
    to prepare Android environment one can run next commands from U-Boot
    shell:

    => env set partitions $partitions_android
    => env save

    After those operations one can go to fastboot mode and perform
    "fastboot oem format" to create Android partition table.

    While at it, enable CONFIG_RANDOM_UUID to spare user from providing
    UUIDs for each partition manually.

    Signed-off-by: Sam Protsenko

    Semen Protsenko
     
  • Add support for distro_bootcmd on MMC and fall back to prior
    behavior if distro_bootcmd fails.

    Tested on Beagleboad xM to boot GRUB2 (and then Linux kernel) in EFI mode
    from MMC.

    Signed-off-by: Guillaume GARDET
    Cc: Tom Rini
    Reviewed-by: Tom Rini

    Guillaume GARDET
     
  • Signed-off-by: Sam Protsenko
    Reviewed-by: Tom Rini

    Semen Protsenko
     
  • Enable USB download gadget (needed for fastboot support) and all
    dependencies.

    Signed-off-by: Sam Protsenko
    Reviewed-by: Tom Rini

    Semen Protsenko
     
  • On "fastboot reboot-bootloader" we check "dofastboot" variable and do
    "fastboot 0" command in U-Boot if it's 1. But there are boards which have
    USB controller number other than 0, so it should be respected when
    performing "fastboot" command.

    This patch reuses CONFIG_FASTBOOT_USB_DEV option toprovide correct USB
    controller number to "fastboot" command.

    Signed-off-by: Sam Protsenko
    Reviewed-by: Tom Rini

    Semen Protsenko
     
  • Some boards (like AM57x EVM) has USB OTG controller other than 0. So in
    order to use correct controller number in compiled environment we should
    define CONFIG_FASTBOOT_USB_DEV option.

    For example, when doing "fastboot reboot-bootloader" we want to enter
    fastboot mode automatically. But to do so we need to provide controller
    number to "fastboot" command. If this procedure is defined in some config
    which is common to bunch of boards, and boards have different USB
    controller numbers, we can't just hardcode "fastboot 0" in the
    environment. We need to use configurable option, which this patch adds.

    Signed-off-by: Sam Protsenko
    Reviewed-by: Tom Rini

    Semen Protsenko
     
  • Detect the board very early and avoid reading eeprom multiple times.

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Lokesh Vutla
     
  • This is similar to Commit 93e6253d11030 ("ARM: OMAP4/5: Centralize
    early clock initialization") that was done for OMAP4+, reflecting the same
    for AM33xx and AM43xx SoCs to centralize clock initialization.

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini
    [trini: Add setup_early_clocks that calls setup_clocks_for_console for
    ti81xx]
    Signed-off-by: Tom Rini

    Lokesh Vutla
     

21 Nov, 2016

1 commit

  • Early system initialization is being done before initf_dm is being called
    in U-Boot. Then system will fail to boot if any of the DM enabled driver
    is being called in this system initialization code. So, rearrange the
    code a bit so that DM enabled drivers can be called during early system
    initialization. This is inspired by commit e850ed82bce8 ("ARM: OMAP4+: Allow
    arch specific code to use early DM")

    Signed-off-by: Lokesh Vutla
    Reviewed-by: Tom Rini

    Lokesh Vutla
     

19 Nov, 2016

2 commits


18 Nov, 2016

2 commits


17 Nov, 2016

8 commits


16 Nov, 2016

4 commits


15 Nov, 2016

9 commits