Searched full:core1 (Results 1 – 25 of 219) sorted by relevance
123456789
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/media/ |
| D | qcom,sdm845-venus-v2.yaml | 67 video-core1:
84 - video-core1
119 video-core1 {
|
| D | qcom,sdm845-venus.yaml | 64 video-core1:
94 - video-core1
124 video-core1 {
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/media/ |
| D | qcom,sdm845-venus-v2.yaml | 71 video-core1:
108 - video-core1
143 video-core1 {
|
| D | qcom,sdm845-venus.yaml | 71 video-core1:
121 - video-core1
151 video-core1 {
|
| /kernel/linux/linux-6.6/arch/powerpc/boot/dts/fsl/ |
| D | mpc8572ds_camp_core1.dts | 3 * 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.
|
| D | p1020rdb-pc_camp_core1.dts | 3 * 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.
|
| /kernel/linux/linux-5.10/arch/powerpc/boot/dts/fsl/ |
| D | p1020rdb-pc_camp_core1.dts | 3 * 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.
|
| D | mpc8572ds_camp_core1.dts | 3 * 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.
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | axm5516-cpus.dtsi | 18 core1 {
32 core1 {
46 core1 {
60 core1 {
|
| /kernel/linux/linux-6.6/arch/arm/boot/dts/intel/axm/ |
| D | axm5516-cpus.dtsi | 18 core1 {
32 core1 {
46 core1 {
60 core1 {
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/amd/ |
| D | amd-seattle-cpus.dtsi | 13 core1 {
21 core1 {
29 core1 {
37 core1 {
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/gpu/ |
| D | arm,mali-bifrost.yaml | 184 - const: core1
207 - const: core1
225 - const: core1
241 - const: core1
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 203 core1 {
223 core1 {
244 core1 {
263 core1 {
416 core1 {
431 core1 {
510 core1 {
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 203 core1 {
223 core1 {
244 core1 {
263 core1 {
416 core1 {
431 core1 {
510 core1 {
|
| /kernel/linux/linux-6.6/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 531 * unhalt both the cores to start the execution - Core1 needs to be unhalted
533 * always in a higher power state that Core1 (implying Core1 needs to be started
554 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
602 * performed first on Core0 followed by Core1. The Split-mode requires that
603 * Core0 to be maintained always in a higher power state that Core1 (implying
604 * Core1 needs to be stopped first before Core0).
624 struct k3_r5_core *core1, *core = kproc->core; in k3_r5_rproc_stop() local
638 core1 = list_last_entry(&cluster->cores, struct k3_r5_core, in k3_r5_rproc_stop()
640 if (core != core1 && core1->rproc->state != RPROC_OFFLINE) { in k3_r5_rproc_stop()
1058 * leveraging the Core1 TCMs as well in certain modes where they would have
[all …]
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/hisilicon/ |
| D | hip05.dtsi | 30 core1 {
44 core1 {
58 core1 {
72 core1 {
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/hisilicon/ |
| D | hip05.dtsi | 30 core1 {
44 core1 {
58 core1 {
72 core1 {
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/ti/ |
| D | k3-j721e-som-p0.dtsi | 126 mbox_mcu_r5fss0_core1: mbox-mcu-r5fss0-core1 {
140 mbox_main_r5fss0_core1: mbox-main-r5fss0-core1 {
154 mbox_main_r5fss1_core1: mbox-main-r5fss1-core1 {
|
| D | k3-am654.dtsi | 20 core1 {
30 core1 {
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/amlogic/ |
| D | meson-g12b.dtsi | 22 core1 {
32 core1 {
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/remoteproc/ |
| D | ti,k3-r5f-rproc.yaml | 22 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 */
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/amlogic/ |
| D | meson-g12b.dtsi | 22 core1 {
32 core1 {
|
| D | amlogic-t7.dtsi | 22 core1 {
37 core1 {
|
| /kernel/linux/linux-6.6/arch/arm64/boot/dts/ti/ |
| D | k3-am654.dtsi | 20 core1 {
30 core1 {
|
| /kernel/linux/linux-5.10/drivers/remoteproc/ |
| D | ti_k3_r5_remoteproc.c | 421 * unhalt both the cores to start the execution - Core1 needs to be unhalted
423 * always in a higher power state that Core1 (implying Core1 needs to be started
467 /* boot vector need not be programmed for Core1 in LockStep mode */ in k3_r5_rproc_start()
505 * performed first on Core0 followed by Core1. The Split-mode requires that
506 * Core0 to be maintained always in a higher power state that Core1 (implying
507 * Core1 needs to be stopped first before Core0).
863 struct k3_r5_core *core, *core1; in k3_r5_cluster_rproc_init() local
869 core1 = list_last_entry(&cluster->cores, struct k3_r5_core, elem); in k3_r5_cluster_rproc_init()
933 /* undo core0 upon any failures on core1 in split-mode */ in k3_r5_cluster_rproc_init()
934 if (cluster->mode == CLUSTER_MODE_SPLIT && core == core1) { in k3_r5_cluster_rproc_init()
[all …]
|
123456789