Skip to content

Commit 92a578b

Browse files
torvaldstorvalds
committed
Merge tag 'pm+acpi-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm
Pull ACPI and power management updates from Rafael Wysocki: "This time we have some more new material than we used to have during the last couple of development cycles. The most important part of it to me is the introduction of a unified interface for accessing device properties provided by platform firmware. It works with Device Trees and ACPI in a uniform way and drivers using it need not worry about where the properties come from as long as the platform firmware (either DT or ACPI) makes them available. It covers both devices and "bare" device node objects without struct device representation as that turns out to be necessary in some cases. This has been in the works for quite a few months (and development cycles) and has been approved by all of the relevant maintainers. On top of that, some drivers are switched over to the new interface (at25, leds-gpio, gpio_keys_polled) and some additional changes are made to the core GPIO subsystem to allow device drivers to manipulate GPIOs in the "canonical" way on platforms that provide GPIO information in their ACPI tables, but don't assign names to GPIO lines (in which case the driver needs to do that on the basis of what it knows about the device in question). That also has been approved by the GPIO core maintainers and the rfkill driver is now going to use it. Second is support for hardware P-states in the intel_pstate driver. It uses CPUID to detect whether or not the feature is supported by the processor in which case it will be enabled by default. However, it can be disabled entirely from the kernel command line if necessary. Next is support for a platform firmware interface based on ACPI operation regions used by the PMIC (Power Management Integrated Circuit) chips on the Intel Baytrail-T and Baytrail-T-CR platforms. That interface is used for manipulating power resources and for thermal management: sensor temperature reporting, trip point setting and so on. Also the ACPI core is now going to support the _DEP configuration information in a limited way. Basically, _DEP it supposed to reflect off-the-hierarchy dependencies between devices which may be very indirect, like when AML for one device accesses locations in an operation region handled by another device's driver (usually, the device depended on this way is a serial bus or GPIO controller). The support added this time is sufficient to make the ACPI battery driver work on Asus T100A, but it is general enough to be able to cover some other use cases in the future. Finally, we have a new cpufreq driver for the Loongson1B processor. In addition to the above, there are fixes and cleanups all over the place as usual and a traditional ACPICA update to a recent upstream release. As far as the fixes go, the ACPI LPSS (Low-power Subsystem) driver for Intel platforms should be able to handle power management of the DMA engine correctly, the cpufreq-dt driver should interact with the thermal subsystem in a better way and the ACPI backlight driver should handle some more corner cases, among other things. On top of the ACPICA update there are fixes for race conditions in the ACPICA's interrupt handling code which might lead to some random and strange looking failures on some systems. In the cleanups department the most visible part is the series of commits targeted at getting rid of the CONFIG_PM_RUNTIME configuration option. That was triggered by a discussion regarding the generic power domains code during which we realized that trying to support certain combinations of PM config options was painful and not really worth it, because nobody would use them in production anyway. For this reason, we decided to make CONFIG_PM_SLEEP select CONFIG_PM_RUNTIME and that lead to the conclusion that the latter became redundant and CONFIG_PM could be used instead of it. The material here makes that replacement in a major part of the tree, but there will be at least one more batch of that in the second part of the merge window. Specifics: - Support for retrieving device properties information from ACPI _DSD device configuration objects and a unified device properties interface for device drivers (and subsystems) on top of that. As stated above, this works with Device Trees and ACPI and allows device drivers to be written in a platform firmware (DT or ACPI) agnostic way. The at25, leds-gpio and gpio_keys_polled drivers are now going to use this new interface and the GPIO subsystem is additionally modified to allow device drivers to assign names to GPIO resources returned by ACPI _CRS objects (in case _DSD is not present or does not provide the expected data). The changes in this set are mostly from Mika Westerberg, Rafael J Wysocki, Aaron Lu, and Darren Hart with some fixes from others (Fabio Estevam, Geert Uytterhoeven). - Support for Hardware Managed Performance States (HWP) as described in Volume 3, section 14.4, of the Intel SDM in the intel_pstate driver. CPUID is used to detect whether or not the feature is supported by the processor. If supported, it will be enabled automatically unless the intel_pstate=no_hwp switch is present in the kernel command line. From Dirk Brandewie. - New Intel Broadwell-H ID for intel_pstate (Dirk Brandewie). - Support for firmware interface based on ACPI operation regions used by the PMIC chips on the Intel Baytrail-T and Baytrail-T-CR platforms for power resource control and thermal management (Aaron Lu). - Limited support for retrieving off-the-hierarchy dependencies between devices from ACPI _DEP device configuration objects and deferred probing support for the ACPI battery driver based on the _DEP information to make that driver work on Asus T100A (Lan Tianyu). - New cpufreq driver for the Loongson1B processor (Kelvin Cheung). - ACPICA update to upstream revision 20141107 which only affects tools (Bob Moore). - Fixes for race conditions in the ACPICA's interrupt handling code and in the ACPI code related to system suspend and resume (Lv Zheng and Rafael J Wysocki). - ACPI core fix for an RCU-related issue in the ioremap() regions management code that slowed down significantly after CPUs had been allowed to enter idle states even if they'd had RCU callbakcs queued and triggered some problems in certain proprietary graphics driver (and elsewhere). The fix replaces synchronize_rcu() in that code with synchronize_rcu_expedited() which makes the issue go away. From Konstantin Khlebnikov. - ACPI LPSS (Low-Power Subsystem) driver fix to handle power management of the DMA engine included into the LPSS correctly. The problem is that the DMA engine doesn't have ACPI PM support of its own and it simply is turned off when the last LPSS device having ACPI PM support goes into D3cold. To work around that, the PM domain used by the ACPI LPSS driver is redesigned so at least one device with ACPI PM support will be on as long as the DMA engine is in use. From Andy Shevchenko. - ACPI backlight driver fix to avoid using it on "Win8-compatible" systems where it doesn't work and where it was used by default by mistake (Aaron Lu). - Assorted minor ACPI core fixes and cleanups from Tomasz Nowicki, Sudeep Holla, Huang Rui, Hanjun Guo, Fabian Frederick, and Ashwin Chaugule (mostly related to the upcoming ARM64 support). - Intel RAPL (Running Average Power Limit) power capping driver fixes and improvements including new processor IDs (Jacob Pan). - Generic power domains modification to power up domains after attaching devices to them to meet the expectations of device drivers and bus types assuming devices to be accessible at probe time (Ulf Hansson). - Preliminary support for controlling device clocks from the generic power domains core code and modifications of the ARM/shmobile platform to use that feature (Ulf Hansson). - Assorted minor fixes and cleanups of the generic power domains core code (Ulf Hansson, Geert Uytterhoeven). - Assorted minor fixes and cleanups of the device clocks control code in the PM core (Geert Uytterhoeven, Grygorii Strashko). - Consolidation of device power management Kconfig options by making CONFIG_PM_SLEEP select CONFIG_PM_RUNTIME and removing the latter which is now redundant (Rafael J Wysocki and Kevin Hilman). That is the first batch of the changes needed for this purpose. - Core device runtime power management support code cleanup related to the execution of callbacks (Andrzej Hajda). - cpuidle ARM support improvements (Lorenzo Pieralisi). - cpuidle cleanup related to the CPUIDLE_FLAG_TIME_VALID flag and a new MAINTAINERS entry for ARM Exynos cpuidle (Daniel Lezcano and Bartlomiej Zolnierkiewicz). - New cpufreq driver callback (->ready) to be executed when the cpufreq core is ready to use a given policy object and cpufreq-dt driver modification to use that callback for cooling device registration (Viresh Kumar). - cpufreq core fixes and cleanups (Viresh Kumar, Vince Hsu, James Geboski, Tomeu Vizoso). - Assorted fixes and cleanups in the cpufreq-pcc, intel_pstate, cpufreq-dt, pxa2xx cpufreq drivers (Lenny Szubowicz, Ethan Zhao, Stefan Wahren, Petr Cvek). - OPP (Operating Performance Points) framework modification to allow OPPs to be removed too and update of a few cpufreq drivers (cpufreq-dt, exynos5440, imx6q, cpufreq) to remove OPPs (added during initialization) on driver removal (Viresh Kumar). - Hibernation core fixes and cleanups (Tina Ruchandani and Markus Elfring). - PM Kconfig fix related to CPU power management (Pankaj Dubey). - cpupower tool fix (Prarit Bhargava)" * tag 'pm+acpi-3.19-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm: (120 commits) i2c-omap / PM: Drop CONFIG_PM_RUNTIME from i2c-omap.c dmaengine / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM tools: cpupower: fix return checks for sysfs_get_idlestate_count() drivers: sh / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM e1000e / igb / PM: Eliminate CONFIG_PM_RUNTIME MMC / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM MFD / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM misc / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM media / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM input / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM leds: leds-gpio: Fix multiple instances registration without 'label' property iio / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM hsi / OMAP / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM i2c-hid / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM drm / exynos / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM gpio / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM hwrandom / exynos / PM: Use CONFIG_PM in #ifdef block / PM: Replace CONFIG_PM_RUNTIME with CONFIG_PM USB / PM: Drop CONFIG_PM_RUNTIME from the USB core PM: Merge the SET*_RUNTIME_PM_OPS() macros ...
2 parents c75059c + e3d857e commit 92a578b

