/openbmc/linux/Documentation/ABI/removed/ |
H A D | sysfs-mce | 1 What: /sys/devices/system/machinecheck/machinecheckX/tolerant 22 risk of deadlock. Higher tolerant values trade potentially 24 (for tolerant >= 3).
|
/openbmc/linux/tools/memory-model/Documentation/ |
H A D | access-marking.txt | 69 3. Reads whose values feed into error-tolerant heuristics. 71 4. Writes setting values that feed into error-tolerant heuristics. 125 Reads Feeding Into Error-Tolerant Heuristics 146 Writes Setting Values Feeding Into Error-Tolerant Heuristics 148 The values read into error-tolerant heuristics come from somewhere,
|
/openbmc/linux/drivers/net/can/ctucanfd/ |
H A D | Kconfig | 30 modified to be CAN FD frames tolerant on MicroZed Zynq based
|
/openbmc/openbmc/poky/meta/files/common-licenses/ |
H A D | JasPer-2.0 | 17 …INTELLECTUAL PROPERTY RIGHTS NEEDED, IF ANY. THE SOFTWARE IS NOT FAULT-TOLERANT AND IS NOT INTEND…
|
/openbmc/linux/arch/powerpc/mm/ptdump/ |
H A D | book3s64.c | 71 .set = "tolerant",
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | Redundancy.v1_5_0.json | 100 …mbers allowed in the redundancy group for the current redundancy mode to still be fault tolerant.", 249 …onal devices needed in the redundancy group for the current redundancy mode to be fault tolerant.",
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Redundancy.v1_5_0.json | 100 …mbers allowed in the redundancy group for the current redundancy mode to still be fault tolerant.", 249 …onal devices needed in the redundancy group for the current redundancy mode to be fault tolerant.",
|
/openbmc/bmcweb/redfish-core/include/registries/ |
H A D | storage_device_message_registry.hpp | 307 … fault-tolerant volume, first back up all data, then replace the drive and restore all data afterw…
|
/openbmc/linux/drivers/gpu/drm/i915/ |
H A D | i915_mitigations.c | 47 /* Be tolerant of leading/trailing whitespace */ in mitigations_set()
|
/openbmc/u-boot/arch/arm/include/asm/arch-tegra/ |
H A D | pinmux.h | 132 u32 e_io_hv:2; /* select 3.3v tolerant receivers */
|
/openbmc/linux/Documentation/devicetree/bindings/i3c/ |
H A D | i3c.yaml | 94 not tolerant to high frequencies
|
/openbmc/linux/Documentation/filesystems/ |
H A D | ubifs.rst | 65 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
|
H A D | fiemap.rst | 204 structure directly. Filesystem handlers should be tolerant to signals and return
|
/openbmc/linux/Documentation/gpu/ |
H A D | vgaarbiter.rst | 85 a bit, but makes the arbiter more tolerant to user space problems and able
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | kernel-parameters.rst | 79 The special case-tolerant group name "all" has a meaning of selecting all CPUs,
|
/openbmc/linux/drivers/phy/intel/ |
H A D | phy-intel-lgm-emmc.c | 99 * failure cases are found which indicates we should be more tolerant in intel_emmc_phy_power()
|
H A D | phy-intel-keembay-emmc.c | 120 * failure cases are found which indicates we should be more tolerant in keembay_emmc_phy_power()
|
/openbmc/ibm-logging/ |
H A D | policy_find.cpp | 153 * This is to be tolerant of the policy table not having
|
/openbmc/linux/drivers/phy/rockchip/ |
H A D | phy-rockchip-emmc.c | 174 * failure cases are found which indicates we should be more tolerant in rockchip_emmc_phy_power()
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | Redundancy_v1.xml | 68 <Annotation Term="OData.LongDescription" String="This property shall contain the minimum number of members allowed in the redundancy group for the current redundancy mode to still be fault tolerant."/> 395 <Annotation Term="OData.LongDescription" String="This property shall contain the minimum number of functional devices needed in the redundancy group for the current redundancy mode to be fault tolerant."/>
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Redundancy_v1.xml | 68 …bers allowed in the redundancy group for the current redundancy mode to still be fault tolerant."/> 395 …nal devices needed in the redundancy group for the current redundancy mode to be fault tolerant."/>
|
/openbmc/linux/drivers/usb/serial/ |
H A D | cyberjack.c | 282 /* "+=" is probably more fault tolerant than "=" */ in cyberjack_read_int_callback()
|
/openbmc/linux/Documentation/powerpc/ |
H A D | eeh-pci-error-recovery.rst | 319 Ext3fs seems to be tolerant, retrying reads/writes until it does
|
/openbmc/qemu/pc-bios/ |
H A D | petalogix-ml605.dts | 78 xlnx,fault-tolerant = < 0x00 >;
|
/openbmc/linux/net/ethernet/ |
H A D | eth.c | 185 * won't work for fault tolerant netware but does for the rest. in eth_type_trans()
|