Home
last modified time | relevance | path

Searched refs:M3 (Results 1 – 18 of 18) sorted by relevance

/linux-4.4.14/arch/sparc/kernel/
Dtraps_64.c1067 #define M3 145 macro
1071 /*00*/NONE, C0, C1, M2, C2, M2, M3, 47, C3, M2, M2, 53, M2, 41, 29, M,
1076 /*05*/M2, 44, 28, M2, M, M2, M2, 52, 68, M2, M2, 62, M2, M3, M3, M4,
1077 /*06*/M2, 26, 106, M2, 64, M, M2, 2, 120, M, M2, M3, M, M3, M3, M4,
1078 /*07*/116, M2, M2, M3, M2, M3, M, M4, M2, 58, 54, M2, M, M4, M4, M3,
1080 /*09*/M, 27, M, M, 99, M, M, 3, 114, M2, M2, 20, M2, M3, M3, M,
1081 /*0a*/M2, 23, 113, M2, 112, M2, M, 51, 95, M, M2, M3, M2, M3, M3, M2,
1082 /*0b*/103, M, M2, M3, M2, M3, M3, M4, M2, 48, M, M, 73, M2, M, M3,
1083 /*0c*/M2, 22, 110, M2, 109, M2, M, 9, 108, M2, M, M3, M2, M3, M3, M,
1084 /*0d*/102, M2, M, M, M2, M3, M3, M, M2, M3, M3, M2, M, M4, M, M3,
[all …]
/linux-4.4.14/Documentation/devicetree/bindings/remoteproc/
Dwkup_m3_rproc.txt1 TI Wakeup M3 Remoteproc Driver
4 The TI AM33xx and AM43xx family of devices use a small Cortex M3 co-processor
5 (commonly referred to as Wakeup M3 or CM3) to help with various low power tasks
10 Wkup M3 Device Node:
12 A wkup_m3 device node is used to represent the Wakeup M3 processor instance
/linux-4.4.14/drivers/remoteproc/
DKconfig22 Say y here to support OMAP's remote processors (dual M3
45 tristate "AMx3xx Wakeup M3 remoteproc support"
49 Say y here to support Wakeup M3 remote processor on TI AM33xx
/linux-4.4.14/arch/xtensa/variants/dc232b/include/variant/
Dtie-asm.h54 rsr \at2, M3
97 wsr \at2, M3
/linux-4.4.14/arch/xtensa/variants/de212/include/variant/
Dtie-asm.h101 rsr.M3 \at1 // MAC16 option
156 wsr.M3 \at1 // MAC16 option
/linux-4.4.14/arch/blackfin/kernel/cplb-mpu/
DMakefile9 -ffixed-M0 -ffixed-M1 -ffixed-M2 -ffixed-M3 \
/linux-4.4.14/arch/blackfin/kernel/cplb-nompu/
DMakefile9 -ffixed-M0 -ffixed-M1 -ffixed-M2 -ffixed-M3 \
/linux-4.4.14/arch/xtensa/variants/dc233c/include/variant/
Dtie-asm.h110 rsr \at1, M3 // MAC16 option
175 wsr \at1, M3 // MAC16 option
/linux-4.4.14/arch/arm/mach-vexpress/
DKconfig69 between the dual cluster test-chip and the M3 microcontroller that
/linux-4.4.14/arch/arm/boot/dts/
Dsun7i-a20-m3.dts54 model = "Mele M3";
/linux-4.4.14/Documentation/
Dhwspinlock.txt9 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
11 is usually running Linux and the slave processors, the M3 and the DSP,
21 remote M3 and/or C64x+ slave processors (by an IPC subsystem called Syslink).
Dremoteproc.txt9 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
11 configuration, and each of the other three cores (two M3 cores and a DSP)
Drpmsg.txt14 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
16 and each of the other three cores (two M3 cores and a DSP) is running
/linux-4.4.14/arch/blackfin/mach-common/
Ddpmc_modes.S293 R0 = M3;
/linux-4.4.14/Documentation/fb/
Dmodedb.txt102 example: .48M3-R - 800x600 with reduced blanking
/linux-4.4.14/arch/blackfin/include/asm/
Ddpmc.h121 M3 = R0;
/linux-4.4.14/Documentation/sound/alsa/
Dcompress_offload.txt56 stereo. Likewise WMA10 level M3 may require too much memory and cpu
/linux-4.4.14/arch/arm/
DKconfig336 bool "ARMv7-M based platforms (Cortex-M0/M3/M4)"
959 Support for NXP's LPC18xx Cortex-M3 and LPC43xx Cortex-M4