File tree

220 files changed

+4877
-1526
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

220 files changed

+4877
-1526
lines changed

‎Documentation/ABI/stable/sysfs-bus-usb

Lines changed: 6 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -32,10 +32,9 @@ Date: January 2008
3232
KernelVersion: 2.6.25
3333
Contact: Sarah Sharp <sarah.a.sharp@intel.com>
3434
Description:
35-
If CONFIG_PM_RUNTIME is enabled then this file
36-
is present. When read, it returns the total time (in msec)
37-
that the USB device has been connected to the machine. This
38-
file is read-only.
35+
If CONFIG_PM is enabled, then this file is present. When read,
36+
it returns the total time (in msec) that the USB device has been
37+
connected to the machine. This file is read-only.
3938
Users:
4039
PowerTOP <powertop@lists.01.org>
4140
https://01.org/powertop/
@@ -45,10 +44,9 @@ Date: January 2008
4544
KernelVersion: 2.6.25
4645
Contact: Sarah Sharp <sarah.a.sharp@intel.com>
4746
Description:
48-
If CONFIG_PM_RUNTIME is enabled then this file
49-
is present. When read, it returns the total time (in msec)
50-
that the USB device has been active, i.e. not in a suspended
51-
state. This file is read-only.
47+
If CONFIG_PM is enabled, then this file is present. When read,
48+
it returns the total time (in msec) that the USB device has been
49+
active, i.e. not in a suspended state. This file is read-only.
5250

