Searched full:sequence (Results 1 – 25 of 362) sorted by relevance
12345678910>>...15
| /Documentation/filesystems/ext4/ |
| D | mmp.rst | 10 sequence number. If the sequence number is EXT4_MMP_SEQ_CLEAN, the
11 open continues. If the sequence number is EXT4_MMP_SEQ_FSCK, then
14 the sequence number again. If the sequence number has changed, then the
16 code passes all of those checks, a new MMP sequence number is generated
21 the MMP sequence number is re-read; if it does not match the in-memory
22 MMP sequence number, then another node (node B) has mounted the
24 sequence numbers match, the sequence number is incremented both in
49 - Sequence number, updated periodically.
|
| /Documentation/locking/ |
| D | seqlock.rst | 2 Sequence counters and sequential locks
8 Sequence counters are a reader-writer consistency mechanism with
14 A data set is consistent when the sequence count at the beginning of the
15 read side critical section is even and the same sequence count value is
17 be copied out inside the read side critical section. If the sequence
21 Writers increment the sequence count at the start and the end of their
22 critical section. After starting the critical section the sequence count
24 the end of the write side critical section the sequence count becomes
27 A sequence counter write side critical section must never be preempted
29 the entire scheduler tick due to the odd sequence count value and the
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-rc-nuvoton | 6 Reading this file returns the stored CIR wakeup sequence.
9 The same format can be used to store a wakeup sequence
12 Note: Some systems reset the stored wakeup sequence to a
14 wakeup sequence in a file and set it on boot using e.g.
|
| D | sysfs-class-chromeos-driver-cros-ec-lightbar | 35 sequence first.
51 What: /sys/class/chromeos/<ec-device-name>/lightbar/sequence
58 file displays the current sequence that the lightbar is
60 sequence.
|
| D | sysfs-pps | 22 and the assert sequence number of the X-th source in the form:
24 <secs>.<nsec>#<sequence>
34 and the clear sequence number of the X-th source in the form:
36 <secs>.<nsec>#<sequence>
|
| D | sysfs-fs-xfs | 6 The log sequence number (LSN) of the current head of the
15 The log sequence number (LSN) of the current tail of the
|
| /Documentation/driver-api/ |
| D | pwrseq.rst | 17 exposed by the power sequence provider and delegate the actual requesting and
28 A unit is a discreet chunk of a power sequence. For instance one unit may
38 share the same parts of a power sequence but ignore parts that are
52 specify the name of the target it wants to reach in the sequence after calling
65 Each provider can logically split the power-up sequence into descrete chunks
67 consumers may use as the final point in the sequence that they wish to reach.
76 mechanism for dynamic matching of consumers and providers. Every power sequence
|
| D | connector.rst | 72 someone sends a message, they use a locally unique sequence and random
73 acknowledge number. The sequence number may be copied into
76 The sequence number is incremented with each message sent.
78 If you expect a reply to the message, then the sequence number in the
82 If we receive a message and its sequence number is not equal to one we
84 its sequence number is the same as one we are expecting, but its
85 acknowledge is not equal to the sequence number in the original
|
| D | pps.rst | 153 sequence number::
159 sequence number. Other files are:
190 source 0 - assert 1186592699.388832443, sequence: 364 - clear 0.000000000, sequence: 0
191 source 0 - assert 1186592700.388931295, sequence: 365 - clear 0.000000000, sequence: 0
192 source 0 - assert 1186592701.389032765, sequence: 366 - clear 0.000000000, sequence: 0
|
| /Documentation/devicetree/bindings/input/ |
| D | input-reset.txt | 1 Input: sysrq reset sequence
4 include/uapi/linux/input.h. This is to communicate a sequence of keys to the
20 sequence has been recognized.
|
| /Documentation/userspace-api/media/v4l/ |
| D | dev-decoder.rst | 38 6. i = [a..b]: sequence of integers from a to b, inclusive, i.e. i =
132 SPS/PPS/IDR sequence (H.264/HEVC); a resume point is required to start decode
150 Sequence Parameter Set; a type of metadata entity in an H.264/HEVC bytestream.
369 initialization sequence completes and the frame is decoded.
389 and continue with the `Capture Setup` sequence. However, it must not
400 5. Continue with the `Capture Setup` sequence.
500 metadata parsed in this initialization sequence, even if more formats
601 :c:func:`VIDIOC_STREAMOFF` on it would abort the sequence and trigger a
703 This state is reached after the `Capture Setup` sequence finishes successfully.
782 before the sequence started. Last of the buffers will have the
[all …]
|
| D | dev-encoder.rst | 38 6. i = [a..b]: sequence of integers from a to b, inclusive, i.e. i =
449 This state is reached after the `Initialization` sequence finishes
535 releasing all buffers and performing the Initialization sequence again.
549 sequence to avoid losing the already queued/encoded frames.
561 drain sequence described below. After the drain sequence ends, the client has
563 sequence was started.
565 1. Begin the drain sequence by issuing :c:func:`VIDIOC_ENCODER_CMD`.
580 The sequence can be only initiated if both ``OUTPUT`` and ``CAPTURE``
584 sequence and so the steps described below would not be applicable.
627 ``CAPTURE`` queue - the encoder will be reset (see the `Reset` sequence)
[all …]
|
| D | vidioc-encoder-cmd.rst | 106 For a device implementing the :ref:`encoder`, once the drain sequence
109 invoke the command while the drain sequence is in progress will trigger
119 the drain sequence as documented in :ref:`encoder`. No flags or other
121 again before the sequence completes will trigger an ``EBUSY`` error
160 A drain sequence of a device implementing the :ref:`encoder` is still in
|
| /Documentation/security/ |
| D | sak.rst | 12 this key sequence before they log in to the system.
15 providing SAK. One is the ALT-SYSRQ-K sequence. You shouldn't use
16 this sequence. It is only available if the kernel was compiled with
19 The proper way of generating a SAK is to define the key sequence using
28 What key sequence should you use? Well, CTRL-ALT-DEL is used to reboot
|
| /Documentation/networking/ |
| D | xfrm_proc.rst | 43 Sequence error
44 i.e. Sequence number is out of window
100 Sequence error
101 i.e. Sequence number overflow
|
| D | tls-offload.rst | 100 as well as TLS record sequence number. ``start_offload_tcp_sn`` indicates
101 which TCP sequence number corresponds to the beginning of the record with
102 sequence number from ``crypto_info``. The driver can add its state
111 of the stream will start exactly at the ``start_offload_tcp_sn`` sequence
112 number, simplifying TCP sequence number matching.
116 the expected sequence number and will have kernel record information.
124 so the initial records' TCP sequence number may be anywhere inside the segment.
134 * record metadata (sequence number, processing offset and length)
135 * expected TCP sequence number
159 Both the device and the driver maintain expected TCP sequence numbers
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | ssh.rst | 72 - Sequence ID (see explanation below).
101 same sequence ID (|SEQ|), stored inside the frame (more on this in the next
102 section). The sequence ID is a wrapping counter.
133 other hand must carry a payload. The flow sequence and interaction of
137 SSH Packet Protocol: Flow Sequence
145 the same sequence ID of the |DATA| frame. In other words, the sequence ID of
148 containing an |NAK|-type frame. As the sequence ID of the previous data
150 upon, the sequence ID of the |NAK| frame should not be used and is set to
154 Sequence IDs are not synchronized between the two parties, meaning that they
156 corresponding to a single exchange thus relies on the sequence ID as well as
[all …]
|
| /Documentation/filesystems/ |
| D | seq_file.rst | 47 loadable module which creates a file called /proc/sequence. The file, when
49 sequence will continue until the user loses patience and finds something
53 dd if=/proc/sequence of=out1 count=1
54 dd if=/proc/sequence skip=1 of=out2 count=1
68 - entry = create_proc_entry("sequence", 0, NULL);
71 + entry = proc_create("sequence", 0, NULL, &ct_file_ops);
80 though with freedom to map the position number to a sequence location
99 The /proc/sequence iterator just uses the count of the next number it
108 For our simple sequence example,
121 holding the current position. There is no upper bound for the sequence
[all …]
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,msm8976-ramp-controller.yaml | 13 The Ramp Controller is used to program the sequence ID for pulse
14 swallowing, enable sequences and link Sequence IDs (SIDs) for the
|
| /Documentation/device-mapper/ |
| D | dm-bow.txt | 79 | Magic | Count | Sequence | Log entry | Log entry | …
82 Magic is a magic number. Count is the number of log entries. Sequence is 0
90 created with sequence number one higher. The first entry in any log entry with
91 sequence > 0 therefore must be the log of the backing up of the previous log
92 sector. Note that sequence is not strictly needed, but is a useful sanity check
|
| /Documentation/driver-api/media/ |
| D | rc-core.rst | 36 In other words, a typical IR transmission can be viewed as a sequence of
49 signal in a sequence of *PULSE/SPACE* events, filtering out the carrier
53 So, a simple IR receiver hardware will just provide a sequence of timings
57 microcontroller that decode the *PULSE/SPACE* sequence and return scan
|
| /Documentation/devicetree/bindings/soc/renesas/ |
| D | renesas,rzv2m-pwc.yaml | 7 title: Renesas RZ/V2M External Power Sequence Controller (PWC)
12 - external power supply on/off sequence generation
|
| /Documentation/driver-api/soundwire/ |
| D | error_handling.rst | 16 Improvements could be invalidating an entire programming sequence and
18 control/command sequence, there is no concealment or recovery for audio
38 backtracking and restarting the entire programming sequence might be a
|
| /Documentation/devicetree/bindings/mmc/ |
| D | mmc-pwrseq-simple.yaml | 7 title: Simple MMC power sequence provider
13 The purpose of the simple MMC power sequence provider is to supports a set
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | gpio-poweroff.yaml | 35 it to an output when the power-off sequence is initiated. If this optional
51 description: Time to wait before assuming the power off sequence failed.
|
12345678910>>...15