Home
last modified time | relevance | path

Searched refs:recovery (Results 1 – 25 of 264) sorted by relevance

1234567891011

/linux-6.3-rc2/drivers/target/iscsi/
A Discsi_target_datain_values.c98 next_burst_len = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
100 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_yes_and_yes()
139 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
147 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_yes()
197 read_data_done = (!dr->recovery) ? in iscsit_set_datain_values_no_and_yes()
258 if (!dr->recovery) { in iscsit_set_datain_values_no_and_yes()
266 if (!dr->recovery) { in iscsit_set_datain_values_no_and_yes()
354 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_no()
367 if (!dr->recovery) { in iscsit_set_datain_values_yes_and_no()
457 if (!dr->recovery) { in iscsit_set_datain_values_no_and_no()
[all …]
/linux-6.3-rc2/include/linux/qed/
A Dqede_rdma.h53 int qede_rdma_dev_add(struct qede_dev *dev, bool recovery);
56 void qede_rdma_dev_remove(struct qede_dev *dev, bool recovery);
62 bool recovery) in qede_rdma_dev_add() argument
70 bool recovery) {} in qede_rdma_dev_remove() argument
/linux-6.3-rc2/drivers/md/
A Dmd.c1941 &mddev->recovery)) in super_1_validate()
4754 unsigned long recovery = mddev->recovery; in action_show() local
5914 mddev->recovery = 0; in md_run()
6173 mddev->recovery = 0; in md_clean()
6297 &mddev->recovery)); in md_set_readonly()
6360 &mddev->recovery))); in do_md_stop()
7581 &mddev->recovery), in md_ioctl()
8953 &mddev->recovery)); in md_do_sync()
9059 &mddev->recovery)) in md_do_sync()
9236 &mddev->recovery)) in md_start_sync()
[all …]
A Ddm-raid.c3243 set_bit(MD_RECOVERY_FROZEN, &rs->md.recovery); in raid_ctr()
3367 if (test_bit(MD_RECOVERY_FROZEN, &recovery)) in decipher_sync_action()
3371 if (!test_bit(MD_RECOVERY_DONE, &recovery) && in decipher_sync_action()
3374 if (test_bit(MD_RECOVERY_RESHAPE, &recovery)) in decipher_sync_action()
3377 if (test_bit(MD_RECOVERY_SYNC, &recovery)) { in decipher_sync_action()
3380 if (test_bit(MD_RECOVERY_CHECK, &recovery)) in decipher_sync_action()
3385 if (test_bit(MD_RECOVERY_RECOVER, &recovery)) in decipher_sync_action()
3516 unsigned long recovery; in raid_status() local
3538 recovery = rs->md.recovery; in raid_status()
3685 recovery = rs->md.recovery; in raid_status()
[all …]
A Draid10.c191 &conf->mddev->recovery)) { in r10buf_pool_alloc()
490 &rdev->mddev->recovery); in raid10_end_write_request()
2046 set_bit(MD_RECOVERY_INTR, &mddev->recovery); in raid10_error()
2364 &rdev->mddev->recovery); in end_sync_write()
2573 &rdev->mddev->recovery); in fix_recovery_read_error()
2596 &mddev->recovery); in fix_recovery_read_error()
2698 &rdev->mddev->recovery); in r10_sync_page_io()
3626 &mddev->recovery)) in raid10_sync_request()
3689 &mddev->recovery)) { in raid10_sync_request()
4701 mddev->recovery = 0; in raid10_start_reshape()
[all …]
/linux-6.3-rc2/Documentation/networking/devlink/
A Ddevlink-health.rst23 attributes of the health reporting and recovery procedures.
50 * Auto recovery attempt is being done. Depends on:
52 - Auto-recovery configuration
80 * Configure reporter's generic parameters (like: disable/enable auto recovery)
81 * Invoke recovery procedure
95 - Triggers reporter's recovery procedure.
98 event in terms of recovery flow should follow closely that of a real
A Dsfc.rst47 * - ``coproc.recovery``
49 - SmartNIC application co-processor (APU) recovery operating system version.
/linux-6.3-rc2/Documentation/ABI/testing/
A Dsysfs-class-remoteproc83 copy the dump. Also recovery process will not proceed until
86 What: /sys/class/remoteproc/.../recovery
89 Description: Remote processor recovery mechanism
91 Reports the recovery mechanism of the remote processor,
99 processor crashes while recovery is disabled, it will
100 be automatically recovered too as soon as recovery is enabled.
/linux-6.3-rc2/drivers/net/wireless/ath/ath6kl/
A Drecovery.c100 struct ath6kl_fw_recovery *recovery = &ar->fw_recovery; in ath6kl_recovery_init() local
103 INIT_WORK(&recovery->recovery_work, ath6kl_recovery_work); in ath6kl_recovery_init()
104 recovery->seq_num = 0; in ath6kl_recovery_init()
105 recovery->hb_misscnt = 0; in ath6kl_recovery_init()
/linux-6.3-rc2/tools/testing/selftests/drivers/net/bonding/
A DMakefile9 mode-1-recovery-updelay.sh \
10 mode-2-recovery-updelay.sh \
/linux-6.3-rc2/Documentation/devicetree/bindings/sound/
A Dst,sta32x.txt44 If present, thermal warning recovery is enabled.
46 - st,fault-detect-recovery:
47 If present, fault detect recovery is enabled.
52 - st,fault-detect-recovery:
53 If present, then fault recovery will be enabled.
/linux-6.3-rc2/Documentation/PCI/
A Dpci-error-recovery.rst26 of a bus disconnection, and then performing error recovery.
29 Reporting and recovery is performed in several steps. First, when
61 device drivers already handle very similar recovery procedures;
75 and the actual recovery steps taken are platform dependent. The
164 then recovery proceeds to STEP 4 (Slot Reset).
212 segment, and thus invalidate the recovery that other devices
232 Same as above. Total failure, no recovery even after
273 for recovery.
346 a new error recovery sequence.
383 That is, the recovery API only requires that:
[all …]
A Dpcieaer-howto.rst43 - Performs error recovery actions.
162 PCI error-recovery callbacks
167 when performing error recovery actions.
172 pci-error-recovery.txt except pci express specific parts (e.g.
173 reset_link). Pls. refer to pci-error-recovery.txt for detailed
184 require any recovery actions. The AER driver clears the device's
210 function. If reset_link is not NULL, recovery function will use it
245 error recovery handler (pci_driver->err_handler is equal to NULL)?
257 Fatal error recovery will fail if the errors are reported by the
282 Debugging PCIe AER error recovery code is quite difficult because it
/linux-6.3-rc2/drivers/ata/
A Dpata_cs5520.c40 int recovery; member
70 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
75 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
79 (cs5520_pio_clocks[pio].recovery << 4) | in cs5520_set_timings()
/linux-6.3-rc2/arch/arm64/boot/dts/marvell/
A Darmada-3720-uDPU.dts23 i2c1_recovery_pins: i2c1-recovery-pins {
31 pinctrl-names = "default", "recovery";
/linux-6.3-rc2/Documentation/i2c/
A Dgpio-fault-injection.rst36 master under test should detect this condition and trigger a bus recovery (see
38 core (see 'struct bus_recovery_info'). However, the bus recovery will not
47 device. Bus recovery should be able to fix these situations. But please note:
51 and will init a bus recovery on its own. If you want to implement bus recovery
64 recovery. This time, however, it should succeed and the device should release
82 This is why bus recovery (up to 9 clock pulses) must either check SDA or send
/linux-6.3-rc2/Documentation/devicetree/bindings/misc/
A Dxlnx,tmr-inject.yaml16 recovery logic is working properly.
31 recovery.
A Dxlnx,tmr-manager.yaml14 TMR subsystem state, including fault detection and error recovery. The core
31 recovery.
/linux-6.3-rc2/Documentation/devicetree/bindings/input/touchscreen/
A Dti,tsc2005.yaml42 ti,esd-recovery-timeout-ms:
99 ti,esd-recovery-timeout-ms = <8000>;
126 ti,esd-recovery-timeout-ms = <8000>;
/linux-6.3-rc2/drivers/net/ethernet/qlogic/qede/
A Dqede_rdma.c86 int qede_rdma_dev_add(struct qede_dev *edev, bool recovery) in qede_rdma_dev_add() argument
94 if (recovery) in qede_rdma_dev_add()
116 void qede_rdma_dev_remove(struct qede_dev *edev, bool recovery) in qede_rdma_dev_remove() argument
122 if (!recovery) { in qede_rdma_dev_remove()
/linux-6.3-rc2/arch/arm/boot/dts/
A Dox810se-wd-mbwe.dts43 recovery {
44 label = "recovery";
/linux-6.3-rc2/drivers/i2c/busses/
A Di2c-uniphier.c161 bool recovery = false; in uniphier_i2c_master_xfer_one() local
175 recovery = true; in uniphier_i2c_master_xfer_one()
183 recovery = true; in uniphier_i2c_master_xfer_one()
188 if (recovery) in uniphier_i2c_master_xfer_one()
/linux-6.3-rc2/Documentation/admin-guide/
A Dfilesystem-monitoring.rst13 sysadmin, start recovery) when a file system problem is detected.
20 early file system problem detection and reporting recovery tools.
76 specific application can use that information to attempt a recovery
/linux-6.3-rc2/Documentation/ABI/stable/
A Dsysfs-devices-node198 ignored by memory error recovery attempt, usually because
200 gives up the recovery.
207 failed by memory error recovery attempt. This usually means
208 a key recovery operation failed.
215 delayed by memory error recovery attempt. Delayed poisoned
223 recovered by memory error recovery attempt.
/linux-6.3-rc2/Documentation/devicetree/bindings/power/reset/
A Dreboot-mode.yaml24 - recovery: Android Recovery mode, it is a mode to format the device or update a new image.
45 mode-recovery = <1>;

Completed in 79 milliseconds

1234567891011