| /kernel/linux/linux-5.10/arch/arm/probes/kprobes/ |
| D | test-arm.c | 1176 #define COPROCESSOR_INSTRUCTIONS_ST_LD(two,cc) \ in kprobe_arm_test_cases() argument
1177 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1178 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
1179 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #4]!") \ in kprobe_arm_test_cases()
1180 TEST_COPROCESSOR("stc"two" 0, cr0, [r13, #-4]!") \ in kprobe_arm_test_cases()
1181 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #4") \ in kprobe_arm_test_cases()
1182 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #-4") \ in kprobe_arm_test_cases()
1183 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], {1}") \ in kprobe_arm_test_cases()
1184 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1185 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
[all …]
|
| /kernel/linux/linux-5.10/lib/ |
| D | test_stackinit.c | 69 #define INIT_STRUCT_static_partial = { .two = 0, }
71 .two = 0, \
75 #define INIT_STRUCT_dynamic_partial = { .two = arg->two, }
77 .two = arg->two, \
82 var.two = 0
85 var.two = 0; \
198 unsigned long two; member
206 char two; member
215 u8 two; member
223 char *two; member
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | fsl,audmix.txt | 3 The Audio Mixer is a on-chip functional module that allows mixing of two
4 audio streams into a single audio stream. Audio Mixer has two input serial
5 audio interfaces. These are driven by two Synchronous Audio interface
8 from two interfaces into a single sample. Before mixing, audio samples of
9 two inputs can be attenuated based on configuration. The output of the
20 Mixing operation is independent of audio sample rate but the two audio
37 DAIs. The current implementation requires two phandles
|
| D | mt6358.txt | 14 - mediatek,dmic-mode : Indicates how many data pins are used to transmit two
15 channels of PDM signal. 0 means two wires, 1 means one wire. Default
|
| D | cs35l32.txt | 20 of the two: Class G or adaptive LED voltage.
28 Determines the data packed in a two-CS35L32 configuration.
34 - cirrus,sdout-share : SDOUT sharing. Determines whether one or two CS35L32
|
| /kernel/linux/linux-5.10/arch/sh/boards/mach-r2d/ |
| D | Kconfig | 11 R2D-PLUS is the smaller of the two R2D board versions, equipped
19 R2D-1 is the larger of the two R2D board versions, equipped
20 with two PCI slots.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-nv12mt.rst | 10 has two planes - one for luminance and one for chrominance. Chroma
19 This is the two-plane versions of the YUV 4:2:0 format where data is
21 two sub-images or planes. The Y plane has one byte per pixel and pixels
27 alignment is 32. Every four adjacent buffers - two horizontally and two
|
| D | pixfmt-nv16m.rst | 18 This is a multi-planar, two-plane version of the YUV 4:2:2 format. The
19 three components are separated into two sub-images or planes.
21 two planes are non-contiguous in memory, i.e. the chroma plane does not
26 Each CbCr pair belongs to two pixels. For example,
|
| /kernel/linux/linux-5.10/tools/testing/selftests/bpf/progs/ |
| D | test_sockmap_kern.h | 97 int *f, two = 2; in bpf_prog1() local
99 f = bpf_map_lookup_elem(&sock_skb_opts, &two); in bpf_prog1()
237 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local
250 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog4()
264 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
280 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog6()
341 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog10() local
353 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog10()
|
| D | test_mmap.c | 32 int zero = 0, one = 1, two = 2, far = 1500; in test_mmap() local
38 bpf_map_update_elem(&data_map, &two, (const void *)&in_val, 0); in test_mmap()
|
| /kernel/linux/linux-5.10/tools/testing/selftests/splice/ |
| D | short_splice_read.sh | 100 two=$(echo "$full" | grep -m1 . | cut -c-2)
110 if ! do_splice "$filename" 2 "$two" "'$two'" ; then
|
| /kernel/linux/linux-5.10/drivers/misc/lkdtm/ |
| D | usercopy.c | 125 unsigned char *one, *two; in do_usercopy_heap_size() local
131 two = kmalloc(size, GFP_KERNEL); in do_usercopy_heap_size()
132 if (!one || !two) { in do_usercopy_heap_size()
146 memset(two, 'B', size); in do_usercopy_heap_size()
181 kfree(two); in do_usercopy_heap_size()
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.txt | 4 this M4U have two generations of HW architecture. Generation one uses flat
5 pagetable, and only supports 4K size page mapping. Generation two uses the
60 "mediatek,mt2712-m4u" for mt2712 which uses generation two m4u HW.
61 "mediatek,mt6779-m4u" for mt6779 which uses generation two m4u HW.
64 "mediatek,mt8167-m4u" for mt8167 which uses generation two m4u HW.
65 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
66 "mediatek,mt8183-m4u" for mt8183 which uses generation two m4u HW.
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/spi/ |
| D | spi-nxp-fspi.txt | 16 - reg : There are two buses (A and B) with two chip selects each.
23 Example showing the usage of two SPI NOR slave devices on bus A:
|
| D | spi-fsl-qspi.txt | 17 - reg: There are two buses (A and B) with two chip selects each.
44 Example showing the usage of two SPI NOR devices on bus A:
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio_atmel.txt | 7 - #gpio-cells: Should be two. The first cell is the pin number and
12 - #interrupt-cells: Should be two. The first cell is the pin number and the
13 second cell is used to specify irq type flags, see the two cell description
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | ifc.txt | 9 - #address-cells : Should be either two or three. The first cell is the
12 - #size-cells : Either one or two, depending on how large each chipselect
15 - interrupts: IFC may have one or two interrupts. If two interrupt
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/device-mapper/ |
| D | unstriped.rst | 85 Intel NVMe drives contain two cores on the physical device.
88 in a 256k stripe across the two cores::
97 neighbor environments. When two partitions are created on the
100 are striped across the two cores. When we unstripe this hardware RAID 0
101 and make partitions on each new exposed device the two partitions are now
121 There will now be two devices that expose Intel NVMe core 0 and 1
|
| /kernel/linux/linux-5.10/Documentation/driver-api/ |
| D | edac.rst | 44 controller. Typically, it contains two channels. Two channels at the
49 is calculated using two DIMMs instead of one. Due to that, it is capable
62 The data size accessed by the memory controller is interlaced into two
78 commonly drive two chip-select pins to a memory stick. A single-ranked
85 A double-ranked stick has two chip-select rows which access different
86 sets of memory devices. The two rows cannot be accessed concurrently.
92 A double-sided stick has two chip-select rows which access different sets
93 of memory devices. The two rows cannot be accessed concurrently.
101 set has two chip-select rows and if double-sided sticks are used these
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| D | usb.txt | 5 - reg : the first two cells should contain usb registers location and
6 length, the next two two cells should contain PRAM location and
|
| /kernel/linux/linux-5.10/Documentation/driver-api/media/drivers/ |
| D | cpia2_devel.rst | 22 division of ST Microelectronics). There are two versions. The first is the
25 which can handle up to 30 fps VGA. Both coprocessors can be attached to two
29 The two chipsets operate almost identically. The core is an 8051 processor,
30 running two different versions of firmware. The 672 runs the VP4 video
32 mappings for the two chips. In these cases, the symbols defined in the
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | at91-kizbox2-2.dts | 4 * two head board
15 model = "Overkiz Kizbox 2 with two heads";
|
| /kernel/linux/linux-5.10/Documentation/gpu/ |
| D | komeda-kms.rst | 66 introduces Layer Split, which splits the whole image to two half parts and feeds
67 them to two Layers A and B, and does the scaling independently. After scaling
68 the result need to be fed to merger to merge two part images together, and then
74 compiz result to two parts and then feed them to two scalers.
80 adjusted to fit different usages. And D71 has two pipelines, which support two
84 Two pipelines work independently and separately to drive two display outputs.
306 capabilities, and a specific component includes two parts:
328 achieve this, split the komeda device into two layers: CORE and CHIP.
384 Layer_Split is quite complicated feature, which splits a big image into two
385 parts and handles it by two layers and two scalers individually. But it
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mtd/ |
| D | aspeed-smc.txt | 5 three chip selects, two of which are always of SPI type and the third
8 The two SPI flash memory controllers in the AST2500 each support two
|
| /kernel/linux/linux-5.10/Documentation/driver-api/iio/ |
| D | core.rst | 25 There are two ways for a user space application to interact with an IIO driver.
33 :doc:`SPI <../spi>` driver and will create two routines, probe and remove.
75 * a light sensor with two channels indicating the measurements in the visible
103 When there are multiple data channels per channel type we have two ways to
110 sensor can have two channels, one for infrared light and one for both
140 This channel's definition will generate two separate sysfs files for raw data
171 This will generate two separate attributes files for raw data retrieval:
|