| /linux-6.1.9/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" p0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1178 TEST_COPROCESSOR("stc"two" p0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
1179 TEST_COPROCESSOR("stc"two" p0, cr0, [r13, #4]!") \ in kprobe_arm_test_cases()
1180 TEST_COPROCESSOR("stc"two" p0, cr0, [r13, #-4]!") \ in kprobe_arm_test_cases()
1181 TEST_COPROCESSOR("stc"two" p0, cr0, [r13], #4") \ in kprobe_arm_test_cases()
1182 TEST_COPROCESSOR("stc"two" p0, cr0, [r13], #-4") \ in kprobe_arm_test_cases()
1183 TEST_COPROCESSOR("stc"two" p0, cr0, [r13], {1}") \ in kprobe_arm_test_cases()
1184 TEST_COPROCESSOR("stc"two"l p0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1185 TEST_COPROCESSOR("stc"two"l p0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
[all …]
|
| /linux-6.1.9/tools/testing/selftests/seccomp/ |
| D | seccomp_benchmark.c | 80 double two = i_two, two_bump = two * 0.01; in approx() local
83 two_bump = two + MAX(two_bump, 2.0); in approx()
86 if (one == two || in approx()
87 (one > two && one <= two_bump) || in approx()
88 (two > one && two <= one_bump)) in approx()
101 unsigned long long one, bool (*eval)(int, int), unsigned long long two) in compare() argument
106 (long long)one, name_eval, (long long)two); in compare()
111 if (two > INT_MAX) { in compare()
112 printf("Miscalculation! Measurement went negative: %lld\n", (long long)two); in compare()
116 good = eval(one, two); in compare()
|
| /linux-6.1.9/lib/ |
| D | stackinit_kunit.c | 82 zero.two = 0; \
97 #define __static_partial { .two = 0, }
99 .two = 0, \
103 #define __dynamic_partial { .two = arg->two, }
105 .two = arg->two, \
109 #define __runtime_partial var.two = 0
111 var.two = 0; \
244 unsigned long two; member
252 char two; member
261 u8 two; member
[all …]
|
| D | memcpy_kunit.c | 23 u16 two; member
40 #define compare(name, one, two) do { \ argument
41 BUILD_BUG_ON(sizeof(one) != sizeof(two)); \
43 KUNIT_EXPECT_EQ_MSG(test, one.data[i], two.data[i], \
45 __LINE__, #one, i, one.data[i], #two, i, two.data[i]); \
|
| /linux-6.1.9/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.yaml | 14 this M4U have two generations of HW architecture. Generation one uses flat
15 pagetable, and only supports 4K size page mapping. Generation two uses the
74 - mediatek,mt2712-m4u # generation two
75 - mediatek,mt6779-m4u # generation two
76 - mediatek,mt6795-m4u # generation two
77 - mediatek,mt8167-m4u # generation two
78 - mediatek,mt8173-m4u # generation two
79 - mediatek,mt8183-m4u # generation two
80 - mediatek,mt8186-iommu-mm # generation two
81 - mediatek,mt8192-m4u # generation two
[all …]
|
| /linux-6.1.9/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 | mt6359.yaml | 23 Indicates how many data pins are used to transmit two channels of PDM
24 signal. 0 means two wires, 1 means one wire. Default value is 0.
27 - 1 # two wires
|
| /linux-6.1.9/Documentation/devicetree/bindings/phy/ |
| D | fsl,imx8qm-lvds-phy.yaml | 14 It converts two groups of four 7/10 bits of CMOS data into two
19 through the two groups of LVDS data streams. Together with the
20 transmit clocks, the two groups of LVDS data streams form two
|
| /linux-6.1.9/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.
|
| /linux-6.1.9/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()
267 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
284 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog6()
348 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local
360 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog10()
|
| D | test_mmap.c | 30 int zero = 0, one = 1, two = 2, far = 1500; in test_mmap() local
36 bpf_map_update_elem(&data_map, &two, (const void *)&in_val, 0); in test_mmap()
|
| /linux-6.1.9/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
|
| /linux-6.1.9/tools/testing/selftests/bpf/prog_tests/ |
| D | subprogs.c | 15 char two = '2'; in toggle_jit_harden() local
20 write(ctx->fd, &two, sizeof(two)); in toggle_jit_harden()
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/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
|
| /linux-6.1.9/Documentation/devicetree/bindings/leds/backlight/ |
| D | lm3630a-backlight.yaml | 16 controls the current in up to two strings of 10 LEDs per string.
51 The control bank that is used to program the two current sinks. The
52 LM3630A has two control banks (A and B) and are represented as 0 or 1
53 in this property. The two current sinks can be controlled
|
| /linux-6.1.9/drivers/misc/lkdtm/ |
| D | usercopy.c | 137 unsigned char *one, *two; in do_usercopy_slab_size() local
143 two = kmalloc(size, GFP_KERNEL); in do_usercopy_slab_size()
144 if (!one || !two) { in do_usercopy_slab_size()
158 memset(two, 'B', size); in do_usercopy_slab_size()
195 kfree(two); in do_usercopy_slab_size()
|
| /linux-6.1.9/Documentation/devicetree/bindings/display/bridge/ |
| D | fsl,imx8qxp-ldb.yaml | 13 The Freescale i.MX8qm/qxp LVDS Display Bridge(LDB) has two channels.
20 format and can map the input to VESA or JEIDA standards. The two channels
22 them to use. Two LDB channels from two LDB instances can work together in
28 input color format. The two channels can be used simultaneously, either
29 in dual mode or split mode. In dual mode, the two channels output identical
|
| /linux-6.1.9/arch/arm/boot/dts/ |
| D | at91-kizbox2-2.dts | 4 * two head board
15 model = "Overkiz Kizbox 2 with two heads";
|
| /linux-6.1.9/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| D | fsl,ifc.yaml | 29 Should be either two or three. The first cell is the chipselect
35 Either one or two, depending on how large each chipselect can be.
44 IFC may have one or two interrupts. If two interrupt specifiers are
|
| /linux-6.1.9/tools/perf/Documentation/ |
| D | intel-hybrid.txt | 10 Kernel exports two new cpu pmus via sysfs:
49 Create two events for one hardware event automatically
52 two events are created automatically. One is for atom, the other is for
84 perf stat -e cycles -a (use system-wide in this example), two events
118 For perf-stat result, it displays two events:
137 As previous, two events are created.
173 it creates two default 'cycles' and adds them to event list. One
|
| /linux-6.1.9/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 …]
|