Searched full:point (Results 1 – 25 of 729) sorted by relevance
12345678910>>...30
| /Documentation/core-api/ |
| D | floating-point.rst | 3 Floating-point API
6 Kernel code is normally prohibited from using floating-point (FP) registers or
9 userspace floating-point register state.
15 floating-point usage.
20 floating-point registers may be wider than general-purpose registers.
22 Usability of floating-point code within the kernel is architecture-specific.
24 both with and without a floating-point unit, FPU availability must be checked
27 Several architectures implement the generic kernel floating-point API from
34 Floating-point code may be built if the option ``ARCH_HAS_KERNEL_FPU_SUPPORT``
61 This function reports if floating-point code can be used on this CPU or
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-firmware-dmi-tables | 6 data referenced by a SMBIOS table entry point. The SMBIOS
7 entry point contains general information, like SMBIOS
9 size of SMBIOS entry point is dependent on SMBIOS version.
10 The format of SMBIOS entry point and DMI structures
13 The dmi/tables provides raw SMBIOS entry point and DMI tables
15 from /dev/mem. The raw SMBIOS entry point and DMI table are
|
| D | sysfs-devices-physical_location | 6 the device connection point with respect to the system's
14 device connection point resides on.
20 Describes vertical position of the device connection point on
27 Describes horizontal position of the device connection point on
34 "Yes" if the device connection point resides in a docking
41 "Yes" if the device connection point resides on the lid of
|
| D | sysfs-class-thermal | 51 The temperature above which trip point will be fired.
59 Strings which indicate the type of the trip point.
68 The hysteresis value for a trip point, represented as an
84 The trip point in this thermal zone which `cdev[0-*]` is
86 associated with any trip point.
142 temperature" trip point. For more information see
152 temperature" trip point. For more information see
159 Temperature offset from the desired temperature trip point
164 temperature trip point. For more information see
|
| D | sysfs-firmware-lefi-boardinfo | 6 this is useful to point out the current used mainboard type
35 # No SMBIOS nor DMI entry point found, sorry.
|
| /Documentation/userspace-api/media/mediactl/ |
| D | media-controller-model.rst | 30 - A **data link** is a point-to-point oriented connection between two
34 - An **interface link** is a point-to-point bidirectional control
37 - An **ancillary link** is a point-to-point connection denoting that two
|
| /Documentation/arch/x86/ |
| D | booting-dt.rst | 6 There is one single 32bit entry point to the kernel at code32_start,
7 the decompressor (the real mode entry point goes to the same 32bit
8 entry point once it switched into protected mode). That entry point
|
| /Documentation/devicetree/bindings/thermal/ |
| D | db8500-thermal.txt | 11 - tripN-temp : temperature of trip point N, should be in ascending order;
12 - tripN-type : type of trip point N, should be one of "active" "passive" "hot"
15 point N, this is required if trip point N is defined, set it 0 if none,
17 - tripN-cdev-nameM : name of the No. M cooling device of trip point N;
|
| D | armada-thermal.txt | 24 marvell,armada380-thermal, and marvell,armadaxp-thermal must point to
25 "control MSB/control 1", with size of 4 (deprecated binding), or point
27 compatibles must point to "control LSB/control 0" with size of 8.
|
| /Documentation/arch/arm/nwfpe/ |
| D | netwinder-fpe.rst | 5 The following describes the current state of the NetWinder's floating point
8 In the following nomenclature is used to describe the floating point
19 Floating Point Coprocessor Data Transfer Instructions (CPDT)
41 for each floating point register into the memory location given in the
46 Floating Point Coprocessor Register Transfer Instructions (CPRT)
51 FLT{cond}<S,D,E>{P,M,Z} Fn, Rd Convert integer to floating point
52 FIX{cond}{P,M,Z} Rd, Fn Convert floating point to integer
53 WFS{cond} Rd Write floating point status register
54 RFS{cond} Rd Read floating point status register
55 WFC{cond} Rd Write floating point control register
[all …]
|
| D | nwfpe.rst | 5 Floating Point Emulator.
10 working version of all the floating point instructions the compiler
25 The floating point operations are based on SoftFloat Release 2, by
26 John Hauser. SoftFloat is a software implementation of floating-point
27 that conforms to the IEC/IEEE Standard for Binary Floating-point
52 The NetWinder Floating Point Emulator is free software. Everything Rebel.com
66 a fixed-point vector processor in collaboration with the University of
|
| D | todo.rst | 22 hardware, but are handled by the floating point support code. They should
59 pulled out from some docs on ARM floating point, specifically
62 The floating point control register (FPCR) may only be present in some
64 specific manner, for example to disable the floating point system. The user
|
| /Documentation/filesystems/spufs/ |
| D | spu_create.rst | 28 point to a non-existing directory in the mount point of the SPU file
65 point.
72 EINVAL pathname is not a directory in the spufs mount point.
110 pathname must point to a location beneath the mount point of spufs. By
|
| /Documentation/scheduler/ |
| D | sched-util-clamp.rst | 22 point; hence the name. That is, by clamping utilization we are making the
23 system run at a certain performance point.
36 performance point to operate at to deliver the desired user experience. Or one
38 much resources and should not go above a specific performance point. Viewing
40 abstraction from user space point of view.
44 performance point required by its display pipeline to ensure no frame is
58 resources background tasks are consuming by capping the performance point they
86 performance point will suffer a delay of ~200ms (PELT HALFIFE = 32ms) for the
98 the device doesn't heat up to the point where it will throttle.
103 performance point rather than being tied to MAX frequency all the time. Which
[all …]
|
| /Documentation/filesystems/ |
| D | autofs-mount-control.rst | 27 because the point from which the path is constructed has been detached
68 top of this mount point". Since these are always directories we can
108 on the mount point for control operations. The references held by the
142 point dentry (covered or not) has also been added.
202 The ioctlfd field is a mount point file descriptor of an autofs mount
203 point. It is returned by the open call and is used by all calls except
204 the check for whether a given path is a mount point, where it may
206 mount point file descriptor, and when requesting the uid and gid of the
230 not a valid descriptor or doesn't correspond to an autofs mount point
261 with the ioctlfd field set to a valid autofs mount point descriptor
[all …]
|
| /Documentation/fault-injection/ |
| D | provoke-crashes.rst | 14 You can select the location of the trigger ("crash point name") and the
15 type of action ("crash point type") either through module arguments when
35 Indicates the action to be taken on hitting the crash point.
42 Indicates the number of times the crash point is to be hit
|
| /Documentation/arch/powerpc/ |
| D | booting.rst | 10 become the ppc32 kernel entry point and the way a new platform should be added
34 Entry point
37 There is one single entry point to the kernel, at the start
38 of the kernel image. That entry point supports two calling
62 point is called by a) after the OF trampoline and can also be
70 PowerPC platform. The entry point definition then becomes:
|
| /Documentation/devicetree/bindings/soc/qcom/ |
| D | qcom,smp2p.yaml | 7 title: Qualcomm Shared Memory Point 2 Point
15 The Shared Memory Point to Point (SMP2P) protocol facilitates communication
123 # defined from the 8974 apps processor's point-of-view. It encompasses one
|
| /Documentation/maintainer/ |
| D | maintainer-entry-profile.rst | 33 device-driver may point to an entry for its parent subsystem. This makes
63 their first posting for consideration before this point. Patches that
64 are submitted after this point should be clear that they are targeting
71 Indicate to contributors the point at which an as yet un-applied patch
74 concluded by this point the expectation is the contributor should wait and
|
| /Documentation/networking/mac80211_hwsim/ |
| D | mac80211_hwsim.rst | 25 point, mac80211_hwsim is yet another hardware driver, i.e., no changes
39 point and a station) or large scale tests (multiple access points with
58 one to act as an access point and the other as a station that
61 processing access point side of association.
|
| /Documentation/networking/ |
| D | ppp_generic.rst | 112 to the user-level process. From that point, the PPP negotiation code
166 point the packets can no longer be reordered, as the decompression
258 to point to a separate object for each open instance of /dev/ppp. In
291 instance the "owner" of the interface. The argument should point to
298 The argument should point to an int containing the unit number.
302 The argument should point to an int containing the channel number.
308 argument should point to an int containing the interface unit
318 point to an int containing the channel number of the channel to bridge
339 The argument should point to an int containing the new MRU value.
368 interface unit. The argument should point to an int where the ioctl
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lm3532.txt | 24 set-point to another after the device has reached its
25 initial target set point from turn-on
27 set-point to another after the device has reached its
28 initial target set point from turn-on
|
| /Documentation/bpf/ |
| D | prog_flow_dissector.rst | 54 skb->data + flow_keys->nhoff point to the first byte of L3_HEADER
71 skb->data + flow_keys->nhoff point the to first byte of TCI
90 skb->data + flow_keys->nhoff point the to first byte of L3_HEADER
131 * ``_dissect`` routine - entry point; it does input ``n_proto`` parsing and
134 Since BPF at this point doesn't support looping (or any jumping back),
|
| /Documentation/mm/ |
| D | mmu_notifier.rst | 14 B) a page table entry is updated to point to a new page (COW, write fault
25 - set page table entry to point to new page
53 CPU-thread-0 {COW_step1: {update page table to point to new page for addrA}}
54 CPU-thread-1 {COW_step1: {update page table to point to new page for addrB}}
93 When changing a pte to write protect or to point to a new write protected page
|
| /Documentation/devicetree/bindings/bus/ |
| D | qcom,ssbi.yaml | 10 Some Qualcomm MSM devices contain a point-to-point serial bus used to
|
12345678910>>...30