1. 14 Jun, 2018 1 commit
  2. 30 May, 2018 3 commits
  3. 22 May, 2018 2 commits
  4. 25 Apr, 2018 1 commit
  5. 17 Apr, 2018 1 commit
  6. 13 Feb, 2018 1 commit
  7. 12 Feb, 2018 1 commit
  8. 15 Jan, 2018 2 commits
  9. 15 Nov, 2017 1 commit
  10. 07 Nov, 2017 1 commit
    • Bjorn Andersson's avatar
      remoteproc: qcom: Drop pr_err in q6v5_xfer_mem_ownership() · 9f2a4342
      Bjorn Andersson authored
      The pr_err() in q6v5_xfer_mem_ownership() prints, upon failure, the
      memory range that failed to be transitioned. But on 32-bit architectures
      with CONFIG_PHYS_ADDR_T_64BIT set we cannot cast the phys_addr_t
      variable to a pointer, per below build error. Instead these should be
      formatted with %pap.
      
      In file included from include/linux/kernel.h:14:0,
                       from include/linux/clk.h:16,
                       from drivers/remoteproc/qcom_q6v5_pil.c:18:
      drivers/remoteproc/qcom_q6v5_pil.c: In function 'q6v5_xfer_mem_ownership':
      drivers/remoteproc/qcom_q6v5_pil.c:337:10: error: cast to pointer from integer of different size [-Werror=int-to-pointer-cast]
                (void *)addr, (void *)(addr + size),
                ^
      
      Most callers will upon failure print a specific error message describing
      which memory region that we failed to pass ownership of, so rather than
      fixing the format string this patch fixes up the last callers and drop
      the print from this function, saving us from spamming the log in most of
      these error cases.
      
      Fixes: 6c5a9dc2
      
       ("remoteproc: qcom: Make secure world call for mem ownership switch")
      Reported-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
      9f2a4342
  11. 31 Oct, 2017 3 commits
  12. 28 Aug, 2017 1 commit
  13. 02 Aug, 2017 1 commit
    • Bjorn Andersson's avatar
      remoteproc: qcom: Add support for SSR notifications · 1e140df0
      Bjorn Andersson authored
      
      
      This adds the remoteproc part of subsystem restart, which is responsible
      for emitting notifications to other processors in the system about a
      dying remoteproc instance.
      
      These notifications are propagated to the various communication systems
      in the various remote processors to shut down communication links that
      was left in a dangling state as the remoteproc was stopped (or crashed).
      Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
      1e140df0
  14. 22 Feb, 2017 1 commit
  15. 06 Feb, 2017 5 commits
  16. 01 Feb, 2017 1 commit
    • Arnd Bergmann's avatar
      remoteproc: qcom: fix initializers for qcom_mss_reg_res array · ec671b53
      Arnd Bergmann authored
      The recently added initialization is rather unusual because it uses a constructor for
      a variable-length array to assign a constant structure to a member that uses a fixed-length
      array. This confuses clang and breaks the build.
      
      drivers/remoteproc/qcom_q6v5_pil.c:1024:18: error: incompatible pointer types initializing 'const char *' with an expression of type
      :%s      'struct qcom_mss_reg_res [4]' [-Werror,-Wincompatible-pointer-types]
              .proxy_supply = (struct qcom_mss_reg_res[]) {
                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      drivers/remoteproc/qcom_q6v5_pil.c:1024:18: warning: suggest braces around initialization of subobject [-Wmissing-braces]
              .proxy_supply = (struct qcom_mss_reg_res[]) {
                              ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      
      We can either turn this constructor into a regular initializer by removing
      the 'struct qcom_mss_reg_res[])', or we can make the array variable length.
      
      The latter approach is used for the arrays of strings in the same structure,
      so let's use that here too.
      
      Fixes: 19f902b5
      
       ("remoteproc: qcom: Initialize and enable proxy and active regulators.")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Signed-off-by: default avatarBjorn Andersson <bjorn.andersson@linaro.org>
      ec671b53
  17. 18 Jan, 2017 3 commits
  18. 18 Oct, 2016 1 commit
  19. 03 Oct, 2016 1 commit
  20. 10 Aug, 2016 1 commit
  21. 04 Aug, 2016 1 commit
    • Krzysztof Kozlowski's avatar
      dma-mapping: use unsigned long for dma_attrs · 00085f1e
      Krzysztof Kozlowski authored
      The dma-mapping core and the implementations do not change the DMA
      attributes passed by pointer.  Thus the pointer can point to const data.
      However the attributes do not have to be a bitfield.  Instead unsigned
      long will do fine:
      
      1. This is just simpler.  Both in terms of reading the code and setting
         attributes.  Instead of initializing local attributes on the stack
         and passing pointer to it to dma_set_attr(), just set the bits.
      
      2. It brings safeness and checking for const correctness because the
         attributes are passed by value.
      
      Semantic patches for this change (at least most of them):
      
          virtual patch
          virtual context
      
          @r@
          identifier f, attrs;
      
          @@
          f(...,
          - struct dma_attrs *attrs
          + unsigned long attrs
          , ...)
          {
          ...
          }
      
          @@
          identifier r.f;
          @@
          f(...,
          - NULL
          + 0
           )
      
      and
      
          // Options: --all-includes
          virtual patch
          virtual context
      
          @r@
          identifier f, attrs;
          type t;...
      00085f1e
  22. 15 Jul, 2016 2 commits
  23. 13 Jul, 2016 1 commit