Home
last modified time | relevance | path

Searched full:again (Results 1 – 25 of 380) sorted by relevance

12345678910>>...16

/Documentation/ABI/testing/
Dsysfs-block-aoe26 cannot come up again until it has been closed. The "up,kickme"
29 commands waiting for a response. It will retry again after being
Ddebugfs-ec20 not get switched on again after you did a wrong write.
/Documentation/admin-guide/
Dclearing-warn-once.rst8 clears the state and allows the warnings to print once again.
/Documentation/i2c/
Dgpio-fault-injection.rst24 change its state to either force it low or to release it again. So, by using
34 change its state to either force it low or to release it again. So, by using
39 succeed because SDA is still pinned low until you manually release it again
73 The injector will again stop at one ACK phase, so the device will keep SDA low
/Documentation/filesystems/nfs/
Dfault_injection.txt53 again.
59 the file again.
/Documentation/usb/
Dchipidea.rst65 5) Remove B-device(unplug micro B plug) and insert again in 10 seconds,
66 A-device should enumerate B-device again.
68 6) Remove B-device(unplug micro B plug) and insert again after 10 seconds,
/Documentation/powerpc/
Ddawr-power9.rst58 migrated back to the POWER8 host, it will start working again.
76 machine once again safe from crashing.
/Documentation/devicetree/bindings/power/supply/
Dmaxim,ds2760.txt21 this time expires, the values are read again from
/Documentation/i2c/busses/
Di2c-via.rst32 Turn USB support on, and try again.
/Documentation/hwmon/
Dabituguru-datasheet.rst20 is once again reverse engineered by Olle the additional databanks have been
41 later on attached again data-port will hold 0x08, more about this later.
107 wait for to DATA to hold 0x08 again indicating that it wants / is ready for
110 Once DATA holds 0x08 again write the sensor address to CMD.
127 if your program / driver is unloaded and later loaded again the detection
147 if your program / driver is unloaded and later loaded again the detection
Dg760a.rst30 from the measured speed pulse period by assuming again a 32kHz clock
/Documentation/s390/
Ddriver-model.rst31 former subchannel. The ccw devices will be moved again to a proper subchannel
32 if they become operational again on that subchannel.
199 * In disconnected state, device operational again (CIO_OPER). The
255 again (only when offline). This is a generic ccwgroup mechanism (the driver does
/Documentation/locking/
Drt-mutex-design.rst66 to understand, let's use the previous example, with processes A, B, and C again.
182 And once again, to show how this can grow I will show the merging chains
183 again::
269 /* do something again */
277 in func4 in the "do something again" area, we have a locking that follows::
499 In both cases, the task will try again to acquire the lock. If it
504 could get the lock, then it will go back to sleep and wait to be woken again.
509 take the lock again, if it succeeds, then the task will return with the
/Documentation/networking/
Dx25-iface.txt114 netif_rx() later when netif_dropping is 0 again. In that case, delivery
121 when a previously congested backlog queue becomes empty again.
/Documentation/trace/
Dmmiotrace.rst93 try again. Buffers are enlarged by first seeing how large the current buffers
103 Then start again from the top.
131 entered. Here mmiotrace again marks the page as not present. The instruction
/Documentation/vm/
Dnuma.rst52 CPUs, memory and/or IO buses. And, again, memory accesses to memory on
63 In addition, for some architectures, again x86 is an example, Linux supports
149 specified CPU. Again, this is the same node from which default, local page
/Documentation/devicetree/bindings/input/touchscreen/
Dtsc2007.txt20 - ti,poll-period: how much time to wait (in milliseconds) before reading again the
/Documentation/media/uapi/dvb/
Daudio-pause.rst48 playing are paused. It is then possible to restart again decoding and
/Documentation/PCI/
Dpci-error-recovery.rst48 again notified, so that they may then perform any device setup/config
185 get the device working again.
193 This is the "early recovery" call. IOs are allowed again, but DMA is
195 start operations again, only to peek/poke at the device, extract diagnostic
219 normal driver operations again. There is no
298 cycle) and then call slot_reset() again. It the device still can't
/Documentation/virt/kvm/devices/
Ds390_flic.txt33 for userspace to try again with a bigger buffer.
129 will be suppressed until the mode is set again to ALL-Interruptions
/Documentation/process/
Dvolatile-considered-harmful.rst59 optimization, so, once again, volatile is unnecessary.
70 barrier, so, once again, volatile is unnecessary. Of course, busy-
/Documentation/driver-api/
Disa.rst107 isa_register_driver which can then unregister the device again.
110 everything is backed out again and the error, or -ENODEV, is returned.
/Documentation/device-mapper/
Ddm-bow.txt62 sector, if the sector is written to directly, it must be moved again.
74 to, the contents must first be backed up again.
/Documentation/
DDMA-API-HOWTO.txt512 * delay and try again later or
548 * delay and try again later or
594 Again, make sure DMA activity has already finished.
623 Then, if you wish to let the device get at the DMA area again,
658 * delay and try again later or
741 * delay and try again later or
760 * delay and try again later or
769 * delay and try again later or
800 * delay and try again later or
827 passes the command to the driver again later.
/Documentation/devicetree/bindings/power/reset/
Dgpio-poweroff.txt15 delay the GPIO is driver active again. If the power is still on and

12345678910>>...16