Home
last modified time | relevance | path

Searched refs:rely (Results 1 – 25 of 171) sorted by relevance

1234567

/linux/Documentation/ABI/testing/
H A Dsysfs-devices11 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 Dsysfs-bus-surface_aggregator-tabletsw30 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 Dsysfs-bus-spi-devices-spi-nor28 The attribute is optional. User space should not rely on
/linux/Documentation/scheduler/
H A Dmembarrier.rst28 - 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 Dmaplemouse.c29 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 Darch-support.txt17 # 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/Documentation/ABI/
H A DREADME26 programs can start to rely on these interfaces, but they must be
88 - Kconfig. Userspace should not rely on the presence or absence of any
93 - Kernel-internal symbols. Do not rely on the presence, absence, location, or
/linux/fs/notify/dnotify/
H A DKconfig9 superior alternatives, but some applications may still rely on
/linux/Documentation/admin-guide/
H A Dabi-testing.rst11 Userspace programs can start to rely on these interfaces, but they must
/linux/tools/bpf/bpftool/Documentation/
H A Dcommon_options.rst12 profile** or showing pids associated to BPF objects may rely on it).
/linux/Documentation/arch/arm/
H A Dswp_emulation.rst23 when accessing uncached shared regions, LDREX/STREX rely on an external
H A Dkernel_mode_neon.rst7 * 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 Dmem_alignment.rst13 Of course this is a bad idea to rely on the alignment trap to perform
/linux/fs/sysfs/
H A DKconfig16 Some system agents rely on the information in sysfs to operate.
/linux/arch/arm64/boot/dts/amlogic/
H A Dmeson-g12b-s922x-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
H A Dmeson-g12b-a311d-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
H A Dmeson-sm1-khadas-vim3l.dts97 * testing purposes, but instead rely on the firmware/bootloader to
/linux/Documentation/accounting/
H A Dcgroupstats.rst21 NOTE: We currently rely on delay accounting for extracting information
/linux/Documentation/devicetree/bindings/clock/
H A Dsilabs,si570.txt31 - silabs,skip-recall: Do not perform NVM->RAM recall operation. It will rely
/linux/Documentation/ABI/stable/
H A Dsysfs-firmware-opal-dump21 Do not rely on any particular size of dump
/linux/Documentation/power/
H A Dapm-acpi.rst26 Both APM and ACPI rely on user-space daemons, apmd and acpid
/linux/drivers/media/v4l2-core/
H A DKconfig31 Only useful if you rely on the old behavior and use mknod instead of udev.
/linux/Documentation/i2c/
H A Dfault-codes.rst22 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 DKconfig66 in boot and cannot rely on the firmware being placed in an initrd or
126 rely on one refer to the permissively licensed firmwared:
236 to support cards that rely on user-initiated updates for firmware files.
/linux/Documentation/devicetree/bindings/net/bluetooth/
H A Dmediatek,bluetooth.txt27 the GPIO control still has to rely on the dedicated GPIO controller such as

1234567