| /linux-4.4.14/Documentation/ |
| D | robust-futexes.txt | 14 that says "there's a waiter pending", and the sys_futex(FUTEX_WAIT)
19 value) that there were waiter(s) pending, and does the
22 state, and there's no in-kernel state associated with it. The kernel
23 completely forgets that there ever was a futex at that address. This
40 the kernel cannot help with the cleanup: if there is no 'futex queue'
41 (and in most cases there is none, futexes being fast lightweight locks)
71 because the kernel has no knowledge about how many robust futexes there
85 At the heart of this new approach there is a per-thread private list of
89 time, the kernel checks this user-space list: are there any robust futex
92 In the common case, at do_exit() time, there is no list registered, so
[all …]
|
| D | logo.txt | 2 ("currently unofficial" just means that there has been no paperwork and
7 Note that there are black-and-white versions of this available that
|
| D | workqueue.txt | 29 While there are work items on the workqueue the worker executes the
31 there is no work item left on the workqueue the worker becomes idle.
126 stalling should be optimal. As long as there are one or more runnable
129 schedules a new worker so that the CPU doesn't sit idle while there
160 there is one.
245 may queue at the same time. Unless there is a specific need for
329 set has an execution context reserved for it. If there is
333 * Unless strict ordering is required, there is no need to use ST wq.
335 * Unless there is a specific need, using 0 for @max_active is
355 there are a few tricks needed to shed some light on misbehaving
[all …]
|
| D | cachetlb.txt | 46 there will be no entries in the TLB for 'mm'.
60 running, there will be no entries in the TLB for 'mm' for
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
171 addresses from the cache. After running, there will be no
199 After running, there will be no entries in the cache for
211 After running, there will be no entries in the cache for
222 there will be no entries in the cache for the kernel address
251 mapped into some user address space, there is always at least one more
[all …]
|
| D | sparse.txt | 18 there because sparse will complain about casting to/from a bitwise type,
26 Quite frankly, you don't need the enum there. The above all really just
42 vs cpu-endian vs whatever), and there the constant "0" really _is_
|
| D | sgi-ioc4.txt | 12 functions, meaning that there's no clear "owning" device driver.
15 drivers, "ioc4", "sgiioc4", and "ioc4_serial". Note that there is no
|
| D | bus-virt-phys-mapping.txt | 14 However, on many setups, there are actually _three_ different ways of looking
29 not the CPU. Now, in theory there could be many different bus
70 (but there are also Alphas where the physical address and the bus address
136 whatever, and there is only one way to access it: the readb/writeb and
138 there is really nothing you can do with such an address: it's not
|
| D | pi-futex.txt | 39 data structures, instead of lockless algorithms. Furthermore, there are
58 different, there we cannot disable interrupts or make the task
91 remaining work: if there is no futex-queue attached to the futex address
113 there is no prior 'registration' of a PI-futex. [which is not quite
|
| D | parport.txt | 9 because there are a lot of people using the same IRQ for their
59 In 2.2 kernels there was a module called parport_probe, which was used
90 see a new directory entry: /proc/sys/dev/parport. In there will be a
138 string "none" means that there are no device drivers
207 that this is different to the way older kernels worked; there used to
|
| D | oops-tracing.txt | 41 run a null modem to a second machine and capture the output there
63 Actually, there are things you can do that make this easier. I have two
123 wonder how the NULL pointer got there, and if it's a valid thing to do
145 In order to help Linus and the other kernel developers there has been
167 kernel's dynamic memory pools there are no fixed locations for either
180 Since the kernel module environment can be dynamic there must be a
254 8: 'D' if the kernel has died recently, i.e. there was an OOPS or BUG.
|
| D | bcache.txt | 25 Since random IO is what SSDs excel at, there generally won't be much benefit
104 but all the cached data will be invalidated. If there was dirty data in the
191 and there's no other traffic - that can be a problem.
193 Solution: warm the cache by doing writes, or use the testing branch (there's
194 a fix for the issue there).
212 Write to this file to detach from a cache set. If there is dirty data in the
248 clean: Part of a cache set, and there is no cached dirty data.
250 dirty: Part of a cache set, and there is cached dirty data.
252 inconsistent: The backing device was forcibly run by the user when there was
|
| D | this_cpu_ops.txt | 14 This means that there are no atomicity issues between the calculation of
30 processor should be accessing that variable and therefore there are no
95 instead of the following operations required if there is no segment
109 per cpu counters is correctly incremented. However, there is no
215 so is expensive. If there are other reasons why the scheduler cannot
216 change the processor we are executing on then there is no reason to
|
| D | CodingStyle | 93 braces. Unlike the indent size, there are few technical reasons to
116 However, there is one special case, namely functions: they have the
231 putting a line of code there, such as if you leave a blank line. As a result,
264 Calling it "loop_counter" is non-productive, if there is no chance of it
297 The reason we have them for things like pte_t etc. is that there
298 really is absolutely _zero_ portably accessible information there.
306 NOTE! Again - there needs to be a _reason_ for this. If something is
307 "unsigned long", then there's no reason to do
311 but if there is a clear reason for why it under certain circumstances
340 Maybe there are other cases too, but the rule should basically be to NEVER
[all …]
|
| D | IRQ.txt | 20 are encouraged to in the case where there is any manual configuration
|
| D | xz.txt | 37 For decompressing the kernel image, initramfs, and initrd, there
63 Using CRC32 is strongly recommended unless there is some other layer
115 kernel-related mailing lists, so if there's something I should know,
|
| D | rpmsg.txt | 70 In case there are no TX buffers available, the function will block until
87 In case there are no TX buffers available, the function will block until
105 In case there are no TX buffers available, the function will block until
120 In case there are no TX buffers available, the function will immediately
134 In case there are no TX buffers available, the function will immediately
149 In case there are no TX buffers available, the function will immediately
|
| D | kprobes.txt | 140 time the probed function is entered but there is no kretprobe_instance
163 In case probed function is entered but there is no kretprobe_instance
180 probepoint, there'll be a probe there.
191 - Kprobes analyzes the entire function and verifies that there is no
198 - there is no near jump to the optimized region (other than to the first
259 returns to original address, there is no valid instruction,
280 that there are some functions where kprobes cannot probe. Probing
519 however, there cannot be multiple jprobes on the same function at
520 the same time. Also, a probepoint for which there is a jprobe or
536 install probes there. gcc may inline a function without being asked,
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/power/ |
| D | twl-charger.txt | 4 to know when charging is permissible, and when there is a connection
7 The choice of phy cannot be configured at a hardware level, so there
9 if there is a sibling of the BCI node which is compatible with
|
| /linux-4.4.14/Documentation/devicetree/bindings/net/ |
| D | brcm,unimac-mdio.txt | 15 Ethernet switch this MDIO block is integrated from, or must be two, if there
18 - interrupt-names: must be "mdio_done_error" when there is a share interrupt fed
20 "mdio_error" for the second when there are separate interrupts
|
| D | snps,dwc-qos-ethernet.txt | 32 mdio, there must be device tree subnode with the following
38 For each phy on the mdio bus, there must be a node with the following
|
| D | altera_tse.txt | 36 mdio, there must be device tree subnode with the following
43 For each phy on the mdio bus, there must be a node with the following
|
| /linux-4.4.14/Documentation/timers/ |
| D | NO_HZ.txt | 35 there are some situations where this old-school approach is still the
37 that use short bursts of CPU, where there are very frequent idle
40 clock interrupts will normally be delivered any way because there
64 If a CPU is idle, there is little point in sending it a scheduling-clock
76 unnecessary scheduling-clock interrupts. In these situations, there
102 If a CPU has only one runnable task, there is little point in sending it
103 a scheduling-clock interrupt because there is no other task to switch to.
116 by one less than the number of CPUs. In these situations, there is
126 (This is not an issue for CONFIG_NO_HZ_IDLE=y because there are no running
165 4. If there are more perf events pending than the hardware can
[all …]
|
| D | timers-howto.txt | 53 driving each of these calls varies, thus there are
78 - Why is there no "usleep" / What is a good range?
|
| /linux-4.4.14/Documentation/networking/ |
| D | spider_net.txt | 44 marks it full, and advances the GDACTDPA by one. Thus, when there is
53 and advance the tail pointer. Thus, when there is flowing RX traffic,
65 then mark the descr as "empty", ready to receive data. Thus, when there
115 the hardware can fill them, there is no problem. If, for some reason,
134 and is filling the next descrs. Since the OS doesn't see this, there
155 marked xa... which is "empty". Thus, from the OS point of view, there
156 is nothing to be done. In particular, there is the implicit assumption
166 and there can be no forward progress; the OS thinks there's nothing
175 operations there. Since this will leave "holes" in the ring, there
189 is full, the netdev is stopped. When there is room in the ring,
|
| D | vxlan.txt | 11 device, there is also a separate implementation of VXLAN for
28 group 239.1.1.1 over eth1 to handle traffic for which there is no
|
| D | policy-routing.txt | 27 RT_CLASS_MAIN=254 - all normal routes are put there
31 normal default routes are put there, if ip_fib_model==2
32 all gateway routes are put there.
|
| D | radiotap-headers.txt | 28 At the moment there are only 13 possible argument indexes defined, but in case
30 indicates that there is another u32 bitmap following (shown as "possible
62 - the above point that there may be no absolute alignment for multibyte
|
| D | 6pack.txt | 50 there is a file named 6pack.tgz.
131 FlexNet, the connect LED is on if there is a connection; the status LED is
132 on if there is data in the buffer of the PC's AX.25 engine that has to be
152 there is still an AX.25 connection left over which an IP connection was
154 occur when there is a bare AX.25 connection still running. I don't know if
|
| D | ieee802154.txt | 8 two layers: Medium Access Control (MAC) and Physical (PHY). And there
42 Like with WiFi, there are several types of devices implementing IEEE 802.15.4.
107 In addition there is a driver available which simulates a real device with
|
| D | rds.txt | 114 notifications via control messages (for instance, there is a
124 POLLIN handling is pretty straightforward. When there's an
130 there's room on the send queue (ie the number of bytes queued
187 it has more credits available (i.e. there is
218 there is space in the peer's receive buffers for more data. This
295 then maintained forever -- if there are transport errors, the
|
| D | ipddp.txt | 43 MacGate. In this distribution there will be a tool called MacRoute
53 This software expects there to be an AppleTalk-IP gateway on the network.
|
| D | nf_conntrack-sysctl.txt | 50 A higher number means there will be fewer delivery retries and it
176 This extended timeout will be used in case there is an UDP stream
|
| D | fib_trie.txt | 28 adjacent to the parent (pos+bits), but there will be some bits
84 and there may be some room for experimentation here.
139 At this point we will repeatedly descend subtries to look for a match, and there
|
| /linux-4.4.14/Documentation/devicetree/bindings/sound/ |
| D | imx-audio-spdif.txt | 16 indicating there's a physical S/PDIF out connector
22 function of S/PDIF will be enabled, indicating there
|
| D | ics43432.txt | 5 frequency (460 kHz to 3.379 MHz according to the data sheet) there must be
|
| D | tdm-slot.txt | 17 And for each spcified driver, there could be one .of_xlate_tdm_slot_mask()
|
| /linux-4.4.14/Documentation/power/ |
| D | basic-pm-debugging.txt | 43 there is the file /sys/power/pm_test that can be used to make the hibernation
101 If the "freezer" test fails, there is a task that cannot be frozen (in that case
104 that there is a problem with the tasks freezer subsystem that should be
107 If the "devices" test fails, most likely there is a driver that cannot suspend
117 Once you have found the failing driver (there can be more than just one of
127 If the "platform" test fails, there is a problem with the handling of the
152 "reboot", "shutdown" and "platform" modes. If that does not work, there
155 individually. Otherwise, there is a problem with a modular driver and you can
158 - if there are n modules loaded and the attempt to suspend and resume fails,
161 - if there are n modules loaded and the attempt to suspend and resume succeeds,
[all …]
|
| D | freezing-of-tasks.txt | 97 Generally speaking, there is a couple of reasons to use the freezing of tasks:
101 filesystems, so if there are any modifications made to filesystem data and/or
137 avoid *that*, there's no question about that. And I suspect that stopping
144 Still, there are kernel threads that may want to be freezable. For example, if
163 V. Are there any problems related to the freezing of tasks?
165 Yes, there are.
173 Second, there are the following two problems related to the freezing of user
202 VI. Are there any precautions to be taken to prevent freezing failures?
204 Yes, there are.
|
| D | charger-manager.txt | 11 represents an independent battery with chargers. If there are multiple
64 if there are multiple batteries. If there are multiple batteries, the
84 same struct. If there is any other wakeup source triggered the
100 If there are no other devices or tasks that want to use suspend_again
183 If there is an charger event is required to notify
|
| /linux-4.4.14/arch/metag/lib/ |
| D | memcpy.S | 15 ! If there are less than 16 bytes to copy use the byte copy loop
74 ! If there are any remaining bytes use the byte copy loop, otherwise we are done
79 ! The destination is 8 byte aligned but the source is not, and there are 8
91 ! if there is no mis-alignment after all, use the aligned copy loop
175 ! If there are no remaining bytes to copy, we are done.
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 6.Followthrough | 10 It is a rare patch which is so good at its first posting that there is no
36 people remember who wrote kernel code, but there is little lasting fame
90 but there are times when somebody simply has to make a decision. If you
106 things. In particular, there may be more than one tree - one, perhaps,
110 For patches applying to areas for which there is no obvious subsystem tree
119 there's a good chance that you will get more comments from a new set of
141 the patch before. It may be tempting to ignore them, since there is no
150 where there are testers, there will be bug reports.
161 After any regressions have been dealt with, there may be other, ordinary
169 And don't forget that there are other milestones which may also create bug
[all …]
|
| D | 3.Early-stage | 125 the MAINTAINERS file for a relevant place to post. If there is a suitable
126 subsystem list, posting there is often preferable to posting on
132 and not all subsystems are represented there. The person listed in the
134 that role currently. So, when there is doubt about who to contact, a
168 matter is (1) kernel developers tend to be busy, (2) there is no shortage
176 not assume that it means there is no interest in the project.
177 Unfortunately, you also cannot assume that there are no problems with your
196 considering whether the secrecy is really necessary; there is often no real
199 That said, there are also cases where a company legitimately cannot
|
| D | 8.Conclusion | 40 the shelves for a while now. Still, there is quite a bit of good
41 information to be found there.
|
| D | 1.Intro | 8 there is some technical material here, this is very much a process-oriented
17 encounter there. There are a great many reasons why kernel code should be
35 patches are covered, and there is an introduction to some of the tools
97 intimidating to new developers, but there are good reasons and solid
207 is there regardless.
256 there is no prospect of a migration to version 3 of the GPL in the
272 legal questions relating to Linux source code, there is no substitute for
|
| /linux-4.4.14/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra20-gpio.txt | 7 there should be 7 interrupts specified, and for Tegra30, there should
|
| /linux-4.4.14/drivers/block/paride/ |
| D | Transition-notes | 50 be preempted there.
51 2) When there is such a thread, pd_busy is set or pd_lock is held by
53 3) When there is such a thread, ps_tq_active is 0 or ps_spinlock is
55 4) When there is such a thread, all PIA belonging to pd.c have NULL
60 (1) can become not true if some thread enters that area while another is there.
72 case that needs consideration is call from pi_wake_up() and there
123 We don't need to reset it to NULL, since we are guaranteed that there
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-firmware-opal-elog | 15 Linux if there is no room for more log entries.
38 For each log entry (directory), there are the following
47 In the future there may be additional types.
|
| /linux-4.4.14/Documentation/blackfin/ |
| D | bfin-gpio-notes.txt | 54 3. But there are some exceptions
62 Note: Consider the case that, if there are two drivers need the
65 there is any abnormal driver behavior, please check the bfin-gpio
|
| D | bfin-spi-notes.txt | 3 With the Blackfin on-chip SPI peripheral, there is some logic tied to the CPHA
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-kernel-boot_params | 9 If there's no setup_data in boot_params the subdirectory will
19 as a link list. In "setup_data" subdirectory there's one
|
| D | sysfs-platform-eeepc-laptop | 32 On the Eee PC 1000H there are three available clock configuration:
36 On Eee PC 701 there is only 2 available clock configurations.
|
| D | sysfs-bus-intel_th-devices-msc | 17 provided there are no active users and tracing is not enabled,
30 there are no active users and tracing is not enabled) and then
|
| D | sysfs-ata | 26 Behind each port, there is a ata_link. If there is a SATA PM in the
53 - Z the device id: for PATA, there is usually 2 devices [0,1],
|
| D | sysfs-bus-iio-gyro-bmg160 | 7 only when there is any motion.
|
| D | sysfs-bus-iio-accel-bmc150 | 7 only when there is any motion.
|
| D | sysfs-firmware-dmi-entries | 8 cases where there are OEM extensions used.
31 to say, if there are 'N' multiple entries with the same type
47 there are likely firmware images that get this wrong in
|
| D | sysfs-kernel-uids | 8 propotional value. What that means is that if there
|
| D | sysfs-bus-intel_th-devices-pti | 13 when there is trace data to send. 1: PTI trace clock is a
|
| D | sysfs-ocfs2 | 84 cluster stack unless there are mounted ocfs2 filesystems.
85 If there are mounted filesystems, attempts to change the
|
| D | sysfs-devices | 14 on the symlinks there to point to the proper location
|
| D | sysfs-bus-platform | 20 the override, there is no support for parsing delimiters.
|
| D | sysfs-bus-amba | 19 Only a single driver may be specified in the override, there is
|
| /linux-4.4.14/Documentation/mmc/ |
| D | mmc-async-req.txt | 39 truly non-blocking. If there is an ongoing async request it waits
41 doesn't wait for the new request to complete. If there is no ongoing
57 with the previous transfer, since there is no previous request.
58 The argument is_first_req in pre_req() indicates that there is no previous
|
| /linux-4.4.14/drivers/staging/media/bcm2048/ |
| D | TODO | 11 support is now available as controls (although there may well be some
14 properties/controls should be there at all.
|
| /linux-4.4.14/Documentation/scsi/ |
| D | sym53c500_cs.txt | 15 of the New Media Bus Toaster PCMCIA SCSI controller. Presumably there are
19 Through the years, there have been a number of downloads of the pcmcia-cs
|
| D | scsi-changer.txt | 35 i.e. there the operator (you !) can use this to
52 should be source code compatible with NetBSD. So if there is any
91 look for LUNs other than 0 as default, because there are too many
143 These insmod options can be used to tell the driver that there
|
| D | dc395x.txt | 22 setup. If there is no EEPROM, the driver uses default values.
100 reliable driver, there is a chance, that it will kill your valuable data.
|
| D | qlogicfas.txt | 38 function. If there are any problems, try setting SLOW_CABLE to 1, and
40 with SCSI, there are other settings which can tune the bus.
|
| D | aha152x.txt | 126 Moreover there are certain limitations to the C/H/S addressing scheme,
142 (but there are already bigger disks out there today).
|
| /linux-4.4.14/Documentation/devicetree/bindings/thermal/ |
| D | st-thermal.txt | 14 and module type (sas or mpe). On stid127 & stih407 there is only
15 one die/module, so there is no module type in the compatible
|
| /linux-4.4.14/Documentation/devicetree/bindings/regulator/ |
| D | tps62360-regulator.txt | 15 If this property is missing, then assume that there is no GPIO
18 If this property is missing, then assume that there is no GPIO
|
| D | gpio-regulator.txt | 6 if there are no states, then use a fixed regulator
|
| /linux-4.4.14/Documentation/vm/ |
| D | active_mm.txt | 11 > Is there a brief description someplace on how "mm" vs. "active_mm" in
50 "mm_users" counter that is how many "real address space users" there are,
52 users) plus one if there are any real users.
54 Usually there is at least one real user, but it could be that the real
|
| /linux-4.4.14/Documentation/RCU/ |
| D | trace.txt | 35 update cycles that the current test has started, or zero if there is
125 periods, and so there is likely to be an extended period of time
143 "N" Indicates that there are callbacks queued that are not
148 "R" Indicates that there are callbacks queued that are
151 "W" Indicates that there are callbacks queued that are
154 "D" Indicates that there are callbacks queued that have
163 If there are no callbacks in a given one of the above states,
204 the first slash is zero if there is no work pending and 1
214 "W" The kernel thread is waiting because there is no work
277 If these two fields are equal, then there is no grace period
[all …]
|
| D | UP.txt | 6 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
62 there are cases where this can be quite ugly:
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | README | 19 As usual, there are two main things to consider:
43 at run-time, and the /proc/sys/ directory is there so that you
45 In fact, there are only four things needed to use these config
|
| D | sunrpc.txt | 16 The files in there are used to control the debugging flags:
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | imx-weim.txt | 53 For i.MX1, i.MX21 ("fsl,imx1-weim") there are two
56 there are three registers: CSCRxU, CSCRxL, CSCRxA.
59 there are six registers: CSxGCR1, CSxGCR2, CSxRCR1,
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | output_arch.ld | 1 /* At the time of this writing, there's no equivalent ld option. */
|
| /linux-4.4.14/arch/cris/arch-v32/ |
| D | output_arch.ld | 1 /* At the time of this writing, there's no equivalent ld option. */
|
| /linux-4.4.14/Documentation/devicetree/ |
| D | changesets.txt | 25 ensures there can only be one editor at a time.
28 entire changeset will get applied, or if there is an error the tree will
|
| /linux-4.4.14/scripts/coccinelle/locks/ |
| D | mini_lock.cocci | 2 /// where the unlock is missing from an if branch, and there is a lock
5 /// supposed to exit with the lock held, or where there is some preceding
|
| /linux-4.4.14/arch/arm/vfp/ |
| D | vfphw.S | 107 @ state if there was a previous (valid) owner.
119 tst r1, #FPEXC_EX @ is there additional state to save?
122 tst r1, #FPEXC_FP2V @ is there an FPINST2 to read?
|
| /linux-4.4.14/Documentation/block/ |
| D | stat.txt | 9 Q. Why are there multiple statistics in a single file? Doesn't sysfs
58 waited on this block device. If there are multiple I/O requests waiting,
80 on this block device. If there are multiple I/O requests waiting, this
|
| D | cfq-iosched.txt | 35 there are multiple spindles behind single LUN (Host based hardware RAID
150 blkio cgroup directory. It is weight-based and there are four knobs
227 dispatch requests from other cfq queues even if requests are pending there.
246 of queues or the tree. So if there are 4 queues waiting for IO to dispatch
247 we will idle only once last queue has dispatched the IO and there is
268 For example, if there are 10 sequential readers doing IO and they get
|
| D | biovecs.txt | 18 bi_size and bi_idx have been moved there; and instead of modifying bv_offset
63 it somewhere else if there was an error) had to save the entire bvec array
118 there's no need to define ->merge_bvec_fn() callbacks for individual block
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Sound-FAQ | 10 To handle the grabber boards correctly, there is a array tvcards[] in
21 If your card isn't listed there, you might check the source code for
22 new entries which are not listed yet. If there isn't one for your
29 module like msp3400.o to make sound work. If there isn't one for the
57 As mentioned above, there is a array which holds the required
|
| D | README | 69 If you have trouble with some specific TV card, try to ask there
71 same card listens there is much higher...
74 for TV sound all over the world. And there are also different chips
|
| /linux-4.4.14/Documentation/mtd/ |
| D | nand_ecc.txt | 5 I felt there was room for optimisation. I bashed the code for a few hours
8 Still I was not too happy as I felt there was additional room for improvement.
247 Still pretty straightforward. The last three invert statements are there to
264 Fortunately there is plenty of room for improvement.
283 Anyway, if there is an issue: this code is developed on x86 (to be
393 This means there is no need to calculate rp14 as it can be calculated from
508 However, still I thought there was more. I didn't like all the if
574 Furthermore there are 4 sequential assignments to rp8. This can be
629 Guess that is what there is to win within the loop. Maybe unrolling one
642 This makes things worse. Let's stick with attempt 6 and continue from there.
[all …]
|
| /linux-4.4.14/arch/arm/mach-vexpress/ |
| D | dcscb_setup.S | 34 @ if any. In this case, there is nothing to do.
|
| /linux-4.4.14/Documentation/trace/ |
| D | events.txt | 79 When reading one of these enable files, there are four results:
83 X - there is a mixture of events enabled and disabled
219 If there is an error in the expression, you'll get an 'Invalid
341 section of Documentation/trace/ftrace.txt), but there are major
365 adds or removes a single trigger and there's no explicit '>>' support
380 The event tracepoint stays in this mode as long as there's a trigger
410 Note that there can be any number of enable/disable_event triggers
411 per triggering event, but there can only be one trigger per
453 Note that there can be only one stacktrace trigger per triggering
482 Note that there can be only one snapshot trigger per triggering
[all …]
|
| D | events-power.txt | 5 within the kernel. Broadly speaking there are three major subheadings:
87 And, there are also events used for device PM QoS add/update/remove request.
|
| /linux-4.4.14/Documentation/devicetree/bindings/ |
| D | graph.txt | 7 control flow to devices, but there can be more complex connections between
34 If more than one port is present in a device node or there is more than one
117 If there is more than one 'port' or more than one 'endpoint' node or 'reg'
|
| /linux-4.4.14/drivers/staging/android/ |
| D | Kconfig | 35 as there is no particular swap space on android.
57 synchronization. Useful when there is no hardware primitive backing
|
| /linux-4.4.14/drivers/gpu/drm/nouveau/nvkm/subdev/pmu/fuc/ |
| D | idle.fuc | 60 // keep looping while there's pending messages for any process
65 // process the process' messages until there's none left
|
| D | kernel.fuc | 161 // ... or if there's no next timer yet
270 /* check if there wasn't any overflow */
302 /* check if there wasn't any overflow */
356 // check for a pending interrupt. if there's one already
364 // or if there's no timeout already set
|
| /linux-4.4.14/Documentation/devicetree/bindings/memory-controllers/ti/ |
| D | emif.txt | 26 instance has a memory part attached to it. If there is a memory
28 so there is no need to give the details of this memory part.
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | knfsd-stats.txt | 42 Note that in the default case there will be a single thread pool
65 The circumstance this statistic tracks indicates that there was NFS
71 This can happen because there are too few nfsd threads in the thread
90 This statistic counts a circumstance where there are more nfsd
|
| /linux-4.4.14/arch/m68k/fpsp040/ |
| D | skeleton.S | 9 | before the jump instruction. If there no handling necessary, then
12 | exception is one that must be reported then there will be a
17 | package returns. Thus, there will be system specific code
21 | the return will be via a 'jmp fpsp_done'. Unless there is
406 | there shouldn't be any supervisor mode floating point exceptions.
|
| /linux-4.4.14/Documentation/frv/ |
| D | features.txt | 54 there).
127 Barring point (1), there is nothing to protect kernel data against
134 imprecise data error exceptions, there are currently no automatic fixup
139 forcing the fault to happen there.
278 kernel is capable of supporting more tasks than there are possible ID
280 there are insufficient available.
307 When there isn't a pinned context, the file shows -1:
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | xfs-self-describing-metadata.txt | 17 validating and repairing the structure, there are limits to what they can
43 supposed to be there and the contents are valid".
89 complexity and so there is no provision for changing the integrity checking
123 whether the corruptions are related, whether there's been multiple corruption
124 events that lead to the eventual failure, and even whether there are corruptions
131 block is more recent than the object and the object's owner, then there is a
156 as there may be certain limitations that operational state enforces of the
157 metadata, or there may be corruption of interblock relationships (e.g. corrupted
268 If there are different magic numbers for the different formats, the verifier
330 self-identifiers, but they are packed so that there are multiple objects per
[all …]
|
| D | debugfs.txt | 7 there. The debugfs filesystem is also intended to not serve as a stable
8 ABI to user space; in theory, there are no stability constraints placed on
9 files exported there. The real world is not always so simple, though [1];
137 can be used to export binary information, but there does not appear to be
208 there is no automatic cleanup of any directories created in debugfs. If a
212 be prepared to remove all files and directories they create there. A file
|
| D | xfs-delayed-logging-design.txt | 75 log buffers made available by the log manager. By default there are 8 log
97 but only one of those copies needs to be there - the last one "D", as it
108 logical to physical formatting to do the relogging because there is no
125 words, instead of there only being a maximum of 2MB of transaction changes not
126 written to the log at any point in time, there may be a much greater amount
132 recovered filesystem is concerned, there may be many thousands of transactions
233 region headers in the formatting stage, which is problematic as there is per
296 reason for this limit is that to find the head and tail of the log, there must
298 transaction is larger than half the log, then there is the possibility that a
417 This allows transactions to be issued asynchronously even though there may be
[all …]
|
| D | hpfs.txt | 25 - there is a list of text extensions (I thing it's better to not convert
71 variable length. OS/2 stores window and icon positions and file types there. So
140 When there's not enough space for extended attributes, they will be truncated
204 If you don't install fixpacks, there are many, many more...
213 0.93 Fixed bug that locked up the machine when there were too many filenames
266 1.99 Corrected a possible problem when there's not enough space while deleting
268 Now it tries to truncate the file if there's not enough space when deleting
270 2.00 Fixed a bug in rename (it was there since 1.96)
|
| /linux-4.4.14/Documentation/arm64/ |
| D | arm-acpi.txt | 59 table as hardware vendors and other OS vendors. In fact, there is no
79 integrated devices, but there are no good processes for supporting what the
80 server vendors need. Linux could potentially get there with DT, but doing so
128 the kernel will try to use DT for device enumeration; if there is no DT
132 fall back to DT if there are no ACPI tables present. The basic idea is that
229 Source Language (section 19 of the specification). This means that there
235 names ("KEY0") to four characters unlike DT; (2) there is no industry
237 there is also no registry for the definition of property values ("value0"),
245 be used if _DSD cannot represent the data required, and there is no way
246 to create a new UUID for the _DSD object. Note that there is even less
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/arc/ |
| D | archs-pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| D | pct.txt | 4 CPU and cache events like cache misses and hits. Like conventional PCT there
|
| /linux-4.4.14/tools/perf/Documentation/ |
| D | perf-buildid-cache.txt | 33 permissions for root only. kcore will not be added if there is already a
52 (or remote) perf.data. Only if there is already a cache which has
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | sysfs.txt | 10 In addition, there is a "ports" subdirectory, with one subdirectory
11 for each port. For example, if mthca0 is a 2-port HCA, there will
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | TODO | 15 such as PCI-based serial ports. Also, there is not a way we can
26 notably) and used from there instead.
|
| /linux-4.4.14/fs/fscache/ |
| D | Kconfig | 22 execution as there are a quite a few stats gathered, and on a
39 execution as there are a number of points at which data is gathered,
|
| /linux-4.4.14/drivers/staging/dgnc/ |
| D | TODO | 6 * there is a lot of unnecessary code in the driver. It was
|
| /linux-4.4.14/Documentation/i2c/ |
| D | slave-eeprom-backend | 12 As of 2015, Linux doesn't support poll on binary sysfs files, so there is no
|
| D | slave-interface | 26 Note: Technically, there is also the I2C core between the backend and the
77 there is nothing to process or return. Wakeup or initialization probably needs
158 automatically ACK when detecting their slave addresses, so there is no option
162 Currently, there is no slave event to report if the master did ACK or NACK a
|
| D | instantiating-devices | 149 is found there it tries address 0x2d, and if still nothing is found, it
164 at 25 different addresses. Given the huge number of mainboards out there,
191 was done there. Two significant differences are:
194 Method 3 should only be used when there is no other way, as it can have
231 can't be done, there is a variety of cases where it can be helpful:
|
| D | fault-codes | 11 recovery, triggered by a fault report, there is no error.
75 address, but with the device found there. Driver probes
88 means there's nothing listening at that address.
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-amd756 | 23 Note that for the 8111, there are two SMBus adapters. The SMBus 1.0 adapter
|
| D | i2c-i801 | 123 /proc/acpi/thermal_zone. If you find anything there, it's likely that
132 and you think there's something interesting on the SMBus (e.g. a
152 If it works, proves useful (i.e. there are usable chips on the SMBus)
158 kernel. It's very convenient if you just want to check if there's
|
| D | i2c-amd8111 | 39 Note that for the 8111, there are two SMBus adapters. The SMBus 2.0 adapter
|
| D | i2c-via | 32 datasheets, but there are several ways the motherboard manufacturer
|
| /linux-4.4.14/Documentation/leds/ |
| D | ledtrig-oneshot.txt | 4 This is a LED trigger useful for signaling the user of an event where there are
15 A one-shot LED only stays in a constant state when there are no events. An
|
| /linux-4.4.14/Documentation/hid/ |
| D | uhid.txt | 6 relies heavily on the definitions declared there.
43 The "type" field defines the payload. For each type, there is a
153 there is actually no other process that reads your data so there is no need to
157 This is sent when there are no more processes which read the HID data. It is
170 The kernel serializes GET_REPORT requests so there will never be two in
|
| D | hid-sensor.txt | 62 with this name and will be probed if there is an accelerometer-3D detected.
118 if there is a field report_interval, which is parsed by a call to
127 if there is a field report_interval, which is parsed by a call to
139 to poll for any field. If there is some new sample, the core driver will call
198 Here there is a custom sensors with four fields, two feature and two inputs.
|
| /linux-4.4.14/Documentation/ide/ |
| D | warm-plug-howto.txt | 15 NOTE: please make sure that partitions are unmounted and that there are
|
| /linux-4.4.14/drivers/staging/media/cxd2099/ |
| D | TODO | 10 While there's no proper fix for it, the driver should be kept in staging.
|
| /linux-4.4.14/Documentation/devicetree/bindings/phy/ |
| D | st-spear-miphy.txt | 14 - phy-id: Instance id of the phy. Only required when there are multiple phys
|
| /linux-4.4.14/arch/mn10300/kernel/ |
| D | profile-low.S | 41 # do nothing if there's no buffer
|
| /linux-4.4.14/Documentation/devicetree/bindings/arm/ |
| D | kirkwood.txt | 11 In order to support the kirkwood cpufreq driver, there must be a node
|
| /linux-4.4.14/Documentation/devicetree/bindings/ata/ |
| D | ahci-fsl-qoriq.txt | 12 - reg-names: register area names when there are more than 1 register area.
|
| D | cavium-compact-flash.txt | 13 the device configuration, there may be one or two banks.
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-riic.txt | 11 Pinctrl properties might be needed, too. See there.
|
| D | i2c-mux-pca954x.txt | 20 children in idle state. This is necessary for example, if there are several
|
| D | i2c-sh_mobile.txt | 29 Pinctrl properties might be needed, too. See there.
|
| /linux-4.4.14/Documentation/devicetree/bindings/mailbox/ |
| D | brcm,bcm2835-mbox.txt | 10 channel. The value shall be 0, since there is only one
|
| D | arm-mhu.txt | 7 received data. However, there is no specified way of knowing if the sent
|
| /linux-4.4.14/Documentation/zh_CN/ |
| D | SecurityBugs | 7 or if there is a problem with the translation.
|
| D | stable_kernel_rules.txt | 7 or if there is a problem with the translation.
|
| D | IRQ.txt | 7 or if there is a problem with the translation.
|
| D | stable_api_nonsense.txt | 6 Contact the Chinese maintainer, if this translation is outdated or there
|
| D | basic_profiling.txt | 6 translation is outdated or there is problem with translation.
|
| /linux-4.4.14/Documentation/device-mapper/ |
| D | dm-log.txt | 33 will not survive a reboot or crash, but there may be a small boost in
40 so log implementations can be done there. This is done by forwarding most
|
| D | switch.txt | 9 It maps I/O to underlying block devices efficiently when there is a large
10 number of fixed-sized address regions but there is no simple pattern
38 members forward it as necessary, but there is a performance advantage to
|
| /linux-4.4.14/Documentation/locking/ |
| D | ww-mutex-design.txt | 12 PRIME / dmabuf, they can even be shared across devices. So there are
16 there is no way to guarantee that buffers appear in a execbuf/batch in
55 Furthermore there are three different class of w/w lock acquire functions:
66 work correctly. After all if no other ww mutex has been acquired yet there's
217 held there's no need for additional book-keeping to break cycles in the graph
223 different when retrying due to hitting the -EDEADLK wound condition) there's
309 normal mutex locks, which are far more common. As such there is only a small
|
| D | rt-mutex-design.txt | 39 Now there's no way of knowing how long A will be sleeping waiting for C
322 in more detail, but is set whenever there are waiters on a mutex.
422 When this function is called, there are no locks held. That also means
444 there is another process higher in priority that is blocked on one of the
493 So as long as there is an owner of this mutex that is not the same
543 mutex has not woken up yet, there's no reason that the higher priority process
566 If there is contention on the lock, whether it is owned or pending owner
579 does not implement CMPXCHG would always grab the lock (if there's no
585 be false, because if the mutex has no owner, there are no waiters and
614 is never blocked on a mutex. So there is no PI chain to worry about. It also
[all …]
|
| D | locktorture.txt | 126 (E): true/false values if there were errors acquiring the lock. This should
127 -only- be positive if there is a bug in the locking primitive's
147 two are self-explanatory, while the last indicates that while there
|
| /linux-4.4.14/Documentation/filesystems/caching/ |
| D | backend-api.txt | 298 object cannot be reclaimed to make space. Return -ENOSPC if there's not
397 This should return 0 if successful, -ENOSPC if there isn't enough space
417 If there's no page in the cache, then -ENODATA should be returned if the
421 If there is suitable data in the cache, then a read operation should be
462 If there was an error such as -ENOMEM, then that should be returned; else
476 read from the cache, even if there's data there that could be retrieved.
480 If there's no backing block available, then -ENOBUFS should be returned
481 (or -ENOMEM if there were other problems). If a block is successfully
501 This is called to write from a page on which there was a previously
647 known at this point that there can't be any data in the cache.
[all …]
|
| D | netfs-api.txt | 258 it has finished. This does not indicate whether there's data on the disk
429 The cache will return -ENOBUFS if there is no backing cache or if there is no
487 Else if there's a copy of the page resident in the cache:
514 Otherwise, if there's not a copy available in cache, but the cache may be able
531 Alternatively, if there's not expected to be any data in the cache for a page
582 Else if there's no space available in the cache, -ENOBUFS will be returned. It
612 (3) If there was an general error, then that error will be returned.
625 be called in interrupt context if there is no error.
799 -ENOSPC if there isn't enough space to honour the operation, -ENOMEM or
800 -EIO if there's any other problem.
[all …]
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/dac/ |
| D | ad7303.txt | 11 only be set if there is an external reference voltage connected to the REF
|
| /linux-4.4.14/Documentation/devicetree/bindings/eeprom/ |
| D | eeprom.txt | 6 If there is no specific driver for <manufacturer>, a generic
|
| /linux-4.4.14/arch/frv/mm/ |
| D | tlb-flush.S | 61 # find out how many lines there are
102 # find out how many lines there are
|
| /linux-4.4.14/Documentation/usb/ |
| D | WUSB-Design-overview.txt | 72 each superframe there is a Beacon Period (BP), where every device
124 interface, winetX). The driver detects when there is a link up for
136 code with the HWA-RC driver; there is a bunch of factorization work that
221 Now it is visible. If there were other devices in the same radio channel
267 As explained above, there are three different types of HCs in the WUSB
327 Every time there is a successful transfer to/from a device, we update a
355 header (segment request) and then if there is any data, a data buffer
369 xfer.c:wa_handle_notif_xfer()). In there we read from the DTI endpoint a
385 information. Buried in there is a lot of URBs for executing the segments
388 For OUT xfers, there is an array of segments, one URB for each, another
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,mxs-pinctrl.txt | 32 On mxs, there is no hardware pin group. The pin group in this binding only
38 pointed in there, while the phandle can have multiple config node referenced
39 there to adjust configurations for some pins in the group.
|
| /linux-4.4.14/Documentation/devicetree/bindings/clock/ |
| D | arm-integrator.txt | 7 core module and there is only one of these.
|
| /linux-4.4.14/Documentation/laptops/ |
| D | disk-shock-protection.txt | 89 IDE) configurations are concerned, there can only be two devices
94 to be very useful in any other environment, there will be mostly one
107 Finally, there are some hard drives that only comply with an earlier
109 feature nonetheless. Unfortunately, there is no safe way Linux can
|
| D | sony-laptop.txt | 107 the CD drive, but there are others and they are usually different from
134 (because there is none), so there is no guarantee this driver
|
| /linux-4.4.14/Documentation/security/ |
| D | keys-request-key.txt | 79 (2) request_key() searches the process's subscribed keyrings to see if there's
80 a suitable key there. If there is, it returns the key. If there isn't,
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | videobuf | 18 Not all video devices use the same kind of buffers. In fact, there are (at
41 [It's worth noting that there's a fourth kind of buffer: "overlay" buffers
46 as a form of scattered buffer, but there are very few implementations in
84 minimum of two buffers are needed for proper streaming, and there is
110 used. The driver should ensure that there is no I/O active on the buffer,
312 - Get a pointer to the memory and put video data there.
350 header files; there are a few low-level functions declared there which have
|
| /linux-4.4.14/Documentation/zh_CN/arm64/ |
| D | tagged-pointers.txt | 7 or if there is a problem with the translation.
|
| D | legacy_instructions.txt | 7 or if there is a problem with the translation.
|
| D | memory.txt | 7 or if there is a problem with the translation.
|
| /linux-4.4.14/arch/openrisc/ |
| D | TODO.openrisc | 11 -- Finish the renaming cleanup... there are references to or32 in the code
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.FAQ | 5 Please note that there is a big FAQ available in the isdn4k-utils.
|
| D | syncPPP.FAQ | 88 isdn4linux! With syncPPP, there is no automatic
196 Check whether you can find there:
204 you can see, whether there is activity on the card/line.
205 - there are at least a few RECV messages in the log:
|
| /linux-4.4.14/Documentation/devicetree/bindings/usb/ |
| D | exynos-usb.txt | 15 - port: if in the SoC there are EHCI phys, they should be listed here.
56 - port: if in the SoC there are OHCI phys, they should be listed here.
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | device.txt | 44 Typically only set if there are some interrupt lines. This
68 How many channels are there?
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Joystick.txt | 30 joystick support is always enabled. In the former ALSA version, there
62 The following drivers don't support gameport natively, but there are
|
| D | CMIPCI.txt | 11 channels can be used for front/rear playbacks. Since there are two
45 time.. Maybe there is an unknown register to achieve this... ]
48 playback should be routed there as default. If not, there is a
141 Additionally there are relevant control switches:
|
| /linux-4.4.14/fs/btrfs/ |
| D | Kconfig | 19 expected to change unless there are strong reasons to do so. If there
|
| /linux-4.4.14/arch/score/ |
| D | Kconfig.debug | 13 On some platforms, there is currently no way for the boot loader to
|
| /linux-4.4.14/Documentation/aoe/ |
| D | todo.txt | 4 there are no other pages available, then deadlock may occur when a
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | abx500 | 21 thermal sensors, and there is also a thermal sensor inside ABx500 too, which
|
| D | ltc4151 | 23 This driver does not probe for LTC4151 devices, since there is no register
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | bh1770glc.txt | 32 by using a delayed work. As long as there is proximity threshold above
34 below the threshold value, there is no interrupt and the delayed work will
|
| /linux-4.4.14/drivers/leds/trigger/ |
| D | Kconfig | 28 sporadic events, when there are no clear begin and end trap points,
79 from there. One use case is n810's keypad LEDs that could
|
| /linux-4.4.14/arch/cris/ |
| D | Kconfig | 322 Selecting LED_on_when_link will light the LED when there is a
323 connection and will flash off when there is activity.
326 there is activity.
334 Selecting LED_on_when_link will light the LED when there is a
335 connection and will flash off when there is activity.
338 there is activity.
|
| /linux-4.4.14/drivers/staging/media/mn88473/ |
| D | TODO | 17 there is less lines. Those error checks are about the last thing to be added.
|
| /linux-4.4.14/Documentation/ABI/obsolete/ |
| D | sysfs-class-rfkill | 26 Description: This file is deprecated because there no longer is a way to
|
| /linux-4.4.14/drivers/staging/media/mn88472/ |
| D | TODO | 17 there is less lines. Those error checks are about the last thing to be added.
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/ |
| D | video-interfaces.txt | 35 one port is present in a device node or there is more than one endpoint at a
48 might need to be different when there is any signal modifications on the bus
49 between two devices, e.g. there are logic signal inverters on the lines.
62 If there is more than one 'port' or more than one 'endpoint' node or 'reg'
|
| /linux-4.4.14/drivers/bcma/ |
| D | README | 2 however from programming point of view there is nothing AMBA specific we use.
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/ |
| D | matrix-keymap.txt | 19 cases where there is a modifier key such as a Fn key. Proposed names
|
| /linux-4.4.14/arch/um/ |
| D | Kconfig.um | 53 the kernel, somewhat like the i386 SysRq interface. Since there is
55 instance, there is much greater flexibility possible than with the
|
| /linux-4.4.14/Documentation/input/ |
| D | joystick-parport.txt | 59 Unfortunately, there are pads that need a lot more of power, and parallel
100 the gamepads side. The NES and SNES have different connectors. Also, there
138 In the era of 8-bit machines, there was something like de-facto standard
218 And there were many others.
267 However, there is nothing for free. To allow more sticks to be used at
306 Steffen's version, there is support for up to 5 buttons per joystick. However,
474 Apart from making an interface, there is nothing difficult on using the
|
| D | rotary-encoder.txt | 58 meaning that there it has seen half the way of a one-step transition.
71 As there is no hardware dependent call in this driver, the platform it is
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | pci_iov_resource_on_powernv.txt | 83 need to ensure Linux doesn't assign anything there, the M32 logic
111 has 256 segments; however, there is no table for mapping a segment
115 there's a defined ordering for which window applies.
193 PEs (the segment number is the PE#), so there isn't as much
267 reserved in software; there are still only total_VFs VFs, and they only
294 allocate 256 segments, there are (256 - numVFs) choices for the PE# of VF0.
300 space will consume (numVFs * n) segments. That means there aren't as many
|
| D | mpc52xx.txt | 34 so. I didn't took 5xxx because there's apparently a lot of 5xxx that have
|
| /linux-4.4.14/scripts/coccinelle/free/ |
| D | clk_put.cocci | 3 //# This only signals a missing clk_put when there is a clk_put later
|
| D | iounmap.cocci | 3 //# This only signals a missing iounmap when there is an iounmap later
|
| /linux-4.4.14/arch/x86/um/ |
| D | Kconfig | 54 N (on x86-64 it's automatically enabled, instead, as it's safe there).
|
| /linux-4.4.14/Documentation/devicetree/bindings/mtd/ |
| D | fsl-quadspi.txt | 18 But if there are two NOR flashes connected to the
|
| /linux-4.4.14/fs/nilfs2/ |
| D | Kconfig | 13 synchronous write basis (unless there is no change). Users can
|
| /linux-4.4.14/Documentation/devicetree/bindings/mfd/ |
| D | max8925.txt | 13 - maxim,tsc-irq: there are 2 IRQ lines for max8925, one is indicated in
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/cpm_qe/ |
| D | qe.txt | 9 the "root" qe node, using the common properties from there.
26 Usage: required only if there is no fsl,qe-firmware child node
|
| /linux-4.4.14/Documentation/x86/ |
| D | tlb.txt | 16 2. The contents of the TLB. If the TLB is empty, then there will
69 be there in some form. You can use pmu-tools 'ocperf list'
|
| /linux-4.4.14/Documentation/bus-devices/ |
| D | ti-gpmc.txt | 23 translated depends on the connected peripheral. Also there is a
38 Then there may be cases where peripheral datasheet doesn't mention
|
| /linux-4.4.14/Documentation/ia64/ |
| D | serial.txt | 9 Prior to 2.6.10, there were confusing exceptions to this:
18 - If there was no HCDP, we assumed there were UARTs at the
|
| /linux-4.4.14/Documentation/gpio/ |
| D | gpio.txt | 8 Due to the history of GPIO interfaces in the kernel, there are two different
36 often have a few such pins to help with pin scarcity on SOCs; and there are
101 support it, there's a common idiom you can use to emulate it with any GPIO pin
|
| /linux-4.4.14/Documentation/pcmcia/ |
| D | driver-changes.txt | 23 ranges. After a call to pcmcia_request_window(), the regions found there
30 ranges. After a call to pcmcia_request_io(), the ports found there
73 necessary now is calling pcmcia_disable_device. As there is no valid
|
| /linux-4.4.14/Documentation/dvb/ |
| D | faq.txt | 110 you have configured with the dvbnet utility. Check if there
117 before checking the statistics.) If there are no packets at
118 all then maybe the PID is wrong. If there are error packets,
|
| /linux-4.4.14/Documentation/s390/ |
| D | monreader.txt | 69 there are other users already connected to the *MONITOR service (e.g.
172 EAGAIN: occurs on a non-blocking read if there is no data available at the
178 In the last case (EOVERFLOW) there may be missing data, in the first two cases
179 (EIO, EFAULT) there will be missing data. It's up to the application if it will
|