Home
last modified time | relevance | path

Searched full:configured (Results 1 – 25 of 3201) sorted by relevance

12345678910>>...129

/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dtlv320adcx140.yaml93 1 - GPIX is configured as a general-purpose input (GPI)
94 2 - GPIX is configured as a master clock input (MCLK)
95 3 - GPIX is configured as an ASI input for daisy-chain (SDIN)
96 4 - GPIX is configured as a PDM data input for channel 1 and channel
98 5 - GPIX is configured as a PDM data input for channel 3 and channel
100 6 - GPIX is configured as a PDM data input for channel 5 and channel
102 7 - GPIX is configured as a PDM data input for channel 7 and channel
121 1 - GPIO1 is configured as a general-purpose output (GPO)
122 2 - (default) GPIO1 is configured as a device interrupt output (IRQ)
123 3 - GPIO1 is configured as a secondary ASI output (SDOUT2)
[all …]
/openbmc/linux/tools/testing/kunit/test_data/
H A Dtest_is_test_passed-no_tests_run_no_header.log39 Using a channel type which is configured out of UML
41 Using a channel type which is configured out of UML
43 Using a channel type which is configured out of UML
45 Using a channel type which is configured out of UML
47 Using a channel type which is configured out of UML
49 Using a channel type which is configured out of UML
51 Using a channel type which is configured out of UML
53 Using a channel type which is configured out of UML
55 Using a channel type which is configured out of UML
57 Using a channel type which is configured out of UML
[all …]
H A Dtest_output_isolated_correctly.log61 Using a channel type which is configured out of UML
63 Using a channel type which is configured out of UML
65 Using a channel type which is configured out of UML
67 Using a channel type which is configured out of UML
69 Using a channel type which is configured out of UML
71 Using a channel type which is configured out of UML
73 Using a channel type which is configured out of UML
75 Using a channel type which is configured out of UML
77 Using a channel type which is configured out of UML
79 Using a channel type which is configured out of UML
[all …]
/openbmc/openbmc-test-automation/redfish/events/
H A Dtest_bmc_snmp_trap.robot3 ... configured and installed. For download, installation and
29 Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${SNMP_DEFAULT_PORT}
39 Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${NON_DEFAULT_PORT1}
50 ... Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${out_of_range_port}
81 ... Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${alpha_port}
89 ... SNMP manager gets configured with default port.
95 Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${SNMP_DEFAULT_PORT}
108 Verify SNMP Manager Configured On BMC ${SNMP_MGR1_IP} ${SNMP_DEFAULT_PORT}
109 Verify SNMP Manager Configured On BMC ${SNMP_MGR2_IP} ${SNMP_DEFAULT_PORT}
161 # Verify if SNMP managers are configured.
[all …]
/openbmc/linux/Documentation/ABI/testing/
H A Ddebugfs-scmi-raw7 in little-endian binary format to have it sent to the configured
10 entry if it arrived within the configured timeout.
22 in little-endian binary format to have it sent to the configured
25 entry if it arrived within the configured timeout.
27 from this same entry too if it arrived within the configured
74 in little-endian binary format to have it sent to the configured
78 entry if it arrived on channel <m> within the configured
88 exist only if the transport is configured to have more than
98 in little-endian binary format to have it sent to the configured
102 entry if it arrived on channel <m> within the configured
[all …]
H A Dsysfs-driver-qat24 Write to the file to change the configured services.
28 * sym;asym: the device is configured for running crypto
31 * dc: the device is configured for running compression services
34 * sym: the device is configured for running symmetric crypto
36 * asym: the device is configured for running asymmetric crypto
38 * asym;dc: the device is configured for running asymmetric
41 * sym;dc: the device is configured for running symmetric crypto
49 a device configured for running crypto services in order to
H A Ddebugfs-scmi26 Description: A string representing the type of transport configured for this
34 Description: A boolean stating if the transport configured on the underlying
43 for the currently configured SCMI transport for instance <n>.
51 configured SCMI transport for instance <n>.
59 the currently configured SCMI transport for instance <n> on the
68 the currently configured SCMI transport for instance <n> on the
/openbmc/linux/include/linux/platform_data/
H A Dad7266.h13 * @AD7266_RANGE_VREF: Device is configured for input range 0V - VREF
15 * @AD7266_RANGE_2VREF: Device is configured for input range 0V - 2VREF
25 * @AD7266_MODE_DIFF: Device is configured for full differential mode
27 * @AD7266_MODE_PSEUDO_DIFF: Device is configured for pseudo differential mode
29 * @AD7266_MODE_SINGLE_ENDED: Device is configured for single-ended mode
40 * @range: Reference voltage range the device is configured for
41 * @mode: Sample mode the device is configured for
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DThreshold.events.yaml31 description: The configured threshold value for this sensor.
53 description: The configured threshold value for this sensor.
75 description: The configured threshold value for this sensor.
97 description: The configured threshold value for this sensor.
119 description: The configured threshold value for this sensor.
141 description: The configured threshold value for this sensor.
163 description: The configured threshold value for this sensor.
185 description: The configured threshold value for this sensor.
207 description: The configured threshold value for this sensor.
229 description: The configured threshold value for this sensor.
[all …]
/openbmc/phosphor-fan-presence/docs/control/
H A Devents.md104 After invoking the configured method, any actions configured for this trigger
116 1. `get_properties` - Read the property configured for the group from every
125 configured group. After handling the signal, any configured actions are run.
161 Timer triggers run actions after the configured type of timer expires.
184 Optional, if set to true, will update the D-Bus properties from the configured
397 Sets the fans to a configured floor when a number of members within the group
398 are at a configured state. Once the number of members at the given state falls
399 below the configured count, the floor hold is released.
411 The above config reads the configured D-Bus property on each group member
412 configured for the action. If two or more members have a property value of false
[all …]
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
H A Drenesas,rza1-ports.yaml50 generally speaking, each of them can be configured in GPIO ("port") mode
87 The hardware reference manual specifies when a pin has to be configured
98 When a pin has to be configured in alternate function mode, use
101 When multiple pins are required to be configured as part of the
146 * Pin #0 on port #3 is configured as alternate function #6.
147 * Pin #2 on port #3 is configured as alternate function #4.
156 * Pin #4 on port #1 is configured as alternate function #1.
157 * Pin #5 on port #1 is configured as alternate function #1.
172 * Pin #0 on port #4 is configured as alternate function #2
182 * Pin #1 on port #4 is configured as alternate function #1
/openbmc/phosphor-fan-presence/control/json/
H A Devent.hpp36 * @class Event - Represents a configured fan control event
40 * how fan control should function. These events contain the configured
43 * to be run when a trigger occurs. The triggers and actions configured must be
46 * When no events exist, the configured fans are set to their corresponding
68 * @param[in] zones - Reference to the configured zones
111 * @brief Load and/or return all groups available to be configured on events
116 * @return Groups available to be configured on events from `groups.json`
124 * @param[in] group - Group object to get configured
136 * @param[out] groups - List of groups to be configured
161 /* Reference to the configured zones */
H A Dprofile.hpp29 * @class Profile - Represents a configured fan control profile
33 * based on the configuration of the profile. Fan control events configured
34 * with no profile(s) are always used and events configured for a specified
37 * When no profiles exist, all configured fan control events are used.
83 * Sets the active state of the profile using the configured method of
93 * Active state method that takes a list of configured dbus properties where
94 * all of those properties must equal their configured values to set the
/openbmc/qemu/docs/specs/
H A Divshmem-spec.rst44 configured for interrupts, obviously.
47 configured for interrupts. It becomes safely accessible only after
54 it is configured for interrupts.
89 IVPosition Register: if the device is not configured for interrupts,
96 configured for interrupts. A positive IVPosition means interrupts,
103 If the device is not configured for interrupts, the write is ignored.
130 When configured for interrupts, the peers share eventfd objects in
176 An ivshmem device configured for interrupts connects to an ivshmem
203 vector 0,..,N-1, in order. If the client is configured for fewer
204 vectors, it closes the extra file descriptors. If it is configured
[all …]
/openbmc/linux/arch/arm/mach-spear/
H A DKconfig34 Supports ST SPEAr1310 machine configured via the device-tree
41 Supports ST SPEAr1340 machine configured via the device-tree
60 Supports ST SPEAr300 machine configured via the device-tree
66 Supports ST SPEAr310 machine configured via the device-tree
72 Supports ST SPEAr320 machine configured via the device-tree
/openbmc/linux/arch/nios2/platform/
H A DKconfig.platform66 Set to true if you configured the Nios II to include the MUL
72 Set to true if you configured the Nios II to include the MULX
78 Set to true if you configured the Nios II to include the DIV
85 Set to true if you configured the Nios II R2 to include
93 Set to true if you configured the Nios II R2 to include
113 Number of the instruction as configured in QSYS Builder.
123 perfectly fine, even if the Nios II is configured with smaller caches.
/openbmc/linux/tools/testing/selftests/drivers/net/netdevsim/
H A Dethtool-fec.sh13 check $? "$s" "Configured FEC encodings: None
20 check $? "$s" "Configured FEC encodings: Auto
28 check $? "$s" "Configured FEC encodings: Off
36 check $? "$s" "Configured FEC encodings: BaseR
44 check $? "$s" "Configured FEC encodings: ${o^^}
52 check $? "$s" "Configured FEC encodings: RS LLRS
58 check $? "$s" "Configured FEC encodings: Auto Off RS
/openbmc/linux/Documentation/devicetree/bindings/dma/xilinx/
H A Dxilinx_dma.txt2 It can be configured to have one channel or two channels. If configured
7 target devices. It can be configured to have one channel or two channels.
8 If configured as two channels, one is to transmit to the device and another
15 target devices. It can be configured to have up to 16 independent transmit
45 - xlnx,num-fstores: Should be the number of framebuffers as configured in h/w.
49 register as configured in h/w. Takes values {8...26}. If the property
77 - xlnx,include-dre: Tells hardware is configured for Data
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
H A Dcache.json105 … whether they allocate. If either the core is configured without a per-core L2 or the cluster is c…
108 … whether they allocate. If either the core is configured without a per-core L2 or the cluster is c…
111 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
114 …configured with a per-core L2 cache: This event does not count. +//0 If the core is configured wit…
/openbmc/linux/Documentation/devicetree/bindings/gpu/host1x/
H A Dnvidia,tegra234-nvdec.yaml67 firmware secure carveout. This carveout is configured by the bootloader and
73 Offset to bootloader manifest from beginning of firmware that was configured by
79 Offset to bootloader code section from beginning of firmware that was configured by
85 Offset to bootloader data section from beginning of firmware that was configured by
91 Offset to operating system manifest from beginning of firmware that was configured by
97 Offset to operating system code section from beginning of firmware that was configured by
103 Offset to operating system data section from beginning of firmware that was configured
/openbmc/phosphor-fan-presence/control/json/actions/
H A Dtimer_based_actions.hpp68 * timer expires. The configured timer is set to callback the list of
69 * actions against the given zones and configured groups.
71 * Where any group does not have a configured value to be compared against,
76 * Where all groups have a configured value to compare against, that will be
89 * Starts the configured timer of this action if not already running
96 * Stops the configured timer of this action if running
103 * Called each time the timer expires, running the configured actions
/openbmc/linux/Documentation/admin-guide/media/
H A Drkisp1.rst160 In the above example the sensor is configured to bayer format:
161 `SRGGB10_1X10/1640x1232`. The rkisp1_isp:0 pad should be configured to the
163 with 'EPIPE' error. So it is also configured to `SRGGB10_1X10/1640x1232`.
164 In addition, the rkisp1_isp:0 pad is configured to cropping `(0,0)/1600x1200`.
167 isp source pad `rkisp1_isp:2`. Another cropping operation is configured on
170 The resizer's sink pad `rkisp1_resizer_selfpath` should be configured to format
172 link. In addition a cropping `(300,400)/1400x1000` is configured on it.
174 The source pad of the resizer, `rkisp1_resizer_selfpath:1` is configured to
190 isp (`rkisp1_isp:2`). The quantization configured on this pad is the
194 ``V4L2_QUANTIZATION_DEFAULT`` even if the quantization is configured to full
[all …]
/openbmc/linux/Documentation/devicetree/bindings/hwmon/
H A Dlm87.txt12 are configured as voltage input pins in0 and in5.
14 - has-in6: When set, pin 5 is configured to be used as voltage input
17 - has-in7: When set, pin 6 is configured to be used as voltage input
21 configured to measure 5.0V power supply. Default is 3.3V.
/openbmc/phosphor-fan-presence/
H A DREADME.md107 Controls the fans based on a set of events that are configured using a group of
108 D-Bus objects and one-or-more triggers that run a configured set of actions.
109 These events are meant to be configured to handle all aspects of controlling the
110 fans within a system. Fans are added to zones that then have events configured
143 combination of both. This updates a configured location of a fan D-Bus object's
168 against the current target, applying any configured adjustments to the target
169 due to fan hardware properties. In addition to updating the configured location
171 configured\* to be taken based on the state of fans, i.e.) creating event logs
174 Another feature that can be configured is the ability to cancel the monitoring
/openbmc/linux/tools/perf/Documentation/
H A Dperf-daemon.txt24 monitors configured record sessions.
37 flight recorder sessions in above example or session that is configured
44 Sessions are configured through config file, see CONFIG FILE section
82 The signal command sends signal to configured sessions.
90 The ping command sends control ping to configured sessions.
98 The daemon is configured within standard perf config file by
139 First line is daemon process info with configured daemon base.

12345678910>>...129