/kernel/linux/linux-5.10/drivers/net/wireless/ath/ |
D | dfs_pri_detector.c | 298 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()
|
D | dfs_pri_detector.h | 69 struct list_head sequences; member
|
/kernel/linux/linux-5.10/Documentation/ABI/testing/ |
D | sysfs-class-chromeos-driver-cros-ec-lightbar | 32 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/ |
D | mt76x02_dfs.c | 220 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()
|
D | mt76x02_dfs.h | 116 struct list_head sequences; member
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/ |
D | .yamllint | 37 indent-sequences: true
|
/kernel/linux/linux-5.10/Documentation/admin-guide/media/ |
D | remote-controller.rst | 14 pulse/space sequences and then to scan codes, returning such codes to 16 sequences ("raw mode").
|
/kernel/linux/linux-5.10/lib/zstd/ |
D | compress.c | 46 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 …]
|
D | zstd_internal.h | 190 seqDef *sequences; member
|
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/input/ |
D | input-reset.txt | 8 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/ |
D | libtraceevent-event_print.txt | 102 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
|
D | libtraceevent-field_get_val.txt | 94 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
|
D | libtraceevent-field_print.txt | 98 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
|
D | libtraceevent-tseq.txt | 32 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.
|
D | libtraceevent-reg_print_func.txt | 127 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
|
D | libtraceevent-reg_event_handler.txt | 128 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
|
D | libtraceevent.txt | 130 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/ |
D | Kconfig.debug | 20 assembler-generated 'longcall' sequences.
|
/kernel/linux/linux-5.10/Documentation/powerpc/ |
D | syscall64-abi.rst | 22 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/ |
D | amlogic,meson-gx-pwrc.txt | 11 sequences.
|
/kernel/linux/linux-5.10/Documentation/s390/ |
D | 3270.ChangeLog | 5 ESC sequences (especially coloring ones) and the strings
|
/kernel/linux/linux-5.10/Documentation/leds/ |
D | leds-blinkm.rst | 13 Also you can store blinking sequences as "scripts" in
|
/kernel/linux/linux-5.10/arch/arm/kernel/ |
D | phys2virt.S | 61 @ 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/ |
D | speculation.rst | 47 More complex sequences involving multiple dependent memory accesses may
|
/kernel/linux/linux-5.10/Documentation/hwmon/ |
D | max16065.rst | 59 The MAX16067 flash-configurable system manager monitors and sequences multiple
|