Home
last modified time | relevance | path

Searched full:multicore (Results 1 – 25 of 26) sorted by relevance

12

/freebsd/sys/contrib/device-tree/Bindings/arm/ti/
H A Dk3.txt1 Texas Instruments K3 Multicore SoC architecture device tree bindings
4 Platforms based on Texas Instruments K3 Multicore SoC architecture
10 Each device tree root node must specify which exact SoC in K3 Multicore SoC
H A Dk3.yaml7 title: Texas Instruments K3 Multicore SoC architecture
13 Platforms based on Texas Instruments K3 Multicore SoC architecture
/freebsd/sys/contrib/device-tree/Bindings/soc/ti/
H A Dk3-socinfo.yaml7 title: Texas Instruments K3 Multicore SoC platforms chipid module
14 Texas Instruments (ARM64) K3 Multicore SoC platforms chipid module is
/freebsd/sys/contrib/device-tree/Bindings/hwinfo/
H A Dti,k3-socinfo.yaml7 title: Texas Instruments K3 Multicore SoC platforms chipid module
14 Texas Instruments (ARM64) K3 Multicore SoC platforms chipid module is
/freebsd/sys/contrib/device-tree/Bindings/arm/
H A Darm-dsu-pmu.txt5 form a multicore cluster. The PMU enables to gather various statistics on
H A Darm,realview.yaml15 the earlier CPUs such as TrustZone and multicore (MPCore).
H A Darm,vexpress-juno.yaml15 multicore Cortex-A class systems. The Versatile Express family contains both
/freebsd/sys/contrib/device-tree/Bindings/perf/
H A Darm,dsu-pmu.yaml16 L3 memory system, control logic and external interfaces to form a multicore
/freebsd/sys/contrib/device-tree/Bindings/powerpc/fsl/
H A Dccf.txt6 that enables the implementation of coherent, multicore systems.
/freebsd/sys/arm/conf/
H A DNOTES15 options SMP # Nearly all v7 SoCs are multicore
/freebsd/contrib/llvm-project/lld/docs/MachO/
H A Dindex.rst15 - LLD is very fast. When you link a large program on a multicore
/freebsd/sys/dev/dpaa2/
H A Ddpaa2_swp_if.m39 * network interfaces, and hardware accelerators in a multicore SoC.
/freebsd/share/man/man4/
H A Dcpuctl.456 For multicore CPUs such a
/freebsd/contrib/llvm-project/lld/docs/
H A Dindex.rst21 - LLD is very fast. When you link a large program on a multicore
/freebsd/sys/contrib/ncsw/Peripherals/FM/MACSEC/
H A Dfm_macsec.h89 called from other modules. In a multicore environment, the other modules may
/freebsd/sys/contrib/device-tree/Bindings/
H A Dtrivial-devices.yaml98 # DA9053: flexible system level PMIC with multicore support
/freebsd/contrib/llvm-project/llvm/include/llvm/BinaryFormat/
H A DELF.h284 EM_TILE64 = 187, // Tilera TILE64 multicore architecture family
285 EM_TILEPRO = 188, // Tilera TILEPro multicore architecture family
288 EM_TILEGX = 191, // Tilera TILE-Gx multicore architecture family
/freebsd/contrib/llvm-project/llvm/lib/Target/PowerPC/
H A DPPCScheduleP7.td
/freebsd/contrib/llvm-project/llvm/lib/Target/RISCV/
H A DRISCVFeatures.td1122 "'XTHeadSync' (T-Head multicore synchronization instructions)">;
1125 "'XTHeadSync' (T-Head multicore synchronization instructions)">;
/freebsd/contrib/elftoolchain/common/
H A Delfdefinitions.h836 "Tilera TILE64 multicore architecture family") \
838 "Tilera TILEPro multicore architecture family") \
843 "Tilera TILE-Gx multicore architecture family") \
/freebsd/sys/x86/x86/
H A Didentcpu.c108 u_int cpu_procinfo2; /* Multicore info */
/freebsd/contrib/llvm-project/llvm/tools/llvm-readobj/
H A DELFDumper.cpp1267 ENUM_ENT(EM_TILE64, "Tilera TILE64 multicore architecture family"),
1268 ENUM_ENT(EM_TILEPRO, "Tilera TILEPro multicore architecture family"),
1271 ENUM_ENT(EM_TILEGX, "Tilera TILE-Gx multicore architecture family"),
/freebsd/sys/contrib/ncsw/Peripherals/FM/
H A Dfm_ncsw.c2481 /* for multicore environment: this depends on the in FmGetClockFreq()
/freebsd/sys/kern/
H A Dvfs_cache.c222 * multicore uses. This would *not* work for open(2) or other calls which need
/freebsd/share/misc/
H A Dpci_vendors6975 8888 Multicore DSP+ARM KeyStone II SOC
22249 a2d3 MT416842 BlueField multicore SoC family VF

12