Home
last modified time | relevance | path

Searched refs:Recovery (Results 1 – 25 of 48) sorted by relevance

12

/openbmc/linux/Documentation/ABI/testing/
H A Dsysfs-driver-chromeos-acpi21 0 Recovery.
37 2 Recovery button was pressed.
38 4 Recovery button was pressed (EC firmware).
76 1 Recovery button.
/openbmc/linux/Documentation/firmware-guide/acpi/
H A Dchromeos-acpi-device.rst64 - Recovery button was pressed when x86 firmware booted.
67 - Recovery button was pressed when EC firmware booted. (required if EC EEPROM is
172 - 0 - Recovery
228 - 0x00000001 - Recovery button
/openbmc/linux/arch/arm64/boot/dts/rockchip/
H A Drk3399-nanopi-m4b.dts23 label = "Recovery";
H A Drk3328-roc-pc.dts22 label = "Recovery";
H A Drk3568-fastrhino-r68s.dts22 label = "Recovery";
H A Drk3399-nanopc-t4.dts43 label = "Recovery";
H A Drk3328-rock-pi-e.dts40 label = "Recovery";
/openbmc/bmcweb/redfish-core/include/generated/enums/
H A Dcomputer_system.hpp27 Recovery, enumerator
234 {BootSource::Recovery, "Recovery"},
/openbmc/u-boot/board/st/stm32mp1/
H A DREADME142 Recovery 1 1 0
143 Recovery 0 0 0
145 Recovery is a boot from serial link (UART/USB) and it is used with
/openbmc/docs/designs/
H A Dbmc-service-failure-debug-and-recovery.md1 # BMC Service Failure Debug and Recovery
156 #### Recovery Mechanisms
163 | Severity | BMC Recovery Mechanism | Used for …
166 | 2 | Forceful reboot request | Recovery from unresponsive platform data transport providers…
202 #### Behavioural Requirements for Recovery Mechanism 2
219 #### Analysis of BMC Recovery Mechanisms for Power10 Platforms
343 7. If `Ready` becomes set before expiry, disarm the escalation timer. Recovery
350 behave correctly without one. Recovery is only necessary if other paths have
H A Dpower-recovery.md1 # OpenBMC Server Power Recovery
59 ### Automated Power-On Recovery
85 ### BMC and System Recovery Paths
163 ### Automated Power-On Recovery
177 ### BMC and System Recovery Paths
/openbmc/linux/Documentation/arch/parisc/
H A Dregisters.rst14 CR 0 (Recovery Counter) used for ptrace
81 R (Recovery Counter trap) 0
/openbmc/linux/arch/arm64/boot/dts/nvidia/
H A Dtegra234-p3768-0000+p3767-0000.dts61 label = "Force Recovery";
H A Dtegra234-p3768-0000.dtsi185 label = "Force Recovery";
H A Dtegra234-p3740-0002+p3701-0008.dts127 label = "Force Recovery";
/openbmc/linux/arch/arm/boot/dts/nxp/imx/
H A Dimx6q-gk802.dts76 /* Recovery button, active-low */
/openbmc/linux/arch/arm64/boot/dts/xilinx/
H A Dzynqmp-sm-k26-revA.dts196 label = "Recovery Image";
202 label = "Recovery Image Backup";
/openbmc/openbmc-test-automation/network/
H A Dtest_cable_pull_recover.robot32 Verify Network Interface Recovery
/openbmc/linux/Documentation/watchdog/
H A Dhpwdt.rst24 an Automatic Server Recovery (ASR)) event will occur.
/openbmc/docs/designs/management-console/
H A DAuthorities_List_Management.md36 4. Recovery at boot up: when the phosphor-certificate-manager gets instantiated,
/openbmc/linux/Documentation/scsi/
H A Dcxgb3i.rst30 - PDU Transmit and Recovery
/openbmc/linux/Documentation/powerpc/
H A Deeh-pci-error-recovery.rst2 PCI Bus EEH Error Recovery
57 Detection and Recovery
92 pending work) and start recovery of the card. Recovery normally
/openbmc/linux/arch/arm/boot/dts/rockchip/
H A Drk3288-rock2-square.dts22 label = "Recovery";
/openbmc/linux/Documentation/networking/devlink/
H A Ddevlink-health.rst33 * Recovery procedures
/openbmc/qemu/docs/devel/
H A Dluks-detached-header.rst54 * Recovery - corruption of a bit in the header may make the

12