2019-05-19 12:07:45 +00:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2007-07-29 21:27:18 +00:00
|
|
|
config SUSPEND
|
|
|
|
|
bool "Suspend to RAM and standby"
|
PM: Make CONFIG_PM depend on (CONFIG_PM_SLEEP || CONFIG_PM_RUNTIME)
From the users' point of view CONFIG_PM is really only used for
making it possible to set CONFIG_SUSPEND, CONFIG_HIBERNATION,
CONFIG_PM_RUNTIME and (surprisingly enough) CONFIG_XEN_SAVE_RESTORE
(CONFIG_PM_OPP also depends on CONFIG_PM, but quite artificially).
However, both CONFIG_SUSPEND and CONFIG_HIBERNATION require platform
support (independent of CONFIG_PM) and it is not quite obvious that
CONFIG_PM has to be set for CONFIG_XEN_SAVE_RESTORE to be available.
Thus, from the users' point of view, it would be more logical to
automatically select CONFIG_PM if any of the above options depending
on it are set.
Make CONFIG_PM depend on (CONFIG_PM_SLEEP || CONFIG_PM_RUNTIME),
which will cause it to be selected when any of CONFIG_SUSPEND,
CONFIG_HIBERNATION, CONFIG_PM_RUNTIME, CONFIG_XEN_SAVE_RESTORE is
set and will clarify its meaning.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-02-10 23:06:30 +00:00
|
|
|
depends on ARCH_SUSPEND_POSSIBLE
|
2007-07-29 21:27:18 +00:00
|
|
|
default y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-07-29 21:27:18 +00:00
|
|
|
Allow the system to enter sleep states in which main memory is
|
|
|
|
|
powered and thus its contents are preserved, such as the
|
2007-12-08 01:14:00 +00:00
|
|
|
suspend-to-RAM state (e.g. the ACPI S3 state).
|
2007-07-29 21:27:18 +00:00
|
|
|
|
2008-01-16 04:17:00 +00:00
|
|
|
config SUSPEND_FREEZER
|
|
|
|
|
bool "Enable freezer for suspend to RAM/standby" \
|
|
|
|
|
if ARCH_WANTS_FREEZER_CONTROL || BROKEN
|
|
|
|
|
depends on SUSPEND
|
|
|
|
|
default y
|
|
|
|
|
help
|
|
|
|
|
This allows you to turn off the freezer for suspend. If this is
|
|
|
|
|
done, no tasks are frozen for suspend to RAM/standby.
|
|
|
|
|
|
|
|
|
|
Turning OFF this setting is NOT recommended! If in doubt, say Y.
|
|
|
|
|
|
2015-07-31 16:46:17 +00:00
|
|
|
config SUSPEND_SKIP_SYNC
|
|
|
|
|
bool "Skip kernel's sys_sync() on suspend to RAM/standby"
|
|
|
|
|
depends on SUSPEND
|
|
|
|
|
depends on EXPERT
|
|
|
|
|
help
|
|
|
|
|
Skip the kernel sys_sync() before freezing user processes.
|
|
|
|
|
Some systems prefer not to pay this cost on every invocation
|
|
|
|
|
of suspend, or they are content with invoking sync() from
|
2020-01-16 11:53:54 +00:00
|
|
|
user-space before invoking suspend. There's a run-time switch
|
|
|
|
|
at '/sys/power/sync_on_suspend' to configure this behaviour.
|
|
|
|
|
This setting changes the default for the run-tim switch. Say Y
|
|
|
|
|
to change the default to disable the kernel sys_sync().
|
2015-07-31 16:46:17 +00:00
|
|
|
|
2011-04-11 20:54:42 +00:00
|
|
|
config HIBERNATE_CALLBACKS
|
|
|
|
|
bool
|
|
|
|
|
|
2007-07-29 21:24:36 +00:00
|
|
|
config HIBERNATION
|
2007-07-29 21:27:18 +00:00
|
|
|
bool "Hibernation (aka 'suspend to disk')"
|
PM: Make CONFIG_PM depend on (CONFIG_PM_SLEEP || CONFIG_PM_RUNTIME)
From the users' point of view CONFIG_PM is really only used for
making it possible to set CONFIG_SUSPEND, CONFIG_HIBERNATION,
CONFIG_PM_RUNTIME and (surprisingly enough) CONFIG_XEN_SAVE_RESTORE
(CONFIG_PM_OPP also depends on CONFIG_PM, but quite artificially).
However, both CONFIG_SUSPEND and CONFIG_HIBERNATION require platform
support (independent of CONFIG_PM) and it is not quite obvious that
CONFIG_PM has to be set for CONFIG_XEN_SAVE_RESTORE to be available.
Thus, from the users' point of view, it would be more logical to
automatically select CONFIG_PM if any of the above options depending
on it are set.
Make CONFIG_PM depend on (CONFIG_PM_SLEEP || CONFIG_PM_RUNTIME),
which will cause it to be selected when any of CONFIG_SUSPEND,
CONFIG_HIBERNATION, CONFIG_PM_RUNTIME, CONFIG_XEN_SAVE_RESTORE is
set and will clarify its meaning.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
2011-02-10 23:06:30 +00:00
|
|
|
depends on SWAP && ARCH_HIBERNATION_POSSIBLE
|
2011-04-11 20:54:42 +00:00
|
|
|
select HIBERNATE_CALLBACKS
|
2010-09-09 21:06:23 +00:00
|
|
|
select LZO_COMPRESS
|
|
|
|
|
select LZO_DECOMPRESS
|
2011-10-13 21:58:07 +00:00
|
|
|
select CRC32
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2007-05-06 21:50:50 +00:00
|
|
|
Enable the suspend to disk (STD) functionality, which is usually
|
|
|
|
|
called "hibernation" in user interfaces. STD checkpoints the
|
|
|
|
|
system and powers it off; and restores that checkpoint on reboot.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2008-02-05 18:27:12 +00:00
|
|
|
You can suspend your machine with 'echo disk > /sys/power/state'
|
|
|
|
|
after placing resume=/dev/swappartition on the kernel command line
|
|
|
|
|
in your bootloader's configuration file.
|
|
|
|
|
|
2007-03-06 09:42:24 +00:00
|
|
|
Alternatively, you can use the additional userland tools available
|
|
|
|
|
from <http://suspend.sf.net>.
|
|
|
|
|
|
|
|
|
|
In principle it does not require ACPI or APM, although for example
|
2007-05-06 21:50:50 +00:00
|
|
|
ACPI will be used for the final steps when it is available. One
|
|
|
|
|
of the reasons to use software suspend is that the firmware hooks
|
|
|
|
|
for suspend states like suspend-to-RAM (STR) often don't work very
|
|
|
|
|
well with Linux.
|
2007-03-06 09:42:24 +00:00
|
|
|
|
|
|
|
|
It creates an image which is saved in your active swap. Upon the next
|
2005-04-16 22:20:36 +00:00
|
|
|
boot, pass the 'resume=/dev/swappartition' argument to the kernel to
|
|
|
|
|
have it detect the saved image, restore memory state from it, and
|
|
|
|
|
continue to run as before. If you do not want the previous state to
|
2007-03-06 09:42:24 +00:00
|
|
|
be reloaded, then use the 'noresume' kernel command line argument.
|
|
|
|
|
Note, however, that fsck will be run on your filesystems and you will
|
|
|
|
|
need to run mkswap against the swap partition used for the suspend.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-03-06 09:42:24 +00:00
|
|
|
It also works with swap files to a limited extent (for details see
|
2019-06-13 10:10:36 +00:00
|
|
|
<file:Documentation/power/swsusp-and-swap-files.rst>).
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2007-03-06 09:42:24 +00:00
|
|
|
Right now you may boot without resuming and resume later but in the
|
|
|
|
|
meantime you cannot use the swap partition(s)/file(s) involved in
|
|
|
|
|
suspending. Also in this case you must not use the filesystems
|
|
|
|
|
that were mounted before the suspend. In particular, you MUST NOT
|
|
|
|
|
MOUNT any journaled filesystems mounted before the suspend or they
|
|
|
|
|
will get corrupted in a nasty way.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2019-06-13 10:10:36 +00:00
|
|
|
For more information take a look at <file:Documentation/power/swsusp.rst>.
|
2006-09-06 07:03:43 +00:00
|
|
|
|
2020-05-07 07:19:53 +00:00
|
|
|
config HIBERNATION_SNAPSHOT_DEV
|
|
|
|
|
bool "Userspace snapshot device"
|
|
|
|
|
depends on HIBERNATION
|
|
|
|
|
default y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2020-05-07 07:19:53 +00:00
|
|
|
Device used by the uswsusp tools.
|
|
|
|
|
|
|
|
|
|
Say N if no snapshotting from userspace is needed, this also
|
|
|
|
|
reduces the attack surface of the kernel.
|
|
|
|
|
|
|
|
|
|
If in doubt, say Y.
|
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
config PM_STD_PARTITION
|
|
|
|
|
string "Default resume partition"
|
2007-07-29 21:24:36 +00:00
|
|
|
depends on HIBERNATION
|
2005-04-16 22:20:36 +00:00
|
|
|
default ""
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2005-04-16 22:20:36 +00:00
|
|
|
The default resume partition is the partition that the suspend-
|
2021-06-08 07:44:37 +00:00
|
|
|
to-disk implementation will look for a suspended disk image.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2021-06-08 07:44:37 +00:00
|
|
|
The partition specified here will be different for almost every user.
|
2005-04-16 22:20:36 +00:00
|
|
|
It should be a valid swap partition (at least for now) that is turned
|
2021-06-08 07:44:37 +00:00
|
|
|
on before suspending.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
The partition specified can be overridden by specifying:
|
|
|
|
|
|
2021-06-08 07:44:37 +00:00
|
|
|
resume=/dev/<other device>
|
2005-04-16 22:20:36 +00:00
|
|
|
|
2021-06-08 07:44:37 +00:00
|
|
|
which will set the resume partition to the device specified.
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
|
Note there is currently not a way to specify which device to save the
|
2021-06-08 07:44:37 +00:00
|
|
|
suspended image to. It will simply pick the first available swap
|
2005-04-16 22:20:36 +00:00
|
|
|
device.
|
|
|
|
|
|
2011-02-10 23:06:42 +00:00
|
|
|
config PM_SLEEP
|
2011-02-18 00:05:36 +00:00
|
|
|
def_bool y
|
2011-04-11 20:54:48 +00:00
|
|
|
depends on SUSPEND || HIBERNATE_CALLBACKS
|
2014-12-19 14:37:54 +00:00
|
|
|
select PM
|
2018-08-14 02:34:42 +00:00
|
|
|
select SRCU
|
2011-02-10 23:06:42 +00:00
|
|
|
|
|
|
|
|
config PM_SLEEP_SMP
|
2011-02-18 00:05:36 +00:00
|
|
|
def_bool y
|
2011-02-10 23:06:42 +00:00
|
|
|
depends on SMP
|
|
|
|
|
depends on ARCH_SUSPEND_POSSIBLE || ARCH_HIBERNATION_POSSIBLE
|
|
|
|
|
depends on PM_SLEEP
|
|
|
|
|
select HOTPLUG_CPU
|
|
|
|
|
|
2019-04-11 03:34:46 +00:00
|
|
|
config PM_SLEEP_SMP_NONZERO_CPU
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PM_SLEEP_SMP
|
|
|
|
|
depends on ARCH_SUSPEND_NONZERO_CPU
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2019-04-11 03:34:46 +00:00
|
|
|
If an arch can suspend (for suspend, hibernate, kexec, etc) on a
|
|
|
|
|
non-zero numbered CPU, it may define ARCH_SUSPEND_NONZERO_CPU. This
|
|
|
|
|
will allow nohz_full mask to include CPU0.
|
|
|
|
|
|
2012-04-29 20:53:22 +00:00
|
|
|
config PM_AUTOSLEEP
|
|
|
|
|
bool "Opportunistic sleep"
|
|
|
|
|
depends on PM_SLEEP
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2012-04-29 20:53:22 +00:00
|
|
|
Allow the kernel to trigger a system transition into a global sleep
|
|
|
|
|
state automatically whenever there are no active wakeup sources.
|
|
|
|
|
|
2022-06-30 19:12:29 +00:00
|
|
|
config PM_USERSPACE_AUTOSLEEP
|
|
|
|
|
bool "Userspace opportunistic sleep"
|
|
|
|
|
depends on PM_SLEEP
|
|
|
|
|
help
|
|
|
|
|
Notify kernel of aggressive userspace autosleep power management policy.
|
|
|
|
|
|
|
|
|
|
This option changes the behavior of various sleep-sensitive code to deal
|
|
|
|
|
with frequent userspace-initiated transitions into a global sleep state.
|
|
|
|
|
|
|
|
|
|
Saying Y here, disables code paths that most users really should keep
|
|
|
|
|
enabled. In particular, only enable this if it is very common to be
|
|
|
|
|
asleep/awake for very short periods of time (<= 2 seconds).
|
|
|
|
|
|
|
|
|
|
Only platforms, such as Android, that implement opportunistic sleep from
|
|
|
|
|
a userspace power manager service should enable this option; and not
|
|
|
|
|
other machines. Therefore, you should say N here, unless you are
|
|
|
|
|
extremely certain that this is what you want. The option otherwise has
|
|
|
|
|
bad, undesirable effects, and should not be enabled just for fun.
|
|
|
|
|
|
|
|
|
|
|
PM / Sleep: Add user space interface for manipulating wakeup sources, v3
Android allows user space to manipulate wakelocks using two
sysfs file located in /sys/power/, wake_lock and wake_unlock.
Writing a wakelock name and optionally a timeout to the wake_lock
file causes the wakelock whose name was written to be acquired (it
is created before is necessary), optionally with the given timeout.
Writing the name of a wakelock to wake_unlock causes that wakelock
to be released.
Implement an analogous interface for user space using wakeup sources.
Add the /sys/power/wake_lock and /sys/power/wake_unlock files
allowing user space to create, activate and deactivate wakeup
sources, such that writing a name and optionally a timeout to
wake_lock causes the wakeup source of that name to be activated,
optionally with the given timeout. If that wakeup source doesn't
exist, it will be created and then activated. Writing a name to
wake_unlock causes the wakeup source of that name, if there is one,
to be deactivated. Wakeup sources created with the help of
wake_lock that haven't been used for more than 5 minutes are garbage
collected and destroyed. Moreover, there can be only WL_NUMBER_LIMIT
wakeup sources created with the help of wake_lock present at a time.
The data type used to track wakeup sources created by user space is
called "struct wakelock" to indicate the origins of this feature.
This version of the patch includes an rbtree manipulation fix from John Stultz.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: NeilBrown <neilb@suse.de>
2012-04-29 20:53:42 +00:00
|
|
|
config PM_WAKELOCKS
|
|
|
|
|
bool "User space wakeup sources interface"
|
|
|
|
|
depends on PM_SLEEP
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
PM / Sleep: Add user space interface for manipulating wakeup sources, v3
Android allows user space to manipulate wakelocks using two
sysfs file located in /sys/power/, wake_lock and wake_unlock.
Writing a wakelock name and optionally a timeout to the wake_lock
file causes the wakelock whose name was written to be acquired (it
is created before is necessary), optionally with the given timeout.
Writing the name of a wakelock to wake_unlock causes that wakelock
to be released.
Implement an analogous interface for user space using wakeup sources.
Add the /sys/power/wake_lock and /sys/power/wake_unlock files
allowing user space to create, activate and deactivate wakeup
sources, such that writing a name and optionally a timeout to
wake_lock causes the wakeup source of that name to be activated,
optionally with the given timeout. If that wakeup source doesn't
exist, it will be created and then activated. Writing a name to
wake_unlock causes the wakeup source of that name, if there is one,
to be deactivated. Wakeup sources created with the help of
wake_lock that haven't been used for more than 5 minutes are garbage
collected and destroyed. Moreover, there can be only WL_NUMBER_LIMIT
wakeup sources created with the help of wake_lock present at a time.
The data type used to track wakeup sources created by user space is
called "struct wakelock" to indicate the origins of this feature.
This version of the patch includes an rbtree manipulation fix from John Stultz.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Reviewed-by: NeilBrown <neilb@suse.de>
2012-04-29 20:53:42 +00:00
|
|
|
Allow user space to create, activate and deactivate wakeup source
|
|
|
|
|
objects with the help of a sysfs-based interface.
|
|
|
|
|
|
2012-05-05 19:57:20 +00:00
|
|
|
config PM_WAKELOCKS_LIMIT
|
|
|
|
|
int "Maximum number of user space wakeup sources (0 = no limit)"
|
|
|
|
|
range 0 100000
|
|
|
|
|
default 100
|
|
|
|
|
depends on PM_WAKELOCKS
|
|
|
|
|
|
2012-05-05 19:57:28 +00:00
|
|
|
config PM_WAKELOCKS_GC
|
|
|
|
|
bool "Garbage collector for user space wakeup sources"
|
|
|
|
|
depends on PM_WAKELOCKS
|
|
|
|
|
default y
|
|
|
|
|
|
2014-12-19 14:37:54 +00:00
|
|
|
config PM
|
|
|
|
|
bool "Device power management core functionality"
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-02-10 23:06:42 +00:00
|
|
|
Enable functionality allowing I/O devices to be put into energy-saving
|
2014-12-19 14:37:54 +00:00
|
|
|
(low power) states, for example after a specified period of inactivity
|
|
|
|
|
(autosuspended), and woken up in response to a hardware-generated
|
2011-02-10 23:06:42 +00:00
|
|
|
wake-up event or a driver's request.
|
|
|
|
|
|
|
|
|
|
Hardware support is generally required for this functionality to work
|
|
|
|
|
and the bus type drivers of the buses the devices are on are
|
2014-12-19 14:37:54 +00:00
|
|
|
responsible for the actual handling of device suspend requests and
|
2011-02-10 23:06:42 +00:00
|
|
|
wake-up events.
|
|
|
|
|
|
|
|
|
|
config PM_DEBUG
|
|
|
|
|
bool "Power Management Debug Support"
|
|
|
|
|
depends on PM
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-02-10 23:06:42 +00:00
|
|
|
This option enables various debugging support in the Power Management
|
|
|
|
|
code. This is helpful when debugging and reporting PM bugs, like
|
|
|
|
|
suspend support.
|
|
|
|
|
|
|
|
|
|
config PM_ADVANCED_DEBUG
|
|
|
|
|
bool "Extra PM attributes in sysfs for low-level debugging/testing"
|
|
|
|
|
depends on PM_DEBUG
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-02-10 23:06:42 +00:00
|
|
|
Add extra sysfs attributes allowing one to access some Power Management
|
|
|
|
|
fields of device objects from user space. If you are not a kernel
|
|
|
|
|
developer interested in debugging/testing Power Management, say "no".
|
|
|
|
|
|
|
|
|
|
config PM_TEST_SUSPEND
|
|
|
|
|
bool "Test suspend/resume and wakealarm during bootup"
|
|
|
|
|
depends on SUSPEND && PM_DEBUG && RTC_CLASS=y
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-02-10 23:06:42 +00:00
|
|
|
This option will let you suspend your machine during bootup, and
|
|
|
|
|
make it wake up a few seconds later using an RTC wakeup alarm.
|
|
|
|
|
Enable this with a kernel parameter like "test_suspend=mem".
|
|
|
|
|
|
|
|
|
|
You probably want to have your system's RTC driver statically
|
|
|
|
|
linked, ensuring that it's available when this test runs.
|
|
|
|
|
|
2012-06-20 22:19:33 +00:00
|
|
|
config PM_SLEEP_DEBUG
|
2011-02-10 23:06:42 +00:00
|
|
|
def_bool y
|
2011-02-11 19:31:11 +00:00
|
|
|
depends on PM_DEBUG && PM_SLEEP
|
2011-02-10 23:06:42 +00:00
|
|
|
|
2013-10-17 17:48:46 +00:00
|
|
|
config DPM_WATCHDOG
|
|
|
|
|
bool "Device suspend/resume watchdog"
|
2016-08-19 04:37:23 +00:00
|
|
|
depends on PM_DEBUG && PSTORE && EXPERT
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2013-10-17 17:48:46 +00:00
|
|
|
Sets up a watchdog timer to capture drivers that are
|
|
|
|
|
locked up attempting to suspend/resume a device.
|
|
|
|
|
A detected lockup causes system panic with message
|
|
|
|
|
captured in pstore device for inspection in subsequent
|
|
|
|
|
boot session.
|
|
|
|
|
|
|
|
|
|
config DPM_WATCHDOG_TIMEOUT
|
|
|
|
|
int "Watchdog timeout in seconds"
|
|
|
|
|
range 1 120
|
2016-08-19 04:37:23 +00:00
|
|
|
default 120
|
2013-10-17 17:48:46 +00:00
|
|
|
depends on DPM_WATCHDOG
|
|
|
|
|
|
2011-02-10 23:06:42 +00:00
|
|
|
config PM_TRACE
|
|
|
|
|
bool
|
|
|
|
|
help
|
|
|
|
|
This enables code to save the last PM event point across
|
|
|
|
|
reboot. The architecture needs to support this, x86 for
|
|
|
|
|
example does by saving things in the RTC, see below.
|
|
|
|
|
|
|
|
|
|
The architecture specific code must provide the extern
|
|
|
|
|
functions from <linux/resume-trace.h> as well as the
|
|
|
|
|
<asm/resume-trace.h> header with a TRACE_RESUME() macro.
|
|
|
|
|
|
|
|
|
|
The way the information is presented is architecture-
|
|
|
|
|
dependent, x86 will print the information during a
|
|
|
|
|
late_initcall.
|
|
|
|
|
|
|
|
|
|
config PM_TRACE_RTC
|
|
|
|
|
bool "Suspend/resume event tracing"
|
2012-06-20 22:19:33 +00:00
|
|
|
depends on PM_SLEEP_DEBUG
|
2011-02-10 23:06:42 +00:00
|
|
|
depends on X86
|
|
|
|
|
select PM_TRACE
|
2020-06-13 16:50:22 +00:00
|
|
|
help
|
2011-02-10 23:06:42 +00:00
|
|
|
This enables some cheesy code to save the last PM event point in the
|
|
|
|
|
RTC across reboots, so that you can debug a machine that just hangs
|
|
|
|
|
during suspend (or more commonly, during resume).
|
|
|
|
|
|
|
|
|
|
To use this debugging feature you should attempt to suspend the
|
|
|
|
|
machine, reboot it and then run
|
|
|
|
|
|
|
|
|
|
dmesg -s 1000000 | grep 'hash matches'
|
|
|
|
|
|
|
|
|
|
CAUTION: this option will cause your machine's real-time clock to be
|
|
|
|
|
set to an invalid time after a resume.
|
|
|
|
|
|
2007-02-09 17:08:57 +00:00
|
|
|
config APM_EMULATION
|
|
|
|
|
tristate "Advanced Power Management Emulation"
|
2016-01-25 15:48:28 +00:00
|
|
|
depends on SYS_SUPPORTS_APM_EMULATION
|
2007-02-09 17:08:57 +00:00
|
|
|
help
|
|
|
|
|
APM is a BIOS specification for saving power using several different
|
|
|
|
|
techniques. This is mostly useful for battery powered laptops with
|
|
|
|
|
APM compliant BIOSes. If you say Y here, the system time will be
|
|
|
|
|
reset after a RESUME operation, the /proc/apm device will provide
|
|
|
|
|
battery status information, and user-space programs will receive
|
|
|
|
|
notification of APM "events" (e.g. battery status change).
|
|
|
|
|
|
|
|
|
|
In order to use APM, you will need supporting software. For location
|
2019-06-13 10:10:36 +00:00
|
|
|
and more information, read <file:Documentation/power/apm-acpi.rst>
|
2011-07-08 21:11:16 +00:00
|
|
|
and the Battery Powered Linux mini-HOWTO, available from
|
2007-02-09 17:08:57 +00:00
|
|
|
<http://www.tldp.org/docs.html#howto>.
|
|
|
|
|
|
|
|
|
|
This driver does not spin down disk drives (see the hdparm(8)
|
|
|
|
|
manpage ("man 8 hdparm") for that), and it doesn't turn off
|
|
|
|
|
VESA-compliant "green" monitors.
|
|
|
|
|
|
|
|
|
|
Generally, if you don't have a battery in your machine, there isn't
|
|
|
|
|
much point in using this driver and you should say N. If you get
|
|
|
|
|
random kernel OOPSes or reboots that don't seem to be related to
|
|
|
|
|
anything, try disabling/enabling this option (or disabling/enabling
|
|
|
|
|
APM in your BIOS).
|
2009-08-18 21:38:32 +00:00
|
|
|
|
2011-07-01 20:13:37 +00:00
|
|
|
config PM_CLK
|
2011-04-29 22:25:44 +00:00
|
|
|
def_bool y
|
2011-07-01 20:13:37 +00:00
|
|
|
depends on PM && HAVE_CLK
|
2011-07-01 20:12:45 +00:00
|
|
|
|
|
|
|
|
config PM_GENERIC_DOMAINS
|
|
|
|
|
bool
|
|
|
|
|
depends on PM
|
2011-08-14 11:34:31 +00:00
|
|
|
|
2013-04-08 11:15:40 +00:00
|
|
|
config WQ_POWER_EFFICIENT_DEFAULT
|
|
|
|
|
bool "Enable workqueue power-efficient mode by default"
|
|
|
|
|
depends on PM
|
|
|
|
|
help
|
|
|
|
|
Per-cpu workqueues are generally preferred because they show
|
|
|
|
|
better performance thanks to cache locality; unfortunately,
|
|
|
|
|
per-cpu workqueues tend to be more power hungry than unbound
|
|
|
|
|
workqueues.
|
|
|
|
|
|
|
|
|
|
Enabling workqueue.power_efficient kernel parameter makes the
|
|
|
|
|
per-cpu workqueues which were observed to contribute
|
|
|
|
|
significantly to power consumption unbound, leading to measurably
|
|
|
|
|
lower power usage at the cost of small performance overhead.
|
|
|
|
|
|
|
|
|
|
This config option determines whether workqueue.power_efficient
|
|
|
|
|
is enabled by default.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
|
2012-08-05 23:39:57 +00:00
|
|
|
config PM_GENERIC_DOMAINS_SLEEP
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on PM_SLEEP && PM_GENERIC_DOMAINS
|
|
|
|
|
|
2014-09-19 18:27:36 +00:00
|
|
|
config PM_GENERIC_DOMAINS_OF
|
|
|
|
|
def_bool y
|
2014-09-19 18:27:43 +00:00
|
|
|
depends on PM_GENERIC_DOMAINS && OF
|
2014-09-19 18:27:36 +00:00
|
|
|
|
2011-02-10 10:04:45 +00:00
|
|
|
config CPU_PM
|
|
|
|
|
bool
|
PM: Introduce an Energy Model management framework
Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a standard API.
As an attempt to address this, introduce a centralized Energy Model
(EM) management framework which aggregates the power values provided
by drivers into a table for each performance domain in the system. The
power cost tables are made available to interested clients (e.g. task
scheduler or thermal) via platform-agnostic APIs. The overall design
is represented by the diagram below (focused on Arm-related drivers as
an example, but applicable to any architecture):
+---------------+ +-----------------+ +-------------+
| Thermal (IPA) | | Scheduler (EAS) | | Other |
+---------------+ +-----------------+ +-------------+
| | em_pd_energy() |
| | em_cpu_get() |
+-----------+ | +--------+
| | |
v v v
+---------------------+
| |
| Energy Model |
| |
| Framework |
| |
+---------------------+
^ ^ ^
| | | em_register_perf_domain()
+----------+ | +---------+
| | |
+---------------+ +---------------+ +--------------+
| cpufreq-dt | | arm_scmi | | Other |
+---------------+ +---------------+ +--------------+
^ ^ ^
| | |
+--------------+ +---------------+ +--------------+
| Device Tree | | Firmware | | ? |
+--------------+ +---------------+ +--------------+
Drivers (typically, but not limited to, CPUFreq drivers) can register
data in the EM framework using the em_register_perf_domain() API. The
calling driver must provide a callback function with a standardized
signature that will be used by the EM framework to build the power
cost tables of the performance domain. This design should offer a lot of
flexibility to calling drivers which are free of reading information
from any location and to use any technique to compute power costs.
Moreover, the capacity states registered by drivers in the EM framework
are not required to match real performance states of the target. This
is particularly important on targets where the performance states are
not known by the OS.
The power cost coefficients managed by the EM framework are specified in
milli-watts. Although the two potential users of those coefficients (IPA
and EAS) only need relative correctness, IPA specifically needs to
compare the power of CPUs with the power of other components (GPUs, for
example), which are still expressed in absolute terms in their
respective subsystems. Hence, specifying the power of CPUs in
milli-watts should help transitioning IPA to using the EM framework
without introducing new problems by keeping units comparable across
sub-systems.
On the longer term, the EM of other devices than CPUs could also be
managed by the EM framework, which would enable to remove the absolute
unit. However, this is not absolutely required as a first step, so this
extension of the EM framework is left for later.
On the client side, the EM framework offers APIs to access the power
cost tables of a CPU (em_cpu_get()), and to estimate the energy
consumed by the CPUs of a performance domain (em_pd_energy()). Clients
such as the task scheduler can then use these APIs to access the shared
data structures holding the Energy Model of CPUs.
Signed-off-by: Quentin Perret <quentin.perret@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: adharmap@codeaurora.org
Cc: chris.redpath@arm.com
Cc: currojerez@riseup.net
Cc: dietmar.eggemann@arm.com
Cc: edubezval@gmail.com
Cc: gregkh@linuxfoundation.org
Cc: javi.merino@kernel.org
Cc: joel@joelfernandes.org
Cc: juri.lelli@redhat.com
Cc: morten.rasmussen@arm.com
Cc: patrick.bellasi@arm.com
Cc: pkondeti@codeaurora.org
Cc: skannan@codeaurora.org
Cc: smuckle@google.com
Cc: srinivas.pandruvada@linux.intel.com
Cc: thara.gopinath@linaro.org
Cc: tkjos@google.com
Cc: valentin.schneider@arm.com
Cc: vincent.guittot@linaro.org
Cc: viresh.kumar@linaro.org
Link: https://lkml.kernel.org/r/20181203095628.11858-4-quentin.perret@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2018-12-03 09:56:16 +00:00
|
|
|
|
|
|
|
|
config ENERGY_MODEL
|
2021-02-09 10:54:34 +00:00
|
|
|
bool "Energy Model for devices with DVFS (CPUs, GPUs, etc)"
|
PM: Introduce an Energy Model management framework
Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a standard API.
As an attempt to address this, introduce a centralized Energy Model
(EM) management framework which aggregates the power values provided
by drivers into a table for each performance domain in the system. The
power cost tables are made available to interested clients (e.g. task
scheduler or thermal) via platform-agnostic APIs. The overall design
is represented by the diagram below (focused on Arm-related drivers as
an example, but applicable to any architecture):
+---------------+ +-----------------+ +-------------+
| Thermal (IPA) | | Scheduler (EAS) | | Other |
+---------------+ +-----------------+ +-------------+
| | em_pd_energy() |
| | em_cpu_get() |
+-----------+ | +--------+
| | |
v v v
+---------------------+
| |
| Energy Model |
| |
| Framework |
| |
+---------------------+
^ ^ ^
| | | em_register_perf_domain()
+----------+ | +---------+
| | |
+---------------+ +---------------+ +--------------+
| cpufreq-dt | | arm_scmi | | Other |
+---------------+ +---------------+ +--------------+
^ ^ ^
| | |
+--------------+ +---------------+ +--------------+
| Device Tree | | Firmware | | ? |
+--------------+ +---------------+ +--------------+
Drivers (typically, but not limited to, CPUFreq drivers) can register
data in the EM framework using the em_register_perf_domain() API. The
calling driver must provide a callback function with a standardized
signature that will be used by the EM framework to build the power
cost tables of the performance domain. This design should offer a lot of
flexibility to calling drivers which are free of reading information
from any location and to use any technique to compute power costs.
Moreover, the capacity states registered by drivers in the EM framework
are not required to match real performance states of the target. This
is particularly important on targets where the performance states are
not known by the OS.
The power cost coefficients managed by the EM framework are specified in
milli-watts. Although the two potential users of those coefficients (IPA
and EAS) only need relative correctness, IPA specifically needs to
compare the power of CPUs with the power of other components (GPUs, for
example), which are still expressed in absolute terms in their
respective subsystems. Hence, specifying the power of CPUs in
milli-watts should help transitioning IPA to using the EM framework
without introducing new problems by keeping units comparable across
sub-systems.
On the longer term, the EM of other devices than CPUs could also be
managed by the EM framework, which would enable to remove the absolute
unit. However, this is not absolutely required as a first step, so this
extension of the EM framework is left for later.
On the client side, the EM framework offers APIs to access the power
cost tables of a CPU (em_cpu_get()), and to estimate the energy
consumed by the CPUs of a performance domain (em_pd_energy()). Clients
such as the task scheduler can then use these APIs to access the shared
data structures holding the Energy Model of CPUs.
Signed-off-by: Quentin Perret <quentin.perret@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: adharmap@codeaurora.org
Cc: chris.redpath@arm.com
Cc: currojerez@riseup.net
Cc: dietmar.eggemann@arm.com
Cc: edubezval@gmail.com
Cc: gregkh@linuxfoundation.org
Cc: javi.merino@kernel.org
Cc: joel@joelfernandes.org
Cc: juri.lelli@redhat.com
Cc: morten.rasmussen@arm.com
Cc: patrick.bellasi@arm.com
Cc: pkondeti@codeaurora.org
Cc: skannan@codeaurora.org
Cc: smuckle@google.com
Cc: srinivas.pandruvada@linux.intel.com
Cc: thara.gopinath@linaro.org
Cc: tkjos@google.com
Cc: valentin.schneider@arm.com
Cc: vincent.guittot@linaro.org
Cc: viresh.kumar@linaro.org
Link: https://lkml.kernel.org/r/20181203095628.11858-4-quentin.perret@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2018-12-03 09:56:16 +00:00
|
|
|
depends on SMP
|
|
|
|
|
depends on CPU_FREQ
|
|
|
|
|
help
|
|
|
|
|
Several subsystems (thermal and/or the task scheduler for example)
|
2021-02-09 10:54:34 +00:00
|
|
|
can leverage information about the energy consumed by devices to
|
|
|
|
|
make smarter decisions. This config option enables the framework
|
|
|
|
|
from which subsystems can access the energy models.
|
PM: Introduce an Energy Model management framework
Several subsystems in the kernel (task scheduler and/or thermal at the
time of writing) can benefit from knowing about the energy consumed by
CPUs. Yet, this information can come from different sources (DT or
firmware for example), in different formats, hence making it hard to
exploit without a standard API.
As an attempt to address this, introduce a centralized Energy Model
(EM) management framework which aggregates the power values provided
by drivers into a table for each performance domain in the system. The
power cost tables are made available to interested clients (e.g. task
scheduler or thermal) via platform-agnostic APIs. The overall design
is represented by the diagram below (focused on Arm-related drivers as
an example, but applicable to any architecture):
+---------------+ +-----------------+ +-------------+
| Thermal (IPA) | | Scheduler (EAS) | | Other |
+---------------+ +-----------------+ +-------------+
| | em_pd_energy() |
| | em_cpu_get() |
+-----------+ | +--------+
| | |
v v v
+---------------------+
| |
| Energy Model |
| |
| Framework |
| |
+---------------------+
^ ^ ^
| | | em_register_perf_domain()
+----------+ | +---------+
| | |
+---------------+ +---------------+ +--------------+
| cpufreq-dt | | arm_scmi | | Other |
+---------------+ +---------------+ +--------------+
^ ^ ^
| | |
+--------------+ +---------------+ +--------------+
| Device Tree | | Firmware | | ? |
+--------------+ +---------------+ +--------------+
Drivers (typically, but not limited to, CPUFreq drivers) can register
data in the EM framework using the em_register_perf_domain() API. The
calling driver must provide a callback function with a standardized
signature that will be used by the EM framework to build the power
cost tables of the performance domain. This design should offer a lot of
flexibility to calling drivers which are free of reading information
from any location and to use any technique to compute power costs.
Moreover, the capacity states registered by drivers in the EM framework
are not required to match real performance states of the target. This
is particularly important on targets where the performance states are
not known by the OS.
The power cost coefficients managed by the EM framework are specified in
milli-watts. Although the two potential users of those coefficients (IPA
and EAS) only need relative correctness, IPA specifically needs to
compare the power of CPUs with the power of other components (GPUs, for
example), which are still expressed in absolute terms in their
respective subsystems. Hence, specifying the power of CPUs in
milli-watts should help transitioning IPA to using the EM framework
without introducing new problems by keeping units comparable across
sub-systems.
On the longer term, the EM of other devices than CPUs could also be
managed by the EM framework, which would enable to remove the absolute
unit. However, this is not absolutely required as a first step, so this
extension of the EM framework is left for later.
On the client side, the EM framework offers APIs to access the power
cost tables of a CPU (em_cpu_get()), and to estimate the energy
consumed by the CPUs of a performance domain (em_pd_energy()). Clients
such as the task scheduler can then use these APIs to access the shared
data structures holding the Energy Model of CPUs.
Signed-off-by: Quentin Perret <quentin.perret@arm.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Galbraith <efault@gmx.de>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Rafael J. Wysocki <rjw@rjwysocki.net>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: adharmap@codeaurora.org
Cc: chris.redpath@arm.com
Cc: currojerez@riseup.net
Cc: dietmar.eggemann@arm.com
Cc: edubezval@gmail.com
Cc: gregkh@linuxfoundation.org
Cc: javi.merino@kernel.org
Cc: joel@joelfernandes.org
Cc: juri.lelli@redhat.com
Cc: morten.rasmussen@arm.com
Cc: patrick.bellasi@arm.com
Cc: pkondeti@codeaurora.org
Cc: skannan@codeaurora.org
Cc: smuckle@google.com
Cc: srinivas.pandruvada@linux.intel.com
Cc: thara.gopinath@linaro.org
Cc: tkjos@google.com
Cc: valentin.schneider@arm.com
Cc: vincent.guittot@linaro.org
Cc: viresh.kumar@linaro.org
Link: https://lkml.kernel.org/r/20181203095628.11858-4-quentin.perret@arm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2018-12-03 09:56:16 +00:00
|
|
|
|
|
|
|
|
The exact usage of the energy model is subsystem-dependent.
|
|
|
|
|
|
|
|
|
|
If in doubt, say N.
|
