1. 29 Jan, 2019 2 commits
    • Anson Huang's avatar
      imx: power optimization for i.mx8qx · e6cf7a46
      Anson Huang authored
      
      
      Current implementation of i.MX8QX power management related
      features does NOT optimize power number, all system resources
      like CCI, DDR, and A cluster etc. are kept in STBY mode (powered
      ON) when system suspend or CPU hotplug.
      
      To lower the power number, OFF mode should be adopted for those
      system resources whenever they can be OFF, A cluster will be OFF
      if the CPUs in the cluster are all off line, DDR/MU/DB can be OFF
      if system suspend, IRQ steer can be OFF if the wakeup source is
      belonged to system controller partition, so wakeup source runtime
      check is used to determine if IRQ steer can be OFF before system
      suspend.
      
      If resources are powered off for suspend, they should be restored
      properly after system resume.
      Signed-off-by: default avatarAnson Huang <Anson.Huang@nxp.com>
      e6cf7a46
    • Anson Huang's avatar
      imx: power optimization for i.mx8qm · 3a2b5199
      Anson Huang authored
      
      
      Current implementation of i.MX8QM power management related
      features does NOT optimize power number, all system resources
      like CCI, DDR, and A cluster etc. are kept in STBY mode (powered
      ON) when system suspend or CPU hotplug.
      
      To lower the power number, OFF mode should be adopted for those
      system resources whenever they can be OFF, A cluster will be OFF
      if the CPUs in the cluster are all off line, DDR/MU/DB can be OFF
      if system suspend, IRQ steer can be OFF if the wakeup source is
      belonged to system controller partition, so wakeup source runtime
      check is used to determine if IRQ steer can be OFF before system
      suspend.
      
      If resources are powered off for suspend, they should be restored
      properly after system resume.
      Signed-off-by: default avatarAnson Huang <Anson.Huang@nxp.com>
      3a2b5199
  2. 25 Jan, 2019 9 commits
  3. 24 Jan, 2019 2 commits
  4. 23 Jan, 2019 26 commits
  5. 22 Jan, 2019 1 commit
    • Andrew F. Davis's avatar
      ti: k3: common: Add support for runtime detection of GICR base address · b5443284
      Andrew F. Davis authored
      
      
      Valid addresses for GICR base are always a set calculable distance from
      the GICD and is based on the number of cores a given instance of GICv3 IP
      can support. The formula for the number of address bits is given by the
      ARM GIC-500 TRM section 3.2 as 2^(18+log2(cores)) with the MSB set to
      one for GICR instances. Holes in the GIC address space are also
      guaranteed to safely return 0 on reads. This allows us to support runtime
      detection of the GICR base address by starting from GIC base address plus
      BIT(18) and walking until the GICR ID register (IIDR) is detected. We
      stop searching after BIT(20) to prevent searching out into space if
      something goes wrong. This can be extended out if we ever have a device
      with 16 or more cores.
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      b5443284