/openbmc/linux/arch/arm/boot/dts/ti/omap/ |
H A D | omap3-beagle-ab4.dts | 16 /* Unusable as clocksource because of unreliable oscillator */ 21 /* Unusable as clockevent because of unreliable oscillator, allow to idle */
|
H A D | omap3-devkit8000-common.dtsi | 161 /* Unusable as clockevent because if unreliable oscillator, allow to idle */
|
/openbmc/linux/Documentation/devicetree/bindings/timer/ |
H A D | arm,arch_timer.yaml | 74 where reading certain values from the counter is unreliable. This also 80 that reading the counter is unreliable unless the same value is returned 87 says that reading the counters is unreliable in some cases, and reads may
|
/openbmc/linux/Documentation/firmware-guide/acpi/ |
H A D | acpi-lid.rst | 70 If the userspace hasn't been prepared to ignore the unreliable "opened" 71 events and the unreliable initial state notification, Linux users can use 96 If the userspace has been prepared to ignore the unreliable "opened" events 97 and the unreliable initial state notification, Linux users should always
|
/openbmc/linux/Documentation/admin-guide/device-mapper/ |
H A D | dm-flakey.rst | 6 unreliable behaviour periodically. It's been found useful in simulating 10 <up interval> seconds, then exhibits unreliable behaviour for <down
|
/openbmc/linux/Documentation/livepatch/ |
H A D | reliable-stacktrace.rst | 46 the stack or other unwind state is corrupt or otherwise unreliable. The 125 unreliable to unwind from, e.g. 151 exceptions (e.g. IRQ) but unreliable to unwind across other exceptions 176 unwinder must report these cases as unreliable. 221 middle of return_to_handler and can report this as unreliable. Architectures 250 such cases, or report the unwinding as unreliable. 263 assumption can lead to unreliable stack traces. For example, consider the
|
/openbmc/linux/net/dccp/ |
H A D | Kconfig | 12 congestion-controlled, unreliable datagrams. It should be suitable
|
/openbmc/openbmc/poky/meta/recipes-devtools/strace/strace/ |
H A D | skip-load.patch | 1 Skip tests which are known to be unreliable under load, typically because they
|
/openbmc/linux/drivers/net/ethernet/mellanox/mlx5/core/diag/ |
H A D | fw_tracer.h | 151 u8 unreliable; member
|
H A D | fw_tracer.c | 476 tracer_event->timestamp_event.unreliable = !!(urts >> 2); in poll_trace() 478 tracer_event->timestamp_event.unreliable = !!(urts & 1); in poll_trace() 682 if (!tracer_event->timestamp_event.unreliable) in mlx5_tracer_handle_trace()
|
/openbmc/linux/drivers/ras/ |
H A D | Kconfig | 29 so have ideal availability, but may be unreliable, with frequent
|
/openbmc/linux/Documentation/hwmon/ |
H A D | w83l785ts.rst | 41 and cause read errors. Or maybe the W83L785TS-S chip is simply unreliable,
|
/openbmc/linux/drivers/hwmon/ |
H A D | k10temp.c | 411 int unreliable = has_erratum_319(pdev); in k10temp_probe() local 417 if (unreliable) { in k10temp_probe()
|
/openbmc/linux/Documentation/PCI/ |
H A D | pcieaer-howto.rst | 115 to be unreliable. Depending on those error conditions, uncorrectable 117 Non-fatal errors cause the particular transaction to be unreliable, 119 the other hand, cause the link to be unreliable.
|
/openbmc/linux/Documentation/admin-guide/ |
H A D | init.rst | 19 --> initial console unavailable. E.g. some serial consoles are unreliable
|
/openbmc/linux/arch/arm64/ |
H A D | Makefile | 36 $(warning Detected assembler with broken .inst; disassembly will be unreliable)
|
/openbmc/linux/Documentation/driver-api/ |
H A D | parport-lowlevel.rst | 1497 times out, the return value may be unreliable. 1535 times out, the return value may be unreliable. 1573 times out, the return value may be unreliable. 1613 times out, the return value may be unreliable.
|
/openbmc/u-boot/doc/ |
H A D | README.nand | 308 If the block is detected as unreliable, it is up to the user to decide to 311 is detected as unreliable earlier).
|
/openbmc/openbmc/poky/meta/lib/oe/ |
H A D | recipeutils.py | 1167 unreliable = data.getVar('UPSTREAM_CHECK_UNRELIABLE') 1168 if unreliable == "1":
|
/openbmc/linux/drivers/firmware/arm_scmi/ |
H A D | Kconfig | 56 SCMI Raw mode support unreliable. If unsure, say N.
|
/openbmc/linux/Documentation/trace/ |
H A D | mmiotrace.rst | 28 supported, but tracing is unreliable and may miss events if more than one CPU
|
/openbmc/linux/Documentation/sound/cards/ |
H A D | emu-mixer.rst | 18 unreliable if the card's PCI bus requests are not handled with the
|
/openbmc/linux/Documentation/admin-guide/blockdev/ |
H A D | floppy.rst | 181 flushings, and slightly more unreliable. Please verify your
|
/openbmc/linux/Documentation/networking/ |
H A D | udplite.rst | 43 UDP-Lite provides a connectionless, unreliable datagram service and hence
|
H A D | dccp.rst | 20 Datagram Congestion Control Protocol (DCCP) is an unreliable, connection
|