Home
last modified time | relevance | path

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

12345678

/linux/Documentation/ABI/testing/
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
/linux/drivers/input/mouse/
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/ABI/
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/
A DKconfig9 superior alternatives, but some applications may still rely on
/linux/Documentation/admin-guide/
A Dabi-testing.rst11 Userspace programs can start to rely on these interfaces, but they must
/linux/tools/bpf/bpftool/Documentation/
A Dcommon_options.rst10 pids associated to BPF objects may rely on it).
/linux/Documentation/devicetree/bindings/soc/amlogic/
A Damlogic,canvas.yaml19 Many IPs within Amlogic SoCs rely on canvas indexes to read/write pixel data
/linux/Documentation/arm/
A Dswp_emulation.rst23 when accessing uncached shared regions, LDREX/STREX rely on an external
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
A Dmem_alignment.rst13 Of course this is a bad idea to rely on the alignment trap to perform
/linux/fs/sysfs/
A DKconfig16 Some system agents rely on the information in sysfs to operate.
/linux/Documentation/devicetree/bindings/mmc/
A Dsdhci-atmel.txt16 - assigned-clock-rates The rate of "multclk" in order to not rely on the
/linux/arch/arm64/boot/dts/amlogic/
A Dmeson-g12b-a311d-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
A Dmeson-g12b-s922x-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
A Dmeson-sm1-khadas-vim3l.dts97 * testing purposes, but instead rely on the firmware/bootloader to
/linux/Documentation/accounting/
A Dcgroupstats.rst21 NOTE: We currently rely on delay accounting for extracting information
/linux/Documentation/features/sched/membarrier-sync-core/
A Darch-support.txt23 # Given that neither SYSRET{L,Q}, nor SYSEXIT, are core serializing, we rely
/linux/Documentation/devicetree/bindings/clock/
A Dsilabs,si570.txt31 - silabs,skip-recall: Do not perform NVM->RAM recall operation. It will rely
/linux/Documentation/ABI/stable/
A Dsysfs-firmware-opal-dump21 Do not rely on any particular size of dump
/linux/Documentation/power/
A Dapm-acpi.rst26 Both APM and ACPI rely on user-space daemons, apmd and acpid
/linux/Documentation/i2c/
A Dfault-codes.rst22 to respond correctly. Other code may need to rely on YOUR code reporting
57 host. Note that even if PECs are in use, you should not rely
/linux/drivers/media/v4l2-core/
A DKconfig39 Only useful if you rely on the old behavior and use mknod instead of udev.
/linux/Documentation/driver-api/media/
A Dcamera-sensor.rst30 can rely on this frequency being used.
129 Existing camera sensor drivers may rely on the old
/linux/Documentation/admin-guide/LSM/
A DSafeSetID.rst64 that rely on certain process-spawning semantics in Linux.
117 once we have the policy checking code in place, which will rely on GID policy
/linux/Documentation/filesystems/
A Dceph.rst25 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
138 must rely on TCP's error correction to detect data corruption

Completed in 28 milliseconds

12345678