Lines Matching full:coherent

25  * cps_nc_entry_fn - type of a generated non-coherent state entry function
27  * @nc_ready_count: pointer to a non-coherent mapping of the core ready_count
29  * The code entering & exiting non-coherent states is generated at runtime
41  * The entry point of the generated non-coherent idle state entry/exit
51  * Indicates the number of coupled VPEs ready to operate in a non-coherent
154 	/* Indicate that this CPU might not be coherent */  in cps_pm_enter_state()
158 	/* Create a non-coherent mapping of the core ready_count */  in cps_pm_enter_state()
172 	/* Remove the non-coherent mapping of ready_count */  in cps_pm_enter_state()
175 	/* Indicate that this CPU is definitely coherent */  in cps_pm_enter_state()
179 	 * If this VPE is the first to leave the non-coherent wait state then  in cps_pm_enter_state()
614 	/* The core is coherent, time to return to C code */  in cps_gen_entry_code()
700 	/* A CM is required for all non-coherent states */  in cps_pm_init()
702 		pr_warn("pm-cps: no CM, non-coherent states unavailable\n");  in cps_pm_init()
708 	 * non-coherent core then the VPE may end up processing interrupts  in cps_pm_init()
709 	 * whilst non-coherent. That would be bad.  in cps_pm_init()
714 		pr_warn("pm-cps: non-coherent wait unavailable\n");  in cps_pm_init()