Home
last modified time | relevance | path

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

12345678

/Linux-v6.6/Documentation/ABI/testing/
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
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
/Linux-v6.6/drivers/input/mouse/
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-v6.6/Documentation/ABI/
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-v6.6/fs/notify/dnotify/
DKconfig9 superior alternatives, but some applications may still rely on
/Linux-v6.6/Documentation/admin-guide/
Dabi-testing.rst11 Userspace programs can start to rely on these interfaces, but they must
Dfilesystem-monitoring.rst45 in the future. Therefore, applications must not rely on the order and
/Linux-v6.6/tools/bpf/bpftool/Documentation/
Dcommon_options.rst13 associated to BPF objects may rely on it).
/Linux-v6.6/Documentation/arch/arm/
Dswp_emulation.rst23 when accessing uncached shared regions, LDREX/STREX rely on an external
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
Dmem_alignment.rst13 Of course this is a bad idea to rely on the alignment trap to perform
/Linux-v6.6/fs/sysfs/
DKconfig16 Some system agents rely on the information in sysfs to operate.
/Linux-v6.6/Documentation/devicetree/bindings/mmc/
Dsdhci-atmel.txt18 - assigned-clock-rates The rate of "multclk" in order to not rely on the
/Linux-v6.6/arch/arm64/boot/dts/amlogic/
Dmeson-g12b-a311d-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
Dmeson-g12b-s922x-khadas-vim3.dts29 * testing purposes, but instead rely on the firmware/bootloader to
Dmeson-sm1-khadas-vim3l.dts97 * testing purposes, but instead rely on the firmware/bootloader to
/Linux-v6.6/Documentation/accounting/
Dcgroupstats.rst21 NOTE: We currently rely on delay accounting for extracting information
/Linux-v6.6/Documentation/features/sched/membarrier-sync-core/
Darch-support.txt23 # Given that neither SYSRET{L,Q}, nor SYSEXIT, are core serializing, we rely
/Linux-v6.6/Documentation/devicetree/bindings/clock/
Dsilabs,si570.txt31 - silabs,skip-recall: Do not perform NVM->RAM recall operation. It will rely
/Linux-v6.6/Documentation/ABI/stable/
Dsysfs-firmware-opal-dump21 Do not rely on any particular size of dump
/Linux-v6.6/Documentation/power/
Dapm-acpi.rst26 Both APM and ACPI rely on user-space daemons, apmd and acpid
/Linux-v6.6/drivers/media/v4l2-core/
DKconfig31 Only useful if you rely on the old behavior and use mknod instead of udev.
/Linux-v6.6/Documentation/i2c/
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-v6.6/drivers/base/firmware_loader/
DKconfig59 in boot and cannot rely on the firmware being placed in an initrd or
119 rely on one refer to the permissively licensed firmwared:
229 to support cards that rely on user-initiated updates for firmware files.
/Linux-v6.6/arch/arm64/boot/dts/qcom/
Dsc7280-chrome-common.dtsi104 * driving them. We rely on the normal pulls configured in

12345678