1. 05 Feb, 2019 1 commit
  2. 31 Jan, 2019 13 commits
    • Varun Wadekar's avatar
      Tegra: restrict non-secure PMC accesses · a01b0f16
      Varun Wadekar authored
      
      
      Platforms that do not support bpmp firmware, do not need access
      to the PMC block from outside of the CPU complex. The agents
      running on the CPU can always access the PMC through the EL3
      exception space.
      
      This patch restricts non-secure world access to the PMC block on
      such platforms.
      
      Change-Id: I2c4318dc07ddf6407c1700595e0f4aac377ba258
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      a01b0f16
    • Varun Wadekar's avatar
      Tegra210: toggle ring oscillator across cluster idle · 6a397d1d
      Varun Wadekar authored
      
      
      This patch toggles the ring oscillator state across cluster idle
      as DFLL loses its state. We dont want garbage values being written
      to the pmic when we enter cluster idle state, so enable "open loop"
      when we enter CC6 and restore the state to "closed loop" on exit.
      
      Change-Id: I56f4649f57bcc651d6c415a6dcdc978e9444c97b
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      6a397d1d
    • kalyani chidambaram's avatar
      Tegra210: clear PMC_DPD registers on resume · da0f4743
      kalyani chidambaram authored
      
      
      This patch clears the PMC's DPD registers on resuming from System
      Suspend, for all Tegra210 platforms that support the sc7entry-fw.
      
      Change-Id: I7881ef0a5f609ed28b158bc2f4016abea3c7f305
      Signed-off-by: default avatarkalyani chidambaram <kalyanic@nvidia.com>
      da0f4743
    • Varun Wadekar's avatar
      Tegra210: suspend/resume bpmp interface across System Suspend · e275ae7a
      Varun Wadekar authored
      
      
      The BPMP firmware takes some time to initialise its state on exiting
      System Suspend state. The CPU needs to synchronize with the BPMP during
      this process to avoid any race conditions. This patch suspends and resumes
      the BPMP interface across a System Suspend cycle, to fix this race.
      
      Change-Id: I82a61d12ef3eee267bdd8d4386bed23397fbfd2d
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      e275ae7a
    • Varun Wadekar's avatar
      Tegra210: skip past sc7entry-fw signature header · c33473d5
      Varun Wadekar authored
      
      
      This patch skips past the signature header added to the sc7entry-fw
      binary by the previous level bootloader. Currently, the size of
      the header is 1KB, so adjust the start address and the binary size
      at the time of copy.
      
      Change-Id: Id0494548009749035846d54df417a960c640c8f9
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      c33473d5
    • Varun Wadekar's avatar
      Tegra210: move sc7entry-fw inside the TZDRAM fence · 7350277b
      Varun Wadekar authored
      
      
      This patch uses the sc7entry-fw base/size values to calculate the
      TZDRAM fence, so as to move sc7entry-fw inside the TZDRAM fence.
      
      Change-Id: I91aeeeece857076c478cdc4c18a6ad70dc265031
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      7350277b
    • kalyani chidambaram's avatar
      Tegra210: SiP handlers to allow PMC access · fdc08e2e
      kalyani chidambaram authored
      
      
      This patch adds SiP handler for Tegra210 platforms to service
      read/write requests for PMC block. None of the secure registers
      are accessible to the NS world though.
      
      Change-Id: I7dc1f10c6a6ee6efc642ddcfb1170fb36d3accff
      Signed-off-by: default avatarkalyani chidambaram <kalyanic@nvidia.com>
      fdc08e2e
    • Varun Wadekar's avatar
      Tegra210: power off all DMA masters before System Suspend entry · 2d5560f9
      Varun Wadekar authored
      
      
      This patch puts all the DMA masters in reset before starting the System
      Suspend sequence. This helps us make sure that there are no rogue agents
      in the system trying to over-write the SC7 Entry Firmware with their own.
      
      Change-Id: I7eb39999d229951e612fbfeb9f86c4efb8f98b5a
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      2d5560f9
    • Varun Wadekar's avatar
      Tegra: support for System Suspend using sc7entry-fw binary · 3ca3c27c
      Varun Wadekar authored
      
      
      This patch adds support to enter System Suspend on Tegra210 platforms
      without the traditional BPMP firmware. The BPMP firmware will no longer
      be supported on Tegra210 platforms and its functionality will be
      divided across the CPU and sc7entry-fw.
      
      The sc7entry-fw takes care of performing the hardware sequence required
      to enter System Suspend (SC7 power state) from the COP. The CPU is required
      to load this firmware to the internal RAM of the COP and start the sequence.
      The CPU also make sure that the COP is off after cold boot and is only
      powered on when we want to start the actual System Suspend sequence.
      
      The previous bootloader loads the firmware to TZDRAM and passes its base and
      size as part of the boot parameters. The EL3 layer is supposed to sanitize
      the parameters before touching the firmware blob.
      
      To assist the warmboot code with the PMIC discovery, EL3 is also supposed to
      program PMC's scratch register #210, with appropriate values. Without these
      settings the warmboot code wont be able to get the device out of System
      Suspend.
      
      Change-Id: I5a7b868512dbfd6cfefd55acf3978a1fd7ebf1e2
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      3ca3c27c
    • Varun Wadekar's avatar
      Tegra210: remove support for cluster power down · 93e3b0f3
      Varun Wadekar authored
      
      
      This patch removes support for powering down a CPU cluster on
      Tegra210 platforms as none of them actually use it.
      
      Change-Id: I9665634cf2b5b7b8a1b5a2700cae152dc9165fe3
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      93e3b0f3
    • Varun Wadekar's avatar
      Tegra210: support for cluster idle from the CPU · 7db077f2
      Varun Wadekar authored
      
      
      This patch adds support to enter/exit to/from cluster idle power
      state on Tegra210 platforms that do not load BPMP firmware.
      
      The CPU initates the cluster idle sequence on the last standing
      CPU, by following these steps:
      
      Entry
      -----
      * stop other CPUs from waking up
      * program the PWM pinmux to tristate for OVR PMIC
      * program the flow controller to enter CC6 state
      * skip L1 $ flush during cluster power down, as L2 $ is inclusive
        of L1 $ on Cortex-A57 CPUs
      
      Exit
      ----
      * program the PWM pinmux to un-tristate for OVR PMIC
      * allow other CPUs to wake up
      
      This patch also makes sure that cluster idle state entry is not
      enabled until CL-DVFS is ready.
      
      Change-Id: I54cf31bf72b4a09d9bf9d2baaed6ee5a963c7808
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      7db077f2
    • Varun Wadekar's avatar
      Tegra210: Enable WDT_CPU interrupt for FIQ Debugger · 51a5e593
      Varun Wadekar authored
      
      
      This patch enables the watchdog timer's interrupt as an FIQ
      interrupt to the CPU. The interrupt generated by the watchdog
      is connected to the flow controller for power management reasons,
      and needs to be routed to the GICD for it to reach the CPU.
      
      Change-Id: I9437b516da2c5d763eca72694ed7f3c7389b3d9e
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      51a5e593
    • Varun Wadekar's avatar
      Tegra: fiq_glue: support to handle LEGACY_FIQ PPIs for Tegra SoCs · d16b045c
      Varun Wadekar authored
      
      
      This patch adds support to handle secure PPIs for Tegra watchdog timers. This
      functionality is currently protected by the ENABLE_WDT_LEGACY_FIQ_HANDLING
      configuration variable and is only enabled for Tegra210 platforms, for now.
      
      Change-Id: I0752ef54a986c58305e1bc8ad9be71d4a8bbd394
      Signed-off-by: default avatarVarun Wadekar <vwadekar@nvidia.com>
      d16b045c
  3. 23 Jan, 2019 2 commits
  4. 18 Jan, 2019 8 commits
  5. 16 Jan, 2019 7 commits
  6. 04 Jan, 2019 1 commit
    • Antonio Nino Diaz's avatar
      Sanitise includes across codebase · 09d40e0e
      Antonio Nino Diaz authored
      Enforce full include path for includes. Deprecate old paths.
      
      The following folders inside include/lib have been left unchanged:
      
      - include/lib/cpus/${ARCH}
      - include/lib/el3_runtime/${ARCH}
      
      The reason for this change is that having a global namespace for
      includes isn't a good idea. It defeats one of the advantages of having
      folders and it introduces problems that are sometimes subtle (because
      you may not know the header you are actually including if there are two
      of them).
      
      For example, this patch had to be created because two headers were
      called the same way: e0ea0928 ("Fix gpio includes of mt8173 platform
      to avoid collision."). More recently, this patch has had similar
      problems: 46f9b2c3 ("drivers: add tzc380 support").
      
      This problem was introduced in commit 4ecca339
      
       ("Move include and
      source files to logical locations"). At that time, there weren't too
      many headers so it wasn't a real issue. However, time has shown that
      this creates problems.
      
      Platforms that want to preserve the way they include headers may add the
      removed paths to PLAT_INCLUDES, but this is discouraged.
      
      Change-Id: I39dc53ed98f9e297a5966e723d1936d6ccf2fc8f
      Signed-off-by: default avatarAntonio Nino Diaz <antonio.ninodiaz@arm.com>
      09d40e0e
  7. 18 Dec, 2018 1 commit
  8. 17 Feb, 2018 1 commit
    • Andreas Färber's avatar
      tegra: Fix mmap_region_t struct mismatch · 28db3e96
      Andreas Färber authored
      Commit fdb1964c
      
       ("xlat: Introduce
      MAP_REGION2() macro") added a granularity field to mmap_region_t.
      
      Tegra platforms were using the v2 xlat_tables implementation in
      common/tegra_common.mk, but v1 xlat_tables.h headers in soc/*/plat_setup.c
      where arrays are being defined. This caused the next physical address to
      be read as granularity, causing EINVAL error and triggering an assert.
      
      Consistently use xlat_tables_v2.h header to avoid this.
      
      Fixes ARM-software/tf-issues#548.
      Signed-off-by: default avatarAndreas Färber <afaerber@suse.de>
      28db3e96
  9. 14 Jul, 2017 1 commit
  10. 14 Jun, 2017 1 commit
  11. 03 May, 2017 1 commit
  12. 01 May, 2017 2 commits
  13. 20 Mar, 2017 1 commit