Searched refs:forcewake (Results 1 - 7 of 7) sorted by relevance
/linux-4.4.14/drivers/gpu/drm/i915/ |
H A D | intel_uncore.c | 91 DRM_ERROR("%s: timed out waiting for forcewake ack to clear.\n", fw_domain_wait_ack_clear() 107 DRM_ERROR("%s: timed out waiting for forcewake ack request.\n", fw_domain_wait_ack() 274 * with forcewake not set correctly. Wait until all pending intel_uncore_forcewake_reset() 298 DRM_ERROR("Timed out waiting for forcewake timers to finish\n"); 317 if (restore) { /* If reset with a user forcewake, try to restore */ 406 * intel_uncore_forcewake_get - grab forcewake domain references 408 * @fw_domains: forcewake domains to get reference on 410 * This function can be used get GT's forcewake domain references. 411 * Normal register access will handle the forcewake domains automatically. 413 * forcewake domains this function should be called at the beginning of the 434 * intel_uncore_forcewake_get__locked - grab forcewake domain references 436 * @fw_domains: forcewake domains to get reference on 476 * intel_uncore_forcewake_put - release a forcewake domain reference 478 * @fw_domains: forcewake domains to put references 497 * intel_uncore_forcewake_put__locked - grab forcewake domain references 499 * @fw_domains: forcewake domains to get reference on 1145 /* IVB configs may use multi-threaded forcewake */ intel_uncore_fw_domains_init() 1148 * MT forcewake, and if the device is in RC6, then intel_uncore_fw_domains_init() 1152 * forcewake being disabled. intel_uncore_fw_domains_init() 1179 DRM_INFO("No MT forcewake available on Ivybridge, this can result in issues\n"); intel_uncore_fw_domains_init() 1463 * for fifo space for the write or forcewake the chip for gen6_do_reset()
|
H A D | i915_gpu_error.c | 378 err_printf(m, "FORCEWAKE: 0x%08x\n", error->forcewake); i915_error_state_to_str() 1184 error->forcewake = I915_READ(FORCEWAKE_VLV); i915_capture_reg_state() 1196 error->forcewake = I915_READ(FORCEWAKE); i915_capture_reg_state() 1203 error->forcewake = I915_READ(FORCEWAKE_MT); i915_capture_reg_state()
|
H A D | intel_pm.c | 4606 /* we're doing forcewake before Disabling RC6, valleyview_disable_rps() 4777 /* 1b: Get forcewake during program sequence. Although the driver gen9_enable_rc6() 4778 * hasn't enabled a state yet where we need forcewake, BIOS may have.*/ gen9_enable_rc6() 4849 /* 1c & 1d: Get forcewake during program sequence. Although the driver gen8_enable_rps() 4850 * hasn't enabled a state yet where we need forcewake, BIOS may have.*/ gen8_enable_rps() 5458 /* 1a & 1b: Get forcewake during program sequence. Although the driver cherryview_enable_rps() 5459 * hasn't enabled a state yet where we need forcewake, BIOS may have.*/ cherryview_enable_rps()
|
H A D | i915_debugfs.c | 1518 "holds a forcewake reference \n"); gen6_drpc_info() 1520 /* NB: we cannot use forcewake, else we read the wrong values */ gen6_drpc_info()
|
H A D | i915_drv.h | 510 u32 forcewake; member in struct:drm_i915_error_state 3452 * criticial sections inside IRQ handlers where forcewake is explicitly
|
H A D | i915_irq.c | 720 /* raw reads, only for fast reads of display block, no need for forcewake etc. */ 1585 /* The RPS events need forcewake, so we add them to a work queue and mask their
|
H A D | i915_gem.c | 4920 * we hold the forcewake during initialisation these problems i915_gem_init()
|
Completed in 334 milliseconds