Kenji Kaneshige 07d92760d2 PCI ASPM: introduce capable flag
Introduce 'aspm_capable' field to maintain the capable ASPM setting of
the link. By the 'aspm_capable', we don't need to recheck latency
every time ASPM policy is changed.

Each bit in 'aspm_capable' is associated to ASPM state (L0S/L1). The
bit is set if the associated ASPM state is supported by the link and
it satisfies the latency requirement (i.e. exit latency < endpoint
acceptable latency). The 'aspm_capable' is updated when

  - an endpoint device is added (boot time or hot-plug time)
  - an endpoint device is removed (hot-unplug time)
  - PCI power state is changed.

Acked-by: Shaohua Li <shaohua.li@intel.com>
Signed-off-by: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
2009-09-09 13:29:47 -07:00
..
2009-07-12 12:22:34 -07:00
2009-08-15 12:58:45 +09:00
2009-07-12 12:22:34 -07:00
2009-08-14 13:09:32 -07:00
2009-08-04 20:31:32 +02:00
2009-09-03 14:59:16 +01:00
2009-09-06 01:41:24 -07:00
2009-09-09 13:29:47 -07:00
2009-09-09 13:29:19 -07:00
2009-08-26 20:06:52 -07:00
2009-08-18 16:31:13 -07:00
2009-07-12 12:22:34 -07:00
2009-07-30 16:03:45 +09:30
2009-07-01 11:19:47 +02:00