5351
Tools can use this file and the connected_duration file to
5452
compute the percentage of time that a device has been active.

‎Documentation/ABI/testing/sysfs-bus-usb

Lines changed: 9 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -104,16 +104,15 @@ What: /sys/bus/usb/devices/.../power/usb2_hardware_lpm
104104
Date: September 2011
105105
Contact: Andiry Xu <andiry.xu@amd.com>
106106
Description:
107-
If CONFIG_PM_RUNTIME is set and a USB 2.0 lpm-capable device
108-
is plugged in to a xHCI host which support link PM, it will
109-
perform a LPM test; if the test is passed and host supports
110-
USB2 hardware LPM (xHCI 1.0 feature), USB2 hardware LPM will
111-
be enabled for the device and the USB device directory will
112-
contain a file named power/usb2_hardware_lpm. The file holds
113-
a string value (enable or disable) indicating whether or not
114-
USB2 hardware LPM is enabled for the device. Developer can
115-
write y/Y/1 or n/N/0 to the file to enable/disable the
116-
feature.
107+
If CONFIG_PM is set and a USB 2.0 lpm-capable device is plugged
108+
in to a xHCI host which support link PM, it will perform a LPM
109+
test; if the test is passed and host supports USB2 hardware LPM
110+
(xHCI 1.0 feature), USB2 hardware LPM will be enabled for the
111+
device and the USB device directory will contain a file named
112+
power/usb2_hardware_lpm. The file holds a string value (enable
113+
or disable) indicating whether or not USB2 hardware LPM is
114+
enabled for the device. Developer can write y/Y/1 or n/N/0 to
115+
the file to enable/disable the feature.
117116

