Searched full:damaged (Results 1 – 25 of 71) sorted by relevance
123
| /linux-6.14.4/Documentation/devicetree/bindings/regulator/ |
| D | regulator.yaml | 144 damaged. Recovery actions should be initiated. Zero can be passed to
165 damaged. Recovery actions should be initiated. Zero can be passed to
187 it gets damaged. Recovery actions should be initiated. Zero can be passed
215 gets damaged. Recovery actions should be initiated. Zero can be passed to
|
| /linux-6.14.4/drivers/mtd/ubi/ |
| D | kapi.c | 440 * If the volume is damaged because of an interrupted update this function just
531 * If the volume is damaged because of an interrupted update this function just
617 * If the volume is damaged because of an interrupted update this function just
678 * case of failure. If the volume is damaged because of an interrupted update
713 * damaged because of an interrupted update, %-EBADMSG if the logical
752 * error code in case of failure. If the volume is damaged because of an
|
| D | cdev.c | 126 ubi_warn(vol->ubi, "update of volume %d not finished, volume is damaged", in vol_cdev_release()
189 ubi_err(vol->ubi, "damaged volume, update marker is set"); in vol_cdev_read()
|
| /linux-6.14.4/arch/sh/include/cpu-sh2/cpu/ |
| D | watchdog.h | 58 * Note: Due to the brain-damaged nature of this register, in sh_wdt_write_rstcsr()
|
| /linux-6.14.4/Documentation/devicetree/bindings/leds/backlight/ |
| D | common.yaml | 32 that a LED can be made so bright that it gets damaged or causes damage
|
| /linux-6.14.4/include/linux/mtd/ |
| D | ubi.h | 67 * is set, the contents of the volume is certainly damaged and a new volume
74 * o the @upd_marker field means that the volume is damaged because of an
|
| /linux-6.14.4/tools/testing/selftests/sync/ |
| D | sync_stress_parallelism.c | 62 "Counter got damaged!\n"); in test_stress_two_threads_shared_timeline_thread()
|
| /linux-6.14.4/arch/sparc/include/asm/ |
| D | swift.h | 11 /* Swift is so brain damaged, here is the mmu control register. */
|
| /linux-6.14.4/Documentation/power/ |
| D | freezing-of-tasks.rst | 117 1. The principal reason is to prevent filesystems from being damaged after
124 from the image (otherwise the filesystems will be damaged in a nasty way,
|
| /linux-6.14.4/drivers/usb/host/ |
| D | uhci-grlib.c | 167 * This routine may be called in a damaged or failing kernel. Hence we
|
| D | uhci-platform.c | 168 * This routine may be called in a damaged or failing kernel. Hence we
|
| D | uhci-pci.c | 160 * This routine may be called in a damaged or failing kernel. Hence we
|
| /linux-6.14.4/Documentation/filesystems/ |
| D | ocfs2.rst | 81 filesystem will not be damaged though, thanks to the
|
| D | hpfs.rst | 39 misidentified and damaged under some circumstances.
327 could be damaged
|
| /linux-6.14.4/drivers/gpu/drm/mcde/ |
| D | mcde_drv.c | 47 * - Enabled damaged rectangles using drm_plane_enable_fb_damage_clips()
48 * so we can selectively just transmit the damaged area to a
|
| /linux-6.14.4/scripts/dtc/libfdt/ |
| D | fdt_overlay.c | 1083 * The overlay has been damaged, erase its magic. in fdt_overlay_apply()
1091 * The overlay might have been damaged, erase its magic. in fdt_overlay_apply()
1096 * The base device tree might have been damaged, erase its in fdt_overlay_apply()
|
| /linux-6.14.4/Documentation/networking/diagnostic/ |
| D | twisted_pair_layer1_diagnostics.rst | 385 - An **Open Circuit** result might not only indicate a damaged or disconnected
423 - An **Open Circuit** result typically indicates that the cable is damaged or
446 - **Next Steps**: Replace or repair the damaged cable. Inspect the cable for
|
| /linux-6.14.4/drivers/pnp/pnpacpi/ |
| D | core.c | 271 /* clear out the damaged flags */ in pnpacpi_add_device()
|
| /linux-6.14.4/Documentation/networking/ |
| D | 6pack.rst | 42 Damaged packets that the TNC has received from the PC are not transmitted.
|
| D | udplite.rst | 10 (video, VoIP) over wireless networks, as partly damaged packets can still be
|
| /linux-6.14.4/drivers/net/ethernet/netronome/nfp/nfpcore/ |
| D | nfp_mutex.c | 278 /* Verify that the lock marker is not damaged */ in nfp_cpp_mutex_trylock()
|
| /linux-6.14.4/Documentation/devicetree/bindings/leds/ |
| D | common.yaml | 168 It could happen that an LED is made so bright that it gets damaged or
|
| /linux-6.14.4/include/linux/regulator/ |
| D | driver.h | 46 /* Hardware is probably damaged/inoperable */
96 * still believed to not be damaged but that a board sepcific
|
| /linux-6.14.4/drivers/net/wireless/ath/carl9170/ |
| D | fw.c | 415 dev_err(&ar->udev->dev, "damaged firmware (%d).\n", err); in carl9170_parse_firmware()
|
| /linux-6.14.4/drivers/net/wireless/intersil/p54/ |
| D | eeprom.c | 206 wiphy_err(dev->wiphy, "Disabling totally damaged %d GHz band\n", in p54_generate_band()
331 "Unsupported or damaged EEPROM detected. " in p54_generate_channel_lists()
|
123