Home
last modified time | relevance | path

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

12345678910>>...63

/Linux-v4.19/arch/arm/probes/kprobes/
Dtest-arm.c1179 #define COPROCESSOR_INSTRUCTIONS_ST_LD(two,cc) \ in kprobe_arm_test_cases() argument
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, #-4]!") \ in kprobe_arm_test_cases()
1184 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #4") \ in kprobe_arm_test_cases()
1185 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], #-4") \ in kprobe_arm_test_cases()
1186 TEST_COPROCESSOR("stc"two" 0, cr0, [r13], {1}") \ in kprobe_arm_test_cases()
1187 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #4]") \ in kprobe_arm_test_cases()
1188 TEST_COPROCESSOR("stc"two"l 0, cr0, [r13, #-4]") \ in kprobe_arm_test_cases()
[all …]
/Linux-v4.19/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-v4.19/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-v4.19/Documentation/media/uapi/v4l/
Dpixfmt-nv12mt.rst10 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
Dpixfmt-nv16m.rst18 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,
Dselections-common.rst10 similar, there's one fundamental difference between the two. On
16 on the two APIs.
/Linux-v4.19/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-v4.19/Documentation/devicetree/bindings/mtd/
Dfsl-quadspi.txt18 - fsl,qspi-has-second-chip: The controller has two buses, bus A and bus B.
19 Each bus can be connected with two NOR flashes.
22 But if there are two NOR flashes connected to the
43 Example showing the usage of two SPI NOR devices:
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-v4.19/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
Dgpio-mvebu.txt24 for which two entries are expected: one for the general registers,
35 interrupt source. Should be two.
48 - #gpio-cells: Should be two. The first cell is the pin number. The
64 - #pwm-cells: Should be two. The first cell is the GPIO line number. The
Dgpio-clps711x.txt6 There should be two registers, first is DATA register, the second
9 - #gpio-cells: Should be two. The first cell is the pin number and
/Linux-v4.19/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-v4.19/Documentation/device-mapper/
Dunstriped.txt81 Intel NVMe drives contain two cores on the physical device.
84 in a 256k stripe across the two cores:
93 neighbor environments. When two partitions are created on the
96 are striped across the two cores. When we unstripe this hardware RAID 0
97 and make partitions on each new exposed device the two partitions are now
114 There will now be two devices that expose Intel NVMe core 0 and 1
/Linux-v4.19/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-v4.19/tools/memory-model/litmus-tests/
DREADME4 Test of read-read coherence, that is, whether or not two
18 Test of write-write coherence, that is, whether or not two
24 sufficient to cause two different reading processes to agree on
32 needed to cause two different reading processes to agree on the
53 of two variables then writes to the other?
57 litmus test, where each process reads from one of two variables then
96 but with two processes instead of three.)
132 These two are members of an extension of the MP litmus-test
/Linux-v4.19/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-v4.19/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-v4.19/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-v4.19/Documentation/devicetree/bindings/sound/
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-v4.19/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
43 "mediatek,mt2712-m4u" for mt2712 which uses generation two m4u HW.
44 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
/Linux-v4.19/Documentation/input/devices/
Delantech.rst53 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-v4.19/Documentation/ABI/testing/
Dsysfs-bus-iio-adc-max961115 These attributes describe a single physical component, exposed as two distinct
16 attributes as it is used to calculate two different values: power load and
/Linux-v4.19/Documentation/devicetree/bindings/net/wireless/
Dieee80211.txt11 An example case for this can be tri-band wireless router with two
12 identical chipsets used for two different 5 GHz subbands. Using them

12345678910>>...63