1. 23 Apr, 2019 4 commits
    • Andrew F. Davis's avatar
      ti: k3: drivers: ti_sci: Retry message receive on bad sequence ID · 71a35273
      Andrew F. Davis authored
      
      
      When we get a sequence ID that does not match what we expect then the we
      are looking at is not the one we are expecting and so we error out. We
      can also assume this message is a stale message left in the queue, in
      this case we can read in the next message and check again for our
      message. Switch to doing that here. We only retry a set number of times
      so we don't lock the system if our message is actually lost and will
      never show up.
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      Change-Id: I6c8186ccc45e646d3ba9d431f7d4c451dcd70c5c
      71a35273
    • Andrew F. Davis's avatar
      ti: k3: drivers: ti_sci: Cleanup sequence ID usage · 7a469035
      Andrew F. Davis authored
      
      
      The sequence ID can be set with a message to identify it when it is
      responded to in the response queue. We assign each message a number and
      check for this same number to detect response mismatches.
      
      Start this at 0 and increase it by one for each message sent, even ones
      that do not request or wait for a response as one may still be delivered
      in some cases and we want to detect this.
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      Change-Id: I72b4d1ef98bf1c1409d9db9db074af8dfbcd83ea
      7a469035
    • Andrew F. Davis's avatar
      ti: k3: drivers: sec_proxy: Use direction definitions · fb98ca5a
      Andrew F. Davis authored
      
      
      The direction of a thread should be explicitly compared to avoid
      confusion. Also fixup message wording based on this direction.
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      Change-Id: Ia3cf9413cd23af476bb5d2e6d70bee15234cbd11
      fb98ca5a
    • Andrew F. Davis's avatar
      ti: k3: drivers: sec_proxy: Fix printf format specifiers · 6c30baee
      Andrew F. Davis authored
      
      
      The ID of a thread is not used outside for printing it out when
      something goes wrong. The specifier used is also not consistent.
      Instead of storing the thread ID, store its name and print that.
      Signed-off-by: default avatarAndrew F. Davis <afd@ti.com>
      Change-Id: Id137c2f8dfdd5c599e220193344ece903f80af7b
      6c30baee
  2. 17 Apr, 2019 3 commits
  3. 16 Apr, 2019 1 commit
  4. 12 Apr, 2019 9 commits
  5. 11 Apr, 2019 11 commits
  6. 10 Apr, 2019 3 commits
    • Wei Yu's avatar
      hikey960: Fix race condition between hotplug and idles · 7d76df7d
      Wei Yu authored
      
      
      From the hotplug testing on Hikey960, in some case cores fail to become
      online in the system. When some cores are hotplugged off, if other
      cores in the same cluster enter into CPU idle states at the meantime,
      the cluster will be powered off. This introduces the state machine
      malfunction in the power controller, thus when hotplug on the core
      afterwards, it fails to boot up the core because the power controller
      thinks the cluster is powered on.
      
      This patch is to avoid race condition between hotplug and idles by
      preventing cluster power off when some of cores in the cluster are
      hotplugged off, if all cores in the same cluster are hotplugged off,
      the cluster can be powered off.
      
      Change-Id: Ib2feeb093357c70409a3536cb4f9da9b504fdcbe
      Signed-off-by: default avatarWei Yu <yuwei3@hisilicon.com>
      Signed-off-by: default avatarLeo Yan <leo.yan@linaro.org>
      7d76df7d
    • Joel Hutton's avatar
      cache_helpers.s:fix mixed tabs and spaces · c554e1ad
      Joel Hutton authored
      
      
      Change-Id: I8b7c7888d09200410e1a1c11a070c94dd8013ea7
      Signed-off-by: default avatarJoel Hutton <Joel.Hutton@Arm.com>
      c554e1ad
    • Joel Hutton's avatar
      Add note about erratum 814220 for A7 · f999faca
      Joel Hutton authored
      
      
      On Cortex-A7 an L2 set/way cache maintenance operation can overtake
      an L1 set/way cache maintenance operation. The mitigation for this is
      to use a `DSB` instruction before changing cache. The cache cleaning
      code happens to already be doing this, so only a comment was added.
      
      Change-Id: Ia1ffb8ca8b6bbbba422ed6f6818671ef9fe02d90
      Signed-off-by: default avatarJoel Hutton <Joel.Hutton@Arm.com>
      f999faca
  7. 09 Apr, 2019 6 commits
  8. 08 Apr, 2019 3 commits