1. 11 Feb, 2019 1 commit
    • Ryan Grachek's avatar
      hikey960: enable IOMCU DMAC · c8ab47d4
      Ryan Grachek authored
      
      
      There exists a third DMA controller on the hi3660
      SoC called the IOMCU DMAC. This controller is used by
      peripherals like SPI2 and UART3. Initialize channels 4-7
      as non-secure, while 0-3 remain reserved and secure.
      Signed-off-by: default avatarRyan Grachek <ryan@edited.us>
      c8ab47d4
  2. 01 Feb, 2019 1 commit
  3. 31 Jan, 2019 1 commit
  4. 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
  5. 29 Nov, 2018 1 commit
  6. 08 Nov, 2018 1 commit
  7. 28 Sep, 2018 1 commit
  8. 05 Mar, 2018 1 commit
  9. 22 Jan, 2018 1 commit
    • Leo Yan's avatar
      Hikey960: Enable invalid FIQ handling · b79f7ed0
      Leo Yan authored
      
      
      When some interrupts are configured as group 0 in GICv2, these
      interrupts trigger FIQ signal; this results in the Linux kernel panic
      by reporting log: "Bad mode in FIQ handler detected on CPU0, code
      0x00000000 -- Unknown/Uncategorized".  Unfortunately from kernel side it
      has no permission to read the GIC register for group 0 interrupts so we
      have no chance to get to know which interrupt is configured as secure
      interrupt and cause the kernel panic.
      
      For upper reason, this commit enables FIQ exception handling for
      SPD_none case.  If the system has not enabled SPD the FIQ interrupt is
      trapped into EL3 and the FIQ handler can report the interrupt number so
      we can easily narrow down which FIQ introduce unexpected interrupt.
      After enable SPD we can rely on SPD interrupt route model to handle FIQ.
      Signed-off-by: default avatarLeo Yan <leo.yan@linaro.org>
      b79f7ed0
  10. 01 Sep, 2017 2 commits
  11. 07 Jun, 2017 1 commit
  12. 31 May, 2017 1 commit
  13. 24 May, 2017 1 commit