Home
last modified time | relevance | path

Searched refs:working (Results 1 – 25 of 323) sorted by relevance

12345678910>>...13

/Linux-v4.19/Documentation/admin-guide/pm/
Dstrategies.rst16 designated devices, triggering a transition to the ``working state`` in which
21 The other strategy, referred to as the :doc:`working-state power management
22 <working-state>`, is based on adjusting the power states of individual hardware
23 components of the system, as needed, in the working state. In consequence, if
24 this strategy is in use, the working state of the system usually does not
40 back to the working state can only be started by a limited set of devices, so
49 away from the laptop keyboard, it probably should stay in the working state and
50 use the working-state power management in case it becomes idle, because the user
Dindex.rst10 working-state
/Linux-v4.19/Documentation/power/
Dtricks.txt5 If you want to trick swsusp/S3 into working, you might want to try:
12 * use ext2. At least it has working fsck. [If something seems to go
23 * due to video issues, swsusp should be easier to get working than
Dvideo.txt25 whitelist of systems, and automatically selects working method for a
28 whitelist, please try to find a working solution, and submit whitelist
61 to life. It needs text console to be working. Do vbetool vbestate
74 the display working in graphical mode again.
86 chance of working.
88 Table of known working notebooks:
172 Known working desktop systems
D00-INDEX28 - How to get suspend to ram working (and debug it when it isn't)
40 - How to trick software suspend (to disk) into working when it isn't
Dapm-acpi.txt12 enabled by default). If a working ACPI implementation is found, the
18 would like to use both to get a full set of working features, but you
/Linux-v4.19/Documentation/filesystems/pohmelfs/
Dinfo.txt21 the system checks that servers have to be added or removed from current working set.
57 Add server server1.net:1025 into the working set with index $idx
62 Client will connect to all servers specified in the working set via previous command:
85 Number of working threads is set to 10.
/Linux-v4.19/tools/iio/
Diio_utils.c36 char *working, *prefix = ""; in iioutils_break_up_name() local
50 working = strtok(current, "_\0"); in iioutils_break_up_name()
51 if (!working) { in iioutils_break_up_name()
56 w = working; in iioutils_break_up_name()
57 r = working; in iioutils_break_up_name()
68 ret = asprintf(generic_name, "%s_%s", prefix, working); in iioutils_break_up_name()
/Linux-v4.19/Documentation/networking/
Dsctp.txt9 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-v4.19/arch/arm/include/asm/
Dvfpmacros.h20 @ read all the working registers back into the VFP in toolkits()
44 @ write all the working registers out of the VFP
/Linux-v4.19/drivers/scsi/
Datp870u.h37 unsigned int working[2]; member
/Linux-v4.19/drivers/gpu/drm/ast/
DKconfig9 this driver without having a working -modesetting,
/Linux-v4.19/Documentation/media/dvb-drivers/
Ddvb-usb.rst109 first almost working version for HanfTek UMT-010
142 - first working version of the dib3000mc/p frontend driver.
192 - firmware-extraction-2.422-problem solved, driver is now working
216 - firmware loader is working
229 working.
305 working like charm now with VDR. Sometimes I even was able to record a channel
/Linux-v4.19/Documentation/usb/
Dusb-help.txt11 Linux-USB device overview (working devices and drivers):
/Linux-v4.19/arch/s390/
DKconfig.debug13 who are working in architecture specific areas of the kernel.
/Linux-v4.19/Documentation/scsi/
D53c700.txt13 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-v4.19/drivers/bcma/
DKconfig48 1) PCIe core working in clientmode
58 bool "Driver for PCI core working in hostmode"
/Linux-v4.19/drivers/connector/
DKconfig6 This is unified userspace <-> kernelspace connector working on top
/Linux-v4.19/arch/m68k/fpsp040/
Ddecbin.S124 | 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-v4.19/Documentation/devicetree/bindings/pinctrl/
Dfsl,imx35-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx51-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx53-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
Dfsl,imx6q-pinctrl.txt10 pin working on a specific function, CONFIG is the pad setting value like
/Linux-v4.19/Documentation/serial/
Dserial-rs485.txt21 working in both modes, and proper ioctls (see later) should be made
35 Any driver for devices capable of working both as RS232 and RS485 should
/Linux-v4.19/arch/powerpc/kernel/
Drtas.c779 if (atomic_dec_return(&data->working) == 0) in __rtas_suspend_last_cpu()
787 atomic_inc(&data->working); in rtas_suspend_last_cpu()
797 atomic_inc(&data->working); in __rtas_suspend_cpu()
833 if (atomic_dec_return(&data->working) == 0) in __rtas_suspend_cpu()
969 atomic_set(&data.working, 0); in rtas_ibm_suspend_me()

12345678910>>...13