| /linux/Documentation/ABI/testing/ |
| H A D | sysfs-devices | 11 Please do not rely on the format of this tree because of
13 the tree, please use the /sys/class structure and rely
16 Or rely on the uevent messages to notify programs of
|
| H A D | sysfs-bus-surface_aggregator-tabletsw | 30 must not rely on this list of states being exhaustive and
56 must not rely on this list of states being exhaustive and
|
| H A D | sysfs-bus-spi-devices-spi-nor | 28 The attribute is optional. User space should not rely on
|
| /linux/Documentation/scheduler/ |
| H A D | membarrier.rst | 28 - alpha, arc, arm, hexagon, mips rely on the full barrier implied by
33 - powerpc, riscv, s390, sparc, x86 rely on the full barrier implied by
34 switch_mm(), if mm is not NULL; they rely on the full barrier implied
|
| /linux/drivers/input/mouse/ |
| H A D | maplemouse.c | 29 int buttons, relx, rely, relz; in dc_mouse_callback() local
37 rely = *(unsigned short *)(res + 14) - 512; in dc_mouse_callback()
44 input_report_rel(dev, REL_Y, rely); in dc_mouse_callback()
|
| /linux/Documentation/features/sched/membarrier-sync-core/ |
| H A D | arch-support.txt | 17 # Given that xRET is not core serializing, we rely on FENCE.I for providing
39 # Given that neither SYSRET{L,Q}, nor SYSEXIT, are core serializing, we rely
|
| /linux/fs/notify/dnotify/ |
| H A D | Kconfig | 9 superior alternatives, but some applications may still rely on
|
| /linux/tools/bpf/bpftool/Documentation/ |
| H A D | common_options.rst | 12 profile** or showing pids associated to BPF objects may rely on it).
|
| /linux/Documentation/arch/arm/ |
| H A D | swp_emulation.rst | 23 when accessing uncached shared regions, LDREX/STREX rely on an external
|
| H A D | kernel_mode_neon.rst | 7 * Use only NEON instructions, or VFP instructions that don't rely on support
68 Earlier versions of VFP (prior to version 3) rely on software support for things
|
| H A D | mem_alignment.rst | 13 Of course this is a bad idea to rely on the alignment trap to perform
|
| /linux/fs/sysfs/ |
| H A D | Kconfig | 16 Some system agents rely on the information in sysfs to operate.
|
| /linux/Documentation/driver-api/soundwire/ |
| H A D | bra.rst | 44 BTP/BRA, the frame should rely on a large number of columns and
72 (10) The address is represented with 32 bits and does not rely on
180 On the host side, most implementations rely on a Port-like concept,
272 Existing codec drivers rely on regmap to download firmware to
315 Manager/Link, so the BRA stream handling does not rely on the
|
| /linux/arch/arm64/boot/dts/amlogic/ |
| H A D | meson-g12b-s922x-khadas-vim3.dts | 29 * testing purposes, but instead rely on the firmware/bootloader to
|
| H A D | meson-g12b-a311d-khadas-vim3.dts | 29 * testing purposes, but instead rely on the firmware/bootloader to
|
| H A D | meson-sm1-khadas-vim3l.dts | 91 * testing purposes, but instead rely on the firmware/bootloader to
|
| /linux/Documentation/accounting/ |
| H A D | cgroupstats.rst | 21 NOTE: We currently rely on delay accounting for extracting information
|
| /linux/Documentation/ABI/stable/ |
| H A D | sysfs-firmware-opal-dump | 21 Do not rely on any particular size of dump
|
| /linux/Documentation/power/ |
| H A D | apm-acpi.rst | 26 Both APM and ACPI rely on user-space daemons, apmd and acpid
|
| /linux/Documentation/i2c/ |
| H A D | fault-codes.rst | 22 to respond correctly. Other code may need to rely on YOUR code reporting
61 host. Note that even if PECs are in use, you should not rely
|
| /linux/drivers/base/firmware_loader/ |
| H A D | Kconfig | 64 in boot and cannot rely on the firmware being placed in an initrd or
124 rely on one refer to the permissively licensed firmwared:
234 to support cards that rely on user-initiated updates for firmware files.
|
| /linux/Documentation/devicetree/bindings/net/bluetooth/ |
| H A D | mediatek,bluetooth.txt | 27 the GPIO control still has to rely on the dedicated GPIO controller such as
|
| /linux/Documentation/admin-guide/ |
| H A D | filesystem-monitoring.rst | 45 in the future. Therefore, applications must not rely on the order and
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | dv-timings.rst | 55 video. The correct approach is to rely on the `V4L2_EVENT_SOURCE_CHANGE`
|
| /linux/Documentation/driver-api/ |
| H A D | io-mapping.rst | 50 migration to make the mapping code work. No caller can rely on this side
|