✓ CI.checkpatch: success for drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP (rev2)

[Patchwork]

== Series Details ==

Series: drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP (rev2)
URL   : https://patchwork.freedesktop.org/series/135370/
State : success

== Summary ==

+ KERNEL=/kernel
+ git clone https://gitlab.freedesktop.org/drm/maintainer-tools mt
Cloning into 'mt'...
warning: redirecting to https://gitlab.freedesktop.org/drm/maintainer-tools.git/
+ git -C mt rev-list -n1 origin/master
51ce9f6cd981d42d7467409d7dbc559a450abc1e
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 9af9408dd2733552e80d12c52e38e9bd2a328ea1
Author: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
Date:   Thu Jun 27 16:51:05 2024 -0700

    drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP
    
    Per client engine utilization uses RING_TIMESTAMP to return
    drm-total-cycles to the user. Current code uses XE_FW_GT to read this
    register on the first available engine in a GT. When testing on DG2, it
    is observed that this value is 0 when running test on some engines. To
    resolve that, get the hwe domain specific FW for reading the engine
    timestamp.
    
    v2:
    - update commit message
    - use domain specific FW (Matt)
    
    v3:
    - Drop check for hwe in the helper (Matt, Michal)
    
    v4:
    - checkpatch fixes
    
    v5: Rebase
    
    Fixes: 188ced1e0ff8 ("drm/xe/client: Print runtime to fdinfo")
    Signed-off-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa at intel.com>
    Reviewed-by: Matt Roper <matthew.d.roper at intel.com>
    Reviewed-by: Lucas De Marchi <lucas.demarchi at intel.com>
+ /mt/dim checkpatch 136e579ec9cc0e020af2b9adee34798fdb748172 drm-intel
9af9408dd273 drm/xe: Get hwe domain specific FW to read RING_TIMESTAMP