Home
last modified time | relevance | path

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

/linux-4.4.14/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-firmware-dmi-entries10 The kernel itself does not rely on the majority of the
/linux-4.4.14/drivers/input/mouse/
Dmaplemouse.c28 int buttons, relx, rely, relz; in dc_mouse_callback() local
36 rely = *(unsigned short *)(res + 14) - 512; in dc_mouse_callback()
43 input_report_rel(dev, REL_Y, rely); in dc_mouse_callback()
/linux-4.4.14/fs/notify/dnotify/
DKconfig8 superior alternatives, but some applications may still rely on
/linux-4.4.14/Documentation/ABI/
DREADME26 programs can start to rely on these interfaces, but they must be
80 - Kconfig. Userspace should not rely on the presence or absence of any
85 - Kernel-internal symbols. Do not rely on the presence, absence, location, or
/linux-4.4.14/fs/sysfs/
DKconfig15 Some system agents rely on the information in sysfs to operate.
/linux-4.4.14/Documentation/arm/
Dswp_emulation22 NOTE: when accessing uncached shared regions, LDREX/STREX rely on an external
Dkernel_mode_neon.txt6 * Use only NEON instructions, or VFP instructions that don't rely on support
67 Earlier versions of VFP (prior to version 3) rely on software support for things
Dmem_alignment9 Of course this is a bad idea to rely on the alignment trap to perform
DPorting6 The following symbol definitions rely on you knowing the translation that
Dcluster-pm-race-avoidance.txt32 mechanisms like Linux spinlocks may rely on coherency mechanisms which
/linux-4.4.14/Documentation/accounting/
Dcgroupstats.txt17 NOTE: We currently rely on delay accounting for extracting information
/linux-4.4.14/Documentation/arm64/
Dtagged-pointers.txt23 of tags cannot rely on the tag information for user virtual
/linux-4.4.14/Documentation/ABI/stable/
Dsysfs-firmware-opal-dump20 Do not rely on any particular size of dump
/linux-4.4.14/Documentation/power/
Dapm-acpi.txt24 Both APM and ACPI rely on user-space daemons, apmd and acpid
Dvideo.txt34 hard/impossible. Methods that do not rely on userland are preferable.
/linux-4.4.14/Documentation/devicetree/bindings/mtd/
Dgpmi-nand.txt29 area with the byte in the data area but rely on the
/linux-4.4.14/drivers/media/v4l2-core/
DKconfig24 Only useful if you rely on the old behavior and use mknod instead of udev.
/linux-4.4.14/Documentation/i2c/
Dsummary14 achieve I2C branding. Modern PC mainboards rely on SMBus. The most common
Dfault-codes18 to respond correctly. Other code may need to rely on YOUR code reporting
53 host. Note that even if PECs are in use, you should not rely
/linux-4.4.14/Documentation/filesystems/
Dceph.txt21 In contrast to cluster filesystems like GFS, OCFS2, and GPFS that rely
119 must rely on TCP's error correction to detect data corruption
Dporting462 taken anymore, so verify that your callbacks do not rely on it (none
Dspufs.txt155 programs should not rely on them because access to any of them except
/linux-4.4.14/arch/arm/boot/dts/
Dsun8i-a23-ippo-q8h-v1.2.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a33-q8-tablet.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a23-q8-tablet.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a23-ippo-q8h-v5.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a33-ippo-q8h-v1.2.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a33-et-q8-v1.6.dts53 * FIXME for now we only support host mode and rely on u-boot to have
Dsun8i-a23-gt90h-v4.dts133 * FIXME for now we only support host mode and rely on u-boot to have
/linux-4.4.14/drivers/nvdimm/
DKconfig64 applications that rely on sector writes not being torn (a
/linux-4.4.14/Documentation/fmc/
Dfmc-chardev.txt12 fdelay-0400 if the FMC core can rely on both a mezzanine name and a bus
Dmezzanine.txt82 The parameters are carrier-specific, in that they rely on the busid
/linux-4.4.14/Documentation/hwmon/
Dltc424543 rely on the sense resistors listed in Table 2: "Sense Resistor Values".
/linux-4.4.14/arch/arm/crypto/
DKconfig101 This implementation does not rely on any lookup tables so it is
/linux-4.4.14/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt92 rely on are still enabled at that point.
/linux-4.4.14/Documentation/parisc/
Dregisters105 since the caller can't rely on the value being the same
/linux-4.4.14/Documentation/
Dunaligned-memory-access.txt93 Therefore, for standard structure types you can always rely on the compiler
97 Similarly, you can also rely on the compiler to align variables and function
Dpreempt-locking.txt123 in doubt, rely on locking or explicit preemption disabling.
Dcpu-hotplug.txt63 should only rely on this to count the # of cpus, but *MUST* not rely
Dcircular-buffers.txt187 is actually awakened. We therefore cannot rely on it for ordering. However,
Dclk.txt233 clocks properly but rely on them being on from the bootloader, bypassing
Dsysfs-rules.txt39 interfaces, and such that you can rely on in userspace. Everything is
Drbtree.txt208 you are not expected to rely on; please stick to the documented APIs
Dinitrd.txt313 Current kernels still support it, but you should _not_ rely on its
DHOWTO63 people on the mailing lists are not lawyers, and you should not rely on
Dmemory-barriers.txt742 You must also be careful not to rely too much on boolean short-circuit
Dkernel-parameters.txt1575 as thermal controls and power capping, that rely on ACPI
/linux-4.4.14/arch/arm/kernel/
Dentry-header.S85 @ we cannot rely on r0-r3 and r12 matching the value saved in the
/linux-4.4.14/Documentation/usb/
Dhotplug.txt29 Because some of those actions rely on information about drivers (metadata)
DURB.txt10 complete; don't rely on it except for a quick overview.
Dproc_usb_info.txt49 you can't rely on them for stable access to devices. For example,
/linux-4.4.14/Documentation/gpio/
Dgpio.txt32 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
Ddriver.txt197 callbacks from the GPIO and irqchip APIs. Do not rely on gpiod_to_irq() having
Dgpio-legacy.txt19 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
154 idea to rely on boot firmware to have set the direction correctly, since
/linux-4.4.14/Documentation/pcmcia/
Ddriver-changes.txt123 driver was reported to rely on them:
/linux-4.4.14/arch/mips/
DKconfig.debug52 Most MIPS systems will normally expect 'N' here and rely upon
/linux-4.4.14/Documentation/scheduler/
Dsched-rt-group.txt42 Realtime scheduling is all about determinism, a group has to be able to rely on
Dsched-design-CFS.txt88 CFS uses nanosecond granularity accounting and does not rely on any jiffies or
/linux-4.4.14/Documentation/video4linux/
Dsoc-camera.txt135 rely on camera drivers implementing .cropcap(). If the camera driver does not
/linux-4.4.14/Documentation/networking/
Dregulatory.txt77 *Most* drivers will rely on the first mechanism of providing a
Drds.txt135 forever if you rely on poll to tell you what to do.
Dvortex.txt347 reproduce problems and must rely on your patience and efforts to get to
Dppp_generic.txt163 algorithms rely on receiving compressed packets in the same order that
Darcnet.txt433 schemes that rely completely on the netmask and a 'default gateway' to
Dcan.txt381 kernel interfaces (ABI) which heavily rely on the CAN frame with fixed eight
Dbonding.txt790 a concern use this variable to disable flow shuffling and rely on
1923 then the MII monitor will rely on the driver for carrier state
Dip-sysctl.txt350 only to prevent simple DoS attacks, you _must_ not rely on this
/linux-4.4.14/Documentation/fb/
Dudlfb.txt76 code. They write to the standard framebuffer interface and rely on udlfb
/linux-4.4.14/Documentation/driver-model/
Dplatform.txt122 original IBM PCs, rely on error-prone "probe-the-hardware" models for hardware
/linux-4.4.14/Documentation/prctl/
Dseccomp_filter.txt209 rip or rsp. (Do not rely on other changes terminating the process.
/linux-4.4.14/Documentation/input/
Dinput-programming.txt259 rely on kernel's default implementation of setting and querying keycode
/linux-4.4.14/Documentation/sound/alsa/
Dtimestamping.txt9 and precise moment. Applications should not rely solely on the first
/linux-4.4.14/Documentation/hid/
Duhid.txt18 dynamically so you need to rely on udev (or similar) to create the device node.
/linux-4.4.14/Documentation/virtual/kvm/
Dmsr.txt199 type 1 was, but guest should not rely on that.
/linux-4.4.14/Documentation/ia64/
Dmca.txt35 handlers cannot rely on the thread pointer, PAL physical mode can
Dfsys.txt188 words, user-level code must not rely on PSR.be being preserved
/linux-4.4.14/arch/tile/
DKconfig361 to not rely on the boot loader to provide them.)
/linux-4.4.14/Documentation/nvdimm/
Dbtt.txt19 persistent memory devices, so that applications that rely on sector writes not
Dnvdimm.txt539 region-types. Userspace can always rely on the generic region
/linux-4.4.14/Documentation/ioctl/
Dbotching-up-ioctls.txt57 extension is supported on a given kernel. If you can't rely on old kernels
/linux-4.4.14/arch/x86/
DKconfig.debug352 This might help diagnose strange hangs that rely on NMI to
DKconfig2087 to not rely on the boot loader to provide them.)
/linux-4.4.14/Documentation/device-mapper/
Dthin-provisioning.txt32 do not yet rely on them in production. But do experiment and offer us
/linux-4.4.14/drivers/net/usb/
DKconfig134 "Laplink" parallel cables or some motherboards. These rely
/linux-4.4.14/scripts/dtc/
Ddtc-parser.tab.c_shipped783 /* Print *YYLOCP on YYO. Private, do not rely on its existence. */
1455 users should not rely upon it. Assigning to YYVAL
/linux-4.4.14/arch/arm64/
DKconfig620 NOTE: when accessing uncached shared regions, LDXR/STXR rely
/linux-4.4.14/Documentation/scsi/
DBusLogic.txt29 costly and rely on the host CPU, rather than including an onboard processor.
DChangeLog.lpfc1561 routines. Remove generic'ness and rely on set attribute.
/linux-4.4.14/arch/arm/mm/
DKconfig706 NOTE: when accessing uncached shared regions, LDREX/STREX rely
/linux-4.4.14/drivers/ide/
DKconfig192 files in sysfs but many legacy applications rely on this.
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.seq561 * selection so we can rely on it even for case #1 above.
1614 * rely on the SCB_RESID* fields. Initialize the
/linux-4.4.14/Documentation/filesystems/caching/
Dnetfs-api.txt218 length. A netfs mustn't rely on being able to provide more than 400 bytes
/linux-4.4.14/scripts/genksyms/
Dparse.tab.c_shipped1672 users should not rely upon it. Assigning to YYVAL
/linux-4.4.14/scripts/kconfig/
Dzconf.tab.c_shipped1673 users should not rely upon it. Assigning to YYVAL
/linux-4.4.14/Documentation/block/
Dbiodoc.txt705 transfer in one go unless it interprets segments), and rely on the block layer
/linux-4.4.14/drivers/hwmon/
DKconfig1676 files which may change in the future, so you shouldn't rely
/linux-4.4.14/drivers/scsi/
DKconfig66 files in sysfs but many legacy applications rely on this.
/linux-4.4.14/init/
DKconfig555 for context tracking and the subsystems that rely on it: RCU
/linux-4.4.14/Documentation/RCU/
DRTFP.txt270 RCU-like usage that does not rely on an automatic garbage
/linux-4.4.14/drivers/video/fbdev/
DKconfig201 Generalized Timing Formula and the EDID parser. A few drivers rely