1. 20 2月, 2018 1 次提交
  2. 03 1月, 2018 1 次提交
    • T
      mei: me: allow runtime pm for platform with D0i3 · cc365dcf
      Tomas Winkler 提交于
      >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: NTomas Winkler <tomas.winkler@intel.com>
      Reviewed-by: NAlexander Usyskin <alexander.usyskin@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      cc365dcf
  3. 06 11月, 2017 1 次提交
  4. 04 10月, 2017 2 次提交
  5. 11 8月, 2017 1 次提交
    • A
      mei: exclude device from suspend direct complete optimization · 557909e1
      Alexander Usyskin 提交于
      MEI device performs link reset during system suspend sequence.
      The link reset cannot be performed while device is in
      runtime suspend state. The resume sequence is bypassed with
      suspend direct complete optimization,so the optimization should be
      disabled for mei devices.
      
      Fixes:
       [  192.940537] Restarting tasks ...
       [  192.940610] PGI is not set
       [  192.940619] ------------[ cut here ]------------ [  192.940623]
       WARNING: CPU: 0
       me.c:653 mei_me_pg_exit_sync+0x351/0x360 [  192.940624] Modules
       linked
       in:
       [  192.940627] CPU: 0 PID: 1661 Comm: kworker/0:3 Not tainted
       4.13.0-rc2+
       #2 [  192.940628] Hardware name: Dell Inc. XPS 13 9343/0TM99H, BIOS
       A11
       12/08/2016 [  192.940630] Workqueue: pm pm_runtime_work <snip> [
       192.940642] Call Trace:
       [  192.940646]  ? pci_pme_active+0x1de/0x1f0 [  192.940649]  ?
       pci_restore_standard_config+0x50/0x50
       [  192.940651]  ? kfree+0x172/0x190
       [  192.940653]  ? kfree+0x172/0x190
       [  192.940655]  ? pci_restore_standard_config+0x50/0x50
       [  192.940663]  mei_me_pm_runtime_resume+0x3f/0xc0
       [  192.940665]  pci_pm_runtime_resume+0x7a/0xa0 [  192.940667]
       __rpm_callback+0xb9/0x1e0 [  192.940668]  ?
       preempt_count_add+0x6d/0xc0 [  192.940670]  rpm_callback+0x24/0x90 [
       192.940672]  ? pci_restore_standard_config+0x50/0x50
       [  192.940674]  rpm_resume+0x4e8/0x800 [  192.940676]
       pm_runtime_work+0x55/0xb0 [  192.940678]
       process_one_work+0x184/0x3e0 [  192.940680]
       worker_thread+0x4d/0x3a0 [ 192.940681]  ?
       preempt_count_sub+0x9b/0x100 [  192.940683]
       kthread+0x122/0x140 [  192.940684]  ? process_one_work+0x3e0/0x3e0 [
       192.940685]  ? __kthread_create_on_node+0x1a0/0x1a0
       [  192.940688]  ret_from_fork+0x27/0x40 [  192.940690] Code: 96 3a
       9e ff 48 8b 7d 98 e8 cd 21 58 00 83 bb bc 01 00 00
       04 0f 85 40 fe ff ff e9 41 fe ff ff 48 c7 c7 5f 04 99 96 e8 93 6b 9f
       ff <0f> ff e9 5d fd ff ff e8 33 fe 99 ff 0f 1f 00 0f 1f 44 00 00 55
       [  192.940719] ---[ end trace
       a86955597774ead8 ]--- [  192.942540] done.
      Suggested-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reported-by: NDominik Brodowski <linux@dominikbrodowski.net>
      Cc: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
      Cc: Dominik Brodowski <linux@dominikbrodowski.net>
      Signed-off-by: NAlexander Usyskin <alexander.usyskin@intel.com>
      Signed-off-by: NTomas Winkler <tomas.winkler@intel.com>
      Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
      557909e1
  6. 17 7月, 2017 2 次提交
  7. 08 4月, 2017 1 次提交
  8. 31 1月, 2017 1 次提交
  9. 30 11月, 2016 1 次提交
  10. 27 9月, 2016 1 次提交
  11. 12 9月, 2016 1 次提交
  12. 30 8月, 2016 2 次提交
  13. 02 3月, 2016 1 次提交
  14. 08 2月, 2016 1 次提交
  15. 08 1月, 2016 1 次提交
  16. 04 8月, 2015 2 次提交
  17. 26 3月, 2015 1 次提交
  18. 02 3月, 2015 1 次提交
  19. 05 12月, 2014 1 次提交
  20. 27 11月, 2014 1 次提交
  21. 29 9月, 2014 4 次提交
  22. 26 9月, 2014 1 次提交
  23. 18 7月, 2014 1 次提交
  24. 10 7月, 2014 2 次提交
  25. 28 5月, 2014 2 次提交
  26. 04 5月, 2014 2 次提交
  27. 17 4月, 2014 1 次提交
  28. 18 3月, 2014 3 次提交