Home
last modified time | relevance | path

Searched refs:since (Results 1 – 200 of 573) sorted by relevance

123

/linux-4.4.14/Documentation/virtual/kvm/
Dlocking.txt32 The mapping from gfn to pfn may be changed since we can only ensure the pfn
61 For direct sp, we can easily avoid it since the spte of direct sp is fixed
76 spte is read-only and the Accessed bit has already been set since the
79 But it is not true after fast page fault since the spte can be marked
124 be flushed caused by this reason in mmu_spte_update() since this is a common
157 Comment: it is a spinlock since it is used in mmu notifier.
178 wakeup notification event since external interrupts from the
Dcpuid.txt6 cpuid. This is not always guaranteed to work, since userspace can
Dmmu.txt151 (since each first-level guest page is shadowed by two first-level
238 since the last time the page table was actually used; if emulation
358 - if CR4.SMEP is enabled: since we've turned the page into a kernel page,
363 - if CR4.SMAP is disabled: since the page has been changed to a kernel
366 here we do not care the case that CR4.SMAP is enabled since KVM will
383 two separate 2M pages, on both guest and host, since the mmu always uses PAE
/linux-4.4.14/drivers/block/paride/
DTransition-notes8 anything except B, since it is under if (!ps_tq_active) under
9 ps_spinlock. C is always preceded by B, since we can't reach it
12 the sum of numbers of A and C, since each call of ps_tq_int() is
16 since at any time number of B can not exceed the number of these
87 we were acquiring the lock, (1) would be already false, since
98 pi_spinlock, or after not tocuhing ->claimed_cont since acquiring pi_spinlock
122 ps_continuation, since the latter is changed only from the area.
123 We don't need to reset it to NULL, since we are guaranteed that there
/linux-4.4.14/Documentation/fb/
Dtgafb.txt18 Major new features since Linux 2.0.x:
24 User-visible changes since Linux 2.2.x:
56 The XFree86 FBDev server has been reported not to work, since tgafb doesn't do
Dsh7760fb.txt13 make the driver a module since at runtime it may become impossible to
40 The driver does NOT do the above for you since board setup is, well, job
Dviafb.txt168 multi-head since SAMM support multi monitor at driver layers, thus fbcon
175 instead of calling common ioctl function FBIOPUT_VSCREENINFO since
/linux-4.4.14/Documentation/power/
Dsuspend-and-cpuhotplug.txt148 argument. But during suspend, since the tasks are already frozen by the time
187 In this case since we probably need to apply different microcode revisions
202 Hence, when a new CPU is brought online, since the kernel finds that it
222 when the CPUs are brought back online, since they wouldn't have lost the
226 However, in the case of hibernation, since all the CPUs are completely
237 And during the CPU online operations (during resume/restore), since the
253 This might not reflect the true current state of the system, since the
265 into the kernel, since the freezing has not yet begun.
Dfreezing-of-tasks.txt196 tasks, since it generally exists anyway.
213 it is strongly discouraged to directly call mutex_[un]lock(&pm_mutex) since
221 since they ask the freezer to skip freezing this task, since it is anyway
/linux-4.4.14/Documentation/
Dunicode.txt26 In particular, ESC ( U is no longer "straight to font", since the font
37 refers to this as a "Corporate Zone", since this is inaccurate for
39 point since it lets the direct-mapping area start on a large power of
65 omitted the scan 5 line, since it is also used as a block-graphics
74 since they are horribly vendor-specific. This, of course, is an
111 However, since the set of symbols appear to be consistent throughout,
Drtc.txt60 raised, and the remaining bytes contain the number of interrupts since
73 the number of interrupts received since the last read to determine if
76 occasional interrupt pileup (i.e. > 1 IRQ event since last read) for
152 since_epoch: The number of seconds since the epoch according to the RTC
156 after wake if a daily wakeup is required. Format is seconds since
Diostats.txt49 All fields except field 9 are cumulative since boot. Field 9 should
89 (field 9) times the number of milliseconds spent doing I/O since the
129 Note that since the address is translated to a disk-relative one, and no
Dhsi.txt9 implemented by multiple vendors since then.
Dpreempt-locking.txt29 First, since the data is per-CPU, it may not have explicit SMP locking, but
82 any locks or interrupts are disabled, since preemption is implicitly disabled
Dstatic-keys.txt245 footprint. We can in fact improve this even further, since the 5-byte no-op
246 really can be a 2-byte no-op since we can reach the branch with a 2-byte jmp.
289 'branch-misses'. This is where we would expect to get the most savings, since
Dcpu-load.txt46 `/proc/stat' (since the timer interrupt will always happen when the
Dsmsc_ece1099.txt42 The implementation in the device is a subset of SMBus since it
Deisa.txt181 code (since probing is now in the core EISA code). Unfortunately, most
187 from eisa_driver_register, since the chances are that the bus has not
Dlzo.txt34 seems to be optimized for literal use only, since there is no dictionary yet
109 noting that this instruction provides little savings since it uses 2
Dkref.txt101 since we already have a valid pointer that we own a refcount for. The
183 kfree() with the lock held in the example above (since it is kind of
Dcachetlb.txt22 First, the TLB flushing interfaces, since they are the simplest. The
38 changed, since such translations are "global" in nature.
141 implement these interfaces since the caches are fully synchronized
255 aliasing problem has the potential to exist since the kernel already
Dbcache.txt188 this to not show up enough to be noticeable (especially since bcache's btree
303 since the synchronization for cache misses was rewritten)
418 reused. Defaults to off, since SATA TRIM is an unqueued command (and thus
426 since buckets are discarded when they move on to the freelist will also make
/linux-4.4.14/Documentation/RCU/
DUP.txt6 is that since there is only one CPU, it should not be necessary to
7 wait for anything else to get done, since there are no other CPUs for
43 RCU usage, since call_rcu() must wait for a grace period to elapse.
117 then, since RCU callbacks can be invoked from softirq context,
122 This restriction might seem gratuitous, since very few RCU
DlistRCU.txt48 on, the list may well have been modified. This makes sense, since if
116 /* Do not use the _rcu iterator here, since this is the only
143 can therefore be eliminated, since use of RCU eliminates the need for
278 /* Do not need to use the _rcu iterator here, since this
Drcubarrier.txt167 re-posting themselves. This will not be necessary in most cases, since
269 The rcu_barrier() primitive has seen relatively little use, since most
303 since each CPU must undergo a context switch (or other quiescent
Drcuref.txt74 overkill, since we hold the update-side spinlock. One might instead
Dstallwarn.txt126 is the number that had executed since boot at the time that this CPU
131 since boot until the current time. If this latter number stays constant
141 prints the number of non-lazy callbacks posted since the last call to
/linux-4.4.14/arch/arc/kernel/
Dentry.S58 ; user mode, in a round about way since that is always done from
164 ; using ERET won't work since next-PC has already committed
183 ; clobbered them (since they are in scratch regs). The tracer could also
318 ; in pt_reg since the "C" ABI (kernel code) will automatically
Dentry-arcv2.S212 ; (since IRQ NOT allowed in DS in ARCv2, this can only happen if orig
/linux-4.4.14/sound/soc/fsl/
DKconfig12 This option is only useful for out-of-tree drivers since
23 This option is only useful for out-of-tree drivers since
34 This option is only useful for out-of-tree drivers since
45 This option is only useful for out-of-tree drivers since
55 This option is only useful for out-of-tree drivers since
70 This option is only useful for out-of-tree drivers since
/linux-4.4.14/net/irda/
DKconfig54 makes sense since most frames will be sent/received on the same
71 will give a lot of speed improvement when receiving much data since
93 If unsure, say Y (since it makes it easier to find the bugs).
/linux-4.4.14/Documentation/ABI/testing/
Dsysfs-fs-ext472 of data that have been written to this filesystem since it was
81 filesystem since it was mounted.
109 write operation (since a 4k random write might turn
Ddebugfs-pfo-nx-crypto14 - A u32 providing a total count of errors since the driver was loaded. The
Dsysfs-devices-edac7 long since the last counter were reset. This is useful for
16 since the last counter reset. This can be used with the error
37 increment, since EDAC will panic the system
Dsysfs-bus-rbd60 The block device minor number. (December 2013, since 3.14.)
Dsysfs-ocfs239 used since its inception.
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt12 Which is nice, since there's no more insanity in the form of fake-generic, but
44 conversion or worse, fiddle the raw __u64 through your code since that
53 pain. And since getting things wrong on the first attempt is guaranteed you
58 rejecting the new flags/modes or ioctls (since doing that was botched in the
64 but isn't a complete solution since newer userspace on older kernels won't
70 future extensions is going right down the gutters since someone will submit
149 frame counter. With a spec laywer hat on this isn't a bug since timeouts can
214 Finally, the name of the game is to get it right on the first attempt, since if
/linux-4.4.14/Documentation/vm/
Dsoft-dirty.txt17 written to since step 1.
27 This is so, since the pages are still mapped to physical memory, and thus all
Dzsmalloc.txt19 since this satisfies the requirements of all its current users (in the
27 zsmalloc does not keep zspages permanently mapped since that would cause
Dpagemap.txt19 * Bit 56 page exclusively mapped (since 4.2)
21 * Bit 61 page is file-page or shared-anon (since 3.5)
125 page has not been accessed since it was marked idle (see
144 2. REFERENCED page has been referenced since last LRU list enqueue/requeue
Didle_page_tracking.txt21 A page is considered idle if it has not been accessed since it was marked idle
52 one wants to ignore certain types of pages, e.g. mlocked pages since they
96 since there are usually not many of them, it should not affect the overall
Dremap_file_pages.txt18 virtual address space. This use-case is not critical anymore since 64-bit
/linux-4.4.14/Documentation/devicetree/bindings/pci/
Dv3-v360epc-pci.txt7 - syscon: should contain a link to the syscon device node (since
/linux-4.4.14/Documentation/devicetree/bindings/mailbox/
Dbrcm,bcm2835-mbox.txt10 channel. The value shall be 0, since there is only one
/linux-4.4.14/Documentation/locking/
Dww-mutex-design.txt53 w/w mutexes, since it is required to initialize the acquire context.
64 required, since simply calling the normal ww_mutex_lock functions on the
71 has a void return type. Note that since ww mutex code needs loops/retries
232 method #3 below. The backoff/retry procedure will be a bit more involved, since
237 Also, method 3 can't fail the lock acquisition step since it doesn't return
253 /* need to do that before unlocking, since only the current lock holder is
300 prevention is obviously overkill, since with grabbing just one lock you can't
Drt-mutex-design.txt37 meantime, B executes, and since B is of a higher priority than C, it preempts C,
68 of A. So now if B becomes runnable, it would not preempt C, since C now has
123 would never diverge, since a process can't be blocked on more than one
166 Also since a mutex may have more than one process blocked on it, we can
237 defined. But is very complex to figure it out, since it depends on all
302 Now since mutexes can be defined by user-land applications, we don't want a DOS
344 This is really nice to have, since it allows you to only update a variable
446 or timeout and has left the PI chain. In either case, the loop is exited, since
475 is OK, since plist_del does nothing if the plist node is not on any
489 since we just grab the mutex's wait_lock. And one could be right.
[all …]
/linux-4.4.14/Documentation/scsi/
DChangeLog.sym53c8xx70 This parameter wasn't that clever since we can use "sync:"
216 Code moved from the FreeBSD sym_hipd driver, since it has
219 function chips, since I cannot make sure for what chip revisions
230 io_request_lock since it seems to be a definite feature now.:)
231 - Change get_pages by GetPages since Linux >= 2.3.27 now wants
254 - Remove the quirk handling that has been useless since day one.
388 - Do a normal soft reset as first chip reset, since aborting current
389 operation may raise an interrupt we are not able to handle since
484 - Rewrite ncr53c8xx_setup (boot command line options) since the
496 since the driver will never performs PCI read transactions, but
[all …]
DFlashPoint.txt3 31 March 1997 since it is no longer needed.
72 Ever since its introduction last October, the BusLogic FlashPoint LT has
115 take quite a while for a usable driver to be written, especially since I'm
148 sure have come a long way since the last time I worked on firmware for an
152 BusLogic asked me to send this announcement since a large percentage of the
DChangeLog.ncr53c8xx128 io_request_lock since it seems to be a definite feature now.:)
135 function chips, since I cannot make sure for what chip revisions
140 io_request_lock since it seems to be a definite feature now.:)
218 since the chip has on-chip RAM.
291 Eddie's patch has been partially applied since current 2.1.109
313 at boot-up. This option is very useful since Linux does not
Dmegaraid.txt68 can easily be more than one. But since megaraid is the only low level driver
Ddpti.txt34 * This was the first full GPL version since the last version used
Dqlogicfas.txt44 after a crash, since they may be busy trying to complete the last
/linux-4.4.14/Documentation/prctl/
Dno_new_privs.txt11 - chroot is disallowed to unprivileged processes, since it would allow
17 These are all ad-hoc fixes. The no_new_privs bit (since Linux 3.5) is a
/linux-4.4.14/tools/perf/Documentation/
Dcallchain-overhead-calculation.txt16 values exceeds 100% since each of them is already an accumulation of
100 So '\_\_libc_start_main' and 'main' are shown first since they have
Dperf-buildid-cache.txt51 older entires since those may be still needed for annotating old
/linux-4.4.14/Documentation/input/
Dsentelic.txt31 Byte 4: Bit3~Bit0 => the scrolling wheel's movement since the last data report.
539 * Note that since the Cx release, the hardware will return 1's
594 * Note that since the Cx release, the hardware will return 1's
724 *supported since Cx
833 *supported since Cx
837 *supported since Cx
841 *supported since Cx
845 *supported since Cx
849 *supported since Cx
856 *supported since Cx
[all …]
Djoystick-api.txt107 is much safer since it can't lose sync with the driver. As you would
116 in milliseconds since ... well, since sometime in the past. This eases the
158 missing events since the queue is finite, and older events will get
Dedt-ft5x06.txt6 focaltec ft5x06 devices, since they contain vendor-specific firmware. In
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-bus-usb89 KernelVersion: since at least 2.6.18
96 KernelVersion: since at least 2.6.18
135 KernelVersion: since at least 2.6.18
/linux-4.4.14/net/wireless/
Ddb.txt7 # package provided by your distribution, since they will probably keep it
/linux-4.4.14/Documentation/devicetree/bindings/clock/
Darm-integrator.txt9 This clock node *must* be a subnode of the core module, since
Dbrcm,iproc-clocks.txt18 Have a value of <1> since there are more than 1 leaf clock of a given PLL
58 Have a value of <1> since there are more than 1 ASIU clocks
/linux-4.4.14/Documentation/sound/oss/
DPAS1631 when answering to these questions since answering y to a question may
45 have some other card made by Media Vision or Logitech since they
82 sound programming easier since they provide a common API. Say Y or M
106 some other card made by Media Vision or Logitech since they are not
DALS38 isapnp. "dma16" should be explicitly set to "-1" for an ALS-007 since this
43 working on an ALS-007 card, the "mpu401" module will be required since this
DPSS4 is not enabled since it doesn't work concurrently with MSS.
DREADME.OSS99 very latest (development) version of OSS/Free since the change may already be
308 appended to it (sometimes not). This causes major confusion since the non-PnP
388 have native support while others work since they emulate some other
416 You have been fooled since there are _no_ SB16 compatible
494 since Yamaha doesn't give information about their sample ROM chip.
545 of RAM since this is potentially dangerous (you may accidentally run out
624 NOTE! Don't ever try to use isapnptools with CS4232 since this will just
659 Using different settings is possible but not recommended since it may cause
732 when answering to these questions since answering y to a question may
735 more cards than you really need since they just consume memory. Also
[all …]
/linux-4.4.14/arch/openrisc/
DTODO.openrisc2 since 2.6.35. There are, however, remaining items to be completed within
/linux-4.4.14/Documentation/devicetree/bindings/input/
Dlpc32xx-key.txt18 since LPC32xx only supports square matrices
Dmatrix-keymap.txt2 defining the keys in the scope of linux key codes since that is a stable and
/linux-4.4.14/arch/arm/mach-prima2/
Dsleep.S46 @ Following code has to run from cache since
/linux-4.4.14/Documentation/devicetree/bindings/iio/adc/
Dxilinx-xadc.txt3 This binding document describes the bindings for both of them since the
9 interface. This binding document describes the bindings for both of them since
/linux-4.4.14/drivers/gpu/drm/omapdrm/
DTODO6 . This is mainly theoretical since most of these devices don't actually
/linux-4.4.14/Documentation/sound/alsa/
Dhdspm.txt22 since unused DMA channels are disabled and less memory is
93 use the standard mixer-controls, since this would break most of
127 frequency or slave), since even not using an Audio-application
162 card should synchronise better in MADI Mode. But since the
/linux-4.4.14/fs/affs/
DKconfig6 disks by Amiga(tm) systems since AmigaOS Version 1.3 (34.20). Say Y
/linux-4.4.14/Documentation/hwmon/
Dltc415123 This driver does not probe for LTC4151 devices, since there is no register
Dltc426024 This driver does not probe for LTC4260 devices, since there is no register
Dibmaem26 is a register that displays an estimate of raw energy consumption since the
Dtmp40147 * Minimum and Maximum temperature measured since power-on, chip-reset
Dpmbus-core27 and supported since kernel version 2.6.39. However, it was necessary to support
28 device specific extensions in addition to the core PMBus driver, since it is
46 PMBus commands. Auto-detection is somewhat limited, since there are simply too
186 page, since the selected page is cached in the core driver and the core driver
Dpmbus59 This driver does not probe for PMBus devices, since there is no register
61 supported by all chips), and since there is no well defined address range for
Dds162158 is somewhat misleading in this point since setting the polarity bit does
72 any of the limits have ever been met or exceeded since last power-up or
Dlineage-pem29 This driver does not probe for Lineage CPL devices, since there is no register
Dltc426124 This driver does not probe for LTC4261 devices, since there is no register
Dsmsc47m157 than 1.5 seconds since the last update). This means that you can easily
Dabituguru350 Unfortunately this doesn't help since the W83L951G is a generic microcontroller
Dltc294524 This driver does not probe for LTC2945 devices, since there is no register
Dadm102538 kind of strange since both are useful, and the reason for designing the
Dlm8059 than 2.0 seconds since the last update). This means that you can easily
Dgl518sm69 (unless it is less than 1.5 seconds since the last update). This means that
Dmax1606560 This driver does not probe for devices, since there is no register which
Dlm8754 than 1.0 seconds since the last update). This means that you can easily
Dlm7864 than 1.5 seconds since the last update). This means that you can easily
Dabituguru81 designed by the ABIT Engineers"). Unfortunately this doesn't help since the
/linux-4.4.14/arch/alpha/kernel/
Dhead.S60 # on the PC164 (at least), since that PALcode manages the interrupt
/linux-4.4.14/Documentation/kbuild/
DKconfig.select-break17 # visit the dependencies of the select target (in this case B). And since
DKconfig.recursion-issue-0139 # since CORE_BELL_A depends on CORE. Recursive dependency issues are not always
/linux-4.4.14/Documentation/accounting/
Ddelay-accounting.txt86 Get delays, since system boot, for pid 10
90 Get sum of delays, since system boot, for all pids with tgid 5
Dtaskstats-struct.txt67 /* The time when a task begins, in [secs] since 1970. */
68 __u32 ac_btime; /* Begin time [sec since 1970] */
Dtaskstats.txt118 Taskstats provides per-process stats, in addition to per-task stats, since
153 path since the kernel and userspace don't need to incur the overhead of
/linux-4.4.14/Documentation/devicetree/bindings/display/msm/
Ddsi.txt11 be 0 or 1, since we have 2 DSI controllers at most for now.
61 be 0 or 1, since we have 2 DSI PHYs at most for now.
/linux-4.4.14/Documentation/devicetree/bindings/soc/ti/
Dkeystone-navigator-qmss.txt77 1 : Time delay since last interrupt
78 2 : Time delay since first new packet
79 3 : Time delay since last new packet
Dkeystone-navigator-dma.txt37 use them since it has a different address space view to reach all
/linux-4.4.14/Documentation/laptops/
Dsonypi.txt65 compiled without ACPI support (since it conflicts
127 external monitor on/off. There is no workaround yet, since this
150 - since all development was done by reverse engineering, there is
Dtoshiba_haps.txt54 since kernel version 3.15.
/linux-4.4.14/drivers/input/
DKconfig59 option is only useful for out-of-tree drivers since
72 useful for out-of-tree drivers since in-tree drivers
85 useful for out-of-tree drivers since in-tree drivers
/linux-4.4.14/Documentation/spi/
Dspi-sc18is60218 The driver does not probe for supported chips, since the SI18IS602/603 does not
Dspi-lm70llp47 Note that since the LM70 uses a "3-wire" variant of SPI, the SI/SO pin
Dbutterfly18 This is more powerful than "ISP programming" cables since it lets kernel
/linux-4.4.14/Documentation/networking/
Dxfrm_sync.txt29 machine is known ahead of time since the decay of the time countdown
83 This TLV carries the running/current counter for byte lifetime since
87 This TLV carries the running/current counter for replay sequence since
Dx25.txt21 the Packet Layer but there will be no confusion since the class of device
Dde4x5.txt110 remove them for Alphas since the Tulip hardware only does longword
143 is the preferred way to use this driver, since it doesn't have this
/linux-4.4.14/Documentation/filesystems/
Ddirectory-locking75 not contended, since any process blocked on it is not holding any locks.
101 to (2) the order hadn't changed since we had acquired filesystem lock.
114 new parent had been equal to or a descendent of source since the moment when
Daffs.txt49 This is useful since most of the plain AmigaOS files
196 will not since the names are matched by the shell.
203 You cannot execute programs on an OFS (Old File System), since the
Decryptfs.txt72 development, since secret values will be written out to the system log
Dlocks.txt20 This should not cause problems for anybody, since everybody using a
Dtmpfs.txt62 since the OOM handler will not be able to free that memory.
76 mount with such options, since it allows any user with write access to
Dcoda.txt230 which does not block Venus since Venus must attend to other tasks even
784 The attributes of the directory should be returned too, since the size
826 The attributes of the parent should be returned since the size and
887 NNOOTTEE The attributes of the target directory should be returned since
916 NNOOTTEE The attributes of the directory should be returned since its
945 NNOOTTEE The attributes of the parent directory should be returned since
1197 since it can be used to deal with read/write memory mapped files.
1292 NNOOTTEE It should be removed since it is against the Coda philosophy that
1329 removed since it causes a jungle of pointers in the VFS mounting area.
1388 noted that it doesn't work. Not surprising, since the kernel does not
[all …]
Domfs.txt45 have a smaller size than a data block, but since they are both addressed by the
/linux-4.4.14/drivers/net/wireless/ath/wil6210/
DKconfig24 For production code, use COR (say y); is default since
/linux-4.4.14/Documentation/driver-model/
Dplatform.txt118 or coldplugged, since those mechanisms require device creation to be in a
131 outside the driver. This will usually be cleanup, since such drivers
183 be probed later if another device registers. (Which is OK, since
219 driver example since the early serial driver code should be disabled
/linux-4.4.14/drivers/block/aoe/
Daoecmd.c664 int since; in rexmit_deferred() local
709 since = tsince_hr(f); in rexmit_deferred()
710 f->waited += since; in rexmit_deferred()
711 f->waited_total += since; in rexmit_deferred()
759 int since; in rexmit_timer() local
791 since = tsince_hr(f); in rexmit_timer()
792 n = f->waited_total + since; in rexmit_timer()
807 n = f->waited + since; in rexmit_timer()
/linux-4.4.14/Documentation/devicetree/bindings/bus/
Dbrcm,bus-axi.txt18 (devices). This is needed since some hardware details can't be auto
/linux-4.4.14/Documentation/usb/
Dohci.txt14 Changes since the 2.4 kernel include
Dehci.txt27 While usb-storage devices have been available since mid-2001 (working
29 been available since late 2001, and other kinds of high speed devices
31 Such new systems have been available since early 2002, and became much
62 since EHCI represents these with a different data structure. So for now,
Ddwc3.txt43 There should be no increase in latency since the interrupt-thread has a
Dgadget_multi.txt61 For mass storage it is trivial since Windows detect it's an interface
86 functionality. As an effect provided INFs won't work since they have
Ddma.txt112 here, since it's cheaper to just synchronize the buffer than to unmap it
130 Note that several of those interfaces are currently commented out, since
Dmtouchusb.txt39 download, I persist in updating this driver since I would like to use the
/linux-4.4.14/Documentation/arm64/
Dtagged-pointers.txt30 since it is likely that C compilers will not hazard two
/linux-4.4.14/net/decnet/
DKconfig20 below when using DECnet, since you will need sysctl support to aid
/linux-4.4.14/drivers/staging/android/
DTODO22 since ion would just be the central allocator for shared buffers.
/linux-4.4.14/Documentation/timers/
Dhpet.txt12 also called "timers", which can be misleading since usually timers are
/linux-4.4.14/arch/avr32/boards/atngw100/
DKconfig39 MCI platform device, since it conflicts with the LCD platform device.
/linux-4.4.14/drivers/staging/media/davinci_vpfe/
DTODO27 As of now since the interface will undergo few changes all the include
/linux-4.4.14/arch/cris/arch-v32/kernel/
Dkgdb_asm.S17 ;; First of all, save the ACR on the stack since we need it for address calculations.
25 ;; to save and restore CCS manually, but since we aren't we treat it like every other
/linux-4.4.14/Documentation/parisc/
Dregisters103 use this, since you need the pointer to get back to your
105 since the caller can't rely on the value being the same
/linux-4.4.14/fs/ncpfs/
DKconfig75 This is only a cosmetic option since the OS2/LONG namespace is case
81 differently under Linux and under Windows, since Windows does an
/linux-4.4.14/Documentation/ide/
DChangeLog.ide-cd.1994-2004171 * messages, since this is not an error.
175 * since the .pdf version doesn't seem to work...
186 * - ide_cdrom_reset enabled since the ide subsystem
200 * CDROMREADRAW, since many drives don't support
DChangeLog.ide-floppy.1996-200223 * IDEFLOPPY_CAPABILITIES_PAGE, since we need the srfp
/linux-4.4.14/Documentation/m68k/
DREADME.buddha110 polls two words out of the same address of IDE port since
121 command access to the harddisk/CD-Rom, since command
185 performance of the card, since this doesn't happen very
/linux-4.4.14/Documentation/devicetree/bindings/i2c/
Di2c-rk3x.txt34 value since they are the same in nearly all cases.
/linux-4.4.14/Documentation/security/
DLSM.txt6 "module" is a bit of a misnomer since these extensions are not actually
/linux-4.4.14/Documentation/fmc/
Dparameters.txt20 EEPROM dumping avoids repeating lines, since most of the contents is
/linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm7038-l1-intc.txt5 since BCM7038 has contained this hardware.
/linux-4.4.14/Documentation/block/
Dqueue-sysfs.txt6 any settings, since their queue merely functions are a remapping target.
97 this amount, since it applies only to reads or writes (not the accumulated
Dbiovecs.txt86 fine to _most_ devices, but since accessing the raw bvec array was the
88 since all drivers _must_ go through the bvec iterator - and have been
Ddeadline-iosched.txt68 Front merges may still occur due to the cached last_merge hint, but since
/linux-4.4.14/arch/arm/nwfpe/
Dfpmodule.inl69 * Operate directly on userRegisters since
/linux-4.4.14/fs/ufs/
DKconfig16 Note that this option is generally not needed for floppies, since a
/linux-4.4.14/Documentation/devicetree/bindings/dma/
Dfsl-imx-sdma.txt11 The -to variants should be preferred since they allow to determine the
/linux-4.4.14/fs/sysv/
DKconfig24 Note that this option is generally not needed for floppies, since a
/linux-4.4.14/Documentation/video4linux/
DREADME.saa713467 - saa7133/35 - saa7135 is probably a marketing decision, since all those
Dvivid.txt16 allows you to use this driver as a test input for application development, since
635 This behavior is also what you want, since a 75% Colorbar
640 to be sent since it emulates a detected colorspace change.
645 This behavior is also what you want, since a 75% Colorbar
650 to be sent since it emulates a detected colorspace change.
657 to be sent since it emulates a detected colorspace change.
663 to be sent since it emulates a detected colorspace change.
727 to be sent since it emulates a changed input condition (e.g. a cable
734 to be sent since it emulates a changed input standard.
743 to be sent since it emulates a changed input condition (e.g. a cable
[all …]
Dv4l2-controls.txt196 controls. There is no min argument since that is always 0 for menu controls,
319 and cur.val fields can be considered an alias since these are used so often.
365 by the same handler since the handler's lock is held. If you need to access
377 will result in a deadlock since these helpers lock the handler as well.
539 present, since that is the 'master' control of the cluster. The master
576 Finally the V4L2_CTRL_FLAG_UPDATE should be set for the auto control since
658 This would be bad since muting the radio would not change the video mute
/linux-4.4.14/Documentation/devicetree/bindings/arm/samsung/
Dpmu.txt18 - #clock-cells : must be <1>, since PMU requires once cell as clock specifier.
/linux-4.4.14/Documentation/s390/
Dmonreader.txt169 should discard the data read since the last successful read with 0 size.
171 discard the data read since the last successful read with 0 size.
175 EOVERFLOW: message limit reached, the data read since the last successful
/linux-4.4.14/drivers/media/radio/
DKconfig298 Note: this driver hasn't been tested since a long time due to lack
413 Note: this driver hasn't been tested since a long time due to lack
428 Note: this driver hasn't been tested since a long time due to lack
451 Note: this driver hasn't been tested since a long time due to lack
485 Note: this driver hasn't been tested since a long time due to lack
/linux-4.4.14/arch/arm/boot/dts/
Dsocfpga_arria10_socdk.dtsi53 * All skews are offset since hardware skew values for the ksz9031
Drk3288-veyron-pinky.dts59 * Use a pullup instead of a drive since the output is 3.3V and
Dexynos5250-spring.dts129 * The following arrays of DVS voltages are not used, since we are
357 * Disabled pullups since external part has its own pullups and
/linux-4.4.14/arch/arm/lib/
Dlib1funcs.S64 @ four bits, since this is the amount of unwinding in the main
151 @ four bits, since this is the amount of unwinding in the main
Ddiv64.S142 @ divisor at this point since divisor can not be smaller than 3 here.
/linux-4.4.14/drivers/media/rc/img-ir/
DKconfig26 power since only a single interrupt is received for each scancode,
/linux-4.4.14/Documentation/devicetree/bindings/sound/
Dnvidia,tegra30-ahub.txt46 Can be empty since the mapping is 1:1.
/linux-4.4.14/arch/cris/boot/rescue/
Dkimagerescue.S48 ;; since etrax actually starts at address 2 when booting from flash, we
/linux-4.4.14/arch/cris/boot/compressed/
Dhead_v10.S58 ;; in the flash (since we wont try to copy it to DRAM
/linux-4.4.14/sound/oss/
DCHANGELOG139 - Removed MAD16+CS4231 hack made in previous version since it didn't
153 - Temporarily disabled recording with ESS1688/688 since it causes crash.
217 since TB doesn't allow me to release that code.
222 to the initialization code. This may break modules support since
/linux-4.4.14/Documentation/w1/slaves/
Dw1_ds242332 - 2 bytes for crc16 which was calculated from the data read since the previous crc bytes
/linux-4.4.14/Documentation/sound/alsa/soc/
DDPCM.txt96 for headset since the path is now disabled.
101 trigger(start) for DAI1 Speakers since the path is enabled.
167 The FE DAI above sets the codec and code DAIs to dummy devices since the BE is
/linux-4.4.14/fs/cramfs/
DREADME69 default mkcramfs doesn't test for & create holes, since cramfs in
92 written for, since comments in <linux/pagemap.h> indicate that
/linux-4.4.14/arch/x86/
DMakefile_32.cpu4 #-mtune exists since gcc 3.4
/linux-4.4.14/Documentation/misc-devices/
Dc2port.txt57 Initially the C2port access is disabled since you hardware may have
Dapds990x.txt60 RO - lux0_input max value. Actually never reaches since sensor tends
/linux-4.4.14/arch/arm/mm/
Dproc-fa526.S114 mcr p15, 0, ip, c7, c5, 6 @ invalidate BTB since mm changed
/linux-4.4.14/Documentation/devicetree/bindings/media/
Dsamsung-s5c73m3.txt40 similarly specified, but it is optional since the S5C73M3 ISP and a raw image
/linux-4.4.14/arch/powerpc/platforms/44x/
DKconfig113 select 460EX # Odd since it uses 460GT but the effects are the same
138 select 460EX # Odd since it uses 460GT but the effects are the same
/linux-4.4.14/Documentation/scheduler/
Dsched-rt-group.txt46 obviously fall short. A fuzzy upper limit is of no use since it cannot be
179 do deadline inheritance (since priority is inversely proportional to the
/linux-4.4.14/arch/cris/arch-v10/kernel/
Dhead.S32 ;; since etrax actually starts at address 2 when booting from flash, we
46 ;; Notice that since we're potentially running at 0x00 or 0x40 right now,
298 ;; We need to copy it backwards, since they can be overlapping
Dentry.S209 ;; using RBF since it was not stacked with SBFS. instead we would like to
408 ;; do the RBFexit since we might have killed off the running
505 ;; since *not* doing that saves us from re-entrancy checks. We don't want
/linux-4.4.14/Documentation/isdn/
DINTERFACE53 ***CHANGE0.6: New since this version.
169 ***CHANGEI1.14: The driver-Id and channel-number are new since this revision.
193 ***CHANGEI1.14: The driver-Id and channel-number are new since this revision.
199 ***CHANGE0.7: New since this version.
264 ***CHANGE0.7.1: New since this version: ServiceIndicator and AddInfo.
324 ***CHANGE0.6: New since this version the "empty-string"-feature.
/linux-4.4.14/fs/f2fs/
DKconfig91 efficient since it avoids caching the encrypted and
/linux-4.4.14/Documentation/devicetree/bindings/gpio/
Dgpio-pcf857x.txt8 low/high value, without knowing the last value written since the chip came out
/linux-4.4.14/Documentation/device-mapper/
Dera.txt81 - Ascertain which blocks have been written since the snapshot was taken
/linux-4.4.14/Documentation/networking/mac80211_hwsim/
DREADME24 since all radio operation is simulated, any channel can be used in
/linux-4.4.14/arch/powerpc/boot/dts/
Dtqm5200.dts143 reg = <0x3000 0x400>; // fec range, since we need to setup fec interrupts
Dcharon.dts141 reg = <0x3000 0x400>; // fec range, since we need to setup fec interrupts
/linux-4.4.14/Documentation/video4linux/bttv/
DPROBLEMS39 Would be nice if somebody could get this to work with XFree since
/linux-4.4.14/Documentation/devicetree/bindings/reset/
Dreset.txt23 the DT node of each affected HW block, since if activated, an unrelated block
/linux-4.4.14/Documentation/devicetree/
Doverlay-notes.txt132 The __symbols__ node is only required for the target=<phandle> method, since it
/linux-4.4.14/arch/xtensa/lib/
Dstrnlen_user.S102 # Do not add an extra one for the NULL terminator since we have
/linux-4.4.14/arch/powerpc/boot/dts/fsl/
Dp1020utm-pc.dtsi132 since U-Boot doesn't clear the status property when
Dp1020mbg-pc.dtsi143 since U-Boot doesn't clear the status property when
/linux-4.4.14/Documentation/filesystems/nfs/
Dfault_injection.txt51 has not changed since the delegation was awarded. Clearing this list will
/linux-4.4.14/lib/raid6/
Dint.uc52 * These sub-operations are separate inlines since they can sometimes be
/linux-4.4.14/Documentation/thermal/
Dcpu-cooling-api.txt164 However, since both implementation specific and complex relationships
188 information is not passed to the model since access to such data, from
/linux-4.4.14/Documentation/watchdog/
Dwatchdog-api.txt47 good idea, since if there is a bug in the watchdog daemon and it
195 The watchdog saw a keepalive ping since it was last queried.
/linux-4.4.14/Documentation/devicetree/bindings/arm/
Didle-states.txt28 states listed above; "off" state is not an idle state since it does not have
106 the worst case since it depends on the CPU operating conditions, ie caches
109 An OS has to reliably probe the wakeup-latency since some devices can enforce
115 The min-residency time parameter deserves further explanation since it is
/linux-4.4.14/Documentation/ptp/
Dptp.txt69 class driver, since the lock may also be needed by the clock
/linux-4.4.14/fs/ntfs/
DKconfig69 write support, included in Linux 2.5.10 and before (since 1997),
/linux-4.4.14/Documentation/gpio/
Ddriver.txt170 data. (Notice handler data, since the irqchip data is likely used by the
254 does not help since it pins the module to the kernel forever (it calls
266 These functions must be used with care since they do not affect module use

123