Searched full:tolerant (Results 1 – 25 of 47) sorted by relevance
12
| /Linux-v6.1/Documentation/ABI/removed/ |
| D | sysfs-mce | 1 What: /sys/devices/system/machinecheck/machinecheckX/tolerant
22 risk of deadlock. Higher tolerant values trade potentially
24 (for tolerant >= 3).
|
| /Linux-v6.1/tools/memory-model/Documentation/ |
| 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,
|
| /Linux-v6.1/drivers/net/can/ctucanfd/ |
| D | Kconfig | 30 modified to be CAN FD frames tolerant on MicroZed Zynq based
|
| /Linux-v6.1/arch/powerpc/mm/ptdump/ |
| D | book3s64.c | 71 .set = "tolerant",
|
| /Linux-v6.1/drivers/gpu/drm/i915/ |
| D | i915_mitigations.c | 47 /* Be tolerant of leading/trailing whitespace */ in mitigations_set()
|
| /Linux-v6.1/Documentation/devicetree/bindings/i3c/ |
| D | i3c.yaml | 94 not tolerant to high frequencies
|
| /Linux-v6.1/Documentation/filesystems/ |
| D | ubifs.rst | 65 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
|
| D | fiemap.rst | 204 structure directly. Filesystem handlers should be tolerant to signals and return
|
| D | ntfs.rst | 271 For NT4 fault tolerant volumes you can obtain the sizes using fdisk. So for
|
| /Linux-v6.1/Documentation/gpu/ |
| D | vgaarbiter.rst | 85 a bit, but makes the arbiter more tolerant to user space problems and able
|
| /Linux-v6.1/drivers/phy/intel/ |
| D | phy-intel-lgm-emmc.c | 99 * failure cases are found which indicates we should be more tolerant in intel_emmc_phy_power()
|
| D | phy-intel-keembay-emmc.c | 120 * failure cases are found which indicates we should be more tolerant in keembay_emmc_phy_power()
|
| D | phy-intel-thunderbay-emmc.c | 243 * failure cases are found which indicates we should be more tolerant in thunderbay_emmc_phy_power()
|
| /Linux-v6.1/Documentation/admin-guide/ |
| D | kernel-parameters.rst | 79 The special case-tolerant group name "all" has a meaning of selecting all CPUs,
|
| /Linux-v6.1/drivers/phy/rockchip/ |
| D | phy-rockchip-emmc.c | 174 * failure cases are found which indicates we should be more tolerant in rockchip_emmc_phy_power()
|
| /Linux-v6.1/drivers/usb/serial/ |
| D | cyberjack.c | 282 /* "+=" is probably more fault tolerant than "=" */ in cyberjack_read_int_callback()
|
| D | ark3116.c | 666 * On my chip, all signals seem to be 3.3V, but 5V tolerant. But that
|
| /Linux-v6.1/Documentation/powerpc/ |
| D | eeh-pci-error-recovery.rst | 319 Ext3fs seems to be tolerant, retrying reads/writes until it does
|
| /Linux-v6.1/Documentation/PCI/ |
| D | pci-error-recovery.rst | 58 of the current Linux file systems are not tolerant of disconnection
|
| /Linux-v6.1/net/ethernet/ |
| D | eth.c | 195 * won't work for fault tolerant netware but does for the rest. in eth_type_trans()
|
| /Linux-v6.1/include/linux/ |
| D | if_vlan.h | 671 * 802.2 SSAP/DSAP. This won't work for fault tolerant netware in vlan_set_encap_proto()
|
| /Linux-v6.1/drivers/gpu/drm/radeon/ |
| D | r500_reg.h | 590 /* 78a8 appears to be some kind of (reasonably tolerant) clock?
|
| /Linux-v6.1/drivers/hid/ |
| D | hid-roccat-kone.c | 719 /* be tolerant about not getting chrdev */ in kone_init_specials()
|
| /Linux-v6.1/drivers/cxl/core/ |
| D | hdm.c | 800 * 8.2.5.12.20), but double it to be tolerant of any clock skew between in devm_cxl_enumerate_decoders()
|
| /Linux-v6.1/Documentation/driver-api/media/drivers/ |
| D | zoran.rst | 389 the LML33 works, the DC10+/DC30+ will work too. They're most tolerant to
|
12
