Home
last modified time | relevance | path

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

12345678910>>...92

/openbmc/linux/tools/testing/kunit/test_data/
Dtest_is_test_passed-no_tests_run_no_header.log
Dtest_output_isolated_correctly.log
/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/include/linux/platform_data/
Dad7266.h
/openbmc/linux/Documentation/ABI/testing/
Ddebugfs-scmi-raw
Ddebugfs-scmi
Dsysfs-bus-dfl-devices-n3000-nios
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/
H A DThreshold.events.yaml21 description: The configured threshold value for this sensor.
43 description: The configured threshold value for this sensor.
65 description: The configured threshold value for this sensor.
87 description: The configured threshold value for this sensor.
109 description: The configured threshold value for this sensor.
131 description: The configured threshold value for this sensor.
153 description: The configured threshold value for this sensor.
175 description: The configured threshold value for this sensor.
197 description: The configured threshold value for this sensor.
219 description: The configured threshol
[all...]
/openbmc/linux/arch/arm/mach-spear/
DKconfig
/openbmc/linux/Documentation/devicetree/bindings/pinctrl/
Drenesas,rza1-ports.yaml
/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
158 /* 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/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
393 Sets the fans to a configured floor when a number of members within the group
394 are at a configured state. Once the number of members at the given state falls
395 below the configured count, the floor hold is released.
407 The above config reads the configured D-Bus property on each group member
408 configured for the action. If two or more members have a property value of false
[all …]
/openbmc/linux/arch/nios2/platform/
DKconfig.platform
/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/tools/testing/selftests/drivers/net/netdevsim/
Dethtool-fec.sh
/openbmc/linux/Documentation/devicetree/bindings/dma/xilinx/
Dxilinx_dma.txt
/openbmc/linux/Documentation/devicetree/bindings/gpu/host1x/
Dnvidia,tegra234-nvdec.yaml
/openbmc/linux/tools/perf/pmu-events/arch/arm64/arm/cortex-a55/
Dcache.json
/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/devicetree/bindings/sound/
Dcs42l52.txt
/openbmc/phosphor-fan-presence/
H A DREADME.md102 Controls the fans based on a set of events that are configured using a group of
103 D-Bus objects and one-or-more triggers that run a configured set of actions.
104 These events are meant to be configured to handle all aspects of controlling the
105 fans within a system. Fans are added to zones that then have events configured
138 combination of both. This updates a configured location of a fan D-Bus object's
163 against the current target, applying any configured adjustments to the target
164 due to fan hardware properties. In addition to updating the configured location
166 configured\* to be taken based on the state of fans, i.e.) creating event logs
169 Another feature that can be configured is the ability to cancel the monitoring
/openbmc/linux/drivers/char/mwave/
DREADME
/openbmc/linux/include/linux/
Di2c-algo-pca.h
/openbmc/linux/tools/perf/Documentation/
Dperf-daemon.txt

12345678910>>...92