Searched full:often (Results 1 – 25 of 305) sorted by relevance
12345678910>>...13
| /Documentation/sound/designs/ |
| D | powersave.rst | 35 state. Also, it often takes certain time to wake up from the
36 power-down to the active state. These are often hardly to fix, so
43 Try to turn it off when you experience such a thing too often.
|
| /Documentation/x86/x86_64/ |
| D | machinecheck.rst | 9 (often with panic), corrected ones cause a machine check log entry.
40 How often to poll for corrected machine check errors, in seconds
42 finds MCEs it triggers an exponential speedup (poll more often) on
44 triggers an exponential backoff (poll less often) on the polling
|
| /Documentation/admin-guide/aoe/ |
| D | udev-install.sh | 7 # find udev.conf, often /etc/udev/udev.conf
22 # find the directory where udev rules are stored, often
|
| /Documentation/maintainer/ |
| D | rebasing-and-merging.rst | 9 features; as is often the case with such tools, there are right and wrong
11 of rebasing and merging. Maintainers often get in trouble when they use
20 merging a little too often.
72 as the new base. The kernel is often in a relatively unstable state
85 patch series that has clearly been reparented, often to a random commit,
144 type of merge is often called a "back merge". Back merges can help to make
154 hide interactions with other trees that should not be happening (often) in
172 resolution - often better than the developers involved.
194 Often, though, dependency issues indicate that a change of approach is
|
| /Documentation/driver-api/ |
| D | spi.rst | 7 often in the range of 1-20 MHz), a "Master Out, Slave In" (MOSI) data
27 whatever bus they sit on (often the platform bus) and SPI, and expose
|
| /Documentation/devicetree/bindings/net/ |
| D | via-velocity.txt | 10 devices quite often set this data in uboot and do not provide an eeprom.
|
| /Documentation/sound/soc/ |
| D | overview.rst | 11 * Codec drivers were often tightly coupled to the underlying SoC
17 event). These are quite common events on portable devices and often require
|
| /Documentation/process/ |
| D | 3.Early-stage.rst | 132 subsystem list, posting there is often preferable to posting on
180 posted by others. Beyond that, high-level designs often hide problems
206 considering whether the secrecy is really necessary; there is often no real
214 best option is often to hire an outside developer to review the plans under
221 This kind of review is often enough to avoid serious problems later on
|
| /Documentation/hwmon/ |
| D | lm78.rst | 69 It is a value in volts. When it is unconnected, you will often find the
79 The LM7* only updates its values each 1.5 seconds; reading it more often
|
| D | max1619.rst | 32 other second; reading them more often will do no harm, but will return
|
| D | g760a.rst | 39 other second; reading them more often will do no harm, but will return
|
| /Documentation/ |
| D | pi-futex.txt | 33 technique that often cannot be replaced with lockless algorithms. As we
38 algorithms often endangers to ability to do robust reviews of said code.
39 I.e. critical RT apps often choose lock structures to protect critical
|
| /Documentation/admin-guide/LSM/ |
| D | SafeSetID.rst | 17 often preferable to use Linux runtime capabilities rather than file
23 CAP_SET{U/G}ID capabilities, this is often at odds with the goals of running a
27 especially since programs often only call setuid() to drop privileges to a
|
| /Documentation/driver-api/gpio/ |
| D | intro.rst | 41 often have a few such pins to help with pin scarcity on SOCs; and there are
58 - Inputs can often be used as IRQ signals, often edge triggered but
|
| /Documentation/devicetree/bindings/timer/ |
| D | arm,global_timer.yaml | 13 Cortex-A9 are often associated with a per-core Global timer.
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-pci-drivers-xhci_hcd | 6 USB3 controllers) are often implemented with the Debug
|
| /Documentation/media/uapi/v4l/ |
| D | colorspaces.rst | 55 The Y value in the CIE XYZ colorspace corresponds to luminance. Often
120 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr
154 colorspace standards correctly define all four, quite often the
156 standards for the missing pieces. The fact that colorspaces are often a
|
| /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
|
| /Documentation/misc-devices/ |
| D | ics932s401.rst | 30 the registers more often than once every other second.
|
| /Documentation/ABI/stable/ |
| D | vdso | 3 the vDSO and it often contains useful and highly-optimized alternatives
|
| /Documentation/timers/ |
| D | timers-howto.rst | 8 This question is most often faced by driver writers who have to
81 will often sleep longer (~20 ms actual sleep for any
|
| /Documentation/spi/ |
| D | spi-summary.rst | 14 The three signal wires hold a clock (SCK, often on the order of 10 MHz),
26 other signals, often including an interrupt to the master.
65 Microcontrollers often support both master and slave sides of the SPI
87 and if dynamic reconfiguration is important, USB will often be a more
145 processors, and often support both Master and Slave roles.
221 Platforms will often abstract the "register SPI controller" operation,
265 * developer boards will often need Linux to do it.
280 on the target board, often with some board-specific data needed for the
339 Developer boards often play by different rules than product boards, and one
622 often DMA (especially if the root filesystem is in SPI flash), and
|
| /Documentation/devicetree/bindings/interrupt-controller/ |
| D | brcm,bcm3380-l2-intc.txt | 8 - contains one or more enable/status word pairs, which often appear at
|
| /Documentation/driver-api/usb/ |
| D | error-codes.rst | 85 reported. That's because transfers often involve several packets, so that
116 Note that often the controller hardware does
119 protocol error, a failure to respond (often
154 ``-ENODEV`` Device was removed. Often preceded by a burst
|
| /Documentation/media/kapi/ |
| D | v4l2-clocks.rst | 12 signal to be supplied by the system. Often this clock is supplied by the
|
12345678910>>...13