Home
last modified time | relevance | path

Searched full:sometimes (Results 1 – 25 of 1190) sorted by relevance

12345678910>>...48

/linux-6.12.1/Documentation/driver-api/gpio/ !
Dintro.rst44 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-6.12.1/Documentation/filesystems/ !
Dhpfs.rst109 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-6.12.1/Documentation/devicetree/bindings/arm/ !
Darm,vexpress-juno.yaml139 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-6.12.1/Documentation/sound/soc/ !
Dclocking.rst12 Every audio subsystem is driven by a master clock (sometimes referred to as MCLK
29 clock is sometimes referred to as LRC (left right clock) or FRAME. This clock
/linux-6.12.1/tools/memory-model/scripts/ !
Djudgelitmus.sh11 # 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"
Dcheckghlitmus.sh39 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
Dcmplitmushist.sh87 echo Matching Observation Always/Sometimes/Never result: $2
116 echo Matching Observation Always/Sometimes/Never result: $obsresult 1>&2
/linux-6.12.1/Documentation/i2c/busses/ !
Di2c-viapro.rst7 Datasheet: Sometimes available at the VIA website
10 Datasheet: Sometimes available at the VIA website
/linux-6.12.1/Documentation/admin-guide/ !
Dreporting-issues.rst238 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-6.12.1/Documentation/rust/ !
Dcoding-guidelines.rst38 individual files, and does not require a kernel configuration. Sometimes it may
67 sometimes it is useful to use both comments and documentation at the same time.
170 While sometimes the reason might look trivial and therefore unneeded,
/linux-6.12.1/Documentation/trace/ !
Dhwlat_detector.rst19 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-6.12.1/drivers/acpi/x86/ !
Dutils.c28 * Likewise sometimes some not-actually present devices are sometimes
114 * drivers sometimes cause crashes under Windows and this is how the
244 * declare a whole bunch of bogus I2C devices in their ACPI tables and sometimes
249 * e.g. GPIO/IRQ resource conflicts because sometimes drivers do bind to them.
/linux-6.12.1/Documentation/gpu/amdgpu/display/ !
Ddc-debug.rst51 Sometimes we need to debug if DCN is splitting pipes correctly, and visual
82 Sometimes, dmesg logs aren't enough. This is especially true if a feature is
/linux-6.12.1/Documentation/driver-api/driver-model/ !
Doverview.rst20 (sometimes just a list) for the devices they control. There wasn't any
43 and sometimes by the device-specific drivers.
/linux-6.12.1/Documentation/process/ !
Dvolatile-considered-harmful.rst9 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
/linux-6.12.1/include/linux/usb/ !
Dusb_phy_generic.h8 /* sometimes transceivers are accessed only through e.g. ULPI */
/linux-6.12.1/tools/memory-model/litmus-tests/ !
DLB+poonceonces.litmus4 * Result: Sometimes
DR+poonceonces.litmus4 * Result: Sometimes
DMP+poonceonces.litmus4 * Result: Sometimes
DSB+poonceonces.litmus4 * Result: Sometimes
DS+poonceonces.litmus4 * Result: Sometimes
DSB+rfionceonce-poonceonces.litmus4 * Result: Sometimes
/linux-6.12.1/Documentation/driver-api/media/ !
Dv4l2-device.rst70 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-6.12.1/Documentation/devicetree/bindings/power/ !
Dpower-controller.txt4 sometimes able to control the system power. The device driver associated with these
/linux-6.12.1/kernel/module/ !
DKconfig10 tool to add (and sometimes remove) them. If you say Y here,
166 Saying Y here makes it sometimes possible to use modules
187 others sometimes change the module source without updating

12345678910>>...48