| /Linux-v4.19/Documentation/devicetree/bindings/gpio/ |
| D | gpio-omap.txt | 27 so will never lose its logic state.
|
| /Linux-v4.19/Documentation/media/uapi/dvb/ |
| D | fe-set-tone.rst | 44 setting a tone may interfere on other devices, as they may lose the
|
| D | fe-set-voltage.rst | 47 setting a voltage level may interfere on other devices, as they may lose
|
| /Linux-v4.19/Documentation/filesystems/ |
| D | ocfs2.txt | 69 This means that if you lose your power, you will lose
|
| D | affs.txt | 30 gain above 4K seems not really worth the price, so you don't lose too
|
| /Linux-v4.19/include/trace/events/ |
| D | rxrpc.h | 953 rxrpc_serial_t serial, u8 flags, bool retrans, bool lose),
955 TP_ARGS(call, seq, serial, flags, retrans, lose),
965 __field(bool, lose )
976 __entry->lose = lose;
987 __entry->lose ? " *LOSE*" : "")
|
| /Linux-v4.19/Documentation/admin-guide/mm/ |
| D | soft-dirty.rst | 36 there is still a scenario when we can lose soft dirty bits -- a task
|
| /Linux-v4.19/Documentation/power/ |
| D | swsusp.txt | 22 * they won't be accessible after resume and you may lose data, as though
354 anything, not even read-only mount, or you are going to lose your
391 I suspend to disk, I can lose data unless the filesystem has been mounted
394 A: That's right ... if you disconnect that device, you may lose data.
395 In fact, even with "-o sync" you can lose data if your programs have
|
| /Linux-v4.19/net/rxrpc/ |
| D | output.c | 377 static int lose; in rxrpc_send_data_packet() local
378 if ((lose++ & 7) == 7) { in rxrpc_send_data_packet()
|
| D | input.c | 1195 static int lose; in rxrpc_input_packet() local
1196 if ((lose++ & 7) == 7) { in rxrpc_input_packet()
|
| /Linux-v4.19/drivers/usb/core/ |
| D | Kconfig | 25 devices that lose power get reenumerated as if they had been
|
| /Linux-v4.19/Documentation/s390/ |
| D | DASD | 62 the partition /dev/dd?1 instead of the whole volume. You only lose 3kB
|
| /Linux-v4.19/drivers/mmc/host/ |
| D | davinci_mmc.c | 757 bool lose = true; in mmc_davinci_set_ios() local
766 lose = false; in mmc_davinci_set_ios()
771 if (lose) in mmc_davinci_set_ios()
|
| /Linux-v4.19/Documentation/hwmon/ |
| D | w83793 | 20 This parameter is not recommended, it will lose motherboard specific
|
| /Linux-v4.19/Documentation/input/joydev/ |
| D | joystick-api.rst | 135 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-v4.19/Documentation/networking/dsa/ |
| D | bcm_sf2.txt | 21 fail-over not to lose packets during a MoCA role re-election, as well as out of
|
| /Linux-v4.19/Documentation/laptops/ |
| D | laptop-mode.txt | 55 so that you won't lose any data at the end of your battery life.
124 comfortable with. Worst case, it's possible that you could lose this
238 # comfortable with. Worst case, it's possible that you could lose this
353 # comfortable with. Worst case, it's possible that you could lose this
|
| /Linux-v4.19/Documentation/i2c/ |
| D | fault-codes | 39 Returned by I2C adapters when they lose arbitration in master
|
| /Linux-v4.19/arch/m68k/q40/ |
| D | README | 19 When something blocks interrupts (HD) it will lose some of them, so far
|
| /Linux-v4.19/Documentation/x86/ |
| D | kernel-stacks | 133 The most important property of this method is that we _never_ lose
|
| /Linux-v4.19/Documentation/input/devices/ |
| D | iforce-protocol.rst | 279 QUERY = 43 ('C')lose
|
| /Linux-v4.19/Documentation/fb/ |
| D | sstfb.txt | 141 patterns at the border of your windows (the pixels lose the lowest
|
| /Linux-v4.19/Documentation/device-mapper/ |
| D | statistics.txt | 173 statistics does not want to lose any statistics (those updated
|
| /Linux-v4.19/Documentation/trace/ |
| D | mmiotrace.rst | 83 Check that mmiotrace did not lose events due to a buffer filling up. Either::
|
| /Linux-v4.19/Documentation/bpf/ |
| D | bpf_design_QA.rst | 135 workaround would be acceptable. Turned out that programs lose performance
|
