| /linux/Documentation/driver-api/gpio/ |
| H A D | intro.rst | 44 input de-glitch/debounce logic, sometimes with software controls.
47 sometimes level triggered. Such IRQs may be configurable as system
82 Sometimes shared signals need to use "open drain" (where only the low signal
86 This is sometimes called a "wire-AND"; or more practically, from the negative
90 Also, bidirectional data bus signals sometimes use open drain signals.
|
| /linux/Documentation/filesystems/ |
| H A D | hpfs.rst | 109 moved ... sometimes it works. But the link is partly stored in directory
159 Sometimes you won't be able to delete some files on a very full filesystem
193 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
194 chkdsk doesn't scream if the tree is unbalanced (and sometimes creates
210 Sometimes (I think it's random) when you create a file with one-char name under
283 Fixed a bug with i_blocks (du sometimes didn't display correct values)
294 error sometimes when opening directories in PMSHELL)
|
| /linux/Documentation/devicetree/bindings/arm/ |
| H A D | arm,vexpress-juno.yaml | 139 the connection between the motherboard and any tiles. Sometimes the
140 compatible is placed directly under this node, sometimes it is placed
141 in a subnode named "motherboard-bus". Sometimes the compatible includes
142 "arm,vexpress,v2?-p1" sometimes (on software models) is is just
|
| /linux/tools/memory-model/scripts/ |
| H A D | judgelitmus.sh | 11 # the Always/Sometimes/Never portion of the "Result:" prediction will be
16 # "HW" is the --hw argument. In addition, non-Sometimes verification
141 if test \( -n "$LKMM_HW_MAP_FILE" -a "$outcome" = Sometimes \) -o -n "$datarace_modeled"
|
| H A D | checkghlitmus.sh | 39 xargs -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' |
45 xargs < $T/list-C -r grep -E -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' > $T/list-C-result
|
| H A D | cmplitmushist.sh | 87 echo Matching Observation Always/Sometimes/Never result: $2
116 echo Matching Observation Always/Sometimes/Never result: $obsresult 1>&2
|
| /linux/Documentation/i2c/busses/ |
| H A D | i2c-viapro.rst | 7 Datasheet: Sometimes available at the VIA website
10 Datasheet: Sometimes available at the VIA website
|
| /linux/Documentation/admin-guide/ |
| H A D | reporting-issues.rst | 238 should be enough for most people. But sometimes there are situations where even
307 Note, the previous paragraph is starting with the word 'most', as sometimes
324 better than not reporting the issue at all: sometimes such reports directly or
416 Problems that look a lot like a kernel issue are sometimes caused by build or
450 Reminder, you are dealing with computers, which sometimes do unexpected things,
520 the issue afterwards. Sometimes simply restarting will be enough, sometimes
529 they are Open Source): they sometimes cause errors in unrelated kernel
652 name is too specific. Sometimes you will need to search on the net for help;
671 that was replaced by a newer solution you need to switch to. Sometimes the code
728 areas rarely changed (like old or unmaintained drivers): sometimes such code is
[all …]
|
| /linux/Documentation/trace/ |
| H A D | hwlat_detector.rst | 19 management of thermal sensors and fans. Sometimes though, SMIs are used for
21 handler (sometimes measured in milliseconds). Obviously this is a problem if
|
| /linux/Documentation/driver-api/driver-model/ |
| H A D | overview.rst | 20 (sometimes just a list) for the devices they control. There wasn't any
43 and sometimes by the device-specific drivers.
|
| /linux/Documentation/process/ |
| H A D | volatile-considered-harmful.rst | 9 sometimes tempted to use it in kernel code when shared data structures are
93 by I/O devices can, sometimes, legitimately be volatile. A ring buffer
|
| H A D | backporting.rst | 30 Sometimes the patch you are backporting already exists as a git commit,
116 each method, and sometimes there's value in using both.
215 look like they might be the source of the conflict. Sometimes there will
363 Sometimes the easiest thing to do is to just remove all but the first
402 Sometimes the right thing to do will be to also backport the patch that
573 The "Upstream commit" line is sometimes slightly different depending on
|
| /linux/Documentation/driver-api/media/ |
| H A D | v4l2-device.rst | 70 Sometimes you need to iterate over all devices registered by a specific
104 Sometimes you need to keep a running counter of the device instance. This is
|
| /linux/Documentation/RCU/ |
| H A D | torture.rst | 107 it is sometimes easier to get the third entry to show up in the
135 It is sometimes desirable to torture RCU on a specific kernel build,
208 Sometimes additional debugging is useful, and in such cases the --kconfig
225 Sometimes all that is needed is a full set of kernel builds. This is
|
| /linux/include/linux/usb/ |
| H A D | usb_phy_generic.h | 8 /* sometimes transceivers are accessed only through e.g. ULPI */
|
| /linux/tools/memory-model/litmus-tests/ |
| H A D | R+poonceonces.litmus | 4 * Result: Sometimes
|
| H A D | LB+poonceonces.litmus | 4 * Result: Sometimes
|
| H A D | SB+poonceonces.litmus | 4 * Result: Sometimes
|
| H A D | MP+poonceonces.litmus | 4 * Result: Sometimes
|
| H A D | S+poonceonces.litmus | 4 * Result: Sometimes
|
| H A D | WRC+poonceonces+Once.litmus | 4 * Result: Sometimes
|
| H A D | SB+rfionceonce-poonceonces.litmus | 4 * Result: Sometimes
|
| /linux/Documentation/devicetree/bindings/power/ |
| H A D | power-controller.txt | 4 sometimes able to control the system power. The device driver associated with these
|
| /linux/kernel/module/ |
| H A D | Kconfig | 10 tool to add (and sometimes remove) them. If you say Y here,
166 Saying Y here makes it sometimes possible to use modules
247 others sometimes change the module source without updating
|
| /linux/Documentation/litmus-tests/atomic/ |
| H A D | cmpxchg-fail-unordered-2.litmus | 4 * Result: Sometimes
|