| /kernel/linux/linux-6.6/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,mt8188-iommu-vdo # generation two
[all …]
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-6.6/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
|
| /kernel/linux/linux-5.10/tools/testing/selftests/net/forwarding/ |
| D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| /kernel/linux/linux-6.6/tools/testing/selftests/net/forwarding/ |
| D | tc_vlan_modify.sh | 108 check_fail $? "ping between two different vlans passed when should not"
111 check_fail $? "ping6 between two different vlans passed when should not"
119 check_err $? "ping between two different vlans failed when should not"
122 check_err $? "ping6 between two different vlans failed when should not"
135 check_fail $? "ping between two different vlans passed when should not"
138 check_fail $? "ping6 between two different vlans passed when should not"
146 check_err $? "ping between two different vlans failed when should not"
149 check_err $? "ping6 between two different vlans failed when should not"
|
| /kernel/linux/linux-6.6/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()
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/lib/ |
| D | test_stackinit.c | 69 #define INIT_STRUCT_static_partial = { .two = 0, }
71 .two = 0, \
75 #define INIT_STRUCT_dynamic_partial = { .two = arg->two, }
77 .two = arg->two, \
82 var.two = 0
85 var.two = 0; \
198 unsigned long two; member
206 char two; member
215 u8 two; member
223 char *two; member
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/phy/ |
| D | apm-xgene-phy.txt | 19 Two set of 3-tuple setting for each (up to 3)
25 Two set of 3-tuple setting for each (up to 3)
28 gain control. Two set of 3-tuple setting for each
31 - apm,tx-amplitude : Amplitude control. Two set of 3-tuple setting for
35 - apm,tx-pre-cursor1 : 1st pre-cursor emphasis taps control. Two set of
39 - apm,tx-pre-cursor2 : 2st pre-cursor emphasis taps control. Two set of
43 - apm,tx-post-cursor : Post-cursor emphasis taps control. Two set of
|
| 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
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/phy/ |
| D | apm-xgene-phy.txt | 19 Two set of 3-tuple setting for each (up to 3)
25 Two set of 3-tuple setting for each (up to 3)
28 gain control. Two set of 3-tuple setting for each
31 - apm,tx-amplitude : Amplitude control. Two set of 3-tuple setting for
35 - apm,tx-pre-cursor1 : 1st pre-cursor emphasis taps control. Two set of
39 - apm,tx-pre-cursor2 : 2st pre-cursor emphasis taps control. Two set of
43 - apm,tx-post-cursor : Post-cursor emphasis taps control. Two set of
|
| /kernel/linux/linux-6.6/drivers/iio/chemical/ |
| D | sps30_i2c.c | 45 * sending two i2c messages in a row we just send one by one. in sps30_i2c_xfer()
71 * PM1: upper two bytes, crc8, lower two bytes, crc8 in sps30_i2c_command()
72 * PM2P5: upper two bytes, crc8, lower two bytes, crc8 in sps30_i2c_command()
73 * PM4: upper two bytes, crc8, lower two bytes, crc8 in sps30_i2c_command()
74 * PM10: upper two bytes, crc8, lower two bytes, crc8 in sps30_i2c_command()
89 /* each two bytes are followed by a crc8 */ in sps30_i2c_command()
|
| /kernel/linux/linux-6.6/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; \
245 unsigned long two; member
253 char two; member
262 u8 two; member
[all …]
|
| /kernel/linux/linux-6.6/tools/testing/selftests/exec/ |
| D | binfmt_script.py | 140 # Two bytes under size, leaving newline visible.
141 test(name="two-under", size=SIZE-2)
159 test(name="two-under-no-nl", size=SIZE-2, newline="")
160 test(name="two-under-trunc-arg", size=SIZE-2, arg=" ")
161 test(name="two-under-leading", size=SIZE-2, leading=" ")
162 test(name="two-under-leading-trunc-arg", size=SIZE-2, leading=" ", arg=" ")
164 test(name="two-under-no-nl", size=int(SIZE/2), newline="")
165 test(name="two-under-trunc-arg", size=int(SIZE/2), arg=" ")
166 test(name="two-under-leading", size=int(SIZE/2), leading=" ")
167 test(name="two-under-lead-trunc-arg", size=int(SIZE/2), leading=" ", arg=" ")
|
| /kernel/linux/linux-5.10/tools/testing/selftests/exec/ |
| D | binfmt_script | 140 # Two bytes under size, leaving newline visible.
141 test(name="two-under", size=SIZE-2)
159 test(name="two-under-no-nl", size=SIZE-2, newline="")
160 test(name="two-under-trunc-arg", size=SIZE-2, arg=" ")
161 test(name="two-under-leading", size=SIZE-2, leading=" ")
162 test(name="two-under-leading-trunc-arg", size=SIZE-2, leading=" ", arg=" ")
164 test(name="two-under-no-nl", size=int(SIZE/2), newline="")
165 test(name="two-under-trunc-arg", size=int(SIZE/2), arg=" ")
166 test(name="two-under-leading", size=int(SIZE/2), leading=" ")
167 test(name="two-under-lead-trunc-arg", size=int(SIZE/2), leading=" ", arg=" ")
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iommu/ |
| D | mediatek,iommu.txt | 4 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.
61 "mediatek,mt6779-m4u" for mt6779 which uses generation two m4u HW.
64 "mediatek,mt8167-m4u" for mt8167 which uses generation two m4u HW.
65 "mediatek,mt8173-m4u" for mt8173 which uses generation two m4u HW.
66 "mediatek,mt8183-m4u" for mt8183 which uses generation two m4u HW.
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | pixfmt-nv12mt.rst | 10 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
|
| /kernel/linux/linux-6.6/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.
87 Two pipelines work together to drive only one display output.
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
[all …]
|
| /kernel/linux/linux-5.10/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.
87 Two pipelines work together to drive only one display output.
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
[all …]
|
| /kernel/linux/linux-5.10/net/l2tp/ |
| D | Kconfig | 3 # Layer Two Tunneling Protocol (L2TP)
7 tristate "Layer Two Tunneling Protocol (L2TP)"
12 Layer Two Tunneling Protocol
54 Layer Two Tunneling Protocol Version 3
58 The Layer Two Tunneling Protocol (L2TP) provides a dynamic
77 The L2TPv3 protocol defines two possible encapsulations for
|
| /kernel/linux/linux-6.6/net/l2tp/ |
| D | Kconfig | 3 # Layer Two Tunneling Protocol (L2TP)
7 tristate "Layer Two Tunneling Protocol (L2TP)"
12 Layer Two Tunneling Protocol
54 Layer Two Tunneling Protocol Version 3
58 The Layer Two Tunneling Protocol (L2TP) provides a dynamic
77 The L2TPv3 protocol defines two possible encapsulations for
|
| /kernel/linux/linux-5.10/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" 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 …]
|
| /kernel/linux/linux-6.6/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 …]
|
| /kernel/linux/linux-5.10/Documentation/input/devices/ |
| D | elantech.rst | 27 5.2.3 Two finger touch
32 6.2.2 Two finger touch
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
482 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.
[all …]
|
| /kernel/linux/linux-6.6/Documentation/input/devices/ |
| D | elantech.rst | 27 5.2.3 Two finger touch
32 6.2.2 Two finger touch
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
482 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.
[all …]
|