Searched full:retry (Results 1 – 25 of 74) sorted by relevance
123
| /Documentation/devicetree/bindings/ata/ |
| D | ceva,ahci-1v84.yaml | 77 ceva,p0-retry-params:
80 Retry interval timing value for port 0.
82 ceva,p0-retry-params = /bits/ 16 <RIT RCT>;
84 - description: RIT - Retry Interval Timer.
123 ceva,p1-retry-params:
126 Retry interval timing value for port 1.
128 ceva,pN-retry-params = /bits/ 16 <RIT RCT>;
130 - description: RIT - Retry Interval Timer.
156 - ceva,p0-retry-params
160 - ceva,p1-retry-params
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ |
| D | sbs,sbs-battery.yaml | 34 sbs,i2c-retry-count:
36 The number of times to retry I2C transactions on I2C IO failure.
40 sbs,poll-retry-count:
79 sbs,i2c-retry-count = <2>;
80 sbs,poll-retry-count = <10>;
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | adi,ltc4282.yaml | 83 adi,overcurrent-retry:
85 If set, enables the chip to auto-retry 256 timer cycles after an
89 adi,overvoltage-retry-disable:
91 If set, disables the chip to auto-retry 50ms after an Overvoltage fault.
95 adi,undervoltage-retry-disable:
97 If set, disables the chip to auto-retry 50ms after an Undervoltage fault.
|
| /Documentation/devicetree/bindings/i2c/ |
| D | i2c-arb-gpio-challenge.yaml | 47 6. Go back to 1 (until retry time has expired).
80 wait-retry-us:
112 wait-retry-us = <3000>;
122 sbs,poll-retry-count = <1>;
|
| D | google,cros-ec-i2c-tunnel.yaml | 62 sbs,poll-retry-count = <1>;
|
| /Documentation/locking/ |
| D | seqlock.rst | 9 lockless readers (read-only retry loops), and no writer starvation. They
11 reader wants a consistent set of information and is willing to retry if
19 the reader must retry.
196 retry if a writer is in progress by detecting change in the sequence
219 starvation (too much retry loops) in case of a sharp spike in write
223 full locking read and no retry loop is necessary::
|
| D | ww-mutex-design.rst | 149 retry:
173 /* we lost out in a seqno race, lock and retry.. */
176 goto retry;
206 /* we lost out in a seqno race, lock and retry.. */
260 method #3 below. The backoff/retry procedure will be a bit more involved, since
294 retry:
310 goto retry;
|
| /Documentation/devicetree/bindings/ipmi/ |
| D | ipmi-ipmb.yaml | 30 retry-time:
64 retry-time = <250>;
|
| /Documentation/admin-guide/ |
| D | xfs.rst | 393 or simply retry forever.
444 i.e. no retries, no retry timeout. This will always allow unmount to
447 If set to 0, the configured retry behaviour will continue until all
450 filesystem from ever unmounting fully in the case of "retry forever"
455 removed by the unmounting filesystem before a "retry forever" error
463 specific handlers defined. Where multiple retry constraints are configured for
464 a single error, the first retry configuration that expires will cause the error
471 the filesystem will propagate the error. The retry count for a given
475 Setting the value to "-1" will cause XFS to retry forever for this
481 Setting the value to "N" (where 0 < N < Max) will make XFS retry the
[all …]
|
| /Documentation/ABI/stable/ |
| D | sysfs-devices-system-xen_memory | 9 A value of zero means retry forever and is the default one.
28 to retry with a 'schedule_delay' delay.
|
| /Documentation/fault-injection/ |
| D | nvme-fault-injection.rst | 5 enabled, the default NVME_SC_INVALID_OPCODE with no retry will be
7 code and no retry flag via the debugfs. The list of Generic Command
16 Example 1: Inject default status code with no retry
71 Example 2: Inject default status code with retry
|
| /Documentation/ABI/testing/ |
| D | sysfs-devices-platform-stratix10-rsu | 82 (RO) the current image's retry counter, which is used by
120 1 firmware to reset current image retry
173 (RO) max retry parameter is stored in the firmware
|
| D | debugfs-pfo-nx-crypto | 19 recorded here (the hcall will retry until -EBUSY goes away).
|
| D | sysfs-block-aoe | 29 commands waiting for a response. It will retry again after being
|
| /Documentation/devicetree/bindings/soc/ti/ |
| D | keystone-navigator-dma.txt | 59 - ti,rx-retry-timeout: Number of dma cycles to wait before retry on buffer
|
| /Documentation/admin-guide/perf/ |
| D | alibaba_pmu.rst | 35 - Group 2: PMU Retry Counters. This group has 10 counters, that intend to
36 count the total retry number of each type of uncorrectable error.
|
| /Documentation/hwmon/ |
| D | w83l785ts.rst | 42 we don't really know. The driver will retry a given number of times
|
| /Documentation/core-api/ |
| D | dma-attributes.rst | 115 drivers which handle failures (eg, retry later) have no problems with them,
117 problem at all, depending on the implementation of the retry mechanism.
|
| /Documentation/networking/net_cachelines/ |
| D | inet_connection_sock.rst | 38 struct_icsk_ack_u8 retry write_mostly read_write …
|
| /Documentation/gpu/amdgpu/ |
| D | debugging.rst | 26 …[gfxhub0] no-retry page fault (src_id:0 ring:24 vmid:3 pasid:32777, for process glxinfo pid 2424 t…
|
| /Documentation/scsi/ |
| D | scsi_eh.rst | 107 issue a retry scmd->allowed + 1 times. Asynchronous aborts are not invoked
110 retry which failed), when retries are exceeded, or when the EH deadline is
247 either retry or error-finish (notify upper layer of failure) recovered
296 - if retry is necessary, scmd is requeued using
|
| /Documentation/gpu/ |
| D | drm-vm-bind-locking.rst | 88 ``mm/mmu_notifier.c`` as a "Collision-retry read-side/write-side
432 retry:
456 goto retry;
494 // sequence number and will always cause a retry. When all
526 If using an invalidated userptr list like this, the retry check in the
|
| /Documentation/arch/powerpc/ |
| D | cxlflash.rst | 266 an asynchronous AFU reset. Should the user choose to retry the operation,
268 can either retry the operation or treat it as a failure.
324 an asynchronous AFU reset. Should the user choose to retry the operation,
326 can either retry the operation or treat it as a failure.
|
| D | transactional_memory.rst | 41 /* Retry the transaction if it failed because it conflicted with
61 abort handler can check the cause of the failure, and retry.
|
| /Documentation/driver-api/media/ |
| D | cec-core.rst | 202 depends on whether this transmit is a retry, a message from a new initiator or
289 hardware retry can just set the counter corresponding to the transmit error
290 to 1, if the hardware does support retry then either set these counters to
|
123