118117
What: /sys/bus/usb/devices/.../removable
119118
Date: February 2012

‎Documentation/acpi/gpio-properties.txt

Lines changed: 96 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,96 @@
1+
_DSD Device Properties Related to GPIO
2+
--------------------------------------
3+
4+
With the release of ACPI 5.1 and the _DSD configuration objecte names
5+
can finally be given to GPIOs (and other things as well) returned by
6+
_CRS. Previously, we were only able to use an integer index to find
7+
the corresponding GPIO, which is pretty error prone (it depends on
8+
the _CRS output ordering, for example).
9+
10+
With _DSD we can now query GPIOs using a name instead of an integer
11+
index, like the ASL example below shows:
12+
13+
// Bluetooth device with reset and shutdown GPIOs
14+
Device (BTH)
15+
{
16+
Name (_HID, ...)
17+
18+
Name (_CRS, ResourceTemplate ()
19+
{
20+
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
21+
"\\_SB.GPO0", 0, ResourceConsumer) {15}
22+
GpioIo (Exclusive, PullUp, 0, 0, IoRestrictionInputOnly,
23+
"\\_SB.GPO0", 0, ResourceConsumer) {27, 31}
24+
})
25+
26+
Name (_DSD, Package ()
27+
{
28+
ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
29+
Package ()
30+
{
31+
Package () {"reset-gpio", Package() {^BTH, 1, 1, 0 }},
32+
Package () {"shutdown-gpio", Package() {^BTH, 0, 0, 0 }},
33+
}
34+
})
35+
}
36+
37+
The format of the supported GPIO property is:
38+
39+
Package () { "name", Package () { ref, index, pin, active_low }}
40+
41+
ref - The device that has _CRS containing GpioIo()/GpioInt() resources,
42+
typically this is the device itself (BTH in our case).
43+
index - Index of the GpioIo()/GpioInt() resource in _CRS starting from zero.
44+
pin - Pin in the GpioIo()/GpioInt() resource. Typically this is zero.
45+
active_low - If 1 the GPIO is marked as active_low.
46+
47+
Since ACPI GpioIo() resource does not have a field saying whether it is
48+
active low or high, the "active_low" argument can be used here. Setting
49+
it to 1 marks the GPIO as active low.
50+
51+
In our Bluetooth example the "reset-gpio" refers to the second GpioIo()
52+
resource, second pin in that resource with the GPIO number of 31.
53+
54+
ACPI GPIO Mappings Provided by Drivers
55+
--------------------------------------
56+
57+
There are systems in which the ACPI tables do not contain _DSD but provide _CRS
58+
with GpioIo()/GpioInt() resources and device drivers still need to work with
59+
them.
60+
61+
In those cases ACPI device identification objects, _HID, _CID, _CLS, _SUB, _HRV,
62+
available to the driver can be used to identify the device and that is supposed
63+
to be sufficient to determine the meaning and purpose of all of the GPIO lines
64+
listed by the GpioIo()/GpioInt() resources returned by _CRS. In other words,
65+
the driver is supposed to know what to use the GpioIo()/GpioInt() resources for
66+
once it has identified the device. Having done that, it can simply assign names
67+
to the GPIO lines it is going to use and provide the GPIO subsystem with a
68+
mapping between those names and the ACPI GPIO resources corresponding to them.
69+
70+
To do that, the driver needs to define a mapping table as a NULL-terminated
71+
array of struct acpi_gpio_mapping objects that each contain a name, a pointer
72+
to an array of line data (struct acpi_gpio_params) objects and the size of that
73+
array. Each struct acpi_gpio_params object consists of three fields,
74+
crs_entry_index, line_index, active_low, representing the index of the target
75+
GpioIo()/GpioInt() resource in _CRS starting from zero, the index of the target
76+
line in that resource starting from zero, and the active-low flag for that line,
77+
respectively, in analogy with the _DSD GPIO property format specified above.
78+
79+
For the example Bluetooth device discussed previously the data structures in
80+
question would look like this:
81+
82+
static const struct acpi_gpio_params reset_gpio = { 1, 1, false };
83+
static const struct acpi_gpio_params shutdown_gpio = { 0, 0, false };
84+
85+
static const struct acpi_gpio_mapping bluetooth_acpi_gpios[] = {
86+
{ "reset-gpio", &reset_gpio, 1 },
87+
{ "shutdown-gpio", &shutdown_gpio, 1 },
88+
{ },
89+
};
90+
91+
Next, the mapping table needs to be passed as the second argument to
92+
acpi_dev_add_driver_gpios() that will register it with the ACPI device object
93+
pointed to by its first argument. That should be done in the driver's .probe()
94+
routine. On removal, the driver should unregister its GPIO mapping table by
95+
calling acpi_dev_remove_driver_gpios() on the ACPI device object where that
96+
table was previously registered.

