/linux-6.12.1/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 …]
|
/linux-6.12.1/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"
|
/linux-6.12.1/Documentation/devicetree/bindings/sound/ |
D | fsl,audmix.yaml | 14 The Audio Mixer is a on-chip functional module that allows mixing of two 15 audio streams into a single audio stream. Audio Mixer has two input serial 16 audio interfaces. These are driven by two Synchronous Audio interface 19 from two interfaces into a single sample. Before mixing, audio samples of 20 two inputs can be attenuated based on configuration. The output of the 31 Mixing operation is independent of audio sample rate but the two audio
|
/linux-6.12.1/lib/ |
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; \ 184 * possible between the two leaf function calls. \ 257 unsigned long two; member 265 char two; member [all …]
|
D | list_sort.c | 114 * This is compatible with two styles of @cmp function: 130 * 2:1 balanced merges. Given two pending sublists of size 2^k, they are 144 * for each bit, when count increments to 2^k), we merge two lists of 149 * so it's safe to merge away two lists of size 2^k. 151 * After this happens twice, we have created two lists of size 2^(k+1), 153 * a third list of size 2^(k+1), so there are never more than two pending. 156 * state of bit k of "count" plus two extra pieces of information: 202 * - Each of the sorted sublists is power-of-two in size. in list_sort() 204 * - There are zero to two sublists of each size. in list_sort() 210 * - Merging the two sublists selected by the highest bit in list_sort()
|
/linux-6.12.1/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()
|
/linux-6.12.1/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 : 2nd 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
|
/linux-6.12.1/tools/testing/selftests/seccomp/ |
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_MAX) { in compare() 126 ksft_print_msg("Miscalculation! Measurement went negative: %lld\n", (long long)two); in compare() 131 good = eval(one, two); in compare()
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/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 …]
|
/linux-6.12.1/tools/testing/selftests/exec/ |
D | binfmt_script.py | 146 # Two bytes under size, leaving newline visible. 147 test(name="two-under", size=SIZE-2) 165 test(name="two-under-no-nl", size=SIZE-2, newline="") 166 test(name="two-under-trunc-arg", size=SIZE-2, arg=" ") 167 test(name="two-under-leading", size=SIZE-2, leading=" ") 168 test(name="two-under-leading-trunc-arg", size=SIZE-2, leading=" ", arg=" ") 170 test(name="two-under-no-nl", size=int(SIZE/2), newline="") 171 test(name="two-under-trunc-arg", size=int(SIZE/2), arg=" ") 172 test(name="two-under-leading", size=int(SIZE/2), leading=" ") 173 test(name="two-under-lead-trunc-arg", size=int(SIZE/2), leading=" ", arg=" ")
|
/linux-6.12.1/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 …]
|
D | alps.rst | 66 PSMOUSE_CMD_GETINFO (E9). The first two bytes of the response contains the 75 alps_identify function. For example, there seem to be two hardware init 157 ALPS protocol version 3 has three different packet formats. The first two are 187 usually only appears when there are two or more contacts (although 216 The last two bytes represent a partial bitmap packet, with 3 full packets 309 byte 0: TWO & MULTI L 1 R M 1 Y0-2 Y0-1 Y0-0 314 byte 4: TWO X1-10 TWO X1-9 X1-8 X1-7 X1-6 X1-5 X1-4 315 byte 4: MULTI X1-10 TWO X1-9 X1-8 X1-7 X1-6 Y1-5 1 316 byte 4: NEW X1-10 TWO X1-9 X1-8 X1-7 X1-6 0 0 317 byte 5: TWO & NEW Y1-10 0 Y1-9 Y1-8 Y1-7 Y1-6 Y1-5 Y1-4 [all …]
|
/linux-6.12.1/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
|
/linux-6.12.1/tools/include/linux/ |
D | log2.h | 33 * Determine whether some value is a power of two, where zero is 34 * *not* considered a power of two. 44 * round up to nearest power of two 53 * round down to nearest power of two 144 * roundup_pow_of_two - round the given value up to nearest power of two 147 * round the given value up to the nearest power of two 161 * rounddown_pow_of_two - round the given value down to nearest power of two 164 * round the given value down to the nearest power of two
|
/linux-6.12.1/Documentation/devicetree/bindings/display/bridge/ |
D | fsl,imx8qxp-ldb.yaml | 13 The Freescale i.MX8qm/qxp LVDS Display Bridge(LDB) has two channels. 20 format and can map the input to VESA or JEIDA standards. The two channels 22 them to use. Two LDB channels from two LDB instances can work together in 28 input color format. The two channels can be used simultaneously, either 29 in dual mode or split mode. In dual mode, the two channels output identical
|
/linux-6.12.1/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
|
/linux-6.12.1/tools/lib/ |
D | list_sort.c | 103 * This is compatible with two styles of @cmp function: 119 * 2:1 balanced merges. Given two pending sublists of size 2^k, they are 133 * for each bit, when count increments to 2^k), we merge two lists of 138 * so it's safe to merge away two lists of size 2^k. 140 * After this happens twice, we have created two lists of size 2^(k+1), 142 * a third list of size 2^(k+1), so there are never more than two pending. 145 * state of bit k of "count" plus two extra pieces of information: 191 * - Each of the sorted sublists is power-of-two in size. in list_sort() 193 * - There are zero to two sublists of each size. in list_sort() 199 * - Merging the two sublists selected by the highest bit in list_sort()
|
/linux-6.12.1/include/uapi/linux/netfilter_bridge/ |
D | ebt_802_3.h | 20 * Control field may be one or two bytes. If the first byte has 21 * the value 0x03 then the entire length is one byte, otherwise it is two. 23 * Two byte controls are used in Numbered Information frames. 29 /* ui has one byte ctrl, ni has two */
|
/linux-6.12.1/include/kunit/ |
D | assert.h | 127 * struct kunit_binary_assert - An expectation/assertion that compares two 134 * Represents an expectation/assertion that compares two non-pointer values. For 150 * struct kunit_binary_ptr_assert - An expectation/assertion that compares two 157 * Represents an expectation/assertion that compares two pointer values. For 173 * struct kunit_binary_str_assert - An expectation/assertion that compares two 180 * Represents an expectation/assertion that compares two string values. For 196 * struct kunit_mem_assert - An expectation/assertion that compares two 204 * Represents an expectation/assertion that compares two memory blocks. For
|
/linux-6.12.1/include/linux/ |
D | log2.h | 37 * is_power_of_2() - check if a value is a power of two 40 * Determine whether some value is a power of two, where zero is 41 * *not* considered a power of two. 51 * __roundup_pow_of_two() - round up to nearest power of two 61 * __rounddown_pow_of_two() - round down to nearest power of two 167 * roundup_pow_of_two - round the given value up to nearest power of two 170 * round the given value up to the nearest power of two 184 * rounddown_pow_of_two - round the given value down to nearest power of two 187 * round the given value down to the nearest power of two
|
/linux-6.12.1/drivers/video/fbdev/ |
D | bt431.h | 17 * Two twin Bt431 are used on the DECstation's PMAG-AA. 79 * The compiler splits the write in two bytes without these in bt431_select_reg() 95 * The compiler splits the write in two bytes without the in bt431_read_reg_inc() 107 * The compiler splits the write in two bytes without the in bt431_write_reg_inc() 132 * The compiler splits the write in two bytes without the in bt431_read_cmap_inc() 144 * The compiler splits the write in two bytes without the in bt431_write_cmap_inc() 188 * V = scanlines between HSYNCH falling, two or more in bt431_position_cursor()
|
/linux-6.12.1/include/media/i2c/ |
D | upd64083.h | 11 /* There are two bits of information that the driver needs in order 15 The first two operating modes expect a composite signal on the Y input, 16 the second two operating modes use both the Y and C inputs. 33 /* Note: the following two modes cannot be used in combination with the
|
/linux-6.12.1/Documentation/maintainer/ |
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``
|