Home
last modified time | relevance | path

Searched full:identify (Results 1 – 25 of 613) sorted by relevance

12345678910>>...25

/openbmc/phosphor-led-sysfs/
H A DREADME.md7 Say we have 'identify' LED in our system, which may be declared in devicetree.
13 identify {
23 ./add-led-action --path /sys/class/leds/identify
34 `- /xyz/openbmc_project/led/physical/identify
36 busctl introspect xyz.openbmc_project.LED.Controller /xyz/openbmc_project/led/physical/identify
55 /xyz/openbmc_project/led/physical/identify \
64 /xyz/openbmc_project/led/physical/identify \
/openbmc/openbmc-test-automation/ipmi/
H A Dtest_ipmi_general.robot202 Verify Chassis Identify via IPMI
203 [Documentation] Set chassis identify using IPMI and verify.
208 # Set to default "chassis identify" and verify that LED blinks for 15s.
209 Run IPMI Standard Command chassis identify
210 Verify Identify LED State Via Redfish True
213 Verify Identify LED State Via Redfish False
215 # Set "chassis identify" to 10s and verify that the LED blinks for 10s.
216 Run IPMI Standard Command chassis identify 10
217 Verify Identify LED State Via Redfish True
220 Verify Identify LE
[all...]
H A Dtest_ipmi_sel_time.robot98 # Identify Time difference and find the difference is less than 6 seconds.
116 ${sel_time} ${set_sel_time}= Identify SEL Time +06:15:00
139 ${sel_time} ${set_sel_time}= Identify SEL Time -24:00:00
217 # Identify Time difference and find the difference is less than 6 seconds.
249 # Identify and find the time difference is less than 60 seconds.
263 ${sel_time} ${set_sel_time}= Identify SEL Time +06:15:00
300 # Identify and find the time difference is less than 60 seconds.
314 ${sel_time} ${set_sel_time}= Identify SEL Time -24:00:00
351 # Identify and find the time difference is less than 60 seconds.
367 ${sel_time} ${set_sel_time}= Identify SE
[all...]
/openbmc/openbmc/meta-nuvoton/meta-evb-npcm845/recipes-phosphor/leds/evb-npcm845-led-manager-config/
H A Dled.yaml8 identify:
12 identify:
16 identify:
/openbmc/openbmc/meta-quanta/meta-olympus-nuvoton/recipes-phosphor/leds/olympus-nuvoton-led-manager-config/
H A Dled.yaml8 identify:
14 identify:
20 identify:
/openbmc/openbmc/meta-ibm/meta-palmetto/recipes-phosphor/leds/palmetto-led-manager-config/
H A Dled.yaml14 identify:
20 identify:
31 identify:
/openbmc/u-boot/include/
H A Dnvme.h13 * nvme_identify - identify controller or namespace capabilities and status
15 * This issues an identify command to the NVMe controller to return a data
19 * @nsid: 0 for controller, namespace id for namespace to identify
21 * @dma_addr: dma buffer address to store the identify result
77 * @return: 0 on success, -EIO if NVMe identify command fails
/openbmc/libpldm/include/libpldm/
H A Dbios.h248 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
275 * @param[out] next_transfer_handle - Pointer to a handle that identify the
288 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
318 * @param[out] next_transfer_handle - Pointer to a handle that identify the
357 * @param[in] next_transfer_handle - handle to identify the next portion of the
374 * @param[in] transfer_handle - Handle to identify a BIOS table transfer
389 * @param[out] transfer_handle - Handle to identify a BIOS table transfer
404 * @param[in] next_transfer_handle - handle to identify the next portion of the
423 * @param[in] transfer_handle - Handle to identify a BIOS attribute transfer
426 * @param[in] attribute_handle - Handle to identify the BIOS attribute
[all …]
H A Dfru.h245 * @param[out] data_transfer_handle - A handle, used to identify a FRU Record
260 * @param[in] next_data_transfer_handle - A handle that is used to identify the
281 * @param[out] data_transfer_handle - A handle, used to identify a FRU Record
283 * @param[out] fru_table_handle - A handle, used to identify a FRU DATA
302 * @param[in] next_data_transfer_handle - A handle that is used to identify the
328 * @param[in] data_transfer_handle - A handle, used to identify a FRU Record
350 * @param[out] next_data_transfer_handle - A handle used to identify the next
374 * @param[out] next_data_transfer_handle - A handle used to identify the next
419 * @param[in] data_transfer_handle - A handle, used to identify a FRU Record
421 * @param[in] fru_table_handle - A handle, used to identify a FRU DATA records
[all …]
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Decorator/
H A DAssetTag.interface.yaml2 Implement to provide Asset Tag. The asset tag is used to uniquely identify
8 The tag provided to an object to identify it.
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Inventory/Source/
H A DDevicePresence.interface.yaml9 Used by entity-manager to identify which hw was detected. For internal
14 Used by entity-manager to identify which hw was detected. For internal
/openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/gpio/id-button/
H A Dtoggle_identify_led.sh2 # Toggle the state of identify LED Group
9 object=$(busctl tree $SERVICE --list | grep identify)
/openbmc/u-boot/drivers/led/
H A DKconfig111 CONFIG_LED_STATUS_BIT is passed into the __led_* functions to identify
146 identify which LED is being acted on. As such, the chosen value must
181 identify which LED is being acted on. As such, the chosen value must
216 identify which LED is being acted on. As such, the chosen value must
251 identify which LED is being acted on. As such, the chosen value must
286 identify which LED is being acted on. As such, the chosen value must
/openbmc/openbmc/meta-ibm/recipes-phosphor/gpio/id-button/
H A Dtoggle_identify_led.sh2 # Toggle the state of identify LED Group
9 object=$(busctl tree $SERVICE --list | grep identify)
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/
H A DThermal.events.yaml14 An [Optional] set of additional failure data to identify the
35 An [Optional] set of additional failure data to identify the
/openbmc/openbmc/poky/documentation/contributor-guide/
H A Didentify-component.rst3 Identify the component
7 so the first step is to identify the component where the issue likely lies.
/openbmc/phosphor-led-sysfs/test/
H A Dtest_dbus_name.cpp36 LedDescr d = {"enclosure-identify", std::nullopt, std::nullopt}; in TEST()
45 LedDescr d = {"enclosure-identify-fault", std::nullopt, std::nullopt}; in TEST()
H A Dtest_led_description.cpp87 LedDescr d = runtest("identify"); in TEST()
89 ASSERT_EQ("identify", d.devicename); in TEST()
/openbmc/openbmc/meta-ampere/meta-jade/recipes-phosphor/leds/phosphor-led-manager/
H A Dcom.ampere.Hardware.Chassis.Model.MtJade.json29 "Name": "identify",
41 "Name": "identify",
/openbmc/openbmc/meta-openembedded/meta-networking/recipes-support/cim-schema/files/
H A DLICENSE15 // identify any or all such third party patent right, owners or
20 // identify any such third party patent rights, or for such party's
/openbmc/openbmc/meta-openembedded/meta-networking/licenses/
H A DDMTF15 // identify any or all such third party patent right, owners or
20 // identify any such third party patent rights, or for such party's
/openbmc/openbmc-test-automation/gui/gui_test/overview_menu/
H A Dtest_overview_menu.robot166 Verify Identify LED State Via Redfish Lit
181 Verify Identify LED State Via Redfish Off
308 Page Should Contain System identify LED
360 Verify Identify LED State Via Redfish
361 [Documentation] Verify that Redfish identify LED system with given state.
365 # expected_state Expected value of Identify LED.
/openbmc/openbmc/meta-ibm/meta-romulus/recipes-phosphor/leds/romulus-led-manager-config/
H A Dled.yaml23 identify:
30 # Both the 'fault' and 'identify' gpios are wired to the same LED.
39 identify:
/openbmc/ipmbbridge/
H A Dipmbdefines.hpp43 uint8_t cmd; /// @brief command required by the network identify the
59 uint8_t cmd; /// @brief command required by the network identify the
/openbmc/openbmc/meta-amd/meta-ethanolx/recipes-phosphor/leds/ethanolx-led-manager-config/
H A Dled.yaml11 identify:
23 identify:

12345678910>>...25