‎Documentation/cpu-freq/intel-pstate.txt

Lines changed: 25 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,28 @@
11
Intel P-state driver
22
--------------------
33

4-
This driver implements a scaling driver with an internal governor for
5-
Intel Core processors. The driver follows the same model as the
6-
Transmeta scaling driver (longrun.c) and implements the setpolicy()
7-
instead of target(). Scaling drivers that implement setpolicy() are
8-
assumed to implement internal governors by the cpufreq core. All the
9-
logic for selecting the current P state is contained within the
10-
driver; no external governor is used by the cpufreq core.
11-
12-
Intel SandyBridge+ processors are supported.
13-
14-
New sysfs files for controlling P state selection have been added to
4+
This driver provides an interface to control the P state selection for
5+
SandyBridge+ Intel processors. The driver can operate two different
6+
modes based on the processor model legacy and Hardware P state (HWP)
7+
mode.
8+
9+
In legacy mode the driver implements a scaling driver with an internal
10+
governor for Intel Core processors. The driver follows the same model
11+
as the Transmeta scaling driver (longrun.c) and implements the
12+
setpolicy() instead of target(). Scaling drivers that implement
13+
setpolicy() are assumed to implement internal governors by the cpufreq
14+
core. All the logic for selecting the current P state is contained
15+
within the driver; no external governor is used by the cpufreq core.
16+
17+
In HWP mode P state selection is implemented in the processor
18+
itself. The driver provides the interfaces between the cpufreq core and
19+
the processor to control P state selection based on user preferences
20+
and reporting frequency to the cpufreq core. In this mode the
21+
internal governor code is disabled.
22+
23+
In addtion to the interfaces provided by the cpufreq core for
24+
controlling frequency the driver provides sysfs files for
25+
controlling P state selection. These files have been added to
1526
/sys/devices/system/cpu/intel_pstate/
1627

1728
max_perf_pct: limits the maximum P state that will be requested by
@@ -33,7 +44,9 @@ frequency is fiction for Intel Core processors. Even if the scaling
3344
driver selects a single P state the actual frequency the processor
3445
will run at is selected by the processor itself.
3546

