| /linux/Documentation/userspace-api/media/v4l/ |
| H A 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/drivers/scsi/isci/ |
| H A 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/mm/damon/tests/ |
| H A D | vaddr-kunit.h | 43 * complex and dynamic memory mappings of each target task to three 44 * discontiguous regions which cover every mapped areas. However, the three 54 * three regions and returns. For more detail, refer to the comment of 60 * mapped. To cover every mappings, the three regions should start with 10, 61 * and end with 305. The process also has three unmapped areas, 25-200, 63 * unmapped areas, and thus it should be converted to three regions of 10-25, 114 * three_regions The three regions that need to be applied now 121 * three regions, and updates the monitoring target regions to fit in the three 125 * This test passes the given target regions and the new three regions that 156 * This function test most common case where the three big regions are only [all …]
|
| /linux/lib/tests/ |
| H A D | stackinit_kunit.c | 100 zero.three = 0; \ 119 .three = 0, \ 125 .three = arg->three, \ 131 var.three = 0; \ 307 unsigned long three; member 316 int three; member 324 u8 three; member 332 char *three; member 341 char __user *three; member 349 unsigned long three; member [all …]
|
| /linux/Documentation/devicetree/bindings/mux/ |
| H A 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/Documentation/hwmon/ |
| H A D | emc1403.rst | 68 (one internal, one external). EMC14x3 support three sensors (one internal, 69 two external), EMC14x4 support four sensors (one internal, three external), 72 The chips implement three limits for each sensor: low (tempX_min), high 77 all three limits.
|
| H A 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
|
| H A 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,
|
| H A D | emc6w201.rst | 27 multiple DC fans using three Pulse Width Modulator (PWM) outputs. Note 28 that it is possible to control more than three fans by connecting two
|
| /linux/tools/perf/pmu-events/arch/x86/jaketown/ |
| H A D | uncore-interconnect.json | 562 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 572 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 582 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 592 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 602 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 612 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 622 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 632 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 642 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… 652 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo… [all …]
|
| /linux/tools/testing/selftests/rcutorture/doc/ |
| H A 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
|
| H A D | TINY_RCU.txt | 6 CONFIG_DEBUG_LOCK_ALLOC -- Do all three and none of the three.
|
| /linux/tools/perf/tests/shell/ |
| H A D | diff.sh | 78 echo "Basic three file diff test" 97 echo "Basic three file diff test [Failed diff]" 101 echo "Basic three file diff test [Success]"
|
| /linux/Documentation/devicetree/bindings/phy/ |
| H A D | realtek,usb2phy.yaml | 20 The USB architecture includes three XHCI controllers. 38 The USB architecture includes three XHCI controllers. 46 The USB architecture includes three XHCI controllers. 54 The USB architecture includes three XHCI controllers.
|
| H A D | realtek,usb3phy.yaml | 20 The USB architecture includes three XHCI controllers. 30 The USB architecture includes three XHCI controllers. 38 The USB architecture includes three XHCI controllers.
|
| /linux/arch/sparc/include/asm/ |
| H A 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/Documentation/devicetree/bindings/interrupt-controller/ |
| H A D | riscv,cpu-intc.yaml | 16 The RISC-V supervisor ISA manual specifies three interrupt sources that are 26 required to have a HLIC with these three interrupt sources present. Since 51 with only the following three interrupts being defined for
|
| /linux/tools/testing/selftests/bpf/progs/ |
| H A D | test_sockmap_kern.h | 236 int *bytes, zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5; in bpf_prog4() local 250 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog4() 266 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, key = 0; in bpf_prog6() local 284 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog6() 352 int zero = 0, one = 1, two = 2, three = 3, four = 4, five = 5, err = 0; in bpf_prog10() local 365 end_push = bpf_map_lookup_elem(&sock_bytes, &three); in bpf_prog10()
|
| H A D | trace_vprintk.c | 19 static const char three[] = "3"; in sys_enter() local 29 one, 2, three, 4, five, 6, seven, 8, nine, 10, ++trace_vprintk_ran); in sys_enter()
|
| /linux/Documentation/devicetree/bindings/i2c/ |
| H A 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/include/linux/sched/ |
| H A 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/drivers/net/ethernet/freescale/fman/ |
| H A D | Kconfig | 29 one of the following three conditions: 38 With any one of the above three conditions present, there is
|
| /linux/Documentation/devicetree/bindings/clock/ti/ |
| H A D | adpll.txt | 4 register-mapped ADPLL with two to three selectable input clocks 5 and three to four children.
|
| /linux/Documentation/devicetree/bindings/net/ |
| H A D | xlnx,gmii-to-rgmii.yaml | 16 This core can be used in all three modes of operation(10/100/1000 Mb/s). 18 speed of operation. This core can switch dynamically between the three
|
| /linux/drivers/input/mouse/ |
| H A D | vsxxxaa.c | 52 * So to get a working adaptor, you need to connect the mouse with three 53 * wires to a RS232 port and two or three additional wires for +5V, +12V and 201 * Check for normal stream packets. This is three bytes, in vsxxxaa_handle_REL_packet() 224 * Get button state. It's the low three bits in vsxxxaa_handle_REL_packet() 225 * (for three buttons) of byte 0. in vsxxxaa_handle_REL_packet() 332 * Get button state. It's the low three bits in vsxxxaa_handle_POR_packet() 333 * (for three buttons) of byte 0. Maybe even the bit <3> in vsxxxaa_handle_POR_packet()
|