three (full) in projects: Linux-v6.1 - OpenGrok search results

Project(s)

Full Search
Definition
Symbol
File Path
History
Type

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

12 3 4 5 6 7 8 9 10 >>...79

/Linux-v6.1/Documentation/userspace-api/media/v4l/
D	colorspaces.rst	10 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
/Linux-v6.1/mm/damon/
D	vaddr-test.h	36 * complex and dynamic memory mappings of each target task to three 37 * discontiguous regions which cover every mapped areas. However, the three 47 * three regions and returns. For more detail, refer to the comment of 53 * mapped. To cover every mappings, the three regions should start with 10, 54 * and end with 305. The process also has three unmapped areas, 25-200, 56 * unmapped areas, and thus it should be converted to three regions of 10-25, 106 * three_regions The three regions that need to be applied now 113 * three regions, and updates the monitoring target regions to fit in the three 117 * This test passes the given target regions and the new three regions that 146 * This function test most common case where the three big regions are only [all …]
D	vaddr.c	104 * 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 169 * Get the three regions in the given target (task) 208 * For the reason, we convert the complex mappings to three distinct regions 210 * between the three regions are the two biggest unmapped areas in the given 213 * Then, it constructs the three regions as below: 248 pr_debug("Failed to get three regions of %dth target\n", tidx); in __damon_va_init_regions() 259 /* Set the initial three regions of the target */ in __damon_va_init_regions()
/Linux-v6.1/drivers/scsi/isci/
D	remote_node_table.h	`65 * 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.`
/Linux-v6.1/Documentation/scheduler/
D	sched-stats.rst	`22 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`
/Linux-v6.1/arch/powerpc/include/asm/nohash/32/
D	pte-44x.h	`45 * - 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.`
/Linux-v6.1/Documentation/devicetree/bindings/mux/
D	adi,adg792a.txt	`5 - #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`
/Linux-v6.1/Documentation/hwmon/
D	emc1403.rst	`57 (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.`
D	lm78.rst	`37 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,`
D	lm85.rst	`93 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`
/Linux-v6.1/lib/
D	stackinit_kunit.c	`83 zero.three = 0; \ 100 .three = 0, \ 106 .three = arg->three, \ 112 var.three = 0; \ 245 unsigned long three; member 254 int three; member 262 u8 three; member 270 char three; member 279 char __user three; member`
/Linux-v6.1/drivers/staging/media/atomisp/pci/isp/kernels/tnr/tnr3/
D	ia_css_tnr3_types.h	`32 * 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`
/Linux-v6.1/tools/perf/pmu-events/arch/x86/jaketown/
D	uncore-other.json	577 …r of cycles when the R2PCIe Ingress is not empty. This tracks one of the three rings that are use… 587 …r of cycles when the R2PCIe Ingress is not empty. This tracks one of the three rings that are use… 597 …r of cycles when the R2PCIe Ingress is not empty. This tracks one of the three rings that are use… 633 …er of cycles when the R2PCIe Egress is not empty. This tracks one of the three rings that are use… 642 …er of cycles when the R2PCIe Egress is not empty. This tracks one of the three rings that are use… 651 …er of cycles when the R2PCIe Egress is not empty. This tracks one of the three rings that are use… 700 …ages on BL to the IIO. There is one credit for each of these three message classes (three credits… 710 …ages on BL to the IIO. There is one credit for each of these three message classes (three credits… 720 …ages on BL to the IIO. There is one credit for each of these three message classes (three credits… 730 … credit was available. There is one credit for each of these three message classes (three credits… [all …]
/Linux-v6.1/tools/testing/selftests/rcutorture/doc/
D	TREE_RCU-kconfig.txt	`7 CONFIG_DEBUG_LOCK_ALLOC -- Do three, covering CONFIG_PROVE_LOCKING & not. 12 CONFIG_PREEMPT -- Do half. (First three and #8.) 18 CONFIG_RCU_NOCB_CPU -- Do three, one with no rcu_nocbs CPUs, one with`
D	TINY_RCU.txt	`6 CONFIG_DEBUG_LOCK_ALLOC -- Do all three and none of the three.`
/Linux-v6.1/arch/x86/include/uapi/asm/
D	e820.h	`13 * 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`
/Linux-v6.1/Documentation/devicetree/bindings/interrupt-controller/
D	riscv,cpu-intc.txt	`10 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`
/Linux-v6.1/arch/sparc/include/asm/
D	backoff.h	`24 * 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`
/Linux-v6.1/arch/x86/include/asm/e820/
D	types.h	`74 * entries, based on a heuristic calculation: up to three entries per 80 * of three memory map entries per node is "enough" entries for 83 * to allow more than three entries per node or otherwise refine`
/Linux-v6.1/Documentation/devicetree/bindings/i2c/
D	i2c-pxa-pci-ce4100.txt	`5 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`
/Linux-v6.1/include/linux/sched/
D	types.h	`13 * This structure groups together three kinds of CPU time that are tracked for 15 * these counts together and treat all three of them in parallel.`
/Linux-v6.1/tools/testing/selftests/bpf/progs/
D	test_sockmap_kern.h	237 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()
/Linux-v6.1/arch/x86/um/
D	Kconfig	`32 bool "Three-level pagetables" if !64BIT 35 Three-level pagetables will let UML have more than 4G of physical`
/Linux-v6.1/drivers/misc/lis3lv02d/
D	Kconfig	`7 tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (SPI)" 23 tristate "STMicroeletronics LIS3LV02Dx three-axis digital accelerometer (I2C)"`
/Linux-v6.1/Documentation/devicetree/bindings/phy/
D	phy-mapphone-mdm6600.txt	`10 - motorola,cmd-gpios Three GPIOs to control the power state of the MDM6600 11 - motorola,status-gpios Three GPIOs to read the power state of the MDM6600`

12 3 4 5 6 7 8 9 10 >>...79