Home
last modified time | relevance | path

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

12345678910>>...78

/kernel/linux/linux-5.10/Documentation/driver-api/gpio/
Dintro.rst56 input de-glitch/debounce logic, sometimes with software controls.
59 sometimes level triggered. Such IRQs may be configurable as system
94 Sometimes shared signals need to use "open drain" (where only the low signal
98 This is sometimes called a "wire-AND"; or more practically, from the negative
102 Also, bidirectional data bus signals sometimes use open drain signals.
/kernel/linux/linux-4.19/Documentation/driver-api/gpio/
Dintro.rst56 input de-glitch/debounce logic, sometimes with software controls.
59 sometimes level triggered. Such IRQs may be configurable as system
94 Sometimes shared signals need to use "open drain" (where only the low signal
98 This is sometimes called a "wire-AND"; or more practically, from the negative
102 Also, bidirectional data bus signals sometimes use open drain signals.
/kernel/linux/linux-4.19/Documentation/filesystems/
Dhpfs.txt98 moved ... sometimes it works. But the link is partly stored in directory
146 Sometimes you won't be able to delete some files on a very full filesystem
178 Old versions of this driver created sometimes unbalanced dnode trees. OS/2
179 chkdsk doesn't scream if the tree is unbalanced (and sometimes creates
194 Sometimes (I think it's random) when you create a file with one-char name under
247 Fixed a bug with i_blocks (du sometimes didn't display correct values)
255 error sometimes when opening directories in PMSHELL)
/kernel/linux/linux-5.10/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)
/kernel/linux/linux-5.10/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
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Darm,vexpress-juno.yaml155 the connection between the motherboard and any tiles. Sometimes the
156 compatible is placed directly under this node, sometimes it is placed
157 in a subnode named "motherboard". Sometimes the compatible includes
158 "arm,vexpress,v2?-p1" sometimes (on software models) is is just
/kernel/linux/linux-4.19/Documentation/i2c/busses/
Di2c-viapro5 Datasheet: Sometimes available at the VIA website
8 Datasheet: Sometimes available at the VIA website
/kernel/linux/linux-5.10/tools/memory-model/scripts/
Dcheckghlitmus.sh38 xargs -r egrep -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' |
44 xargs < $T/list-C -r egrep -l '^ \* Result: (Never|Sometimes|Always|DEADLOCK)' > $T/list-C-result
Dcmplitmushist.sh50 echo Matching Observation Always/Sometimes/Never result: $2
79 echo Matching Observation Always/Sometimes/Never result: $obsresult 1>&2
/kernel/linux/linux-5.10/Documentation/i2c/busses/
Di2c-viapro.rst7 Datasheet: Sometimes available at the VIA website
10 Datasheet: Sometimes available at the VIA website
/kernel/linux/linux-5.10/Documentation/ide/
DChangeLog.ide-tape.1995-200284 * user backup program. On my tape drive, it sometimes
117 * now sometimes be used with IDE tape drives as well.
135 * MTTELL was sometimes returning incorrect results.
202 * Also, sometimes an application finishes but the
/kernel/linux/linux-4.19/Documentation/ide/
DChangeLog.ide-tape.1995-200284 * user backup program. On my tape drive, it sometimes
117 * now sometimes be used with IDE tape drives as well.
135 * MTTELL was sometimes returning incorrect results.
202 * Also, sometimes an application finishes but the
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/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
/kernel/linux/linux-4.19/Documentation/driver-model/
Doverview.txt18 (sometimes just a list) for the devices they control. There wasn't any
41 and sometimes by the device-specific drivers.
/kernel/linux/linux-5.10/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.
/kernel/linux/linux-4.19/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
/kernel/linux/linux-5.10/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
/kernel/linux/linux-5.10/include/linux/usb/
Dusb_phy_generic.h8 /* sometimes transceivers are accessed only through e.g. ULPI */
/kernel/linux/linux-5.10/tools/memory-model/litmus-tests/
DMP+poonceonces.litmus4 * Result: Sometimes
DLB+poonceonces.litmus4 * Result: Sometimes
DR+poonceonces.litmus4 * Result: Sometimes
/kernel/linux/linux-4.19/tools/memory-model/litmus-tests/
DLB+poonceonces.litmus4 * Result: Sometimes
DR+poonceonces.litmus4 * Result: Sometimes

12345678910>>...78