1. 30 Sep, 2017 30 commits
  2. 29 Sep, 2017 10 commits
    • Sam Protsenko's avatar
      env: ti: boot: Show boot status information · 6ca43a58
      Sam Protsenko authored and Tom Rini's avatar Tom Rini committed
      
      
      Add tracing printings to Linux/Android boot commands, so that we can see
      what's going on. Helps to trace possible bugs on early stages and
      improves the output for user (which is especially useful, because we
      have a bunch of boot commands executing one by one).
      
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      6ca43a58
    • Sam Protsenko's avatar
      env: ti: boot: Extract command for eMMC Linux boot · 2717c084
      Sam Protsenko authored and Tom Rini's avatar Tom Rini committed
      
      
      Extract commands for booting Linux from eMMC to separate command. It
      seems more logical that way, and allows us to run the whole command set
      from U-Boot shell with only one command.
      
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      2717c084
    • Sam Protsenko's avatar
      arm: dra7xx: Fix Linux boot from eMMC · a0b0ff0a
      Sam Protsenko authored and Tom Rini's avatar Tom Rini committed
      
      
      Right now on OMAP5-based boards we have only one partition defined for
      Linux boot, which is rootfs. That doesn't work with bootpart=1:2 (that
      is defined in include/environment/ti/boot.h). To fix Linux boot we may
      either:
      
       1. Change bootpart to be 1:1
       2. Or add preceding partition, so that rootfs is actually 1:2
      
      Second choice seems more reasonable, as DFU is already using similar
      partition table and can rely on bootpart to be 1:2.
      
      This patch adds "bootloader" partition. So now eMMC layout for Linux
      boot looks like this:
      
      offset               content                 size          partition
      (KiB)                                        (KiB)
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      
      =======================================================================
      
      0       +--------------------------------+
              | MBR/GPT header                 |   128           -
      128     +--------------------------------+
              | MLO                            |   256           -
      384     +--------------------------------+
              | u-boot.img                     |   1792          bootloader
      2176    +--------------------------------+
              | //////////// hole //////////// |   256           -
      2432    +--------------------------------+
              | U-Boot environment             |   128           -
      2560    +--------------------------------+
              | U-Boot environment (redundant) |   128           -
      2688    +--------------------------------+
              | rootfs                         |   remaining     rootfs
      end     +--------------------------------+
      
      =======================================================================
      
      Guard hole appears because U-Boot environment offset was calculated for
      Android partition table, which has two additional partitions in place of
      that hole ("environment" and "misc" partitions).
      
      This patch also changes rootfs offset from 2 MiB further to 2688 KiB,
      so that there won't be any collisions with U-Boot environment when we
      flash rootfs.
      
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      a0b0ff0a
    • Sam Protsenko's avatar
      arm: am57xx: Fix Linux boot from eMMC · f6d245b8
      Sam Protsenko authored and Tom Rini's avatar Tom Rini committed
      
      
      Right now on OMAP5-based boards we have only one partition defined for
      Linux boot, which is rootfs. That doesn't work with bootpart=1:2 (that
      is defined in include/environment/ti/boot.h). To fix Linux boot we may
      either:
      
       1. Change bootpart to be 1:1
       2. Or add preceding partition, so that rootfs is actually 1:2
      
      Second choice seems more reasonable, as DFU is already using similar
      partition table and can rely on bootpart to be 1:2.
      
      This patch adds "bootloader" partition. So now eMMC layout for Linux
      boot looks like this:
      
      offset               content                 size          partition
      (KiB)                                        (KiB)
      Reviewed-by: Tom Rini's avatarTom Rini <trini@konsulko.com>
      
      =======================================================================
      
      0       +--------------------------------+
              | MBR/GPT header                 |   128           -
      128     +--------------------------------+
              | MLO                            |   256           -
      384     +--------------------------------+
              | u-boot.img                     |   1792          bootloader
      2176    +--------------------------------+
              | //////////// hole //////////// |   256           -
      2432    +--------------------------------+
              | U-Boot environment             |   128           -
      2560    +--------------------------------+
              | U-Boot environment (redundant) |   128           -
      2688    +--------------------------------+
              | rootfs                         |   remaining     rootfs
      end     +--------------------------------+
      
      =======================================================================
      
      Guard hole appears because U-Boot environment offset was calculated for
      Android partition table, which has two additional partitions in place of
      that hole ("environment" and "misc" partitions).
      
      This patch also changes rootfs offset from 2 MiB further to 2688 KiB,
      so that there won't be any collisions with U-Boot environment when we
      flash rootfs.
      
      Signed-off-by: default avatarSam Protsenko <semen.protsenko@linaro.org>
      f6d245b8
    • Karthik Tummala's avatar
      arm: dts: omap3: sync DTS with Linux 4.14-rc1 · 8adb6ec8
      Karthik Tummala authored and Tom Rini's avatar Tom Rini committed
      
      
      This re-syncs omap3 DTS file with current file from
      Linux v4.14-rc1 to ensure a consistent configuration. Upstream
      Linux removed the redundant Interrupt-parent property from usbhsohci,
      usbhsehci, ssi_port1 and ssi_port2 sub nodes.
      
      Signed-off-by: default avatarKarthik Tummala <karthik@techveda.org>
      8adb6ec8
    • Patrice Chotard's avatar
      dm: clk: add missing .priv_auto_alloc_size() for stm32f7 · 0cc40dfc
      Patrice Chotard authored and Tom Rini's avatar Tom Rini committed
      
      
      Add missing .priv_auto_alloc_size() callback.
      Previously private struct stm32_clk was not allocate
      which leads to unpredictable behaviour
      
      Signed-off-by: Patrice Chotard's avatarPatrice Chotard <patrice.chotard@st.com>
      Reviewed-by: Simon Glass's avatarSimon Glass <sjg@chromium.org>
      0cc40dfc
    • Lokesh Vutla's avatar
      ARM: dts: OMAP5+: Enable all gpios in SPL · df518f80
      Lokesh Vutla authored and Tom Rini's avatar Tom Rini committed
      
      
      With DM enabled, gpio numbering is assigned based on the
      probed order of gpios, irrespective of the gpio base. So enable
      all necessary gpios in SPL.
      
      Fixes: edf25d94d55c (“ARM: dts: OMAP5+: Enable gpio in SPL”)
      Reported-by: default avatarGou, Hongmei <h-gou@ti.com>
      Tested-by: default avatarAparna Balasubramanian <aparnab@ti.com>
      Signed-off-by: default avatarSuman Anna <s-anna@ti.com>
      Signed-off-by: Lokesh Vutla's avatarLokesh Vutla <lokeshvutla@ti.com>
      df518f80
    • Lokesh Vutla's avatar
      configs: keystone2: env: Fix burn_uboot_spi command · ba7f58b1
      Lokesh Vutla authored and Tom Rini's avatar Tom Rini committed
      
      
      Now the u-boot spi image is greater than 0x80000, increase the same
      in env during spi erase.
      
      Reported-by: default avatarYan Liu <yan-liu@ti.com>
      Signed-off-by: Lokesh Vutla's avatarLokesh Vutla <lokeshvutla@ti.com>
      ba7f58b1
    • Andrew F. Davis's avatar
      configs: k2g_evm: Make findfdt command populate fdtfile variable · f8e714eb
      Andrew F. Davis authored and Tom Rini's avatar Tom Rini committed
      
      
      On all other platforms the command 'findfdt' populates the variable
      'fdtfile', but on K2G we only populate 'name_fdt'. The generic boot
      and automation scripts fail when 'findfdt' is not populated, fix
      this for K2G.
      
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      f8e714eb
    • Andrew F. Davis's avatar
      configs: am43xx_evm: Avoid relocation onto firewall at the end of DRAM · 373358f2
      Andrew F. Davis authored and Tom Rini's avatar Tom Rini committed
      
      
      On secure devices the initial secure software may install a firewall at
      the end of DRAM, define protected RAM to avoid space.
      
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      373358f2