Home
last modified time | relevance | path

Searched full:often (Results 1 – 25 of 321) sorted by relevance

12345678910>>...13

/Documentation/sound/designs/
Dpowersave.rst35 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/
Dmachinecheck.rst9 (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/
Dudev-install.sh7 # find udev.conf, often /etc/udev/udev.conf
22 # find the directory where udev rules are stored, often
/Documentation/maintainer/
Drebasing-and-merging.rst9 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/networking/devlink/
Ddevlink-info.rst32 This is usually the serial number of the ASIC, also often available
50 This is usually the serial number of the board, often available in
71 These versions often only update after a reboot, sometimes device reset.
152 Overall firmware version, often representing the collection of
/Documentation/driver-api/
Dspi.rst7 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/
Dvia-velocity.txt10 devices quite often set this data in uboot and do not provide an eeprom.
/Documentation/sound/soc/
Doverview.rst11 * 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/
D3.Early-stage.rst132 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/
Dlm78.rst69 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
Dmax1619.rst32 other second; reading them more often will do no harm, but will return
Dg760a.rst39 other second; reading them more often will do no harm, but will return
/Documentation/locking/
Dpi-futex.rst33 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/driver-api/gpio/
Dintro.rst41 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/userspace-api/media/v4l/
Dcolorspaces.rst48 The Y value in the CIE XYZ colorspace corresponds to luminance. Often
113 in the CIE XYZ colorspace. Also note that Y'CbCr is often called YCbCr
147 colorspace standards correctly define all four, quite often the
149 standards for the missing pieces. The fact that colorspaces are often a
/Documentation/ABI/testing/
Dsysfs-bus-pci-drivers-xhci_hcd6 USB3 controllers) are often implemented with the Debug
/Documentation/devicetree/bindings/timer/
Darm,global_timer.yaml13 Cortex-A9 are often associated with a per-core Global timer.
/Documentation/vm/
Dactive_mm.rst14 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/doc-guide/
Dcontributing.rst41 Warnings issued by a compiler for C code can often be dismissed as false
49 Another important point is that documentation warnings are often created by
52 documentation tree is often not the right one to actually carry those
202 current, adding whatever information is needed. Such work often requires
204 course. Developers are often more than willing to cooperate with people
/Documentation/misc-devices/
Dics932s401.rst30 the registers more often than once every other second.
/Documentation/admin-guide/LSM/
DSafeSetID.rst17 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/timers/
Dtimers-howto.rst8 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/
Dspi-summary.rst14 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/driver-api/usb/
Derror-codes.rst85 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/devicetree/bindings/interrupt-controller/
Dbrcm,bcm3380-l2-intc.txt8 - contains one or more enable/status word pairs, which often appear at

12345678910>>...13