| /linux/arch/arm/probes/kprobes/ |
| A 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()
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()
1191 TEST_COPROCESSOR("ldc"two" p0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1195 TEST_COPROCESSOR("ldc"two" p0, cr0, [r13], #4") \ in kprobe_arm_test_cases()
1233 TEST_COPROCESSOR( "ldc"two"l p0, cr0, [r15], {1}") in kprobe_arm_test_cases()
[all …]
|
| /linux/tools/testing/selftests/seccomp/ |
| A 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/lib/ |
| A D | test_stackinit.c | 137 zero.two = 0; \
154 .two = 0, \
158 #define __dynamic_partial { .two = arg->two, }
160 .two = arg->two, \
164 #define __runtime_partial var.two = 0
166 var.two = 0; \
305 unsigned long two; member
313 char two; member
322 u8 two; member
330 char *two; member
[all …]
|
| A D | memcpy_kunit.c | 23 u16 two; member
41 #define compare(name, one, two) do { \ argument
43 BUILD_BUG_ON(sizeof(one) != sizeof(two)); \
45 KUNIT_EXPECT_EQ_MSG(test, one.data[i], two.data[i], \
47 __LINE__, #one, i, one.data[i], #two, i, two.data[i]); \
|
| /linux/Documentation/devicetree/bindings/sound/ |
| A 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
|
| A 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/Documentation/devicetree/bindings/iommu/ |
| A 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,mt8167-m4u # generation two
77 - mediatek,mt8173-m4u # generation two
78 - mediatek,mt8183-m4u # generation two
79 - mediatek,mt8192-m4u # generation two
|
| /linux/tools/testing/selftests/bpf/progs/ |
| A 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()
|
| /linux/arch/sh/boards/mach-r2d/ |
| A 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/drivers/misc/lkdtm/ |
| A 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()
183 kfree(two); in do_usercopy_heap_size()
|
| /linux/tools/testing/selftests/splice/ |
| A D | short_splice_read.sh | 100 two=$(echo "$full" | grep -m1 . | cut -c-2)
110 if ! do_splice "$filename" 2 "$two" "'$two'" ; then
|
| /linux/Documentation/driver-api/ |
| A 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/Documentation/admin-guide/device-mapper/ |
| A 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/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| A 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
|
| /linux/Documentation/driver-api/media/drivers/ |
| A 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/Documentation/devicetree/bindings/gpio/ |
| A 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
|
| A D | gpio-mvebu.txt | 22 for which two entries are expected: one for the general registers,
33 interrupt source. Should be two.
46 - #gpio-cells: Should be two. The first cell is the pin number. The
62 - #pwm-cells: Should be two. The first cell is the GPIO line number. The
|
| /linux/Documentation/gpu/ |
| A 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 …]
|
| /linux/Documentation/devicetree/bindings/leds/backlight/ |
| A 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/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/ |
| A 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/tools/perf/Documentation/ |
| A D | intel-hybrid.txt | 10 Kernel exports two new cpu pmus via sysfs:
55 Create two events for one hardware event automatically
59 two events are created automatically. One is for atom, the other is for
91 perf stat -e cycles -a (use system-wide in this example), two events
125 For perf-stat result, it displays two events:
145 As previous, two events are created.
182 it creates two default 'cycles' and adds them to event list. One
|
| /linux/Documentation/input/devices/ |
| A D | elantech.rst | 55 for 2 fingers the concatenation of two 6 bytes packets) and allows tracking
282 firmware 1.x seem to map one, two and three finger taps
331 tw = 1 when two finger touch
488 defined by these two points.
543 T: 1 = enable two finger mode auto correct
646 two fingers' position delta.
757 x7..x0 = delta x (two's complement)
764 y7..y0 = delta y (two's complement)
778 x7..x0 = delta x (two's complement)
785 y7..y0 = delta y (two's complement)
[all …]
|
| /linux/Documentation/driver-api/iio/ |
| A 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:
|
| /linux/arch/sh/lib/ |
| A D | checksum.S | 73 add #-2, r5 ! Alignment uses up two bytes.
75 bt/s 1f ! Jump if we had at least two bytes.
209 add #-2,r6 ! Alignment uses up two bytes.
210 cmp/pz r6 ! Jump if we had at least two bytes.
255 ! src and dest equally aligned, but to a two byte boundary.
256 ! Handle first two bytes as a special case
|
| /linux/Documentation/devicetree/bindings/mtd/ |
| A 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
|