Home
last modified time | relevance | path

Searched refs:lose (Results 1 – 25 of 51) sorted by relevance

123

/Linux-v5.4/Documentation/devicetree/bindings/gpio/
Dgpio-omap.txt31 so will never lose its logic state.
/Linux-v5.4/Documentation/filesystems/
Docfs2.txt69 This means that if you lose your power, you will lose
Daffs.txt30 gain above 4K seems not really worth the price, so you don't lose too
/Linux-v5.4/Documentation/media/uapi/dvb/
Dfe-set-tone.rst51 setting a tone may interfere on other devices, as they may lose the
Dfe-set-voltage.rst54 setting a voltage level may interfere on other devices, as they may lose
/Linux-v5.4/include/trace/events/
Drxrpc.h950 rxrpc_serial_t serial, u8 flags, bool retrans, bool lose),
952 TP_ARGS(call, seq, serial, flags, retrans, lose),
962 __field(bool, lose )
973 __entry->lose = lose;
984 __entry->lose ? " *LOSE*" : "")
/Linux-v5.4/Documentation/admin-guide/mm/
Dsoft-dirty.rst36 there is still a scenario when we can lose soft dirty bits -- a task
/Linux-v5.4/Documentation/power/
Dswsusp.rst29 they won't be accessible after resume and you may lose data, as though
401 anything, not even read-only mount, or you are going to lose your
441 I suspend to disk, I can lose data unless the filesystem has been mounted
445 That's right ... if you disconnect that device, you may lose data.
446 In fact, even with "-o sync" you can lose data if your programs have
/Linux-v5.4/drivers/usb/core/
DKconfig26 devices that lose power get reenumerated as if they had been
/Linux-v5.4/net/rxrpc/
Doutput.c387 static int lose; in rxrpc_send_data_packet() local
388 if ((lose++ & 7) == 7) { in rxrpc_send_data_packet()
Dinput.c1215 static int lose; in rxrpc_input_packet() local
1216 if ((lose++ & 7) == 7) { in rxrpc_input_packet()
/Linux-v5.4/drivers/mmc/host/
Ddavinci_mmc.c744 bool lose = true; in mmc_davinci_set_ios() local
753 lose = false; in mmc_davinci_set_ios()
758 if (lose) in mmc_davinci_set_ios()
/Linux-v5.4/Documentation/hwmon/
Dw83793.rst25 This parameter is not recommended, it will lose motherboard specific
/Linux-v5.4/Documentation/input/joydev/
Djoystick-api.rst135 is much safer since it can't lose sync with the driver. As you would
199 If time between reads is enough to fill the queue and lose an event,
/Linux-v5.4/Documentation/networking/dsa/
Dbcm_sf2.rst22 fail-over not to lose packets during a MoCA role re-election, as well as out of
/Linux-v5.4/Documentation/admin-guide/laptops/
Dlaptop-mode.rst57 so that you won't lose any data at the end of your battery life.
126 comfortable with. Worst case, it's possible that you could lose this
241 # comfortable with. Worst case, it's possible that you could lose this
355 # comfortable with. Worst case, it's possible that you could lose this
/Linux-v5.4/Documentation/i2c/
Dfault-codes.rst43 Returned by I2C adapters when they lose arbitration in master
/Linux-v5.4/arch/m68k/q40/
DREADME19 When something blocks interrupts (HD) it will lose some of them, so far
/Linux-v5.4/Documentation/networking/
Dtls-offload.rst194 In presence of packet drops or network packet reordering, the device may lose
265 In particular the device should not lose synchronization
302 the device will lose synchronization with the stream.
/Linux-v5.4/Documentation/admin-guide/device-mapper/
Dstatistics.rst176 statistics does not want to lose any statistics (those updated
/Linux-v5.4/Documentation/x86/
Dkernel-stacks.rst144 The most important property of this method is that we _never_ lose
/Linux-v5.4/Documentation/trace/
Dmmiotrace.rst83 Check that mmiotrace did not lose events due to a buffer filling up. Either::
Dring-buffer-design.txt57 will stop writing to the buffer. This will lose most recent events.
61 overwrite the older data. This will lose the oldest events.
/Linux-v5.4/Documentation/input/devices/
Diforce-protocol.rst279 QUERY = 43 ('C')lose
/Linux-v5.4/Documentation/fb/
Dsstfb.rst175 patterns at the border of your windows (the pixels lose the lowest

123