Home
last modified time | relevance | path

Searched refs:two (Results 1 – 25 of 1807) sorted by relevance

12345678910>>...73

/Linux-v5.4/arch/arm/probes/kprobes/
Dtest-arm.c1176 #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 …]
/Linux-v5.4/lib/
Dtest_stackinit.c69 #define INIT_STRUCT_static_partial = { .two = 0, }
71 .two = arg->two, \
75 #define INIT_STRUCT_dynamic_partial = { .two = arg->two, }
77 .two = arg->two, \
82 var.two = 0
85 var.two = 0; \
197 unsigned long two; member
205 char two; member
219 u8 two; member
227 char *two; member
[all …]
/Linux-v5.4/drivers/net/ethernet/mellanox/mlx5/core/steering/
Ddr_crc32.c68 u32 crc = 0, one, two; in mlx5dr_crc32_slice8_calc() local
76 two = *curr++; in mlx5dr_crc32_slice8_calc()
78 crc = dr_ste_crc_tab32[0][(two >> 24) & 0xff] in mlx5dr_crc32_slice8_calc()
79 ^ dr_ste_crc_tab32[1][(two >> 16) & 0xff] in mlx5dr_crc32_slice8_calc()
80 ^ dr_ste_crc_tab32[2][(two >> 8) & 0xff] in mlx5dr_crc32_slice8_calc()
81 ^ dr_ste_crc_tab32[3][two & 0xff] in mlx5dr_crc32_slice8_calc()
/Linux-v5.4/Documentation/devicetree/bindings/sound/
Dfsl,audmix.txt3 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
Dcs35l32.txt20 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
/Linux-v5.4/Documentation/driver-api/
Ddevice_connection.rst16 two separate devices.
18 Device connections alone do not create a dependency between the two devices.
20 A dependency between the two devices exists only if one of the two endpoint
32 The connection description consists of the names of the two devices with the
34 is needed if there are multiple connections between the two devices.
Dedac.rst44 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-v5.4/arch/sh/boards/mach-r2d/
DKconfig11 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-v5.4/tools/testing/selftests/bpf/
Dtest_sockmap_kern.h177 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local
190 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog4()
204 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog5() local
232 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog5()
270 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
286 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog6()
312 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog7() local
340 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog7()
426 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog10() local
438 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog10()
/Linux-v5.4/Documentation/media/uapi/v4l/
Dpixfmt-nv12mt.rst17 has two planes - one for luminance and one for chrominance. Chroma
26 This is the two-plane versions of the YUV 4:2:0 format where data is
28 two sub-images or planes. The Y plane has one byte per pixel and pixels
34 alignment is 32. Every four adjacent buffers - two horizontally and two
Dpixfmt-nv16m.rst25 This is a multi-planar, two-plane version of the YUV 4:2:2 format. The
26 three components are separated into two sub-images or planes.
28 two planes are non-contiguous in memory, i.e. the chroma plane does not
33 Each CbCr pair belongs to two pixels. For example,
/Linux-v5.4/drivers/misc/lkdtm/
Dusercopy.c125 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()
/Linux-v5.4/Documentation/devicetree/bindings/spi/
Dspi-nxp-fspi.txt13 - reg : There are two buses (A and B) with two chip selects each.
20 Example showing the usage of two SPI NOR slave devices on bus A:
Dspi-fsl-qspi.txt17 - 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:
/Linux-v5.4/Documentation/devicetree/bindings/gpio/
Dgpio_atmel.txt7 - #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-v5.4/Documentation/devicetree/bindings/memory-controllers/fsl/
Difc.txt9 - #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-v5.4/Documentation/admin-guide/device-mapper/
Dunstriped.rst85 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-v5.4/Documentation/devicetree/bindings/soc/fsl/cpm_qe/qe/
Dusb.txt5 - reg : the first two cells should contain usb registers location and
6 length, the next two two cells should contain PRAM location and
/Linux-v5.4/Documentation/gpu/
Dkomeda-kms.rst66 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-v5.4/Documentation/devicetree/bindings/timer/
Dsamsung,exynos4210-mct.txt3 The Samsung's Multi Core Timer (MCT) module includes two main blocks, the
39 Example 1: In this example, the IP contains two local timers, using separate
40 interrupts, so two local timer interrupts have been specified,
50 Example 2: In this example, the timer interrupts are connected to two separate
/Linux-v5.4/Documentation/devicetree/bindings/mtd/
Daspeed-smc.txt5 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
/Linux-v5.4/Documentation/devicetree/bindings/iommu/
Dmediatek,iommu.txt4 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.
63 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
64 "mediatek,mt8183-m4u" for mt8183 which uses generation two m4u HW.
/Linux-v5.4/Documentation/devicetree/bindings/dma/xilinx/
Dxilinx_dma.txt2 It can be configured to have one channel or two channels. If configured
3 as two channels, one is to transmit to the video device and another is
7 target devices. It can be configured to have one channel or two channels.
8 If configured as two channels, one is to transmit to the device and another
22 two channels per device. This node specifies the properties of each
/Linux-v5.4/Documentation/driver-api/iio/
Dcore.rst25 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-v5.4/drivers/thermal/intel/
DKconfig20 two trip points which can be set by user to get notifications via thermal
40 temperature sensor (DTS). These SoCs have two additional DTSs in
42 thermal zone. There are two trip points. One of the trip point can
53 The DTS will be registered as a thermal zone. There are two trip points:

12345678910>>...73