Searched full:working (Results 1 – 25 of 1359) sorted by relevance
12345678910>>...55
| /Linux-v5.10/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 | 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.
146 The working-state configuration of IRQs is restored after the *noirq* resume
167 The following steps are taken in order to transition the system from the working
[all …]
|
| /Linux-v5.10/drivers/scsi/ufs/ |
| D | ufshcd-pltfrm.h | 20 u32 rx_pwr_pwm; /* rx pwm working pwr */
21 u32 tx_pwr_pwm; /* tx pwm working pwr */
22 u32 rx_pwr_hs; /* rx hs working pwr */
23 u32 tx_pwr_hs; /* tx hs working pwr */
|
| /Linux-v5.10/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.10/arch/riscv/include/asm/ |
| D | ptrace.h | 64 /* Helpers for working with the instruction pointer */
77 /* Helpers for working with the user stack pointer */
88 /* Helpers for working with the frame pointer */
|
| /Linux-v5.10/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
166 orl #0x40000000,(%a0) |and in working bcd
184 | ( ) a0: pointer to working bcd value
187 | ( ) FP_SCR1: working copy of original bcd value
275 | ( ) a0: pointer to working bcd value
276 | ( ) FP_SCR1: working copy of original bcd value
403 | ( ) a0: pointer to working copy of bcd
477 | ( ) a0: pointer to working bcd value
|
| /Linux-v5.10/lib/ |
| D | test_linear_ranges.c | 27 * Problem is that testing working code is pointless. And if it is not
28 * working, your test must not assume it is working. You won't catch any bugs
47 * working.
51 * working. And I definitely don't want to add 500+ test cases that break when
|
| /Linux-v5.10/Documentation/driver-api/media/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.10/Documentation/process/ |
| D | 6.Followthrough.rst | 22 Working with reviewers
26 developers as they review the code. Working with reviewers can be, for
49 be working on the kernel years from now, but they understand that their
51 working toward the creation of the best kernel they can; they are not
121 patch. Now other developers working with that tree will get the patch by
131 Other times, conflict resolution will involve working with the other
|
| D | 5.Posting.rst | 87 changes found in your working revision control system. Instead, the
108 working kernel. Partial application of a patch series is a common
127 Working to create the perfect patch series can be a frustrating process
285 - Other developers who have been working in the same area - especially
286 those who might be working there now. Using git to see who else has
287 modified the files you are working on can be helpful.
|
| /Linux-v5.10/kernel/time/ |
| D | Kconfig | 141 dynticks working.
145 requirements to make the full dynticks feature working.
153 Say Y only if you're working on the development of an
|
| /Linux-v5.10/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | crc32.h | 11 * crc32_posix_end() - Finalize POSIX CRC32 working state
12 * @crc: Current CRC32 working state
|
| /Linux-v5.10/Documentation/networking/ |
| 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-v5.10/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | fgraph-filter-stack.tc | 46 fail "Graph filtering not working with stack tracer?"
63 fail "Graph filtering not working after stack tracer disabled?"
|
| /Linux-v5.10/tools/testing/selftests/ftrace/test.d/kprobe/ |
| D | kprobe_args_user.tc | 9 :;: "user-memory access syntax and ustring working on user memory";:
25 :;: "user-memory access syntax and ustring not working with kernel memory";:
|
| /Linux-v5.10/drivers/misc/echo/ |
| D | fir.h | 38 * 16 bit integer FIR descriptor. This defines the working state for a single
49 * 32 bit integer FIR descriptor. This defines the working state for a single
61 * Floating point FIR descriptor. This defines the working state for a single
|
| /Linux-v5.10/include/xen/interface/io/ |
| D | tpmif.h | 33 VTPM_STATE_SUBMIT, /* request ready / vTPM working */
35 VTPM_STATE_CANCEL, /* cancel requested / vTPM working */
|
| /Linux-v5.10/Documentation/scsi/ |
| 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-v5.10/drivers/bcma/ |
| D | Kconfig | 48 1) PCIe core working in clientmode
58 bool "Driver for PCI core working in hostmode"
|
| /Linux-v5.10/drivers/input/mouse/ |
| D | cypress_ps2.h | 37 /* Cypress trackpad working mode. */
48 * report mode bit is set, firmware working in Remote Mode.
49 * report mode bit is cleared, firmware working in Stream Mode.
|
| /Linux-v5.10/arch/arm/include/asm/ |
| D | vfpmacros.h | 30 @ read all the working registers back into the VFP
56 @ write all the working registers out of the VFP
|
| /Linux-v5.10/tools/testing/ktest/examples/include/ |
| D | tests.conf | 53 # working.
62 # working.
|
| /Linux-v5.10/Documentation/admin-guide/ |
| D | init.rst | 1 Explaining the "No working init found." boot hang message
32 shebang header line (``#!/...``) that is fully working (including its
|
12345678910>>...55
