Home
last modified time | relevance | path

Searched full:tolerant (Results 1 – 25 of 47) sorted by relevance

12

/linux-6.14.4/Documentation/ABI/removed/
Dsysfs-mce1 What: /sys/devices/system/machinecheck/machinecheckX/tolerant
22 risk of deadlock. Higher tolerant values trade potentially
24 (for tolerant >= 3).
/linux-6.14.4/tools/memory-model/Documentation/
Daccess-marking.txt75 3. Reads whose values feed into error-tolerant heuristics.
77 4. Writes setting values that feed into error-tolerant heuristics.
131 Reads Feeding Into Error-Tolerant Heuristics
152 Writes Setting Values Feeding Into Error-Tolerant Heuristics
154 The values read into error-tolerant heuristics come from somewhere,
/linux-6.14.4/drivers/net/can/ctucanfd/
DKconfig30 modified to be CAN FD frames tolerant on MicroZed Zynq based
/linux-6.14.4/arch/powerpc/mm/ptdump/
Dbook3s64.c71 .set = "tolerant",
/linux-6.14.4/drivers/gpu/drm/i915/
Di915_mitigations.c47 /* Be tolerant of leading/trailing whitespace */ in mitigations_set()
/linux-6.14.4/Documentation/devicetree/bindings/i3c/
Di3c.yaml101 not tolerant to high frequencies
/linux-6.14.4/Documentation/filesystems/
Dubifs.rst65 Similarly to JFFS2, UBIFS is tolerant of unclean reboots and power-cuts.
Dfiemap.rst185 structure directly. Filesystem handlers should be tolerant to signals and return
/linux-6.14.4/Documentation/gpu/
Dvgaarbiter.rst85 a bit, but makes the arbiter more tolerant to user space problems and able
/linux-6.14.4/drivers/phy/intel/
Dphy-intel-lgm-emmc.c99 * failure cases are found which indicates we should be more tolerant in intel_emmc_phy_power()
Dphy-intel-keembay-emmc.c120 * failure cases are found which indicates we should be more tolerant in keembay_emmc_phy_power()
/linux-6.14.4/Documentation/admin-guide/
Dkernel-parameters.rst89 The special case-tolerant group name "all" has a meaning of selecting all CPUs,
/linux-6.14.4/drivers/phy/rockchip/
Dphy-rockchip-emmc.c174 * failure cases are found which indicates we should be more tolerant in rockchip_emmc_phy_power()
/linux-6.14.4/drivers/usb/serial/
Dcyberjack.c281 /* "+=" is probably more fault tolerant than "=" */ in cyberjack_read_int_callback()
Dark3116.c668 * On my chip, all signals seem to be 3.3V, but 5V tolerant. But that
Dch341.c233 * Note that this makes the receiver more tolerant to errors. in ch341_get_divisor()
/linux-6.14.4/Documentation/arch/powerpc/
Deeh-pci-error-recovery.rst319 Ext3fs seems to be tolerant, retrying reads/writes until it does
/linux-6.14.4/Documentation/PCI/
Dpci-error-recovery.rst58 of the current Linux file systems are not tolerant of disconnection
/linux-6.14.4/net/ethernet/
Deth.c183 * won't work for fault tolerant netware but does for the rest. in eth_type_trans()
/linux-6.14.4/drivers/gpu/drm/radeon/
Dr500_reg.h590 /* 78a8 appears to be some kind of (reasonably tolerant) clock?
/linux-6.14.4/include/linux/
Dif_vlan.h711 * 802.2 SSAP/DSAP. This won't work for fault tolerant netware in vlan_set_encap_proto()
/linux-6.14.4/Documentation/driver-api/media/drivers/
Dzoran.rst389 the LML33 works, the DC10+/DC30+ will work too. They're most tolerant to
/linux-6.14.4/drivers/hid/
Dhid-roccat-kone.c722 /* be tolerant about not getting chrdev */ in kone_init_specials()
/linux-6.14.4/Documentation/driver-api/gpio/
Ddriver.rst385 These kinds of irqchips are inherently realtime tolerant as they are
/linux-6.14.4/drivers/gpu/drm/tilcdc/
Dtilcdc_crtc.c240 * 5% is an arbitrary value - LCDs are usually quite tolerant in tilcdc_crtc_set_clk()

12