diff options
author | Alan Previn <alan.previn.teres.alexis@intel.com> | 2023-02-24 03:17:58 +0300 |
---|---|---|
committer | John Harrison <John.C.Harrison@Intel.com> | 2023-03-03 04:13:59 +0300 |
commit | 0591bdad58c4b83a286872305e748bfd77d16d28 (patch) | |
tree | 2a9fbc367267b1cade0403c6bf58307eff41fa22 /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 3cba09a6ac86ea1d456909626eb2685596c07822 (diff) | |
download | linux-0591bdad58c4b83a286872305e748bfd77d16d28.tar.xz |
drm/i915/gsc: Fix the Driver-FLR completion
The Driver-FLR flow may inadvertently exit early before the full
completion of the re-init of the internal HW state if we only poll
GU_DEBUG Bit31 (polling for it to toggle from 0 -> 1). Instead
we need a two-step completion wait-for-completion flow that also
involves GU_CNTL. See the patch and new code comments for detail.
This is new direction from HW architecture folks.
v2: - Add error message for the teardown timeout (Anshuman)
- Don't duplicate code in comments (Jani)
v3: - Add get/put runtime-pm for this function. Though
not functionally required during unload, its so the uncore
doesn't complain.
v4: - Remove the get/put runtime-pm - that was for a prior
version of this patch (not needed for drm-managed callback).
- Remove the fixes tag since this is only for MTL and MTL
still needs force probe (Daniele).
- Bit 31 of GU_CNTL should be DRIVERFLR instead of
DRIVERFLR_STATUS (Daniele).
Signed-off-by: Alan Previn <alan.previn.teres.alexis@intel.com>
Tested-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
Reviewed-by: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
Signed-off-by: John Harrison <John.C.Harrison@Intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20230224001758.544817-1-alan.previn.teres.alexis@intel.com
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions