| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/seccomp/ |
| H A 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()
|
| /OK3568_Linux_fs/kernel/lib/ |
| H A 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 …]
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sound/ |
| H A 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
|
| /OK3568_Linux_fs/u-boot/doc/ |
| H A D | README.VSC3316-3308 | 10 … 8 input and 8 output ports. Programming of these devices are performed by two-wire or four-wire s… 15 First thing required is to program it to interface with either two-wire or four-wire interface. 16 … the interface is two-wire I2C serial interface. So the value in Interface mode register at addres… 23 …two-wire or four-wire interface. In our case the interface is two-wire I2C serial interface. So th…
|
| /OK3568_Linux_fs/yocto/meta-openembedded/meta-perl/recipes-perl/libalgorithm/ |
| H A D | libalgorithm-diff-perl_1.15.bb | 1 SUMMARY = "Algorithm::Diff - Compute 'intelligent' differences between two \ 3 DESCRIPTION = "This is a module for computing the difference between two files, \ 4 two strings, or any other two lists of things. It uses an intelligent \
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/bpf/progs/ |
| H A D | test_sockmap_kern.h | 97 int *f, two = 2; in bpf_prog1() local 99 f = bpf_map_lookup_elem(&sock_skb_opts, &two); in bpf_prog1() 237 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local 250 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog4() 267 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local 284 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog6() 348 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local 360 start_push = bpf_map_lookup_elem(&sock_bytes, &two); in bpf_prog10()
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A 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
|
| H A D | pixfmt-nv16m.rst | 18 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,
|
| /OK3568_Linux_fs/kernel/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.
|
| /OK3568_Linux_fs/kernel/drivers/misc/lkdtm/ |
| H A D | usercopy.c | 136 unsigned char *one, *two; in do_usercopy_heap_size() local 142 two = kmalloc(size, GFP_KERNEL); in do_usercopy_heap_size() 143 if (!one || !two) { in do_usercopy_heap_size() 157 memset(two, 'B', size); in do_usercopy_heap_size() 192 kfree(two); in do_usercopy_heap_size()
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/u-boot/doc/SPI/ |
| H A D | README.dual-flash | 9 hw logics(ex: xilinx zynq qspi) that describes two/dual memories are 29 line and these two memories are operating stacked fasion with shared buses. 46 - two memory flash devices should has same hw part attributes (like size, 59 line and these two memories are operating parallel with separate buses. 76 - two memory flash devices should has same hw part attributes (like size,
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/ |
| H A 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
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/memory-controllers/fsl/ |
| H A D | ifc.txt | 9 - #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
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/media/drivers/ |
| H A D | cpia2_devel.rst | 22 division of ST Microelectronics). There are two versions. The first is the 25 which can handle up to 30 fps VGA. Both coprocessors can be attached to two 29 The two chipsets operate almost identically. The core is an 8051 processor, 30 running two different versions of firmware. The 672 runs the VP4 video 32 mappings for the two chips. In these cases, the symbols defined in the
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/spi/ |
| H A D | spi-nxp-fspi.txt | 16 - reg : There are two buses (A and B) with two chip selects each. 23 Example showing the usage of two SPI NOR slave devices on bus A:
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/gpio/ |
| H A D | gpio_atmel.txt | 7 - #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
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/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 …]
|
| /OK3568_Linux_fs/kernel/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:
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/numeric/conversion/ |
| H A D | converter_policies.hpp | 111 S const two(2.0); in nearbyint() local 119 bool is_prev_even = two * floor(prev / two) == prev ; in nearbyint()
|
| /OK3568_Linux_fs/buildroot/dl/qt5location/git/src/3rdparty/mapbox-gl-native/deps/boost/1.65.1/include/boost/geometry/strategies/cartesian/ |
| H A D | buffer_end_round.hpp | 137 promoted_type const two = 2.0; in apply() local 138 promoted_type dist_half_diff = (dist_left - dist_right) / two; in apply() 148 generate_points(shifted_point, alpha, (dist_left + dist_right) / two, range_out); in apply()
|