✓ CI.checkpatch: success for drm/xe: Eliminate usage of TIMESTAMP_OVERRIDE

[Patchwork]

== Series Details ==

Series: drm/xe: Eliminate usage of TIMESTAMP_OVERRIDE
URL   : https://patchwork.freedesktop.org/series/145437/
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
22f9cda3436b4fe965b5c5f31d2f2c1bcb483189
+ cd /kernel
+ git config --global --add safe.directory /kernel
+ git log -n1
commit 6758b8fc825d74a5ccbaf463654ba090e2dd8736
Author: Matt Roper <matthew.d.roper at intel.com>
Date:   Tue Feb 25 14:49:09 2025 -0800

    drm/xe: Eliminate usage of TIMESTAMP_OVERRIDE
    
    Recent discussions with the hardware architects have revealed that
    the TIMESTAMP_OVERRIDE register is never expected to hold a valid/useful
    value on production hardware.  That register would only get used by
    hardware workarounds (although there are none that use it today) or
    during early internal hardware testing.
    
    Due to lack of documentation it's not clear exactly what the driver
    should be doing if CTC_MODE[0] is set (or even whether that's a setting
    that would ever be encountered on real hardware), but it's definitely
    not what Xe and i915 have been doing.  So drop the incorrect code trying
    to use TIMESTAMP_REGISTER.  If the driver does encounter CTC_MODE[0] in
    the wild, we'll print a warning and just continue trying to use the
    crystal clock frequency since that's probably less incorrect than what
    we're doing today.
    
    Cc: Lucas De Marchi <lucas.demarchi at intel.com>
    Cc: Balasubramani Vivekanandan <balasubramani.vivekanandan at intel.com>
    Signed-off-by: Matt Roper <matthew.d.roper at intel.com>
+ /mt/dim checkpatch 533a24b8fa29455518aed9ac72209c834d814238 drm-intel
6758b8fc825d drm/xe: Eliminate usage of TIMESTAMP_OVERRIDE