Lines Matching full:r5f

3  * TI K3 R5F (MCU) Remote Processor driver
71  * struct k3_r5_cluster - K3 R5F Cluster structure
168 		dev_err(dev, "K3 R5F rproc %s crashed\n", name);  in k3_r5_rproc_mbox_callback()
352  * The R5F cores have controls for both a reset and a halt/run. The code
393  * or Split mode). This completes the second portion of powering down the R5F
415  * The R5F start sequence includes two different operations
416  * 1. Configure the boot vector for R5F core(s)
417  * 2. Unhalt/Run the R5F core(s)
465 	dev_dbg(dev, "booting R5F core using boot addr = 0x%x\n", boot_addr);  in k3_r5_rproc_start()
499  * The R5F stop function includes the following operations
500  * 1. Halt R5F core(s)
509  * Note that the R5F halt operation in general is not effective when the R5F
631  * Internal R5F Core configuration
635  * oriented Split mode. Each R5F core has a number of settings to either
636  * enable/disable each of the TCMs, control which TCM appears at the R5F core's
641  * This function is used to pre-configure these settings for each R5F core, and
653  * The function behavior is different based on the cluster mode. The R5F cores
813 		 * RAT is programmable only by the R5F cores. Support for RAT  in k3_r5_reserved_mem_init()
815 		 * supported. The absence of MMUs implies that the R5F device  in k3_r5_reserved_mem_init()
1021 		 * The R5F cores can place ATCM & BTCM anywhere in its address  in k3_r5_core_of_get_internal_memories()
1242  * for the child R5F devices
1336 		dev_err(dev, "MCU cluster requires both R5F cores to be enabled, num_cores = %d\n",  in k3_r5_probe()
1396 MODULE_DESCRIPTION("TI K3 R5F remote processor driver");