Home
last modified time | relevance | path

Searched refs:after (Results 1 – 200 of 848) sorted by relevance

12345

/linux-4.4.14/scripts/
Dconfig25 --enable-after|-E beforeopt option
26 Enable option directly after other option
27 --disable-after|-D beforeopt option
28 Disable option directly after other option
29 --module-after|-M beforeopt option
30 Turn option into module directly after other option
/linux-4.4.14/tools/testing/selftests/vm/
Dthuge-gen.c142 unsigned long before, after; in test_mmap() local
151 after = read_free(size); in test_mmap()
153 before, after, before - after, size); in test_mmap()
154 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_mmap()
163 unsigned long before, after; in test_shmget() local
182 after = read_free(size); in test_shmget()
185 before, after, before - after, size); in test_shmget()
186 assert(size == getpagesize() || (before - after) == NUM_PAGES); in test_shmget()
/linux-4.4.14/sound/usb/
Dhelper.c44 void *snd_usb_find_desc(void *descstart, int desclen, void *after, u8 dtype) in snd_usb_find_desc() argument
56 if (p[1] == dtype && (!after || (void *)p > after)) { in snd_usb_find_desc()
67 void *snd_usb_find_csint_desc(void *buffer, int buflen, void *after, u8 dsubtype) in snd_usb_find_csint_desc() argument
69 unsigned char *p = after; in snd_usb_find_csint_desc()
Dhelper.h6 void *snd_usb_find_desc(void *descstart, int desclen, void *after, u8 dtype);
7 void *snd_usb_find_csint_desc(void *descstart, int desclen, void *after, u8 dsubtype);
/linux-4.4.14/tools/testing/selftests/powerpc/pmu/ebb/
Dpmae_handling_test.c29 static uint64_t before, after; variable
49 after = mfspr(SPRN_MMCR0); in syscall_ebb_callee()
50 if (before != after) in syscall_ebb_callee()
90 printf("Saw MMCR0 before 0x%lx after 0x%lx\n", before, after); in test_body()
/linux-4.4.14/arch/powerpc/lib/
Drheap.c155 rh_block_t *after; in attach_free_block() local
169 after = NULL; in attach_free_block()
185 after = blk; in attach_free_block()
188 if (before != NULL && after != NULL) in attach_free_block()
196 if (after && e != after->start) in attach_free_block()
197 after = NULL; in attach_free_block()
200 if (before == NULL && after == NULL) { in attach_free_block()
214 if (before != NULL && after == NULL) { in attach_free_block()
220 if (before == NULL && after != NULL) { in attach_free_block()
221 after->start -= size; in attach_free_block()
[all …]
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-transport-srp12 Description: Number of seconds the SCSI layer will wait after a transport
21 Description: Number of seconds the SCSI layer will wait after a transport
37 Description: Number of seconds the SCSI layer will wait after a reconnect
55 after the fast_io_fail_tmo timer has fired and before the
56 "dev_loss_tmo" timer has fired; "lost" after the
Dsysfs-firmware-opal-elog27 entries than firmware can, so after you acknowledge
57 Shortly after acknowledging it, the log
/linux-4.4.14/mm/
DKconfig.debug18 Unmap pages from the kernel linear mapping after free_pages().
23 fill the pages with poison patterns after free_pages() and verify
26 that would result in incorrect warnings of memory corruption after
/linux-4.4.14/scripts/kconfig/
Dqconf.h126 ConfigItem(ConfigList *parent, ConfigItem *after, struct menu *m, bool v) in ConfigItem() argument
127 : Parent(parent, after), nextItem(0), menu(m), visible(v), goParent(false) in ConfigItem()
131 ConfigItem(ConfigItem *parent, ConfigItem *after, struct menu *m, bool v) in ConfigItem() argument
132 : Parent(parent, after), nextItem(0), menu(m), visible(v), goParent(false) in ConfigItem()
136 ConfigItem(ConfigList *parent, ConfigItem *after, bool v) in ConfigItem() argument
137 : Parent(parent, after), nextItem(0), menu(0), visible(v), goParent(true) in ConfigItem()
/linux-4.4.14/Documentation/devicetree/bindings/display/panel/
Dsamsung,s6e8aa0.txt12 - power-on-delay: delay after turning regulators on [ms]
13 - reset-delay: delay after reset sequence [ms]
14 - init-delay: delay after initialization sequence [ms]
Dsamsung,ld9040.txt14 - power-on-delay: delay after turning regulators on [ms]
15 - reset-delay: delay after reset sequence [ms]
/linux-4.4.14/scripts/coccinelle/misc/
Difcol.cocci1 /// Find confusingly indented code in or after an if. An if branch should
3 /// Sometimes, code after an if that is indented is actually intended to be
39 cocci.print_secs("after",p2)
Dcstptr.cocci40 msg = "ERROR: PTR_ERR applied after initialization to constant on line %s" % (p1[0].line)
/linux-4.4.14/net/netfilter/
Dnf_conntrack_seqadj.c85 if (after(ntohl(sack->start_seq) - seq->offset_before, in nf_ct_sack_block_adjust()
93 if (after(ntohl(sack->end_seq) - seq->offset_before, in nf_ct_sack_block_adjust()
182 if (after(ntohl(tcph->seq), this_way->correction_pos)) in nf_ct_seq_adjust()
187 if (after(ntohl(tcph->ack_seq) - other_way->offset_before, in nf_ct_seq_adjust()
225 return after(seq, this_way->correction_pos) ? in nf_ct_seq_offset()
Dnf_conntrack_proto_tcp.c489 if (after(tmp, *sack)) in tcp_sack()
594 && after(end, sender->td_end)) { in tcp_in_window()
641 after(end, sender->td_end - receiver->td_maxwin - 1); in tcp_in_window()
647 after(sack, receiver->td_end - MAXACKWINDOW(sender) - 1)); in tcp_in_window()
652 after(sack, receiver->td_end - MAXACKWINDOW(sender) - 1)) { in tcp_in_window()
665 if (after(end, sender->td_end)) { in tcp_in_window()
673 } else if (after(ack, sender->td_maxack)) in tcp_in_window()
680 if (receiver->td_maxwin != 0 && after(end, sender->td_maxend)) in tcp_in_window()
682 if (after(sack + win, receiver->td_maxend - 1)) { in tcp_in_window()
721 after(sack, receiver->td_end - MAXACKWINDOW(sender) - 1) ? "BUG" in tcp_in_window()
/linux-4.4.14/Documentation/m68k/
DREADME.buddha140 value 0 (Default after reset)
142 497ns Select (7 clock cycles) , IOR/IOW after 172ns (2 clock cycles)
148 639ns Select (9 clock cycles), IOR/IOW after 243ns (3 clock cycles)
152 781ns Select (11 clock cycles), IOR/IOW after 314ns (4 clock cycles)
156 355ns Select (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
160 355ns Select (5 clock cycles), IOR/IOW after 172ns (2 clock cycles)
164 355ns Select (5 clock cycles), IOR/IOW after 243ns (3 clock cycles)
168 1065ns Select (15 clock cycles), IOR/IOW after 314ns (4 clock cycles)
172 355ns Select, (5 clock cycles), IOR/IOW after 101ns (1 clock cycle)
178 781ns select, IOR/IOW after 4 clock cycles (=314ns) aktive.
/linux-4.4.14/Documentation/power/
Dsuspend-and-interrupts.txt11 suspend after the "late" phase of suspending devices (that is, after all of the
15 The rationale for doing so is that after the "late" phase of device suspend
20 not prepared for interrupts triggering after their devices had been suspended.
50 for it will be executed as usual after suspend_device_irqs(), even if the
88 already suspended. However, after suspend_device_irqs() interrupt handlers are
99 interrupts right after the "noirq" phase of suspending devices.
120 interrupts (interrupt handlers are invoked after suspend_device_irqs()) are
122 handlers are not invoked after suspend_device_irqs()).
Ds2ram.txt54 until after the hash is checked. You can check the hash against the current
55 devices again after more modules are loaded using sysfs:
76 Consequence is that after a resume (even if it is successful) your system
83 quickly after the resume failure. The trace option does not use the seconds
Dpci.txt403 a notification for the PCI subsystem after the source device has been
411 example, it is called right after the device has just been resumed), in which
425 after tasks have been frozen.
462 The pci_pm_suspend_noirq() routine is executed after suspend_device_irqs() has
548 The freezing of devices is carried out after enough memory has been freed (at
703 (when a hibernation image is about to be created), during power-off after
720 The suspend() callback is only executed during system suspend, after prepare()
746 The suspend_noirq() callback is only executed during system suspend, after
748 after device interrupts have been disabled by the PM core.
758 during hibernation, after prepare() callbacks have been executed for all devices
[all …]
Duserland-swsusp.txt41 the value of which will indicate whether the call returned after
42 creating the snapshot (1) or after restoring the system memory state
43 from it (0) (after resume the system finds itself finishing the
44 SNAPSHOT_CREATE_IMAGE ioctl() again); after the snapshot
92 to use the SNAPSHOT_UNFREEZE call after the system wakes up. This call
153 system MUST be powered off or rebooted after the snapshot
Dfreezing-of-tasks.txt56 If a freezable kernel thread fails to call try_to_freeze() after the freezer has
99 1. The principal reason is to prevent filesystems from being damaged after
105 on-disk data and metadata after the system memory state has been restored from
108 cause the on-disk filesystems' data and metadata to be modified after the
116 after the memory for the image has been freed, we don't want tasks to allocate
149 thawed after the driver's .resume() callback has run, so it won't be accessing
155 and should continue running without any problems after the restore (or resume
223 only after the entire suspend/hibernation sequence is complete.
Dnotifiers.txt5 before hibernation/suspend or after restore/resume, but they require the system
8 For example, device drivers may want to upload firmware to their devices after
Dswsusp.txt8 * If you do resume from initrd after your filesystems are mounted...
22 * they won't be accessible after resume and you may lose data, as though
228 after resume. swapoff -a; swapon -a may also be useful.
278 protect from leaking sensitive data after resume from suspend.
285 that after resume your sensitive data are accessible to all
287 for suspend. If you don't need swap after resume these data can remain
305 suspend image to prevent sensitive data from being stolen after
406 before suspending; then remount them after resuming.
432 after resume).
Dvideo.txt32 systems. Unfortunately, vbetool only runs after userland is resumed,
39 There are a few types of systems where video works after S3 resume:
142 IBM TP T41p s3_bios (2), switch to X after resume
148 IBM TP X32 none (1), but backlight is on and video is trashed after long suspend. s3_bios,s3_mode…
Dbasic-pm-debugging.txt81 /sys/power/pm_test , then after suspending devices the kernel will additionally
103 dmesg obtained after the failing test). Failure at this level usually means
109 after the test, so please take that into consideration). To find this driver,
121 It is also possible that the "devices" test will still fail after you have
186 Namely, after writing "freezer", "devices", "platform", "processors", or "core"
Dsuspend-and-cpuhotplug.txt104 after the entire cycle is complete (i.e., suspend + resume).
189 image for each CPU (after appropriate CPU type/model discovery using
212 discovery is performed and the right microcode is applied to the CPU after
225 This is the usual scenario encountered during a resume after a suspend.
/linux-4.4.14/net/ipv4/
Dtcp_input.c734 if (after(tp->snd_una, tp->rtt_seq)) { in tcp_rtt_estimator()
896 after(TCP_SKB_CB(skb)->end_seq, tp->retransmit_high)) in tcp_verify_retransmit_hint()
1018 if (after(end_seq, tp->snd_nxt) || !before(start_seq, end_seq)) in tcp_is_sackblock_valid()
1028 if (after(start_seq, tp->snd_una)) in tcp_is_sackblock_valid()
1035 if (after(end_seq, tp->snd_una)) in tcp_is_sackblock_valid()
1042 if (!after(end_seq, tp->undo_marker)) in tcp_is_sackblock_valid()
1068 if (!after(end_seq_0, end_seq_1) && in tcp_check_dsack()
1079 !after(end_seq_0, prior_snd_una) && in tcp_check_dsack()
1080 after(end_seq_0, tp->undo_marker)) in tcp_check_dsack()
1114 in_sack = !after(start_seq, TCP_SKB_CB(skb)->seq) && in tcp_match_skb_to_sack()
[all …]
Dtcp_minisocks.c45 if (after(end_seq, s_win) && before(seq, e_win)) in tcp_in_window()
138 !after(TCP_SKB_CB(skb)->end_seq, tcptw->tw_rcv_nxt) || in tcp_timewait_state_process()
233 (after(TCP_SKB_CB(skb)->seq, tcptw->tw_rcv_nxt) || in tcp_timewait_state_process()
722 if (tmp_opt.saw_tstamp && !after(TCP_SKB_CB(skb)->seq, tcp_rsk(req)->rcv_nxt)) in tcp_check_req()
Dtcp_recovery.c53 if (!after(scb->end_seq, tp->snd_una) || in tcp_rack_mark_lost()
Dtcp_cdg.c157 if (after(now_us, ca->round_start + base_owd)) { in tcp_cdg_hystart_update()
270 if (after(ack, ca->rtt_seq) && ca->rtt.v64) { in tcp_cdg_cong_avoid()
Dtcp_cubic.c168 if (after(ca->epoch_start, now)) in bictcp_cwnd_event()
345 if (hystart && after(ack, ca->end_seq)) in bictcp_cong_avoid()
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dfsl-upm-nand.txt10 - fsl,upm-wait-flags : add chip-dependent short delays after running the
11 UPM pattern (0x1), after writing a data byte (0x2) or after
Dgpio-control-nand.txt24 the GPIO's and the NAND flash data bus. If present, then after changing
25 GPIO state and before and after command byte writes, this register will be
Dfsmc-nand.txt20 kept in Hi-Z (tristate) after the start of a write access.
24 when writing) after the command deassertation. Zero means
/linux-4.4.14/arch/ia64/
DKconfig.debug28 Faults, that is, for Read-after-Write (RAW), Write-after-Write (WAW),
29 or Write-after-Read (WAR) violations. This option is ignored if you
/linux-4.4.14/Documentation/
Ddcdbas.txt6 power off after OS shutdown) on certain Dell systems.
48 to perform a power cycle or power off of the system after the OS has finished
50 a driver perform a SMI after the OS has finished shutting down.
54 action after the system has finished shutting down:
Dlzo.txt115 state = S (copy S literals after this block)
125 state = S (copy S literals after this block)
134 state = S (copy S literals after this block)
142 state = S (copy S literals after this block)
146 state = S (copy S literals after this block)
153 state = S (copy S literals after this block)
Dcachetlb.txt9 after the interface is invoked.
45 'mm' will be visible to the cpu. That is, after running,
59 'start' to 'end-1' will be visible to the cpu. That is, after
85 is, after running, there will be no entries in the TLB for
149 the caches. That is, after running, there will be no cache
158 the caches. That is, after running, there will be no cache
225 The first of these two routines is invoked after map_vm_area()
359 with kmap, it calls this function after all modifications are
388 I/O and invalidating it after the I/O returns.
Dkref.txt20 You must initialize the kref after you allocate it. To do this, call
113 /* BAD BAD BAD - get is after the handoff */
188 /* All work is done after the return from kref_put(). */
297 rcu grace period after release_entry_rcu was called. That can be accomplished
Ddebugging-modules.txt1 Debugging Modules after 2.6.3
Drobust-futexes.txt42 then the kernel has no information to clean up after the held lock!
43 Userspace has no chance to clean up after the lock either - userspace is
105 list is done after the futex is acquired by glibc, there is a few
109 kernel to clean up if the thread dies after acquiring the lock, but just
112 it after the list-add (or list-remove) has finished.
Dassoc_array.txt97 This is also used to keep track of dead blocks and dead objects after the
99 after an RCU grace period has passed - thus allowing access functions to
178 period after assoc_array_apply_edit() was called, so synchronize_rcu() may
528 matching leaf pointer with the pointer to the new leaf after a barrier.
530 until after the RCU grace period.
534 after the RCU grace period.
570 the parent slot number is read after the back pointer.
572 Obsolete blocks and leaves are freed up after an RCU grace period has passed,
Dlockup-watchdogs.txt30 to cause the system to reboot automatically after a specified amount
53 will dump useful debug information to the system log, after which it
Dmemory-barriers.txt346 operations specified after the barrier with respect to the other
354 occur in the sequence _before_ all the stores after the write barrier.
379 touched by the load will be perceptible to any loads issued after the data
400 all the LOAD operations specified after the barrier with respect to the
417 the LOAD and STORE operations specified after the barrier with respect to
431 operations after the ACQUIRE operation will appear to happen after the
437 happen after it completes.
451 Memory operations that occur after a RELEASE operation may appear to
457 pair is -not- guaranteed to act as a full memory barrier. However, after
672 assembly code even after all compiler optimizations have been applied.
[all …]
Dramoops.txt13 survive after a restart.
39 on restart (i.e. new dumps after the restart will overwrite old ones).
Diostats.txt42 In 2.4, the statistics fields are those after the device name. In
137 reads/writes before merges for partitions and after for disks. Since a
145 the partition which contains the first sector of the request after the
/linux-4.4.14/Documentation/vm/
Dsoft-dirty.txt21 when the soft-dirty bit is cleared. So, after this, when the task tries to
25 Note, that although all the task's address space is marked as r/o after the
26 soft-dirty bits clear, the #PF-s that occur after that are processed fast.
Dslub.txt217 corruption by a write after free.
221 writes after the object. All bytes should always have the same
222 value. If there is any deviation then it is due to a write after
277 If the corruption occurs by writing after the end of the object then it
315 to compare slabs' behaviour "prior to" and "after" some code modification.
/linux-4.4.14/drivers/staging/gs_fpgaboot/
DREADME50 b. For the FPGA that runs without config after the download, which
55 after the download.
57 c. For the FPGA that requires config after the download, which talk to
/linux-4.4.14/Documentation/devicetree/bindings/c6x/
Dclocks.txt26 - ti,c64x+pll-reset-delay: CPU cycles to delay after PLL reset
28 - ti,c64x+pll-lock-delay: CPU cycles to delay after PLL frequency change
Demifa.txt21 Number of memory transfers after which the EMIF will elevate the priority
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-restart.txt40 - active-delay: Delay (default 100) to wait after driving gpio active [ms]
41 - inactive-delay: Delay (default 100) to wait after driving gpio inactive [ms]
42 - wait-delay: Delay (default 3000) to wait after completing restart
Dgpio-poweroff.txt16 the CPU still running after a 3000ms delay, a WARN_ON(1) is emitted.
/linux-4.4.14/Documentation/devicetree/bindings/usb/
Dusb-ehci.txt7 (debug-port or other) can be also specified here, but only after
15 - needs-reset-on-resume : boolean, set this to force EHCI reset after resume
Dbrcm,bcm3384-usb.txt9 - Restoring state after systemwide power save modes
/linux-4.4.14/
D.gitignore7 # command after changing this file, to see if there are
8 # any tracked files which get ignored after the change.
/linux-4.4.14/Documentation/pcmcia/
Ddevicetable.txt27 The hex value after "pa" is the hash of product ID string 1, after "pb" for
Ddriver.txt30 after loading the driver.
/linux-4.4.14/Documentation/fmc/
Dfmc-write-eeprom.txt60 after two seconds. Please note, however, that if fmc-write-eeprom is
62 will be reprogrammed and thus will be unloaded after two seconds. The
63 following example removes the module after it reflashed fakedev the
92 only with its golden gateware: after a mezzanine driver reprogrammed
/linux-4.4.14/Documentation/hwmon/
Damc682166 4 degree C. Read it out after writing to get
72 pwm1_auto_point2_pwm. Read it out after
88 and pwm1_auto_point2_pwm. Read it out after
/linux-4.4.14/Documentation/serial/
Dserial-rs485.txt68 /* Set logical level for RTS pin equal to 1 after sending: */
70 /* or, set logical level for RTS pin equal to 0 after sending: */
76 /* Set rts delay after send, if needed: */
/linux-4.4.14/lib/
DKconfig.kasan12 designed to find out-of-bounds accesses and use-after-free bugs.
50 out of bounds accesses, use after free. It is useful for testing
/linux-4.4.14/arch/powerpc/boot/dts/
Dps3.dts33 * We'll get the size of the bootmem block from lv1 after startup,
46 * we'll put a null entries here. These will be initialized after
/linux-4.4.14/Documentation/usb/
Dfunctionfs.txt4 unique behaviour. It may be added to an USB configuration only after
61 The gadget is registered only after all the declared function
65 Conversely, the gadget is unregistered after the first USB function
Dcallbacks.txt37 * @post_reset: Called after the device has been reset
81 You are not allowed any IO to a device after returning from this
87 time after the physical disconnection. Thus your driver must be prepared
DURB.txt22 usb_submit_urb(urb) call returns immediately after it has successfully
27 - Each URB has a completion handler, which is called after the action
54 // (OUT) status after each completion
165 until after the URB has been returned and the completion handler
/linux-4.4.14/Documentation/ia64/
Dserial.txt7 starting after the ACPI devices.
23 after /dev/ttyS0 as they were discovered.
74 all the serial devices, which can happen a minute or more after the
85 No kernel output after elilo prints "Uncompressing Linux... done":
151 box after changing console configuration.
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dcache.c15 (unsigned)(descr->after - descr->buf)); in flush_dma_descr()
/linux-4.4.14/fs/jffs2/
DTODO12 - make the scan code populate real inodes so read_inode just after
15 decide which inodes should be in-core immediately after mount.
DREADME.Locking109 if we need to deal with wrapping after 4 milliard inode numbers are used.
148 Lock wbuf_sem last, after the alloc_sem or and f->sem.
165 after release read-semaphore, if it's necessary to load name/value pair
169 Lock xattr_sem last, after the alloc_sem.
/linux-4.4.14/Documentation/devicetree/bindings/power/
Dpd-samsung.txt17 and restored back after powering on a domain. This is required for
24 Their original parent will be brought back after turning on
/linux-4.4.14/Documentation/acpi/
Ddebug.txt31 command line argument, and you can change it after boot by writing values
79 command line argument, and you can change it after boot by writing values
142 Enable all ACPI_DB_INFO messages after boot:
Dscan_handlers.txt23 appropriate data, but some of them require additional handling after they have
45 executed, respectively, after registration of new device nodes and before
/linux-4.4.14/drivers/staging/clocking-wizard/
DTODO7 - overflow after multiplication?
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-bus-coresight-devices-tmc6 formatter after a defined number of words have been stored
Ddev-kmsg54 seek after the last entry in the buffer
56 seek after the last record available at the time
68 The human readable text string starts directly after the ';'
Ddebugfs-olpc14 To read the response (if any), read from the generic node after executing
Dsysfs-class-led-flash27 is stopped after this period of time has passed from the start
55 Flash faults are re-read after strobing the flash. Possible
Dsysfs-power117 this case cat /sys/power/pm_trace_dev_match (see below) after
121 clock to be set to a random invalid time after a resume.
132 the device hash in the RTC at boot, with a newline after each
137 devices created after boot by loadable kernel modules.
171 to a sleep state if any wakeup events are reported after the
223 deactivated after it has expired. The timeout, if present, is
Dsysfs-bus-coresight-devices-etb1021 formatter after a defined number of words have been stored
Ddebugfs-ec20 not get switched on again after you did a wrong write.
Dsysfs-bus-iio83 unique to allow association with event codes. Units after
99 is required is a consistent labeling. Units after application
111 unique to allow association with event codes. Units after
118 Raw capacitance measurement from channel Y. Units after
129 is required is a consistent labeling. Units after application
146 less measurements. Units after application of scale and offset
164 after application of scale and offset are m/s^2.
174 Units after application of scale and offset are radians per
219 Raw pressure measurement from channel Y. Units after
233 Raw humidity measurement of air. Units after application of
[all …]
Dsysfs-driver-hid-picolcd14 disconnected and reconnects after above delay (see attribute
Dpstore34 soon after boot to free up space ready for the next
/linux-4.4.14/Documentation/blockdev/drbd/
Dconn-states-8.dot4 WFConnection -> WFReportParams [ label = "in connect() after accept" ]
/linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/
Dmvebu-devbus.txt38 drive the AD bus after the completion of a device read.
39 This prevents contentions on the Device Bus after a read
76 DEV_OEn is always de-asserted the next cycle after
100 data after DEV_WEn rise.
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/ab8500/
Dcharger.txt18 Boolean value depicting the presence of 'automatic poweron after powerloss'
/linux-4.4.14/Documentation/block/
Dcfq-iosched.txt72 queue level. This was introduced after a bottleneck was observed
226 on same queue after completion of a request. In this process CFQ will not
231 sequential reads (next read will come on only after completion of previous
270 roughly after 1 second. If after completion of REQ_NOIDLE request we
271 do not idle, and after a couple of milli seconds a another REQ_NOIDLE
272 request comes in, again it will be scheduled after 1second. Repeat it
278 data comes in only after fsync has finished its IO (atleast for ext4
Dwriteback_cache_control.txt38 signaled after the data has been committed to non-volatile storage.
86 layer turns it into an empty REQ_FLUSH request after the actual write.
/linux-4.4.14/Documentation/leds/
Dledtrig-oneshot.txt27 LED_FULL brightness after it has been armed.
31 LED_OFF brightness after it has been armed.
/linux-4.4.14/Documentation/dvb/
Dopera-firmware.txt13 and after that you have 2 files:
/linux-4.4.14/drivers/infiniband/hw/mthca/
DKconfig16 debug_level module parameter (which can also be set after
/linux-4.4.14/Documentation/devicetree/bindings/power_supply/
Dsbs_sbs-battery.txt11 after an external change notification.
/linux-4.4.14/Documentation/devicetree/bindings/timer/
Dlsi,zevio-timer.txt13 (always after timer base address)
/linux-4.4.14/arch/m68k/hp300/
DREADME.hp30012 The LANCE driver works after a fashion but only if you reset the chip before
/linux-4.4.14/arch/arm/boot/compressed/
Dll_char_wr.S70 sub r1, r1, #1 @ avoid using r7 directly after
75 tst r1, #7 @ avoid using r7 directly after
/linux-4.4.14/Documentation/sound/alsa/soc/
Dmachine.txt23 * after the codec and DAIs do any PM work. */
46 of any machine audio tasks that have to be done before or after the codec, DAIs
DDAI.txt33 o I2S - MSB is transmitted on the falling edge of the first BCLK after LRC
54 o Mode A - MSB is transmitted on falling edge of first BCLK after FRAME/SYNC.
Ddapm.txt75 o Post - Special POST widget (exec after all others)
236 Finally, snd_soc_dapm_new_widgets(codec) must be called after all widgets and
301 #define SND_SOC_DAPM_POST_PMU 0x2 /* after widget power up */
303 #define SND_SOC_DAPM_POST_PMD 0x8 /* after widget power down */
305 #define SND_SOC_DAPM_POST_REG 0x20 /* after audio path setup */
Doverview.txt15 Headphone/Mic insertion, Headphone/Mic detection after an insertion
17 machine specific code to re-route audio, enable amps, etc., after such an
/linux-4.4.14/arch/m32r/
DKconfig.debug9 Unmap pages from the kernel linear mapping after free_pages().
/linux-4.4.14/drivers/zorro/
DKconfig11 15KB, but it gets freed after the system boots up, so it doesn't
/linux-4.4.14/Documentation/misc-devices/
Dc2port.txt63 after that you should read the device ID and revision ID of the
88 after writing you have to reset the device to execute the new code:
/linux-4.4.14/drivers/watchdog/
DKconfig15 on-line as fast as possible after a lock-up. There's both a watchdog
616 it does, it reboots your computer after a certain amount of time.
672 the machine after its expiration. The expiration time can be
685 it doesn't freeze, and if it does, it reboots your computer after
698 freeze, and if it does, it reboots your computer after a certain
741 it does, it reboots your computer after a certain amount of time.
830 that will reboot the machine after its second expiration. The
874 freeze, and if it does, it reboots your computer after a certain
938 freeze, and if it does, it reboots your computer after a certain
952 watchdog timer that will reboot the machine after its second
[all …]
/linux-4.4.14/drivers/of/
Dunittest.c1206 int before, int after, enum overlay_type ovtype) in of_unittest_apply_overlay_check() argument
1226 if (of_unittest_device_exists(unittest_nr, ovtype) != after) { in of_unittest_apply_overlay_check()
1230 !after ? "enabled" : "disabled"); in of_unittest_apply_overlay_check()
1239 int unittest_nr, int before, int after, in of_unittest_apply_revert_overlay_check() argument
1261 if (of_unittest_device_exists(unittest_nr, ovtype) != after) { in of_unittest_apply_revert_overlay_check()
1265 !after ? "enabled" : "disabled"); in of_unittest_apply_revert_overlay_check()
1373 int before = 0, after = 1; in of_unittest_overlay_6() local
1411 != after) { in of_unittest_overlay_6()
1416 !after ? "enabled" : "disabled"); in of_unittest_overlay_6()
/linux-4.4.14/arch/m68k/kernel/
Dvmlinux-sun3.lds34 /* will be freed after init */
Dvmlinux-std.lds38 /* will be freed after init */
/linux-4.4.14/drivers/scsi/
D53c700.scr300 ; We return here after a reselection
351 ; we return here after a reselection
364 ; we return here after a reselection
391 ; we return here after a reselection
/linux-4.4.14/drivers/block/paride/
DTransition-notes94 after resetting ps_tq_active to 0.
97 the area are either after resetting ->claimed_cont to NULL while holding
98 pi_spinlock, or after not tocuhing ->claimed_cont since acquiring pi_spinlock
100 in the area, under pi_spinlock and we do not release it until after leaving
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt102 Postmap ABA : The block number in the "Data Blocks" area obtained after
109 For example, after adding a BTT, we surface a disk of 1024G. We get a read for
125 old_map : The old postmap ABA - after 'this' write completes, this will be a
173 into rtt[lane_number], the postmap ABA it is reading, and clears it after the
174 read is complete. Every writer thread, after grabbing a free block, checks the
268 It may register with the BTT after it adds its own gendisk, using btt_init:
/linux-4.4.14/net/ax25/
DTODO6 A device might be deleted after lookup in the SIOCADDRT ioctl but before it's
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-arb-gpio-challenge.txt52 - wait-retry-us: we'll attempt another claim after this many microseconds.
54 - wait-free-us: we'll give up after this many microseconds. Default is 50000 us.
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dads7846.txt41 ti,penirq-recheck-delay-usecs If set to non-zero, after samples are
62 required after the first two (u16).
Dgpio-matrix-keypad.txt26 before we can scan keypad after activating column gpio
/linux-4.4.14/tools/perf/util/
Dmap.c697 struct map *after = map__clone(pos); in maps__fixup_overlappings() local
699 if (after == NULL) { in maps__fixup_overlappings()
704 after->start = map->end; in maps__fixup_overlappings()
705 __map_groups__insert(pos->groups, after); in maps__fixup_overlappings()
707 map__fprintf(after, fp); in maps__fixup_overlappings()
/linux-4.4.14/Documentation/devicetree/bindings/spi/
Dspi-cadence.txt17 chip selects after the decoder.
Dspi-rockchip.txt27 - rx-sample-delay-ns: nanoseconds to delay after the SCLK edge before sampling
Dfsl-spi.txt47 - fsl,csaft: chip select negation time in bits after frame ends
/linux-4.4.14/arch/mn10300/kernel/
Dsmp-low.S96 # Jump here after RTI to suppress the icache lookahead
/linux-4.4.14/arch/arm/vfp/
Dentry.S21 @ r2 = PC value to resume execution after successful emulation
/linux-4.4.14/tools/power/acpi/
DMakefile.config70 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
/linux-4.4.14/fs/ext4/
Dpage-io.c190 struct list_head *cur, *before, *after; in dump_completed_IO() local
201 after = cur->next; in dump_completed_IO()
202 io1 = container_of(after, ext4_io_end_t, list); in dump_completed_IO()
/linux-4.4.14/net/netfilter/ipvs/
Dip_vs_app.c295 if(after(seq, vseq->init_seq)) { in vs_fix_seq()
324 if(after(ack_seq, vseq->init_seq+vseq->delta)) { in vs_fix_ack_seq()
348 if (!(cp->flags & flag) || after(seq, vseq->init_seq)) { in vs_seq_update()
/linux-4.4.14/Documentation/devicetree/bindings/mmc/
Dmmc-pwrseq-simple.txt13 They will be de-asserted right after the power has been provided to the
Dmmc-pwrseq-emmc.txt5 performed just after MMC core enabled power to the given mmc host (to
/linux-4.4.14/Documentation/cpuidle/
Dgovernor.txt17 * reflect() called after returning from the idle state, which can be used
/linux-4.4.14/Documentation/fb/
Ddeferred_io.txt15 - schedule a workqueue task to be run after a delay
25 writes to occur at minimum cost. Then after some time when hopefully things
Dcirrusfb.txt58 modelled after that in atyfb and matroxfb.
/linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/
Dti-tsc-adc.txt40 The pen-up detection happens immediately after the
49 clock cycles to wait after applying the
Dfocaltech-ft6236.txt22 Swapping is done after inverting the axis
Dtouchscreen.txt20 Swapping is done after inverting the axis
Dchipone_icn8318.txt24 Swapping is done after inverting the axis
Dtsc2005.txt15 - ti,esd-recovery-timeout-ms : integer, if the touchscreen does not respond after
Dbrcm,iproc-touchscreen.txt15 the tsc waits to allow the voltage to settle after
/linux-4.4.14/drivers/staging/iio/Documentation/
Dsysfs-bus-iio-impedance-analyzer-ad593329 after each frequency increment, and before the ADC is triggered
/linux-4.4.14/Documentation/devicetree/bindings/regulator/
Dtps65023.txt10 after their hardware counterparts: VDCDC[1-3] and LDO[1-2]
Dtps65217.txt7 after their hardware counterparts: dcdc[1-3] and ldo[1-4]
/linux-4.4.14/arch/arm/mach-omap2/
Dsleep24xx.S88 nop @ start auto refresh only after clk ok
/linux-4.4.14/firmware/advansys/
Dmcode.bin.ihex147 /* Microcode buffer is kept after initialization for error recovery. */
/linux-4.4.14/tools/scripts/
DMakefile.include23 EXTRA_WARNINGS += -Wdeclaration-after-statement
/linux-4.4.14/Documentation/devicetree/bindings/watchdog/
Dsamsung-wdt.txt4 after a preset amount of time during which the WDT reset event has not
/linux-4.4.14/drivers/video/fbdev/omap2/dss/
DKconfig125 bool "Sleep 20ms after VENC reset"
128 There is a 20ms sleep after VENC reset which seemed to fix the
/linux-4.4.14/Documentation/filesystems/
Domfs.txt53 __be32 h_body_size; /* size of useful data after header */
89 __be64 e_blocks; /* number of blocks after e_cluster */
/linux-4.4.14/arch/cris/boot/rescue/
Dhead_v10.S70 ;; The partitiontable is looked for at the first sector after the boot
79 ;; of itself (after having setup the DRAM etc).
138 ;; code after this and altering the jumptarget in an upgrade.
/linux-4.4.14/Documentation/arm/
Dkernel_mode_neon.txt33 another core). Lazy restore is implemented by disabling the NEON/VFP unit after
43 Likewise, the NEON/VFP unit should be disabled again after use to make sure user
121 * Include <arm_neon.h> last, or at least after <linux/types.h>
/linux-4.4.14/Documentation/target/
Dtcmu-design.txt156 iovec entries immediately after that in iov[] cover the Data-In
176 This is shared-memory space after the command ring. The organization
223 the LIO device, so that after determining the device is supported
231 - TCMU will post commands, and then abort them after a timeout period
237 devices. Command ring is preserved. However, after the timeout period,
242 - The kernel will abort pending tasks after a timeout period.
/linux-4.4.14/Documentation/devicetree/bindings/mfd/
Dtwl4030-audio.txt14 - ti,digimic_delay: Delay need after enabling the digimic to reduce artifacts
Dtwl4030-power.txt5 binding only supports the complete shutdown of the system after poweroff.
/linux-4.4.14/Documentation/devicetree/bindings/serial/
Drs485.txt13 it corresponds to the delay after sending data and actual release of the line.
/linux-4.4.14/Documentation/arm/VFP/
Drelease-notes.txt37 after rounding, we do not signal an underflow exception.
/linux-4.4.14/drivers/net/ethernet/mellanox/mlx4/
DKconfig45 debug_level module parameter (which can also be set after
/linux-4.4.14/fs/nilfs2/
DKconfig9 consistency like conventional LFS, it achieves quick recovery after
/linux-4.4.14/drivers/net/ethernet/microchip/
DKconfig33 Enable the verify after the buffer write useful for debugging purpose.
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Darm-mhu.txt9 STAT register and the remote clears it after having read the data.
/linux-4.4.14/arch/cris/include/arch-v32/arch/hwregs/
Ddma.h69 char *after; member
/linux-4.4.14/Documentation/scsi/
Dqlogicfas.txt44 after a crash, since they may be busy trying to complete the last
66 realbig.doc realbig.doc". Then do it after the computer gets warm.
DChangeLog.megaraid_sas211 will re-issue those pending cmds again to FW after the OCR
230 will not need to do the device update after application add/del the device
233 failed state. Driver will kill adapter if can't bring back FW after the
250 keep the logic drive list internal after driver load.
252 3. driver fixed the device update issue after get the AEN
283 1. Add the fix of pending in FW after deleted the logic drives.
284 2. Add the fix of deallocating memory after get pdlist.
577 Interrupt is enabled after required initialization is over.
DChangeLog.lpfc29 if we timed out waiting for command to complete after abort was
145 sli layer now frees the response iocbs after processing it.
159 * Added code to prevent waking up worker thread after the exit of
190 hostdata readjust code so that they are no use after free's
191 (don't use after scsi_host_put) - make lpfc_alloc_sysfs_attr
251 lpfc_els_abort to reset txq and txcmplq iterator after a
253 * Fixed a use after free issue in lpfc_init.c.
355 freed (after nodev tmo). This bug was causing i/o received in
367 properly after ADISC handling completes.
399 * Janitorial cleanup after removal of sliinit and ringinit[] ring
[all …]
DChangeLog.ncr53c8xx273 after abitration while the SCSI core is performing SCSI selection).
281 was read from the SFBR i/o register after the previous message had
327 verbose level after boot-up. Setting this level to zero, for
368 - Add a check of the MSG_OUT phase after Selection with ATN.
410 - Call scsi_done() for all completed commands after interrupt
424 - Since the SCRIPTS processor continues SCRIPTS execution after
487 This option enables checking of SCSI BUS data lines after SCSI
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt109 This option prints messages to the serial console before and after
116 Allows the entire memory to be checksummed before and after the
/linux-4.4.14/drivers/base/
DKconfig48 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
52 devtmpfs filesystem at /dev, directly after the kernel has
57 after the rootfs is mounted.
95 use these is to run "make firmware_install", which, after
160 (e.g. udev) for loading firmware files as a fallback after the
/linux-4.4.14/Documentation/sound/oss/
Doss-parameters.txt9 module. Loadable modules, after being loaded into the running kernel, also
/linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/
Dccf.txt21 chips. It should be specified after either
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dst,sti-picophyreset.txt10 registers and after an assert/deassert sequence the hardware's previous state
Dst,sti-softreset.txt11 registers and after an assert/deassert sequence the hardware's previous state
Dst,sti-powerdown.txt12 registers and after an assert/deassert sequence the hardware's previous state
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Dal,alpine.txt58 The CPU resume register are used to define required resume address after
/linux-4.4.14/Documentation/ABI/obsolete/
Dsysfs-bus-usb29 This file is deprecated and will be removed after 2010.
/linux-4.4.14/drivers/gpu/drm/msm/
DNOTES22 pageflip after rendering completes (ie. have the kms/crtc code build
23 up gpu cmdstream to update scanout and write FLUSH register after).
/linux-4.4.14/Documentation/video4linux/bttv/
DREADME.quirks30 after the video request but before the PCI external arbiter has granted
44 (2) Do not reassert REQ to request another bus transaction until after
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt60 after having dropped all already acquired locks. These functions have the
65 contending lock (after having dropped all other already acquired locks) will
325 - Attempting to lock more mutexes after ww_acquire_done.
326 - Attempting to lock the wrong mutex after -EDEADLK and
328 - Attempting to lock the right mutex after -EDEADLK,
/linux-4.4.14/tools/power/cpupower/
DMakefile121 WARNINGS += $(call cc-supports,-Wdeclaration-after-statement)
/linux-4.4.14/arch/cris/arch-v32/lib/
Dchecksum.S47 ;; to prepare for what is needed after mloop.
Dchecksumcopy.S50 ;; r12 <= acr is needed after mloop and in the exception handlers.
/linux-4.4.14/Documentation/devicetree/bindings/display/exynos/
Dexynos_hdmi.txt25 after configuration, parent is set to sclk_hdmiphy else
/linux-4.4.14/Documentation/devicetree/bindings/phy/
Dphy-mt65xx-usb.txt23 cell after port phandle is phy type from:
/linux-4.4.14/drivers/misc/
Dkgdbts.c835 char after[BREAK_INSTR_SIZE]; in run_plant_and_detach_test() local
845 probe_kernel_read(after, (char *)kgdbts_break_test, in run_plant_and_detach_test()
847 if (memcmp(before, after, BREAK_INSTR_SIZE)) { in run_plant_and_detach_test()
/linux-4.4.14/Documentation/driver-model/
Ddevres.txt229 and 400 bytes on 32bit machine after naive conversion (we can
316 pcim_enable_device() : after success, all PCI ops become managed
317 pcim_pin_device() : keep PCI device enabled after release
/linux-4.4.14/Documentation/networking/
Dnetconsole.txt17 netconsole initializes immediately after NIC cards and will bring up
57 Built-in netconsole starts immediately after the TCP stack is
102 "1" to the "enabled" attribute (usually after setting parameters accordingly)
Dnetdev-FAQ.txt42 features get mainlined after this -- only fixes to the rc1 content
46 things are in a state of churn), and a week after the last vX.Y-rcN
62 Shortly after the two weeks have passed (and vX.Y-rc1 is released), the
153 to request a commit be added the day after it appears should be avoided.
/linux-4.4.14/Documentation/input/
Dmulti-touch-protocol.txt99 The sequence after moving one of the contacts looks exactly the same; the
103 Here is the sequence after lifting the first contact:
110 And here is the sequence after lifting the second contact:
137 Here is the sequence after moving contact 45 in the x direction:
143 Here is the sequence after lifting the contact in slot 0:
152 Finally, here is the sequence after lifting the second contact:
Dnotifier.txt19 - KBD_POST_KEYSYM events are sent after the treatment of non-unicode keysyms.
/linux-4.4.14/arch/cris/arch-v32/drivers/
Dcryptocop.c344 cdesc->dma_descr->after = NULL; in alloc_cdesc()
426 cdesc->dma_descr->after = cdesc->dma_descr->buf + plen; in create_pad_descriptor()
459 key_desc->dma_descr->after = key_desc->dma_descr->buf + tc->tctx->init.keylen/8; in setup_key_dl_desc()
462 key_desc->dma_descr->after = key_desc->dma_descr->buf + tc->tctx->init.keylen/8; in setup_key_dl_desc()
510 iv_desc->dma_descr->after = iv_desc->dma_descr->buf + tc->blocklength; in setup_cipher_iv_desc()
579 outdesc->dma_descr->after = outdesc->dma_descr->buf + dlength; in create_input_descriptors()
629 cdesc->dma_descr->after = cdesc->dma_descr->buf + dlength; in create_output_descriptors()
682 (*current_in_cdesc)->dma_descr->after = (*current_in_cdesc)->dma_descr->buf + desclen; in append_input_descriptors()
963 indata_ix += (unsigned int)(key_desc->dma_descr->after - key_desc->dma_descr->buf); in cryptocop_setup_dma_list()
978 indata_ix += (unsigned int)(iv_desc->dma_descr->after - iv_desc->dma_descr->buf); in cryptocop_setup_dma_list()
[all …]
/linux-4.4.14/scripts/coccinelle/free/
Dkfree.cocci1 /// Find a use after free.
/linux-4.4.14/Documentation/devicetree/
Dchangesets.txt5 previous state. A changeset can also be removed after it has been
/linux-4.4.14/scripts/coccinelle/locks/
Dmini_lock.cocci3 /// before the if and an unlock after the if. False positives are due to
/linux-4.4.14/Documentation/devicetree/bindings/ata/
Dsata_highbank.txt29 cycles to transmit after sending an SGPIO pattern
/linux-4.4.14/kernel/power/
DKconfig47 after placing resume=/dev/swappartition on the kernel command line
147 (low power) states, for example after a specified period of inactivity
234 set to an invalid time after a resume.
243 reset after a RESUME operation, the /proc/apm device will provide
/linux-4.4.14/arch/cris/arch-v10/
DKconfig27 <file:arch/cris/include/asm/io.h>, and those macros are defined after
37 <file:arch/cris/include/asm/io.h>, and those macros are defined after
47 <file:arch/cris/include/asm/io.h>, and those macros are defined after
379 powerbutton and then do a power off after unmounting disks.
/linux-4.4.14/Documentation/RCU/
DwhatisRCU.txt67 callback that is invoked after they finish. Only readers that are active
69 after the removal phase will be unable to gain a reference to the removed
177 any that begin after synchronize_rcu() is invoked.
180 -immediately- after the last pre-existing RCU read-side critical
194 after all ongoing RCU read-side critical sections have completed.
285 at any time, including immediately after the rcu_dereference().
373 * frees up the old structure after a grace period.
433 o Use synchronize_rcu() -after- removing a data element from an
456 This function invokes func(head) after a grace period has elapsed.
474 * frees up the old structure after a grace period.
[all …]
/linux-4.4.14/drivers/eisa/
DKconfig48 image by about 40KB, but it gets freed after the system
/linux-4.4.14/drivers/char/mwave/
DREADME5 are not saved by the BIOS and so do not persist after unload and reload.
/linux-4.4.14/Documentation/isdn/
DREADME.pcbit20 allow you to load the firmware after a hard reset.
/linux-4.4.14/drivers/infiniband/ulp/ipoib/
DKconfig34 can also be set after the driver is loaded through sysfs).
/linux-4.4.14/scripts/coccinelle/iterators/
Dfen.cocci122 msg = "ERROR: of_node_put not needed after iterator on line %s" % (p1[0].line)
/linux-4.4.14/Documentation/scheduler/
Dsched-domains.txt21 CPUs as they contain read only data after they have been set up.
29 through scheduler_tick(). It raises a softirq after the next regularly scheduled
/linux-4.4.14/Documentation/video4linux/
Dpxa_camera.txt21 smoothly captured one frame after the other.
168 Note: if DMA stops just after pxa_camera_check_link_miss() reads DDADR()
/linux-4.4.14/Documentation/trace/
Dring-buffer-design.txt108 The page after the inserted page (old reader_page) will become the
245 If a write happens after the first reserve:
290 The tail page is always equal to or after the commit page. It may
311 There is a special case that the head page is after either the commit page
479 The reader sets the reader page next pointer as HEADER to the page after
825 Another writer preempts and sees the page after the tail page is a head page.
928 writers means that it only needs to check this after setting the HEAD page.
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-kernel-api.txt78 * bootstatus: status of the device after booting (reported with watchdog
179 is active or not. When the watchdog is active after booting, then you should
191 after calling watchdog_unregister_device, and then checked before calling
193 unref) will get called after unregister, even if userspace still holds a

12345