/linux/Documentation/admin-guide/pm/ |
A D | strategies.rst | 20 designated devices, triggering a transition to the ``working state`` in which 25 The other strategy, referred to as the :doc:`working-state power management 26 <working-state>`, is based on adjusting the power states of individual hardware 27 components of the system, as needed, in the working state. In consequence, if 28 this strategy is in use, the working state of the system usually does not 44 back to the working state can only be started by a limited set of devices, so 53 away from the laptop keyboard, it probably should stay in the working state and 54 use the working-state power management in case it becomes idle, because the user
|
A D | suspend-flows.rst | 13 system to get from the working state into one of the supported 19 For those sleep states, the transition from the working state of the system into 23 working state is referred to as *system resume*. 45 The following steps are taken in order to transition the system from the working 54 up after getting back to the working state. 92 would be triggered in the working state of the system (those actions are 124 :ref:`suspend-to-idle <s2idle>` sleep state into the working state: 137 2. Resuming devices and restoring the working-state configuration of IRQs. 237 platform-dependent suspend state into the working state: 243 control is passed back to the kernel (the working configuration of the [all …]
|
A D | index.rst | 12 working-state
|
/linux/Documentation/power/ |
A D | tricks.rst | 7 If you want to trick swsusp/S3 into working, you might want to try: 14 * use ext2. At least it has working fsck. [If something seems to go 25 * due to video issues, swsusp should be easier to get working than
|
A D | video.rst | 26 whitelist of systems, and automatically selects working method for a 29 whitelist, please try to find a working solution, and submit whitelist 62 to life. It needs text console to be working. Do vbetool vbestate 75 the display working in graphical mode again. 87 chance of working. 89 Table of known working notebooks: 198 Known working desktop systems
|
A D | apm-acpi.rst | 14 enabled by default). If a working ACPI implementation is found, the 20 would like to use both to get a full set of working features, but you
|
/linux/tools/iio/ |
A D | iio_utils.c | 33 char *working, *prefix = ""; in iioutils_break_up_name() local 47 working = strtok(current, "_\0"); in iioutils_break_up_name() 48 if (!working) { in iioutils_break_up_name() 53 w = working; in iioutils_break_up_name() 54 r = working; in iioutils_break_up_name() 65 ret = asprintf(generic_name, "%s_%s", prefix, working); in iioutils_break_up_name()
|
/linux/arch/arm/include/asm/ |
A D | vfpmacros.h | 30 @ read all the working registers back into the VFP 56 @ write all the working registers out of the VFP
|
/linux/Documentation/networking/ |
A D | sctp.rst | 13 RFC2960 defines the core protocol. The IETF SIGTRAN working group originally 15 Transport Area (TSVWG) working group for the continued evolvement of SCTP as a
|
/linux/Documentation/ABI/testing/ |
A D | sysfs-bus-dfl-devices-n3000-nios | 17 Description: Read-only. Returns the enumeration value of the working mode of 37 Description: Read-only. Returns the enumeration value of the working mode of
|
/linux/Documentation/driver-api/serial/ |
A D | serial-iso7816.rst | 18 working in both modes, and proper ioctls (see later) should be made 29 Any driver for devices capable of working both as RS232 and ISO7816 should
|
A D | serial-rs485.rst | 25 working in both modes, and proper ioctls (see later) should be made 40 Any driver for devices capable of working both as RS232 and RS485 should
|
/linux/Documentation/driver-api/media/drivers/ |
A D | dvb-usb.rst | 111 first almost working version for HanfTek UMT-010 144 - first working version of the dib3000mc/p frontend driver. 194 - firmware-extraction-2.422-problem solved, driver is now working 218 - firmware loader is working 231 working. 307 working like charm now with VDR. Sometimes I even was able to record a channel
|
/linux/kernel/time/ |
A D | Kconfig | 151 dynticks working. 155 requirements to make the full dynticks feature working. 163 Say Y only if you're working on the development of an
|
/linux/drivers/bcma/ |
A D | Kconfig | 48 1) PCIe core working in clientmode 58 bool "Driver for PCI core working in hostmode"
|
/linux/Documentation/admin-guide/ |
A D | init.rst | 1 Explaining the "No working init found." boot hang message 32 shebang header line (``#!/...``) that is fully working (including its
|
/linux/arch/m68k/fpsp040/ |
A D | decbin.S | 124 | 1. Copy bcd value in memory for use as a working copy. 138 | ( ) a0: pointer to working bcd value 140 | (*) FP_SCR1: working copy of original bcd value 477 | ( ) a0: pointer to working bcd value
|
/linux/Documentation/scsi/ |
A D | 53c700.rst | 19 fill in to get the driver working. 36 In order to plumb the 53c700 chip core driver into a working SCSI 49 even by examining the configuration of a working driver under another
|
/linux/drivers/scsi/ |
A D | atp870u.h | 37 unsigned int working[2]; member
|
/linux/drivers/media/test-drivers/vidtv/ |
A D | Kconfig | 8 working on userspace applications.
|
/linux/drivers/gpu/drm/ast/ |
A D | Kconfig | 11 this driver without having a working -modesetting,
|
/linux/Documentation/admin-guide/mm/damon/ |
A D | start.rst | 87 You can also visualize the distribution of the working set size, sorted by the 106 Using ``--sortby`` option with the above command, you can show how the working
|
/linux/Documentation/usb/ |
A D | usb-help.rst | 14 - Linux-USB device overview (working devices and drivers):
|
/linux/drivers/connector/ |
A D | Kconfig | 7 This is unified userspace <-> kernelspace connector working on top
|
/linux/Documentation/translations/zh_CN/admin-guide/ |
A D | init.rst | 9 解释“No working init found.”启动挂起消息
|