Home
last modified time | relevance | path

Searched refs:VFP (Results 1 – 16 of 16) sorted by relevance

/Linux-v5.4/Documentation/arm/
Dkernel_mode_neon.rst7 * Use only NEON instructions, or VFP instructions that don't rely on support
19 It is possible to use NEON instructions (and in some cases, VFP instructions) in
20 code that runs in kernel mode. However, for performance reasons, the NEON/VFP
24 may call schedule()], as NEON or VFP instructions will be executed in a
30 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
33 contending for the NEON/VFP unit (or, in the SMP case, when a task migrates to
34 another core). Lazy restore is implemented by disabling the NEON/VFP unit after
35 every context switch, resulting in a trap when subsequently a NEON/VFP
39 Any use of the NEON/VFP unit in kernel mode should not interfere with this, so
40 it is required to do an 'eager' preserve of the NEON/VFP register file, and
[all …]
Dmarvel.rst449 ARMv5TE, VFP, dual-issue
452 ARMv5TE, VFP, dual-issue
/Linux-v5.4/arch/arm/kvm/hyp/
Dvfp.S18 @ Make sure *really* VFP is enabled so we can touch the registers.
20 tst r5, #FPEXC_EX @ Check for VFP Subarchitecture
34 VFPFSTMIA r0, r5 @ Save VFP registers
43 VFPFLDMIA r0, r1 @ Load VFP registers
47 tst r0, #FPEXC_EX @ Check for VFP Subarchitecture
Dentry.S99 @ NEON/VFP used. Turn on VFP access.
105 @ Switch VFP/NEON hardware state to the guest's
/Linux-v5.4/arch/arm/vfp/
Dentry.S15 @ VFP entry point.
29 ldr pc, [r4] @ call VFP entry point
41 @ This code is called if the VFP does not exist. It needs to flag the
42 @ failure to the VFP initialisation code.
Dvfphw.S69 @ VFP hardware support entry point.
86 VFPFMRX r1, FPEXC @ Is the VFP enabled?
89 bne look_for_VFP_exceptions @ VFP is already enabled
102 @ On UP, we lazily save the VFP context. As a different
103 @ thread wants ownership of the VFP hardware, save the old
106 VFPFMXR FPEXC, r5 @ enable VFP, disable any pending
/Linux-v5.4/arch/arm/include/asm/
Dvfpmacros.h11 @ Macros to allow building with old toolkits (with no VFP support) in toolkits()
20 @ read all the working registers back into the VFP in toolkits()
35 VFPFMRX \tmp, MVFR0 @ Media and VFP Feature Register 0
44 @ write all the working registers out of the VFP
59 VFPFMRX \tmp, MVFR0 @ Media and VFP Feature Register 0
/Linux-v5.4/Documentation/arm/vfp/
Drelease-notes.rst2 Release notes for Linux Kernel VFP support code
9 This is the first release of the Linux Kernel VFP support code. It
10 provides support for the exceptions bounced from VFP hardware found
/Linux-v5.4/include/video/
Dkyro.h25 u32 VFP; /* Ver Front Porch */ member
/Linux-v5.4/drivers/video/fbdev/kyro/
Dfbdev.c459 var->lower_margin = par->VFP; in kyrofb_check_var()
509 par->VFP = info->var.lower_margin; in kyrofb_set_par()
512 par->VTot = par->YRES + par->VBP + par->VST + par->VFP; in kyrofb_set_par()
/Linux-v5.4/arch/arm/mach-omap2/
DKconfig138 select VFP
/Linux-v5.4/arch/arm/
DKconfig2038 config VFP config
2039 bool "VFP-format floating point maths"
2042 Say Y to include VFP support code in the kernel. This is needed
2043 if your hardware includes a VFP unit.
2048 Say N if your target does not have VFP hardware.
2052 depends on VFP
/Linux-v5.4/arch/arm64/
DKconfig1166 the user helper functions, VFP support and the ptrace interface are
/Linux-v5.4/drivers/eisa/
Deisa.ids687 ICU06B0 "Zoom VFP V.32bis FAX Modem"
/Linux-v5.4/Documentation/virt/kvm/
Dapi.txt2123 ARM 32-bit VFP control registers have the following id bit patterns:
/Linux-v5.4/
DMAINTAINERS2513 ARM/VFP SUPPORT