| /openbmc/linux/Documentation/driver-api/gpio/ |
| H A D | intro.rst | 56 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.
|
| /openbmc/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)
|
| /openbmc/linux/Documentation/sound/soc/ |
| H A D | clocking.rst | 12 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
|
| /openbmc/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
|
| /openbmc/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
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | presence_service.cpp | 76 // Sometimes the object path does not exist. Sometimes the object path in isExpectedException()
|
| /openbmc/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
|
| /openbmc/docs/designs/ |
| H A D | voltage-regulator-configuration.md | 16 However, this default configuration sometimes must be modified by firmware. A
42 sometimes require new configuration values to work around the issue. The
45 sometimes conditional, applied only to regulators with a certain version
47 - Improve manufacturing yields. Sometimes regulator configuration values must be
|
| /openbmc/u-boot/arch/arm/cpu/armv8/ |
| H A D | generic_timer.c | 28 * This sometimes leads to a consecutive counter read returning a lower
51 * This erratum sometimes flips the lower 11 bits of the counter value
|
| /openbmc/u-boot/drivers/sound/ |
| H A D | Kconfig | 60 be used by U-Boot to play simple beeps. This is also sometimes called
71 sometimes called Azalia. The audio codec is detected using a
|
| /openbmc/openbmc/poky/bitbake/lib/bb/fetch2/ |
| H A D | gcp.py | 67 # Path sometimes has leading slash, so strip it
97 # Path sometimes has leading slash, so strip it
|
| /openbmc/linux/Documentation/rust/ |
| H A D | coding-guidelines.rst | 38 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,
|
| /openbmc/phosphor-dbus-monitor/src/ |
| H A D | sdbusplus.hpp | 83 // Empty responses are expected sometimes, and the calling in callMethodAndRead()
116 // Empty responses are expected sometimes, and the calling in getBusName()
|
| /openbmc/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 …]
|
| /openbmc/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
|
| /openbmc/qemu/tests/functional/qemu_test/ |
| H A D | tuxruntest.py | 48 # reasonable defaults but we sometimes need to tweak the
110 # Sometimes we need extra devices attached
|
| /openbmc/linux/drivers/gpu/drm/ci/xfails/ |
| H A D | msm-sc7180-flakes.txt | 4 # sometimes.. tbd if this is a kernel CRC bug or a test
|
| H A D | msm-sdm845-flakes.txt | 5 # sometimes.. tbd if this is a kernel CRC bug or a test
|
| /openbmc/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.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Common/ |
| H A D | FaultLogType.interface.yaml | 16 sometimes on-demand).
|
| /openbmc/linux/drivers/acpi/x86/ |
| H A D | utils.c | 29 * Likewise sometimes some not-actually present devices are sometimes
106 * drivers sometimes cause crashes under Windows and this is how the
237 * declare a whole bunch of bogus I2C devices in their ACPI tables and sometimes
242 * e.g. GPIO/IRQ resource conflicts because sometimes drivers do bind to them.
|
| /openbmc/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
|
| /openbmc/phosphor-power/phosphor-power-sequencer/src/ |
| H A D | services.cpp | 134 // Sometimes the object path does not exist. Sometimes the object path in isExpectedException()
|