Home
last modified time | relevance | path

Searched +full:point +full:- +full:to +full:- +full:point (Results 1 – 25 of 710) sorted by relevance

12345678910>>...29

/Documentation/core-api/
Dfloating-point.rst1 .. SPDX-License-Identifier: GPL-2.0+
3 Floating-point API
6 Kernel code is normally prohibited from using floating-point (FP) registers or
8 system call overhead, because the kernel does not need to save and restore the
9 userspace floating-point register state.
11 However, occasionally drivers or library functions may need to include FP code.
12 This is supported by isolating the functions containing FP code to a separate
14 state around calls to those functions. This creates "critical sections" of
15 floating-point usage.
17 The reason for this isolation is to prevent the compiler from generating code
[all …]
/Documentation/userspace-api/media/mediactl/
Dmedia-controller-model.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _media-controller-model:
9 is one of the goals of the media controller API. To achieve this,
14 - An **entity** is a basic media hardware or software building block.
15 It can correspond to a large variety of logical blocks such as
17 hardware devices (a building block in a System-on-Chip image
20 - An **interface** is a graph representation of a Linux Kernel
24 - A **pad** is a data connection endpoint through which an entity can
25 interact with other entities. Data (not restricted to video) produced
26 by an entity flows from the entity's output to one or more entity
[all …]
/Documentation/arch/x86/
Dbooting-dt.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
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
11 The physical pointer to the device-tree block is passed via setup_data
17 This device-tree is used as an extension to the "boot page". As such it
/Documentation/arch/arm/nwfpe/
Dnetwinder-fpe.rst5 The following describes the current state of the NetWinder's floating point
8 In the following nomenclature is used to describe the floating point
14 {P|M|Z} = {round to +infinity,round to -infinity,round to zero},
15 default = round to nearest
19 Floating Point Coprocessor Data Transfer Instructions (CPDT)
20 ------------------------------------------------------------
22 LDF/STF - load and store floating
30 LFM/SFM - load and store multiple floating
41 for each floating point register into the memory location given in the
42 instruction. The format in memory is unlikely to be compatible with
[all …]
Dnwfpe.rst5 Floating Point Emulator.
10 working version of all the floating point instructions the compiler
11 emits as the first target. I have attempted to be as optimal as
14 I have attempted to make the emulator as portable as possible. One of
17 have attempted to use the C_SYMBOL_NAME macro wherever this may be
20 Another choice I made was in the file structure. I have attempted to
23 others to port the emulator to NetBSD for instance relatively easily.
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
[all …]
Dtodo.rst6 POW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - power
7 RPW{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - reverse power
8 POL{cond}<S|D|E>{P,M,Z} Fd, Fn, <Fm,#value> - polar angle (arctan2)
10 LOG{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base 10
11 LGN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - logarithm to base e
12 EXP{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - exponent
13 SIN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - sine
14 COS{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - cosine
15 TAN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - tangent
16 ASN{cond}<S|D|E>{P,M,Z} Fd, <Fm,#value> - arcsine
[all …]
Dnotes.rst4 There seems to be a problem with exp(double) and our emulator. I haven't
5 been able to track it down yet. This does not occur with the emulator
9 will point it out. The ARM calling conventions require floating point
10 registers f4-f7 to be preserved over a function call. The compiler quite
11 often uses an stfe instruction to save f4 on the stack upon entry to a
12 function, and an ldfe instruction to restore it before returning.
16 f4 had been converted to an extended value in the emulator.
18 This is a side effect of the stfe instruction. The double in f4 had to be
19 converted to extended, then stored. If an lfm/sfm combination had been used,
22 emulator sees a multiply of a double and extended, it promotes the double to
[all …]
/Documentation/devicetree/bindings/thermal/
Ddb8500-thermal.txt1 * ST-Ericsson DB8500 Thermal
5 - compatible : "stericsson,db8500-thermal";
6 - reg : address range of the thermal sensor registers;
7 - interrupts : interrupts generated from PRCMU;
8 - interrupt-names : "IRQ_HOTMON_LOW" and "IRQ_HOTMON_HIGH";
9 - num-trips : number of total trip points, this is required, set it 0 if none,
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"
14 - tripN-cdev-num : number of the cooling devices which can be bound to trip
15 point N, this is required if trip point N is defined, set it 0 if none,
[all …]
Darmada-thermal.txt5 - compatible: Should be set to one of the following:
6 * marvell,armada370-thermal
7 * marvell,armada375-thermal
8 * marvell,armada380-thermal
9 * marvell,armadaxp-thermal
10 * marvell,armada-ap806-thermal
11 * marvell,armada-ap807-thermal
12 * marvell,armada-cp110-thermal
16 Documentation/devicetree/bindings/arm/marvell/ap80x-system-controller.txt
17 Documentation/devicetree/bindings/arm/marvell/cp110-system-controller.txt
[all …]
/Documentation/filesystems/spufs/
Dspu_create.rst1 .. SPDX-License-Identifier: GPL-2.0
9 spu_create - create a new spu context
25 the Cell Broadband Engine Architecture in order to access Synergistic
27 pathname and returns a handle to associated with it. pathname must
28 point to a non-existing directory in the mount point of the SPU file
29 system (spufs). When spu_create is successful, a directory gets cre-
32 The returned file handle can only be passed to spu_run(2) or closed,
33 other operations are not defined on it. When it is closed, all associ-
35 pointing either inside of the context directory or to this file
56 spu_create returns a new file descriptor. It may return -1 to indicate
[all …]
/Documentation/ABI/testing/
Dsysfs-class-thermal6 In order to keep it consistent with hwmon sys attribute; this
51 The temperature above which trip point will be fired.
59 Strings which indicate the type of the trip point.
61 E.g. it can be one of critical, hot, passive, `active[0-*]`
68 The hysteresis value for a trip point, represented as an
77 Sysfs link to the thermal cooling device node where the sys I/F
84 The trip point in this thermal zone which `cdev[0-*]` is
85 associated with; -1 means the cooling device is not
86 associated with any trip point.
92 The influence of `cdev[0-*]` in this thermal zone. This value
[all …]
Dsysfs-firmware-lefi-boardinfo6 this is useful to point out the current used mainboard type
20 Board Name : LEMOTE-LS3A4000-7A1000-1w-V01-pc
25 Version : Kunlun-A1901-V4.1.3-20200414093938
27 Release Date : 2020-04-14
35 # No SMBIOS nor DMI entry point found, sorry.
/Documentation/scheduler/
Dsched-util-clamp.rst1 .. SPDX-License-Identifier: GPL-2.0
11 feature that allows user space to help in managing the performance requirement
15 Uclamp is a hinting mechanism that allows the scheduler to understand the
17 scheduler to make a better decision. And when schedutil cpufreq governor is
21 util clamp acts on that to achieve its goal by clamping the signal to a certain
22 point; hence the name. That is, by clamping utilization we are making the
23 system run at a certain performance point.
25 The right way to view util clamp is as a mechanism to make request or hint on
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
[all …]
/Documentation/filesystems/
Dautofs-mount-control.rst1 .. SPDX-License-Identifier: GPL-2.0
10 There is a problem with active restarts in autofs (that is to say
14 directory that is being managed in order to be able to issue control
15 operations. Using a file descriptor gives ioctl operations access to
20 mount itself which prevents us being able to use open(2) to obtain a
23 Currently autofs uses "umount -l" (lazy umount) to clear active mounts
25 needs to walk back up the mount tree to construct a path, such as
27 because the point from which the path is constructed has been detached
30 The actual problem with autofs is that it can't reconnect to existing
31 mounts. Immediately one thinks of just adding the ability to remount
[all …]
/Documentation/fault-injection/
Dprovoke-crashes.rst1 .. SPDX-License-Identifier: GPL-2.0
7 The lkdtm module provides an interface to disrupt (and usually crash)
8 the kernel at predefined code locations to evaluate the reliability of
9 the kernel's exception handling and to test crash dumps obtained using
10 different dumping solutions. The module uses KPROBEs to instrument the
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
26 goal of being just large enough to exhaust the kernel stack. The
30 Where in the kernel to trigger the action. It can be
35 Indicates the action to be taken on hitting the crash point.
[all …]
/Documentation/arch/powerpc/
Dbooting.rst1 .. SPDX-License-Identifier: GPL-2.0
4 ------------------
8 was decided to enforce some strict rules regarding the kernel entry and
9 bootloader <-> kernel interfaces, in order to avoid the degeneration that had
10 become the ppc32 kernel entry point and the way a new platform should be added
11 to the kernel. The legacy iSeries platform breaks those rules as it predates
14 merged architecture for ppc32 and ppc64, new 32-bit platforms and 32-bit
15 platforms which move into arch/powerpc will be required to use these rules as
19 of a device-tree whose format is defined after Open Firmware specification.
20 However, in order to make life easier to embedded board vendors, the kernel
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,smp2p.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Shared Memory Point 2 Point
10 - Andy Gross <agross@kernel.org>
11 - Bjorn Andersson <bjorn.andersson@linaro.org>
12 - Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
15 The Shared Memory Point to Point (SMP2P) protocol facilitates communication
16 of a single 32-bit value between two processors. Each value has a single
18 uniquely identified in the system by the directed edge (local processor ID to
[all …]
/Documentation/maintainer/
Dmaintainer-entry-profile.rst6 The Maintainer Entry Profile supplements the top-level process documents
7 (submitting-patches, submitting drivers...) with
8 subsystem/device-driver-local customs as well as details about the patch
9 submission life-cycle. A contributor uses this document to level set
11 profiles to look across subsystems for opportunities to converge on
16 --------
17 Provide an introduction to how the subsystem operates. While MAINTAINERS
18 tells the contributor where to send patches for which files, it does not
19 convey other subsystem-local infrastructure and mechanisms that aid
22 Example questions to consider:
[all …]
/Documentation/networking/mac80211_hwsim/
Dmac80211_hwsim.rst3 .. SPDX-License-Identifier: GPL-2.0
7 mac80211_hwsim - software simulator of 802.11 radio(s) for mac80211
20 mac80211_hwsim is a Linux kernel module that can be used to simulate
21 arbitrary number of IEEE 802.11 radios for mac80211. It can be used to
25 point, mac80211_hwsim is yet another hardware driver, i.e., no changes
26 to mac80211 are needed to use this testing tool.
28 The main goal for mac80211_hwsim is to make it easier for developers
29 to test their code and work with new features to mac80211, hostapd,
31 of real hardware, so it is easy to generate an arbitrary test setup
37 to select how many radios are simulated (default 2). This allows
[all …]
/Documentation/networking/
Dppp_generic.rst1 .. SPDX-License-Identifier: GPL-2.0
12 The generic PPP driver in linux-2.4 provides an implementation of the
16 * the interface to the networking code
19 * the interface to pppd, via a /dev/ppp character device
27 mechanism for transporting PPP frames from one machine to another. A
30 to be able to send PPP frames, receive PPP frames, and optionally
35 This architecture makes it possible to implement PPP multilink in a
36 natural and straightforward way, by allowing more than one channel to
37 be linked to each ppp network interface unit. The generic layer is
43 ---------------
[all …]
/Documentation/bpf/
Dprog_flow_dissector.rst1 .. SPDX-License-Identifier: GPL-2.0
13 BPF flow dissector is an attempt to reimplement C-based flow dissector logic
14 in BPF to gain all the benefits of BPF verifier (namely, limits on the
26 * ``nhoff`` - initial offset of the networking header
27 * ``thoff`` - initial offset of the transport header, initialized to nhoff
28 * ``n_proto`` - L3 protocol type, parsed out of L2 header
29 * ``flags`` - optional flags
35 The return code of the BPF program is either BPF_OK to indicate successful
36 dissection, or BPF_DROP to indicate parsing error.
38 __sk_buff->data
[all …]
/Documentation/devicetree/bindings/leds/
Dleds-lm3532.txt1 * Texas Instruments - lm3532 White LED driver with ambient light sensing
4 The LM3532 provides the 3 high-voltage, low-side current sinks. The device is
5 programmable over an I2C-compatible interface and has independent
11 each with 32 internal voltage setting resistors, 8-bit logarithmic and linear
12 brightness control, dual external PWM brightness control inputs, and up to
16 - compatible : "ti,lm3532"
17 - reg : I2C slave address
18 - #address-cells : 1
19 - #size-cells : 0
22 - enable-gpios : gpio pin to enable (active high)/disable the device.
[all …]
/Documentation/mm/
Dmmu_notifier.rst1 When do you need to notify inside page table lock ?
4 When clearing a pte/pmd we are given a choice to notify the event through
9 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
10 process virtual address space). There is only 2 cases when you need to notify
14 B) a page table entry is updated to point to a new page (COW, write fault
17 Case A is obvious you do not want to take the risk for the device to write to
20 Case B is more subtle. For correctness it requires the following sequence to
23 - take page table lock
24 - clear page table entry and notify ([pmd/pte]p_huge_clear_flush_notify())
25 - set page table entry to point to new page
[all …]
/Documentation/ABI/stable/
Dvdso9 the vDSO and it often contains useful and highly-optimized alternatives
10 to real syscalls.
12 These functions are called according to your platform's ABI. On many
16 (For example, if you set CS on x86 to something strange, the vDSO functions are
17 within their rights to crash.) In addition, if you pass a bad
18 pointer to a vDSO function, you might get SIGSEGV instead of -EFAULT.
20 To find the DSO, parse the auxiliary vector passed to the program's
21 entry point. The AT_SYSINFO_EHDR entry will point to the vDSO.
26 Programs that dynamically link to glibc will use the vDSO automatically.
36 The maintainers of the other vDSO-using architectures should confirm
/Documentation/userspace-api/media/v4l/
Dext-ctrls-colorimetry.rst1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
3 .. _colorimetry-controls:
15 -----------------------
17 .. _colorimetry-control-id:
32 .. flat-table:: struct v4l2_ctrl_hdr10_cll_info
33 :header-rows: 0
34 :stub-columns: 0
37 * - __u16
38 - ``max_content_light_level``
39 - The upper bound for the maximum light level among all individual
[all …]

12345678910>>...29