Home
last modified time | relevance | path

Searched full:core1 (Results 1 – 25 of 148) sorted by relevance

123456

/Linux-v6.6/Documentation/devicetree/bindings/media/
Dqcom,sdm845-venus.yaml64 video-core1:
94 - video-core1
124 video-core1 {
Dqcom,sdm845-venus-v2.yaml67 video-core1:
84 - video-core1
119 video-core1 {
/Linux-v6.6/arch/powerpc/boot/dts/fsl/
Dmpc8572ds_camp_core1.dts3 * MPC8572 DS Core1 Device Tree Source in CAMP mode.
7 * This dts allows core1 to have l2, dma2, eth2, eth3, pci2, msi.
9 * Please note to add "-b 1" for core1's dts compiling.
Dp1020rdb-pc_camp_core1.dts3 * P1020 RDB-PC Core1 Device Tree Source in CAMP mode.
7 * This dts allows core1 to have l2, eth0, crypto.
9 * Please note to add "-b 1" for core1's dts compiling.
/Linux-v6.6/arch/arm/boot/dts/intel/axm/
Daxm5516-cpus.dtsi18 core1 {
32 core1 {
46 core1 {
60 core1 {
/Linux-v6.6/arch/arm64/boot/dts/amd/
Damd-seattle-cpus.dtsi13 core1 {
21 core1 {
29 core1 {
37 core1 {
/Linux-v6.6/Documentation/devicetree/bindings/gpu/
Darm,mali-bifrost.yaml184 - const: core1
207 - const: core1
225 - const: core1
241 - const: core1
/Linux-v6.6/Documentation/devicetree/bindings/cpu/
Dcpu-topology.txt203 core1 {
223 core1 {
244 core1 {
263 core1 {
416 core1 {
431 core1 {
510 core1 {
/Linux-v6.6/arch/arm64/boot/dts/hisilicon/
Dhip05.dtsi30 core1 {
44 core1 {
58 core1 {
72 core1 {
Dhip07.dtsi30 core1 {
45 core1 {
60 core1 {
75 core1 {
90 core1 {
105 core1 {
120 core1 {
135 core1 {
150 core1 {
165 core1 {
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/remoteproc/
Dti,k3-r5f-rproc.yaml22 Core1's TCMs as well.
145 # modes, and are mandatory for R5F Core1 _only_ in Split mode. They are unused for
146 # R5F Core1 in LockStep mode:
297 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
/Linux-v6.6/arch/arm64/boot/dts/amlogic/
Dmeson-g12b.dtsi22 core1 {
32 core1 {
Damlogic-t7.dtsi22 core1 {
37 core1 {
Dmeson-gxm.dtsi18 core1 {
33 core1 {
/Linux-v6.6/arch/arm64/boot/dts/ti/
Dk3-am654.dtsi20 core1 {
30 core1 {
Dk3-j784s4.dtsi33 core1 {
51 core1 {
275 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
Dk3-j721e-som-p0.dtsi330 mbox_mcu_r5fss0_core1: mbox-mcu-r5fss0-core1 {
345 mbox_main_r5fss0_core1: mbox-main-r5fss0-core1 {
360 mbox_main_r5fss1_core1: mbox-main-r5fss1-core1 {
Dk3-am642-tqma64xxl.dtsi129 mbox_main_r5fss0_core1: mbox-main-r5fss0-core1 {
143 mbox_main_r5fss1_core1: mbox-main-r5fss1-core1 {
Dk3-j7200.dtsi32 core1 {
147 <0x00 0x41400000 0x00 0x41400000 0x00 0x00020000>, /* MCU R5F Core1 */
/Linux-v6.6/drivers/remoteproc/
Dti_k3_r5_remoteproc.c530 * unhalt both the cores to start the execution - Core1 needs to be unhalted
532 * always in a higher power state that Core1 (implying Core1 needs to be started
557 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
595 * performed first on Core0 followed by Core1. The Split-mode requires that
596 * Core0 to be maintained always in a higher power state that Core1 (implying
597 * Core1 needs to be stopped first before Core0).
1062 * leveraging the Core1 TCMs as well in certain modes where they would have
1064 * AM64x SoCs). This is done by making a Core1 TCM visible immediately after the
1212 struct k3_r5_core *core, *core1; in k3_r5_cluster_rproc_init() local
1218 core1 = list_last_entry(&cluster->cores, struct k3_r5_core, elem); in k3_r5_cluster_rproc_init()
[all …]
/Linux-v6.6/arch/arm64/boot/dts/apple/
Dt6002.dtsi31 core1 {
40 core1 {
55 core1 {
Dt600x-common.dtsi23 core1 {
32 core1 {
47 core1 {
/Linux-v6.6/arch/arm/boot/dts/samsung/
Dexynos5422-cpus.dtsi29 core1 {
44 core1 {
Dexynos5420-cpus.dtsi30 core1 {
45 core1 {
/Linux-v6.6/arch/arm64/boot/dts/freescale/
Dimx8qm.dtsi28 vpu-core1 = &vpu_core1;
41 core1 {
56 core1 {

123456