Searched refs:working (Results 1 – 25 of 331) sorted by relevance
12345678910>>...14
| /Linux-v5.4/Documentation/admin-guide/pm/ |
| 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
|
| D | index.rst | 12 working-state
|
| /Linux-v5.4/Documentation/power/ |
| 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
|
| 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
|
| 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-v5.4/tools/iio/ |
| 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-v5.4/Documentation/networking/ |
| D | sctp.txt | 9 RFC2960 defines the core protocol. The IETF SIGTRAN working group originally
11 Transport Area (TSVWG) working group for the continued evolvement of SCTP as a
|
| /Linux-v5.4/arch/arm/include/asm/ |
| D | vfpmacros.h | 20 @ read all the working registers back into the VFP in toolkits()
44 @ write all the working registers out of the VFP
|
| /Linux-v5.4/Documentation/driver-api/serial/ |
| 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
|
| /Linux-v5.4/drivers/scsi/ |
| D | atp870u.h | 37 unsigned int working[2]; member
|
| /Linux-v5.4/kernel/time/ |
| D | Kconfig | 132 dynticks working.
136 requirements to make the full dynticks feature working.
144 Say Y only if you're working on the development of an
|
| /Linux-v5.4/drivers/gpu/drm/ast/ |
| D | Kconfig | 9 this driver without having a working -modesetting,
|
| /Linux-v5.4/Documentation/media/dvb-drivers/ |
| 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-v5.4/Documentation/usb/ |
| D | usb-help.rst | 14 - Linux-USB device overview (working devices and drivers):
|
| /Linux-v5.4/Documentation/scsi/ |
| D | 53c700.txt | 13 fill in to get the driver working.
30 In order to plumb the 53c700 chip core driver into a working SCSI
43 even by examining the configuration of a working driver under another
|
| /Linux-v5.4/arch/s390/ |
| D | Kconfig.debug | 13 who are working in architecture specific areas of the kernel.
|
| /Linux-v5.4/drivers/bcma/ |
| D | Kconfig | 48 1) PCIe core working in clientmode
58 bool "Driver for PCI core working in hostmode"
|
| /Linux-v5.4/Documentation/RCU/ |
| D | torture.txt | 48 that RCU is working when it is not. :-/
60 rcu_assign_pointer() and rcu_dereference() are not working
64 family of functions is not working correctly.
93 The output displayed above was taken from a correctly working
|
| /Linux-v5.4/drivers/connector/ |
| D | Kconfig | 7 This is unified userspace <-> kernelspace connector working on top
|
| /Linux-v5.4/arch/m68k/fpsp040/ |
| 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-v5.4/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx35-pinctrl.txt | 10 pin working on a specific function, CONFIG is the pad setting value like
|
| D | fsl,imx50-pinctrl.txt | 10 pin working on a specific function, CONFIG is the pad setting value like
|
| D | fsl,imx51-pinctrl.txt | 10 pin working on a specific function, CONFIG is the pad setting value like
|
| D | fsl,imx53-pinctrl.txt | 10 pin working on a specific function, CONFIG is the pad setting value like
|
| D | fsl,imx6q-pinctrl.txt | 10 pin working on a specific function, CONFIG is the pad setting value like
|
12345678910>>...14
