| /linux/arch/arm/probes/kprobes/ |
| H 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()
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/tools/testing/selftests/seccomp/ |
| H A D | seccomp_benchmark.c | 86 double two = i_two, two_bump = two * 0.1; in approx() local
89 two_bump = two + MAX(two_bump, 2.0); in approx()
92 if (one == two || in approx()
93 (one > two && one <= two_bump) || in approx()
94 (two > one && two <= one_bump)) in approx()
107 unsigned long long one, bool (*eval)(int, int), unsigned long long two, in compare() argument
119 (long long)one, name_eval, (long long)two); in compare()
125 if (two > INT_MA in compare()
[all...] |
| /linux/lib/ |
| H A D | stackinit_kunit.c | 91 zero.two = 0; \
106 #define __static_partial { .two = 0, }
108 .two = 0, \
112 #define __dynamic_partial { .two = arg->two, }
114 .two = arg->two, \
118 #define __runtime_partial var.two = 0
120 var.two = 0; \
258 unsigned long two; member
266 char two; member
275 u8 two; member
[all …]
|
| H A 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/tools/testing/selftests/bpf/progs/ |
| H A D | test_sockmap_kern.h | 98 int *f, two = 2; in bpf_prog1() local
100 f = bpf_map_lookup_elem(&sock_skb_opts, &two); in bpf_prog1()
236 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local
249 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog4()
266 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
283 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog6()
352 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local
364 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog10()
|
| H A 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/arch/sh/boards/mach-r2d/ |
| H 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/tools/testing/selftests/splice/ |
| H 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/tools/testing/selftests/bpf/prog_tests/ |
| H A D | subprogs.c | 15 char two = '2'; in toggle_jit_harden() local
20 write(ctx->fd, &two, sizeof(two)); in toggle_jit_harden()
|
| /linux/Documentation/admin-guide/device-mapper/ |
| H 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/soc/fsl/cpm_qe/qe/ |
| H 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/arch/sh/lib/ |
| H A D | checksum.S | 54 add #-2, r5 ! Alignment uses up two bytes.
56 bt/s 1f ! Jump if we had at least two bytes.
178 add #-2,r6 ! Alignment uses up two bytes.
179 cmp/pz r6 ! Jump if we had at least two bytes.
224 ! src and dest equally aligned, but to a two byte boundary.
225 ! Handle first two bytes as a special case
|
| /linux/drivers/misc/lkdtm/ |
| H A 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/Documentation/gpu/ |
| H 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/tools/perf/Documentation/ |
| H A 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/Documentation/devicetree/bindings/sound/ |
| H A D | mvebu-audio.txt | 13 With "marvell,armada-380-audio" two other regions are required:
20 with "marvell,dove-audio", a list of two interrupts, the first for
23 - clocks: one or two phandles.
|
| H A 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
|
| H A D | mt6358.txt | 16 - mediatek,dmic-mode : Indicates how many data pins are used to transmit two
17 channels of PDM signal. 0 means two wires, 1 means one wire. Default
|
| /linux/Documentation/maintainer/ |
| H A D | messy-diffstat.rst | 25 If one wants to see what has changed between two points, a command like
30 Here, there are two clear points in the history; Git will essentially
43 the mainline branch (let's call it "linus") and cN, there are still two
55 two were then subsequently merged into c2. Now a pull request generated
59 What is happening here is that there are no longer two clear end points for
61 started in two different places; to generate the diffstat, ``git diff``
|
| /linux/Documentation/input/devices/ |
| H A D | elantech.rst | 53 per packet, and provides additional features such as position of two fingers,
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
485 Note that the two pairs of coordinates are not exactly the coordinates of the
486 two fingers, but only the pair of the lower-left and upper-right coordinates.
488 defined by these two points.
543 T: 1 = enable two finger mode auto correct
617 The packet format is exactly the same for two finger touch, except the hardware
618 sends two 6 byte packets. The first packet contains data for the first finger,
[all …]
|
| /linux/Documentation/driver-api/iio/ |
| H 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/arm/boot/dts/microchip/ |
| H A D | at91-kizbox2-2.dts | 4 * two head board
15 model = "Overkiz Kizbox 2 with two heads";
|
| /linux/Documentation/userspace-api/media/drivers/ |
| H A D | vgxy61.rst | 10 Change the sensor HDR mode. A HDR picture is obtained by merging two
11 captures of the same scene using two different exposure periods.
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | selections-common.rst | 10 similar, there's one fundamental difference between the two. On
16 on the two APIs.
|
| /linux/net/hsr/ |
| H A D | Kconfig | 15 needs (at least) two physical Ethernet interfaces.
24 For DANP, it must be connected as a node connecting to two
25 separate networks over the two slave interfaces. Like HSR, Ethernet
|