1. 24 10月, 2012 1 次提交
    • R
      PM / QoS: Make it possible to expose PM QoS device flags to user space · e39473d0
      Rafael J. Wysocki 提交于
      Define two device PM QoS flags, PM_QOS_FLAG_NO_POWER_OFF
      and PM_QOS_FLAG_REMOTE_WAKEUP, and introduce routines
      dev_pm_qos_expose_flags() and dev_pm_qos_hide_flags() allowing the
      caller to expose those two flags to user space or to hide them
      from it, respectively.
      
      After the flags have been exposed, user space will see two
      additional sysfs attributes, pm_qos_no_power_off and
      pm_qos_remote_wakeup, under the device's /sys/devices/.../power/
      directory.  Then, writing 1 to one of them will update the
      PM QoS flags request owned by user space so that the corresponding
      flag is requested to be set.  In turn, writing 0 to one of them
      will cause the corresponding flag in the user space's request to
      be cleared (however, the owners of the other PM QoS flags requests
      for the same device may still request the flag to be set and it
      may be effectively set even if user space doesn't request that).
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reviewed-by: NJean Pihet <j-pihet@ti.com>
      Acked-by: Nmark gross <markgross@thegnar.org>
      e39473d0
  2. 23 10月, 2012 3 次提交
    • R
      PM / QoS: Introduce PM QoS device flags support · ae0fb4b7
      Rafael J. Wysocki 提交于
      Modify the device PM QoS core code to support PM QoS flags requests.
      
      First, add a new field of type struct pm_qos_flags called "flags"
      to struct dev_pm_qos for representing the list of PM QoS flags
      requests for the given device.  Accordingly, add a new "type" field
      to struct dev_pm_qos_request (along with an enum for representing
      request types) and a new member called "flr" to its data union for
      representig flags requests.
      
      Second, modify dev_pm_qos_add_request(), dev_pm_qos_update_request(),
      the internal routine apply_constraint() used by them and their
      existing callers to cover flags requests as well as latency
      requests.  In particular, dev_pm_qos_add_request() gets a new
      argument called "type" for specifying the type of a request to be
      added.
      
      Finally, introduce two routines, __dev_pm_qos_flags() and
      dev_pm_qos_flags(), allowing their callers to check which PM QoS
      flags have been requested for the given device (the caller is
      supposed to pass the mask of flags to check as the routine's
      second argument and examine its return value for the result).
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reviewed-by: NJean Pihet <j-pihet@ti.com>
      Reviewed-by: Nmark gross <markgross@thegnar.org>
      ae0fb4b7
    • R
      PM / QoS: Prepare struct dev_pm_qos_request for more request types · 021c870b
      Rafael J. Wysocki 提交于
      The subsequent patches will use struct dev_pm_qos_request for
      representing both latency requests and flags requests.  To make that
      easier, put the node member of struct dev_pm_qos_request (under the
      name "pnode") into a union called "data" that will represent the
      request's  value and list node depending on its type.
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reviewed-by: NJean Pihet <j-pihet@ti.com>
      Reviewed-by: Nmark gross <markgross@thegnar.org>
      021c870b
    • R
      PM / QoS: Prepare device structure for adding more constraint types · 5f986c59
      Rafael J. Wysocki 提交于
      Currently struct dev_pm_info contains only one PM QoS constraints
      pointer reserved for latency requirements.  Since one more device
      constraints type (i.e. flags) will be necessary, introduce a new
      structure, struct dev_pm_qos, that eventually will contain all of
      the available device PM QoS constraints and replace the "constraints"
      pointer in struct dev_pm_info with a pointer to the new structure
      called "qos".
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      Reviewed-by: NJean Pihet <j-pihet@ti.com>
      5f986c59
  3. 20 10月, 2012 4 次提交
  4. 18 10月, 2012 29 次提交
  5. 17 10月, 2012 3 次提交