36-
New debugfs files have also been added to /sys/kernel/debug/pstate_snb/
47+
For legacy mode debugfs files have also been added to allow tuning of
48+
the internal governor algorythm. These files are located at
49+
/sys/kernel/debug/pstate_snb/ These files are NOT present in HWP mode.
3750

3851
deadband
3952
d_gain_pct

‎Documentation/devicetree/bindings/arm/idle-states.txt

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -317,6 +317,26 @@ follows:
317317
In such systems entry-latency-us + exit-latency-us
318318
will exceed wakeup-latency-us by this duration.
319319

320+
- status:
321+
Usage: Optional
322+
Value type: <string>
323+
Definition: A standard device tree property [5] that indicates
324+
the operational status of an idle-state.
325+
If present, it shall be:
326+
"okay": to indicate that the idle state is
327+
operational.
328+
"disabled": to indicate that the idle state has
329+
been disabled in firmware so it is not
330+
operational.
331+
If the property is not present the idle-state must
332+
be considered operational.
333+
334+
- idle-state-name:
335+
Usage: Optional
336+
Value type: <string>
337+
Definition: A string used as a descriptive name for the idle
338+
state.
339+
320340
In addition to the properties listed above, a state node may require
321341
additional properties specifics to the entry-method defined in the
322342
idle-states node, please refer to the entry-method bindings

‎Documentation/gpio/consumer.txt

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -219,6 +219,24 @@ part of the IRQ interface, e.g. IRQF_TRIGGER_FALLING, as are system wakeup
219219
capabilities.
220220

221221

222+
GPIOs and ACPI
223+
==============
224+
225+
On ACPI systems, GPIOs are described by GpioIo()/GpioInt() resources listed by
226+
the _CRS configuration objects of devices. Those resources do not provide
227+
connection IDs (names) for GPIOs, so it is necessary to use an additional
228+
mechanism for this purpose.
229+
230+
Systems compliant with ACPI 5.1 or newer may provide a _DSD configuration object
231+
which, among other things, may be used to provide connection IDs for specific
232+
GPIOs described by the GpioIo()/GpioInt() resources in _CRS. If that is the
233+
case, it will be handled by the GPIO subsystem automatically. However, if the
234+
_DSD is not present, the mappings between GpioIo()/GpioInt() resources and GPIO
235+
connection IDs need to be provided by device drivers.
236+
237+
For details refer to Documentation/acpi/gpio-properties.txt
238+
239+
222240
Interacting With the Legacy GPIO Subsystem
223241
==========================================
224242
Many kernel subsystems still handle GPIOs using the legacy integer-based

‎Documentation/kernel-parameters.txt

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1446,6 +1446,9 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
14461446
disable
14471447
Do not enable intel_pstate as the default
14481448
scaling driver for the supported processors
1449+
no_hwp
1450+
Do not enable hardware P state control (HWP)
1451+
if available.
14491452

14501453
intremap= [X86-64, Intel-IOMMU]
14511454
on enable Interrupt Remapping (default)

‎Documentation/usb/power-management.txt

