Home
last modified time | relevance | path

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

/linux-4.1.27/Documentation/arm/
Dkernel_mode_neon.txt6 * Use only NEON instructions, or VFP instructions that don't rely on support
18 It is possible to use NEON instructions (and in some cases, VFP instructions) in
19 code that runs in kernel mode. However, for performance reasons, the NEON/VFP
23 may call schedule()], as NEON or VFP instructions will be executed in a
29 The NEON/VFP register file is managed using lazy preserve (on UP systems) and
32 contending for the NEON/VFP unit (or, in the SMP case, when a task migrates to
33 another core). Lazy restore is implemented by disabling the NEON/VFP unit after
34 every context switch, resulting in a trap when subsequently a NEON/VFP
38 Any use of the NEON/VFP unit in kernel mode should not interfere with this, so
39 it is required to do an 'eager' preserve of the NEON/VFP register file, and
[all …]
D00-INDEX27 VFP/
/linux-4.1.27/arch/arm/vfp/
Dentry.S18 @ VFP entry point.
32 ldr pc, [r4] @ call VFP entry point
44 @ This code is called if the VFP does not exist. It needs to flag the
45 @ failure to the VFP initialisation code.
Dvfphw.S72 @ VFP hardware support entry point.
89 VFPFMRX r1, FPEXC @ Is the VFP enabled?
92 bne look_for_VFP_exceptions @ VFP is already enabled
105 @ On UP, we lazily save the VFP context. As a different
106 @ thread wants ownership of the VFP hardware, save the old
109 VFPFMXR FPEXC, r5 @ enable VFP, disable any pending
/linux-4.1.27/arch/arm/include/asm/
Dvfpmacros.h10 @ Macros to allow building with old toolkits (with no VFP support) in toolkits()
19 @ read all the working registers back into the VFP in toolkits()
34 VFPFMRX \tmp, MVFR0 @ Media and VFP Feature Register 0
43 @ write all the working registers out of the VFP
58 VFPFMRX \tmp, MVFR0 @ Media and VFP Feature Register 0
/linux-4.1.27/Documentation/arm/VFP/
Drelease-notes.txt1 Release notes for Linux Kernel VFP support code
7 This is the first release of the Linux Kernel VFP support code. It
8 provides support for the exceptions bounced from VFP hardware found
/linux-4.1.27/arch/arm/kvm/
Dinterrupts.S483 @ NEON/VFP used. Turn on VFP access.
486 @ Switch VFP/NEON hardware state to the guest's
Dinterrupts_head.S21 @ Make sure VFP is enabled so we can touch the registers.
26 tst r2, #FPEXC_EX @ Check for VFP Subarchitecture
36 VFPFSTMIA \vfp_base, r6 @ Save VFP registers
42 VFPFLDMIA \vfp_base, r6 @ Load VFP registers
46 tst r2, #FPEXC_EX @ Check for VFP Subarchitecture
599 * If a label is specified with vmexit, it is branched to if VFP wasn't
/linux-4.1.27/include/video/
Dkyro.h25 u32 VFP; /* Ver Front Porch */ member
/linux-4.1.27/drivers/video/fbdev/kyro/
Dfbdev.c464 var->lower_margin = par->VFP; in kyrofb_check_var()
514 par->VFP = info->var.lower_margin; in kyrofb_set_par()
517 par->VTot = par->YRES + par->VBP + par->VST + par->VFP; in kyrofb_set_par()
/linux-4.1.27/arch/arm/mach-omap2/
DKconfig112 select VFP
/linux-4.1.27/arch/arm/
DKconfig2046 config VFP config
2047 bool "VFP-format floating point maths"
2050 Say Y to include VFP support code in the kernel. This is needed
2051 if your hardware includes a VFP unit.
2053 Please see <file:Documentation/arm/VFP/release-notes.txt> for
2056 Say N if your target does not have VFP hardware.
2060 depends on VFP
/linux-4.1.27/arch/arm64/
DKconfig746 the user helper functions, VFP support and the ptrace interface are
/linux-4.1.27/drivers/eisa/
Deisa.ids687 ICU06B0 "Zoom VFP V.32bis FAX Modem"
/linux-4.1.27/Documentation/virtual/kvm/
Dapi.txt2013 ARM 32-bit VFP control registers have the following id bit patterns:
/linux-4.1.27/
DMAINTAINERS1582 ARM/VFP SUPPORT