1. 09 Jan, 2018 26 commits
  2. 08 Jan, 2018 4 commits
  3. 03 Jan, 2018 6 commits
  4. 02 Jan, 2018 4 commits
    • Sinan Kaya's avatar
      i7300_idle: remove unused file · 337ccce6
      Sinan Kaya authored
      i7300_idle.h is not being called by any source file and contains calls to
      pci_get_bus_and_slot() that we are trying to deprecate. Remove unused file.
      Signed-off-by: default avatarSinan Kaya <okaya@codeaurora.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      337ccce6
    • Colin Ian King's avatar
      mei: fix incorrect logical operator in if statement · 912ed8af
      Colin Ian King authored
      The current expression using the || operator is always true because
      dev->dev_state cannot be equal to two different values at the same time.
      Fix this by replacing the || with &&.
      
      Detected by CoverityScan, CID#1463042 ("Constant expression result")
      
      Fixes: 8d52af67 ("mei: speed up the power down flow")
      Signed-off-by: default avatarColin Ian King <colin.king@canonical.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      912ed8af
    • Tomas Winkler's avatar
      mei: me: allow runtime pm for platform with D0i3 · cc365dcf
      Tomas Winkler authored
      >From the pci power documentation:
      "The driver itself should not call pm_runtime_allow(), though. Instead,
      it should let user space or some platform-specific code do that (user space
      can do it via sysfs as stated above)..."
      
      However, the S0ix residency cannot be reached without MEI device getting
      into low power state. Hence, for mei devices that support D0i3, it's better
      to make runtime power management mandatory and not rely on the system
      integration such as udev rules.
      This policy cannot be applied globally as some older platforms
      were found to have broken power management.
      
      Cc: <stable@vger.kernel.org> v4.13+
      Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
      Signed-off-by: default avatarTomas Winkler <tomas.winkler@intel.com>
      Reviewed-by: default avatarAlexander Usyskin <alexander.usyskin@intel.com>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      cc365dcf
    • Arnd Bergmann's avatar
      slimbus: qcom-ctrl: use normal allocation · c127f98b
      Arnd Bergmann authored
      The previous patch addressed a warning but not the cause:
      
      drivers/slimbus/qcom-ctrl.c: In function 'qcom_slim_probe':
      drivers/slimbus/qcom-ctrl.c:584:9: error: passing argument 3 of 'dmam_alloc_coherent' from incompatible pointer type [-Werror=incompatible-pointer-types]
      
      There are two things wrong here:
      
      - The naming is very confusing, we now have a member named 'phys'
        that doesn't refer to a phys_addr_t but a dma_addr_t. If we needed
        a dma address, it should be named 'dma' to avoid confusion, and
        to make it less likely that someone passes it into a function that
        expects a physical address.
      
      - The dma address is not used at all at this point. It may have been
        designed to support DMA in the future, but today it doesn't, so
        the only effect right now is to make transfers artificially slower
        by using uncached memory instead of cached memory for a temporary
        buffer.
      
      This removes the unused structure member and instead changes the code
      to call devm_kcalloc(), which matches the usage of the 'base' pointer
      as an array of temporary buffers.
      
      Fixes: db809859 ("slimbus: qcom: fix incompatible pointer warning")
      Signed-off-by: default avatarArnd Bergmann <arnd@arndb.de>
      Cc: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>
      Signed-off-by: default avatarGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      c127f98b