/linux/Documentation/admin-guide/pm/ |
H 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
|
H 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. 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/drivers/ufs/host/ |
H A 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/Documentation/bpf/standardization/ |
H A D | index.rst | 8 standardization effort with the IETF. See the `IETF BPF Working Group`_ page 9 for the working group charter, documents, and more. 18 .. _IETF BPF Working Group: https://datatracker.ietf.org/wg/bpf/about/
|
/linux/Documentation/admin-guide/mm/ |
H A D | multigen_lru.rst | 71 Users can write ``N`` to ``min_ttl_ms`` to prevent the working set of 73 if this working set cannot be kept in memory. In other words, this 94 Working set estimation 96 Working set estimation measures how much memory an application needs 103 scheduler needs to estimate the working sets of the existing jobs. 160 server according to the ranking result obtained from the working set
|
/linux/Documentation/power/ |
H 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
|
H 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
|
/linux/drivers/media/platform/mediatek/mdp3/ |
H A D | mtk-mdp3-vpu.h | 30 u32 work_addr; /* [in] working buffer address */ 31 u32 work_size; /* [in] working buffer size */ 41 /* synchronization protect for accessing vpu working buffer info */
|
/linux/arch/m68k/fpsp040/ |
H 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 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/Documentation/admin-guide/ |
H A D | verify-bugs-and-bisect-regressions.rst | 40 consider the newest Linux kernel you regularly use to be the 'working' kernel. 48 the 'working' kernel and 6.1.5 to be the first 'broken', which is why 6.0 56 # * If you are not already running the 'working' kernel, reboot into it. 67 # * Ensure the former command picked the .config of the 'working' kernel. 79 cp .config ~/kernel-config-working 94 cp ~/kernel-config-working .config 120 * **Segment 2**: ensure the 'good' kernel is also a 'working' kernel. 177 cp ~/kernel-config-working .config 213 cp ~/kernel-config-working .config 325 mainline release your working kernel is based on to be the 'good' [all …]
|
H A D | bug-bisect.rst | 10 working after upgrading from Linux 6.0 to 6.1. 32 you consider to be working and broken, which Git calls 'good' and 'bad':: 118 * `Working with git bisect <https://nathanchance.dev/posts/working-with-git-bisect/>`_
|
/linux/lib/ |
H A 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/Documentation/driver-api/media/drivers/ |
H 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/Documentation/process/ |
H A 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 128 patch. Now other developers working with that tree will get the patch by 138 Other times, conflict resolution will involve working with the other
|
/linux/Documentation/trace/coresight/ |
H A D | coresight-perf.rst | 19 is working correctly. You can dump the content of this file as 108 These tests will log historical results in the current working 117 good way to know that it's working in a very simple way). One problem 157 keep the output of tests outside of the current working directory for
|
/linux/drivers/net/ethernet/netronome/nfp/nfpcore/ |
H A D | crc32.h | 10 * crc32_posix_end() - Finalize POSIX CRC32 working state 11 * @crc: Current CRC32 working state
|
/linux/drivers/misc/echo/ |
H A 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/kernel/time/ |
H A D | Kconfig | 171 dynticks working. 175 requirements to make the full dynticks feature working. 183 Say Y only if you're working on the development of an
|
/linux/arch/riscv/include/asm/ |
H A D | ptrace.h | 69 /* Helpers for working with the instruction pointer */ 82 /* Helpers for working with the user stack pointer */ 99 /* Helpers for working with the frame pointer */
|
/linux/Documentation/networking/ |
H 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/tools/testing/selftests/ftrace/test.d/ftrace/ |
H A 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/tools/testing/selftests/ftrace/test.d/kprobe/ |
H A 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/Documentation/scsi/ |
H 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/Documentation/filesystems/bcachefs/ |
H A D | CodingStyle.rst | 52 elide - if we were working in a language with embedded correctness proofs that 56 invariants with runtime checks - much like the way people working in 77 everywhere. Having functions to print whatever object you're working with will 173 essential for working productively. We learn, gain experience, and discover the
|
/linux/Documentation/ABI/testing/ |
H 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
|