Home
last modified time | relevance | path

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

12345678910>>...103

/openbmc/phosphor-led-manager/test/
H A Dled-test-map.hpp39 {"Three", phosphor::led::Layout::Action::On, 0, 0,
52 {"Three", phosphor::led::Layout::Action::Blink, 0, 0,
65 {"Three", phosphor::led::Layout::Action::Blink, 0, 0,
82 {"Three", phosphor::led::Layout::Action::On, 0, 0,
105 {"Three", phosphor::led::Layout::Action::On, 0, 0,
113 {"Three", phosphor::led::Layout::Action::On, 0, 0,
129 {"Three", phosphor::led::Layout::Action::Blink, 0, 0,
137 {"Three", phosphor::led::Layout::Action::On, 0, 0,
152 {"Three", phosphor::led::Layout::Action::Blink, 0, 0,
160 {"Three", phosphor::led::Layout::Action::On, 0, 0,
[all …]
H A Dutest.cpp153 {"Three", phosphor::led::Layout::Action::On, 0, 0, in TEST_F()
189 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
225 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
255 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
291 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
321 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
370 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
410 {"Three", phosphor::led::Layout::Action::On, 0, 0, in TEST_F()
476 {"Three", phosphor::led::Layout::Action::On, 0, 0, in TEST_F()
541 {"Three", phosphor::led::Layout::Action::Blink, 0, 0, in TEST_F()
[all …]
/openbmc/linux/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
/openbmc/linux/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.
/openbmc/linux/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
/openbmc/linux/mm/damon/
H A Dvaddr-test.h43 * 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 …]
/openbmc/linux/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
/openbmc/linux/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 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,
/openbmc/linux/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
/openbmc/linux/lib/
H A Dstackinit_kunit.c83 zero.three = 0; \
100 .three = 0, \
106 .three = arg->three, \
112 var.three = 0; \
246 unsigned long three; member
255 int three; member
263 u8 three; member
271 char *three; member
280 char __user *three; member
H A Dhashtable_test.c130 /* Add three entries to the hashtable. */ in hashtable_test_hash_for_each()
160 /* Add three entries to the hashtable. */ in hashtable_test_hash_for_each_safe()
193 /* Add three entries with key = 0 to the hashtable. */ in hashtable_test_hash_for_each_possible()
227 * key = 0, check it was visited. Otherwise ensure that only three in hashtable_test_hash_for_each_possible()
248 /* Add three entries with key = 0 to the hashtable. */ in hashtable_test_hash_for_each_possible_safe()
285 * key = 0, check it was visited. Otherwise ensure that only three in hashtable_test_hash_for_each_possible_safe()
/openbmc/openbmc-test-automation/lib/
H A Dfunc_args.py85 result = source_to_object("[('one', 1), ('two', 2), ('three', 3)]")
92 [three]: 3
99 ('three', 3)])")
122 result = source_to_object("dict(one=1, two=2, three=3)")
123 result = source_to_object("{'one':1, 'two':2, 'three':3}")
/openbmc/linux/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.)
18 CONFIG_RCU_NOCB_CPU -- Do three, one with no rcu_nocbs CPUs, one with
H A DTINY_RCU.txt6 CONFIG_DEBUG_LOCK_ALLOC -- Do all three and none of the three.
/openbmc/linux/tools/perf/pmu-events/arch/x86/jaketown/
H A Duncore-interconnect.json502 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
511 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
520 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
529 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
538 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
547 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
556 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
565 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
574 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
583 …: "Counts the number of flits received from the QPI Link. This is one of three 'groups' that allo…
[all …]
/openbmc/linux/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
/openbmc/linux/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
/openbmc/linux/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
/openbmc/linux/Documentation/devicetree/bindings/phy/
H A Drealtek,usb2phy.yaml20 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 Drealtek,usb3phy.yaml20 The USB architecture includes three XHCI controllers.
30 The USB architecture includes three XHCI controllers.
38 The USB architecture includes three XHCI controllers.
/openbmc/linux/include/linux/sched/
H A Dtypes.h13 * 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.
/openbmc/linux/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
/openbmc/linux/arch/x86/include/asm/e820/
H A Dtypes.h74 * 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
/openbmc/linux/arch/x86/um/
H A DKconfig32 bool "Three-level pagetables" if !64BIT
35 Three-level pagetables will let UML have more than 4G of physical

12345678910>>...103