Skip to content
Snippets Groups Projects
  1. Jul 07, 2014
  2. Jul 05, 2014
  3. Jul 04, 2014
  4. Jul 03, 2014
    • J. German Rivera's avatar
      armv8/fsl-lsch3: Add support to load and start MC Firmware · b940ca64
      J. German Rivera authored
      
      Adding support to load and start the Layerscape Management Complex (MC)
      firmware. First, the MC GCR register is set to 0 to reset all cores. MC
      firmware and DPL images are copied from their location in NOR flash to
      DDR. MC registers are updated with the location of these images.
      Deasserting the reset bit of MC GCR register releases core 0 to run.
      Core 1 will be released by MC firmware. Stop bits are not touched for
      this step. U-boot waits for MC until it boots up. In case of a failure,
      device tree is updated accordingly. The MC firmware image uses FIT format.
      
      Signed-off-by: default avatarJ. German Rivera <German.Rivera@freescale.com>
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      Signed-off-by: default avatarLijun Pan <Lijun.Pan@freescale.com>
      Signed-off-by: default avatarShruti Kanetkar <Shruti@Freescale.com>
      b940ca64
    • York Sun's avatar
      ARMv8/FSL_LSCH3: Add FSL_LSCH3 SoC · 2f78eae5
      York Sun authored
      
      Freescale LayerScape with Chassis Generation 3 is a set of SoCs with
      ARMv8 cores and 3rd generation of Chassis. We use different MMU setup
      to support memory map and cache attribute for these SoCs. MMU and cache
      are enabled very early to bootst performance, especially for early
      development on emulators. After u-boot relocates to DDR, a new MMU
      table with QBMan cache access is created in DDR. SMMU pagesize is set
      in SMMU_sACR register. Both DDR3 and DDR4 are supported.
      
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      Signed-off-by: default avatarVarun Sethi <Varun.Sethi@freescale.com>
      Signed-off-by: default avatarArnab Basu <arnab.basu@freescale.com>
      2f78eae5
    • York Sun's avatar
      ARMv8: Adjust MMU setup · 22932ffc
      York Sun authored
      
      Make MMU function reusable. Platform code can setup its own MMU tables.
      
      Signed-off-by: default avatarYork Sun <yorksun@freescale.com>
      CC: David Feng <fenghua@phytium.com.cn>
      22932ffc
    • J. German Rivera's avatar
      Added 64-bit MMIO accessors for ARMv8 · 0d031e04
      J. German Rivera authored
      
      This is needed for accessing peripherals with 64-bit MMIO registers,
      from ARMv8 processors.
      
      Signed-off-by: default avatarJ. German Rivera <German.Rivera@freescale.com>
      0d031e04
    • Darwin Rambo's avatar
      arm: Add support for semihosting for armv8 fastmodel targets. · 261d2760
      Darwin Rambo authored
      
      The armv8 ARM Trusted Firmware (ATF) can be used to load various ATF
      images and u-boot, and does this for virtual platforms by using
      semihosting. This commit extends this idea by allowing u-boot to also
      use semihosting to load the kernel/ramdisk/dtb. This eliminates the need
      for a bootwrapper and produces a more realistic boot sequence with
      virtual models.
      
      Though the semihosting code is quite generic, support for armv7 in
      fastmodel is less useful due to the wide range of available silicon
      and the lack of a free armv7 fastmodel, so this change contains an
      untested armv7 placeholder for the service trap opcode.
      
      Please refer to doc/README.semihosting for a more detailed description
      of semihosting and how it is used with the armv8 virtual platforms.
      
      Signed-off-by: default avatarDarwin Rambo <drambo@broadcom.com>
      Cc: trini@ti.com
      Cc: fenghua@phytium.com.cn
      Cc: bhupesh.sharma@freescale.com
      261d2760
    • Stephen Warren's avatar
      i2c: tegra: dump alen in debug statements · ad3091ad
      Stephen Warren authored
      
      Since tegra_i2c_{read,write}'s debug() call dumps the chip address, dump
      the address length (alen) too, so the address value can be correctly
      interpreted.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Reviewed-by: default avatarYen Lin <yelin@nvidia.com>
      ad3091ad
    • Stephen Warren's avatar
      i2c: tegra: write clean data to TX FIFO · 981b14f0
      Stephen Warren authored
      
      The Tegra I2C controller's TX FIFO contains 32-bit words. If the final
      FIFO entry of a transaction contains fewer than 4 bytes, the driver
      currently fills the unused FIFO bytes with uninitialized data. This can
      be confusing when reading back the FIFO content for debugging purposes.
      
      Solve this by explicitly initializing the variable containing FIFO data
      before filling it (partially) with data. With this change,
      send_recv_packets()'s loop's if (is_write) code mirrors the else (i.e.
      read) branch.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Reviewed-by: default avatarYen Lin <yelin@nvidia.com>
      981b14f0
    • Stephen Warren's avatar
      i2c: tegra: use repeated start for reads · 68049a08
      Stephen Warren authored
      
      I2C read transactions are typically implemented as follows:
      
      START(write) address REPEATED_START(read) data... STOP
      
      However, Tegra's I2C driver currently implements reads as follows:
      
      START(write) address STOP START(read) data... STOP
      
      This sequence confuses at least the AS3722 PMIC on the Jetson TK1 board,
      leading to corrupted read data in some cases. Fix the driver to chain
      the transactions together using repeated starts to solve this.
      
      Signed-off-by: default avatarStephen Warren <swarren@nvidia.com>
      Reviewed-by: default avatarYen Lin <yelin@nvidia.com>
      68049a08
  5. Jul 02, 2014
Loading