Lines changed: 9 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -47,14 +47,15 @@ dynamic PM is implemented in the USB subsystem, although system PM is
4747
covered to some extent (see Documentation/power/*.txt for more
4848
information about system PM).
4949

50-
Note: Dynamic PM support for USB is present only if the kernel was
51-
built with CONFIG_USB_SUSPEND enabled (which depends on
52-
CONFIG_PM_RUNTIME). System PM support is present only if the kernel
53-
was built with CONFIG_SUSPEND or CONFIG_HIBERNATION enabled.
54-
55-
(Starting with the 3.10 kernel release, dynamic PM support for USB is
56-
present whenever the kernel was built with CONFIG_PM_RUNTIME enabled.
57-
The CONFIG_USB_SUSPEND option has been eliminated.)
50+
System PM support is present only if the kernel was built with CONFIG_SUSPEND
51+
or CONFIG_HIBERNATION enabled. Dynamic PM support for USB is present whenever
52+
the kernel was built with CONFIG_PM enabled.
53+
54+
[Historically, dynamic PM support for USB was present only if the
55+
kernel had been built with CONFIG_USB_SUSPEND enabled (which depended on
56+
CONFIG_PM_RUNTIME). Starting with the 3.10 kernel release, dynamic PM support
57+
for USB was present whenever the kernel was built with CONFIG_PM_RUNTIME
58+
enabled. The CONFIG_USB_SUSPEND option had been eliminated.]
5859

5960

6061
What is Remote Wakeup?

‎MAINTAINERS

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2655,6 +2655,16 @@ T: git git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
26552655
S: Maintained
26562656
F: drivers/cpuidle/cpuidle-big_little.c
26572657

2658+
CPUIDLE DRIVER - ARM EXYNOS
2659+
M: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
2660+
M: Daniel Lezcano <daniel.lezcano@linaro.org>
2661+
M: Kukjin Kim <kgene@kernel.org>
2662+
L: linux-pm@vger.kernel.org
2663+
L: linux-samsung-soc@vger.kernel.org
2664+
S: Supported
2665+
F: drivers/cpuidle/cpuidle-exynos.c
2666+
F: arch/arm/mach-exynos/pm.c
2667+
26582668
CPUIDLE DRIVERS
26592669
M: Rafael J. Wysocki <rjw@rjwysocki.net>
26602670
M: Daniel Lezcano <daniel.lezcano@linaro.org>

‎arch/arm/include/asm/cpuidle.h

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,6 @@ static inline int arm_cpuidle_simple_enter(struct cpuidle_device *dev,
1515
.exit_latency = 1,\
1616
.target_residency = 1,\
1717
.power_usage = p,\
18-
.flags = CPUIDLE_FLAG_TIME_VALID,\
1918
.name = "WFI",\
2019
.desc = "ARM WFI",\
2120
}

‎arch/arm/mach-davinci/cpuidle.c

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,6 @@ static struct cpuidle_driver davinci_idle_driver = {
6666
.enter = davinci_enter_idle,
6767
.exit_latency = 10,
6868
.target_residency = 10000,
69-
.flags = CPUIDLE_FLAG_TIME_VALID,
7069
.name = "DDR SR",
7170
.desc = "WFI and DDR Self Refresh",
7271
},

‎arch/arm/mach-imx/cpuidle-imx5.c

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,6 @@ static struct cpuidle_driver imx5_cpuidle_driver = {
2424
.enter = imx5_cpuidle_enter,
2525
.exit_latency = 2,
2626
.target_residency = 1,
27-
.flags = CPUIDLE_FLAG_TIME_VALID,
2827
.name = "IMX5 SRPG",
2928
.desc = "CPU state retained,powered off",
3029
},

‎arch/arm/mach-imx/cpuidle-imx6q.c

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -53,8 +53,7 @@ static struct cpuidle_driver imx6q_cpuidle_driver = {
5353
{
5454
.exit_latency = 50,
5555
.target_residency = 75,
56-
.flags = CPUIDLE_FLAG_TIME_VALID |
57-
CPUIDLE_FLAG_TIMER_STOP,
56+
.flags = CPUIDLE_FLAG_TIMER_STOP,
5857
.enter = imx6q_enter_wait,
5958
.name = "WAIT",
6059
.desc = "Clock off",

‎arch/arm/mach-imx/cpuidle-imx6sl.c

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,8 +40,7 @@ static struct cpuidle_driver imx6sl_cpuidle_driver = {
4040
{
4141
.exit_latency = 50,
4242
.target_residency = 75,
43-
.flags = CPUIDLE_FLAG_TIME_VALID |
44-
CPUIDLE_FLAG_TIMER_STOP,
43+
.flags = CPUIDLE_FLAG_TIMER_STOP,
4544
.enter = imx6sl_enter_wait,
4645
.name = "WAIT",
4746
.desc = "Clock off",

0 commit comments

Comments
 (0)