Home
last modified time | relevance | path

Searched full:three (Results 1 – 25 of 3912) sorted by relevance

12345678910>>...157

/OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/
H A Dcolorspaces.rst10 biology. Just because you have three numbers that describe the 'red',
20 the human eye has color receptors that are sensitive to three different
21 wavelengths of light. Hence the need to use three numbers to describe
33 Since the human eye has only three color receptors it is perfectly
67 A monitor or TV will reproduce colors by emitting light at three
78 to define the three color primaries (these are typically defined as x, y
80 reference: that is the color obtained when all three primaries are at
86 Other colorspaces are defined by three chromaticity coordinates defined
144 The colorspace definition itself consists of the three chromaticity
/OK3568_Linux_fs/kernel/mm/damon/
H A Dvaddr-test.h50 * complex and dynamic memory mappings of each target task to three
51 * discontiguous regions which cover every mapped areas. However, the three
61 * three regions and returns. For more detail, refer to the comment of
67 * mapped. To cover every mappings, the three regions should start with 10,
68 * and end with 305. The process also has three unmapped areas, 25-200,
70 * unmapped areas, and thus it should be converted to three regions of 10-25,
118 * three_regions The three regions that need to be applied now
125 * three regions, and updates the monitoring target regions to fit in the three
129 * This test passes the given target regions and the new three regions that
158 * This function test most common case where the three big regions are only
[all …]
H A Dvaddr.c104 * Find three regions separated by two biggest unmapped regions
107 * regions an array of three address ranges that results will be saved
109 * This function receives an address space and finds three regions in it which
168 * Get the three regions in the given target (task)
207 * For the reason, we convert the complex mappings to three distinct regions
209 * between the three regions are the two biggest unmapped areas in the given
212 * Then, it constructs the three regions as below:
247 pr_debug("Failed to get three regions of %dth target\n", tidx); in __damon_va_init_regions()
258 /* Set the initial three regions of the target */ in __damon_va_init_regions()
300 * Update damon regions for the three big regions of the given target
[all …]
/OK3568_Linux_fs/kernel/drivers/scsi/isci/
H A Dremote_node_table.h65 * SCU hardware requires that STP remote node entries take three consecutive
66 * remote node index so the table is arranged in sets of three. The bits are
67 * used as 0111 0111 to make a byte and the bits define the set of three remote
151 * the remote nodes must occupy three consecutive remote node context
153 * sets of three into a single nibble. When the STP RNi is allocated all
162 * This field is the nibble selector for the above table. There are three
164 * three remote node entries.
/OK3568_Linux_fs/kernel/Documentation/scheduler/
H A Dsched-stats.rst22 are no architectures which need more than three domain levels. The first
45 Next three are schedule() statistics:
57 Next three are statistics describing scheduling latency:
126 Next three are active_load_balance() statistics:
132 Next three are sched_balance_exec() statistics:
138 Next three are sched_balance_fork() statistics:
144 Next three are try_to_wake_up() statistics:
155 the same information on a per-process level. There are three fields in
/OK3568_Linux_fs/kernel/arch/powerpc/include/asm/nohash/32/
H A Dpte-44x.h45 * - PRESENT *must* be in the bottom three bits because swap cache
62 * 3-24th LSB are shared with swp_entry, however the 0-2nd three LSB still
63 * hold protection values. That means the three protection bits are
64 * reserved for both PTE and SWAP entry at the most significant three
67 * There are three protection bits available for SWAP entry:
71 * So those three bits have to be inside of 0-2nd LSB of PTE.
/OK3568_Linux_fs/kernel/lib/
H A Dtest_stackinit.c72 .three = 0, \
78 .three = arg->three, \
86 var.three = 0; \
199 unsigned long three; member
208 int three; member
216 u8 three; member
224 char *three; member
233 char __user *three; member
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/mux/
H A Dadi,adg792a.txt5 - #mux-control-cells : <0> if parallel (the three muxes are bound together
6 with a single mux controller controlling all three muxes), or <1> if
27 * Three independent mux controllers (of which one is used).
53 * Three parallel muxes with one mux controller, useful e.g. if
/OK3568_Linux_fs/kernel/Documentation/hwmon/
H A Demc1403.rst57 (one internal, one external). EMC14x3 support three sensors (one internal,
58 two external), and EMC14x4 support four sensors (one internal, three
61 The chips implement three limits for each sensor: low (tempX_min), high
66 all three limits.
H A Dlm85.rst93 specification. Using an analog to digital converter it measures three (3)
96 VID signals from the processor to the VRM. Lastly, there are three (3) PWM
112 three temperature sensors. Each PWM output is individually adjustable and
212 Each temperature sensor is associated with a Zone. There are three
213 sensors and therefore three zones (# 1, 2 and 3). Each zone has the following
228 There are three PWM outputs. The LM85 datasheet suggests that the
H A Dlm78.rst37 There is almost no difference between the three supported chips. Functionally,
40 From here on, LM7* means either of these three types.
42 The LM7* implements one temperature sensor, three fan rotation speed sensors,
/OK3568_Linux_fs/kernel/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr3/
H A Dia_css_tnr3_types.h32 * 1. Three piecewise linear graphs (one for each plane) with three segments
34 * each plane on the y axis. The three linear segments may have a different
36 * a "Knee" point. As there are three such segments, four points need to be
/OK3568_Linux_fs/kernel/Documentation/ABI/testing/
H A Dsysfs-class-backlight-adp55204 The backlight brightness control operates at three different levels for the
16 is at one of the three levels (daylight, office or dark). This
29 one of the three levels (daylight, office or dark). This is an
H A Dsysfs-class-backlight-adp88604 The backlight brightness control operates at three different levels for the
21 is at one of the three levels (daylight, office or dark). This
35 one of the three levels (daylight, office or dark). This is an
/OK3568_Linux_fs/kernel/tools/testing/selftests/rcutorture/doc/
H A DTREE_RCU-kconfig.txt7 CONFIG_DEBUG_LOCK_ALLOC -- Do three, covering CONFIG_PROVE_LOCKING & not.
12 CONFIG_PREEMPT -- Do half. (First three and #8.)
19 CONFIG_RCU_NOCB_CPU -- Do three, one with no rcu_nocbs CPUs, one with
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/share/i18n/charmaps/
H A DISO_8859-1,GL.gz ... ONE 86<two> \d050 DIGIT TWO 87<three> \d051 DIGIT THREE 88<four> \d052 DIGIT ...
/OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/share/i18n/charmaps/
H A DISO_8859-1,GL.gz ... ONE 86<two> \d050 DIGIT TWO 87<three> \d051 DIGIT THREE 88<four> \d052 DIGIT ...
HDINIS-8.gz ... DC2) 28<U0013> /x13 DEVICE CONTROL THREE (DC3) 29<U0014> /x14 DEVICE ...
/OK3568_Linux_fs/kernel/arch/x86/include/uapi/asm/
H A De820.h13 * nodes, based on up to three entries per node for which the
18 * of three memory map entries per node is "enough" entries for
21 * to allow more than three entries per node or otherwise refine
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/interrupt-controller/
H A Driscv,cpu-intc.txt10 The RISC-V supervisor ISA manual specifies three interrupt sources that are
19 required to have a HLIC with these three interrupt sources present. Since the
29 RISC-V supervisor ISA manual, with only the following three interrupts being
/OK3568_Linux_fs/u-boot/arch/powerpc/cpu/mpc85xx/
H A Dfsl_corenet_serdes.c120 * For banks two and three, use the srds_lpd_b[] array instead of the in serdes_lane_enabled()
538 * Display a warning if banks two and three are not disabled in the RCW, in fsl_serdes_init()
545 "three to be disabled in the RCW\n"); in fsl_serdes_init()
615 * Bank two uses the clock from bank three, so if bank two is enabled, in fsl_serdes_init()
616 * then bank three must also be enabled. in fsl_serdes_init()
625 * is disabled and bank three is enabled. The converse is also true, in fsl_serdes_init()
641 * down after bank three is powered up, so don't power in fsl_serdes_init()
845 * Re-enable devices on banks two and three that were in fsl_serdes_init()
846 * disabled by the RCW, and then enable bank three. The in fsl_serdes_init()
853 /* Enable bank two now that bank three is enabled. */ in fsl_serdes_init()
/OK3568_Linux_fs/kernel/drivers/media/platform/davinci/
H A DKconfig47 be three modules called vpfe_capture.ko, vpss.ko and dm644x_ccdc.ko
63 be three modules called vpfe_capture.ko, vpss.ko and dm355_ccdc.ko
77 be three modules called vpfe_capture.ko, vpss.ko and isif.ko
/OK3568_Linux_fs/kernel/arch/sparc/include/asm/
H A Dbackoff.h24 * On all cpus prior to SPARC-T4 we do three dummy reads of the
38 * To achieve the same amount of backoff as the three %ccr reads give
39 * on earlier chips, we shift the backoff value up by 7 bits. (Three
/OK3568_Linux_fs/kernel/tools/testing/selftests/bpf/progs/
H A Dtest_sockmap_kern.h237 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local
251 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog4()
267 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local
285 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog6()
348 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local
361 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog10()
/OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/i2c/
H A Di2c-pxa-pci-ce4100.txt5 PCI device has three PCI-bars, each bar contains a complete I2C
6 controller. So we have a total of three independent I2C-Controllers
43 * three is the bar number followed by the 64bit bar address

12345678910>>...157