Searched full:because (Results 1 – 25 of 680) sorted by relevance
12345678910>>...28
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | msi-pic.txt | 17 region must be added because different MSI group has different MSIIR1 offset.
30 MPIC v4.3 does not support this property because the 32 interrupts of an
89 because of hardware limitations of the Peripheral Access Management Unit
96 Because PCI devices must be able to DMA to memory, the primary window must
102 means they cannot be located at just any address. Because of these
|
| /Documentation/locking/ |
| D | spinlocks.rst | 40 before, because you have to make sure the spinlocks correctly protect the
102 but partly **because** they are safe they are also fairly slow. They are slower
103 than they'd need to be, because they do have to disable interrupts
131 interrupt happens on the same CPU that already holds the lock, because the
132 lock will obviously never be released (because the interrupt is waiting
138 on other CPU's, because an interrupt on another CPU doesn't interrupt the
|
| /Documentation/vm/ |
| D | active_mm.rst | 14 Cc'd to linux-kernel, because I don't write explanations all that often,
65 lazy users. That is often a short-lived state, because once that thread
67 released because "mm_users" becomes zero.
85 because it slightly changes the interfaces to accommodate the alpha (who
|
| D | page_migration.rst | 113 page then we back out because someone else modified the radix tree.
120 10. The reference count of the old page is dropped because the address space
121 reference is gone. A reference to the new page is established because
190 because VM interprets -EAGAIN as "temporal migration failure". On returning
227 However, it doesn't guarantee to identify non-lru movable page because
232 page is LRU or non-lru movable once the page has been isolated. Because
250 because VM will set/clear it automatically. Keep in mind that if driver
|
| /Documentation/kbuild/ |
| D | Kconfig.select-break | 12 # symbols. Because of this use of select should be used with caution. An
16 # However, when A is set, C can be set as well because Kconfig does not
|
| /Documentation/driver-api/md/ |
| D | raid5-ppl.rst | 8 in degraded state, there is no way to recalculate parity, because one of the
12 be incorrect. Such condition is known as the RAID5 Write Hole. Because of
23 the array. Because of this, using write-intent bitmap and PPL together is not
|
| /Documentation/networking/ |
| D | checksum-offloads.rst | 38 Because csum_offset cannot be negative, this ensures that the previous value of
53 software. This is OK because when we build the IP header, we obviously have it
56 The requirements for GSO are more complicated, because when segmenting an
88 to the complement of the sum of the pseudo header, because everything else gets
89 'cancelled out' by the checksum field. This is because the sum was
|
| /Documentation/i2c/ |
| D | gpio-fault-injection.rst | 26 because the bus master under test will not be able to clock. It should detect
39 succeed because SDA is still pinned low until you manually release it again
61 transmitted. Because the device will ACK its presence, this results in SDA
74 because it acknowledges data. However, there are two differences compared to
103 There doesn't need to be a device at this address because arbitration lost
|
| D | ten-bit-addresses.rst | 20 * Not all bus drivers support 10-bit addresses. Some don't because the
22 support for example), some don't because nobody bothered adding the
|
| D | slave-interface.rst | 148 should use pm_runtime_get_sync() because your device usually needs to be
175 arises. However, cases should be extremely rare because the master is expected
188 byte-based transactions as the ultimate fallback anyhow because this is how
192 because after each byte written an action should be immediately triggered.
194 updated a register because of internal processing.
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-mic | 69 OS can shutdown because of various reasons. When read, this
74 "crashed" - Shutdown because of a HW or SW crash.
75 "halted" - Shutdown because of a halt command.
76 "poweroff" - Shutdown because of a poweroff command.
77 "restart" - Shutdown because of a restart command.
|
| D | configfs-usb-gadget-tcm | 5 There are no attributes because all the configuration
|
| /Documentation/media/uapi/v4l/ |
| D | vidioc-query-dv-timings.rst | 64 If the timings could not be detected because there was no signal, then
68 (e.g. because the pixelclock is out of range of the hardware
87 No timings could be detected because no signal was found.
|
| D | selection-api-vs-crop-api.rst | 21 because the described operation is actually the composing. The
33 because they are not portable (endianness), and do not work for
|
| /Documentation/scheduler/ |
| D | sched-nice-design.rst | 12 scheduler, (otherwise we'd have done it long ago) because nice level
45 we felt to be a bit excessive. Excessive _not_ because it's too small of
46 a CPU utilization, but because it causes too frequent (once per
51 So for HZ=1000 we changed nice +19 to 5msecs, because that felt like the
|
| /Documentation/dev-tools/ |
| D | sparse.rst | 27 there because sparse will complain about casting to/from a bitwise type,
28 but in this case we really _do_ want to force the conversion). And because
49 This is because "bitwise" (as the name implies) was designed for making
|
| /Documentation/x86/ |
| D | usb-legacy-support.rst | 24 system crashes, because the SMM BIOS is not expecting to be in PAE mode.
28 because the SMM BIOS isn't expecting the CPU to be in 64-bit mode. The
|
| /Documentation/devicetree/bindings/mtd/ |
| D | jedec,spi-nor.txt | 74 carefully by a system. Because these sorts of flash don't
75 have a standardized software reset command, and because some
|
| /Documentation/driver-api/ |
| D | edid.rst | 11 either correctly working because all components follow the standards -
12 or the computer is unusable, because the screen remains dark after
|
| /Documentation/filesystems/caching/ |
| D | object.txt | 132 because:
147 Because only one worker thread may be operating on any particular object's
237 The object comes here if it is dying because of a lookup or creation
243 The object comes here if it is dying due to an error, because its parent
244 cookie has been relinquished by the netfs or because the cache is being
261 all its children, if it is dying because the netfs relinquished its
269 error or just because the whole cache is being withdrawn.
317 Because the withdrawing releasing/retiring events are all handled by the object
|
| /Documentation/fb/ |
| D | vesafb.rst | 14 Version 2.0 are required, because we need a linear frame buffer.
74 If this does not work, this might be because your BIOS does not support
75 linear framebuffers or because it does not support this mode at all.
116 to pan the display. It is turned off by default because it
136 * scrolling (fullscreen) is fast, because there is
|
| /Documentation/filesystems/ |
| D | path-lookup.txt | 28 because of the locks and atomic operations required for every dentry element
29 slows things down. It is not scalable because many parallel applications that
118 There is no fundamental problem with walking down the wrong list, because the
161 Because we didn't wait for a grace period, there may be a concurrent lookup
270 | children:NULL | its refcount because we're holding d_lock.
278 parent snapshot fails, the house comes down, because we had closed the d_seq
287 these cases is fundamental for performance and scalability because blocking
324 very least because i_mutex needs to be grabbed, and objects allocated.
361 the reference count needs to be taken for some reason. This is either because
362 we have reached the target of the path walk, or because we have encountered a
[all …]
|
| /Documentation/ABI/obsolete/ |
| D | sysfs-firmware-acpi | 6 use for some hotplugable resources like memory (because ignoring
|
| /Documentation/power/ |
| D | freezing-of-tasks.rst | 80 - freezes all tasks (including kernel threads) because we can't freeze
89 - thaws all tasks (including kernel threads) because we can't thaw userspace
123 devices are deactivated, because we generally need them for swapping out.
169 changed and may start to work incorrectly because of that.
187 userspace, it gets even more complicated because some userspace processes are
200 fail, because the user land process that should respond to the request is frozen
226 that could lead to freezing failures, because if the suspend/hibernate code
|
| /Documentation/ |
| D | bus-virt-phys-mapping.txt | 22 (because all bus master devices see the physical memory mappings directly).
47 because the memory and the devices share the same address space, and that is
125 And you generally **never** want to use the physical address, because you can't
131 address is needed if you use memory mappings, for example, because the
149 related functions. You should never take the address of such memory, because
|
12345678910>>...28