Home
last modified time | relevance | path

Searched refs:sequences (Results 1 – 25 of 67) sorted by relevance

123

/kernel/linux/linux-5.10/drivers/net/wireless/ath/
Ddfs_pri_detector.c298 list_add(&new_ps->head, &pde->sequences); in pseq_handler_create_sequences()
309 list_for_each_entry_safe(ps, ps2, &pde->sequences, head) { in pseq_handler_add_to_existing_seqs()
341 if (list_empty(&pde->sequences)) in pseq_handler_check_detection()
344 list_for_each_entry(ps, &pde->sequences, head) { in pseq_handler_check_detection()
363 list_for_each_entry_safe(ps, ps0, &pde->sequences, head) { in pri_detector_reset()
429 INIT_LIST_HEAD(&de->sequences); in pri_detector_init()
Ddfs_pri_detector.h69 struct list_head sequences; member
/kernel/linux/linux-5.10/Documentation/ABI/testing/
Dsysfs-class-chromeos-driver-cros-ec-lightbar32 sequences, you probably won’t see anything change because
49 This allows you to upload and run custom lightbar sequences.
55 The Pixel lightbar has a number of built-in sequences
68 sequences.
/kernel/linux/linux-5.10/drivers/net/wireless/mediatek/mt76/
Dmt76x02_dfs.c220 list_for_each_entry_safe(seq, tmp_seq, &dfs_pd->sequences, head) { in mt76x02_dfs_detector_reset()
506 list_add(&seq_p->head, &dfs_pd->sequences); in mt76x02_dfs_create_sequence()
523 list_for_each_entry_safe(seq, tmp_seq, &dfs_pd->sequences, head) { in mt76x02_dfs_add_event_to_sequence()
550 if (list_empty(&dfs_pd->sequences)) in mt76x02_dfs_check_detection()
553 list_for_each_entry(seq, &dfs_pd->sequences, head) { in mt76x02_dfs_check_detection()
859 INIT_LIST_HEAD(&dfs_pd->sequences); in mt76x02_dfs_init_detector()
Dmt76x02_dfs.h116 struct list_head sequences; member
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/
D.yamllint37 indent-sequences: true
/kernel/linux/linux-5.10/Documentation/admin-guide/media/
Dremote-controller.rst14 pulse/space sequences and then to scan codes, returning such codes to
16 sequences ("raw mode").
/kernel/linux/linux-5.10/lib/zstd/
Dcompress.c46 ssPtr->sequences = ssPtr->sequencesStart; in ZSTD_resetSeqStore()
567 const seqDef *const sequences = seqStorePtr->sequencesStart; in ZSTD_seqToCodes() local
571 U32 const nbSeq = (U32)(seqStorePtr->sequences - seqStorePtr->sequencesStart); in ZSTD_seqToCodes()
574 U32 const llv = sequences[u].litLength; in ZSTD_seqToCodes()
575 U32 const mlv = sequences[u].matchLength; in ZSTD_seqToCodes()
577 ofCodeTable[u] = (BYTE)ZSTD_highbit32(sequences[u].offset); in ZSTD_seqToCodes()
594 const seqDef *const sequences = seqStorePtr->sequencesStart; in ZSTD_compressSequences_internal() local
601 size_t const nbSeq = seqStorePtr->sequences - seqStorePtr->sequencesStart; in ZSTD_compressSequences_internal()
762 BIT_addBits(&blockStream, sequences[nbSeq - 1].litLength, LL_bits[llCodeTable[nbSeq - 1]]); in ZSTD_compressSequences_internal()
765 BIT_addBits(&blockStream, sequences[nbSeq - 1].matchLength, ML_bits[mlCodeTable[nbSeq - 1]]); in ZSTD_compressSequences_internal()
[all …]
Dzstd_internal.h190 seqDef *sequences; member
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/
Dinput-reset.txt8 Key sequences are global to the system but all the keys in a set must be coming
/kernel/linux/linux-5.10/tools/lib/traceevent/Documentation/
Dlibtraceevent-event_print.txt102 Header file to include in order to have access to trace sequences related APIs.
103 Trace sequences are used to allow a function to call several other functions
Dlibtraceevent-field_get_val.txt94 Header file to include in order to have access to trace sequences
95 related APIs. Trace sequences are used to allow a function to call
Dlibtraceevent-field_print.txt98 Header file to include in order to have access to trace sequences related APIs.
99 Trace sequences are used to allow a function to call several other functions
Dlibtraceevent-tseq.txt32 Trace sequences are used to allow a function to call several other functions
132 Header file to include in order to have access to trace sequences related APIs.
Dlibtraceevent-reg_print_func.txt127 Header file to include in order to have access to trace sequences
128 related APIs. Trace sequences are used to allow a function to call
Dlibtraceevent-reg_event_handler.txt128 Header file to include in order to have access to trace sequences
129 related APIs. Trace sequences are used to allow a function to call
Dlibtraceevent.txt130 Trace sequences:
164 Header file to include in order to have access to trace sequences related APIs.
165 Trace sequences are used to allow a function to call several other functions
/kernel/linux/linux-5.10/arch/xtensa/
DKconfig.debug20 assembler-generated 'longcall' sequences.
/kernel/linux/linux-5.10/Documentation/powerpc/
Dsyscall64-abi.rst22 different calling sequences (e.g., rt_sigreturn).
113 following differences. Some vsyscalls may have different calling sequences.
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Damlogic,meson-gx-pwrc.txt11 sequences.
/kernel/linux/linux-5.10/Documentation/s390/
D3270.ChangeLog5 ESC sequences (especially coloring ones) and the strings
/kernel/linux/linux-5.10/Documentation/leds/
Dleds-blinkm.rst13 Also you can store blinking sequences as "scripts" in
/kernel/linux/linux-5.10/arch/arm/kernel/
Dphys2virt.S61 @ The Thumb-2 versions of the patchable sequences are
142 @ The ARM versions of the patchable sequences are
/kernel/linux/linux-5.10/Documentation/staging/
Dspeculation.rst47 More complex sequences involving multiple dependent memory accesses may
/kernel/linux/linux-5.10/Documentation/hwmon/
Dmax16065.rst59 The MAX16067 flash-configurable system manager monitors and sequences multiple

123