Re: [Intel-gfx] [CI] drm/i915: Track hw reported context runtime

On 16/02/2020 00:06, Chris Wilson wrote: From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from w

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/dsb: Pre allocate and late cleanup of cmd buffer (rev2)

== Series Details == Series: drm/i915/dsb: Pre allocate and late cleanup of cmd buffer (rev2) URL : https://patchwork.freedesktop.org/series/73036/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16543_full =

[Intel-gfx] [CI] drm/i915: Track hw reported context runtime

From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from where it can be easily read even if the cont

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track hw reported context runtime (rev3)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev3) URL : https://patchwork.freedesktop.org/series/73499/ State : warning == Summary == $ dim checkpatch origin/drm-tip 953502e2ee73 drm/i915: Track hw reported context runtime -:109: WARNING:LINE_SPACING: Missing a bl

Re: [Intel-gfx] kernel 5.5.4: BUG: kernel NULL pointer dereference, address: 000000000000000

On 2/16/20 4:26 AM, Hillf Danton wrote: > Looks like a stray lock counts for the above NULL dereference. Hi, the patch applied on top of 5.5.4 breaks the internal display now even in the boot phase. Gert just a black screen after few seconds, nothing in the logs except: Feb 16 11:21:57 t44 kernel

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Track hw reported context runtime (rev3)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev3) URL : https://patchwork.freedesktop.org/series/73499/ State : success == Summary == CI Bug Log - changes from CI_DRM_7948 -> Patchwork_16584 Summary ---

[Intel-gfx] [CI] drm/i915: Track hw reported context runtime

From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from where it can be easily read even if the cont

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Force state->modeset=true when distrust_bios_wm==true

== Series Details == Series: drm/i915: Force state->modeset=true when distrust_bios_wm==true URL : https://patchwork.freedesktop.org/series/73367/ State : success == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16544_full ==

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track hw reported context runtime (rev4)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev4) URL : https://patchwork.freedesktop.org/series/73499/ State : warning == Summary == $ dim checkpatch origin/drm-tip e134ee9aa337 drm/i915: Track hw reported context runtime -:109: WARNING:LINE_SPACING: Missing a bl

[Intel-gfx] [CI] drm/i915: Track hw reported context runtime

From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from where it can be easily read even if the cont

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Track hw reported context runtime (rev4)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev4) URL : https://patchwork.freedesktop.org/series/73499/ State : success == Summary == CI Bug Log - changes from CI_DRM_7948 -> Patchwork_16585 Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track hw reported context runtime (rev5)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev5) URL : https://patchwork.freedesktop.org/series/73499/ State : warning == Summary == $ dim checkpatch origin/drm-tip 5da4eb1bc1fd drm/i915: Track hw reported context runtime -:109: WARNING:LINE_SPACING: Missing a bl

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Track hw reported context runtime (rev5)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev5) URL : https://patchwork.freedesktop.org/series/73499/ State : success == Summary == CI Bug Log - changes from CI_DRM_7948 -> Patchwork_16586 Summary ---

[Intel-gfx] [CI] drm/i915: Track hw reported context runtime

From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from where it can be easily read even if the cont

[Intel-gfx] [CI] drm/i915: Track hw reported context runtime

From: Tvrtko Ursulin GPU saves accumulated context runtime (in CS timestamp units) in PPHWSP which will be useful for us in cases when we are not able to track context busyness ourselves (like with GuC). Keep a copy of this in struct intel_context from where it can be easily read even if the cont

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track hw reported context runtime (rev6)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev6) URL : https://patchwork.freedesktop.org/series/73499/ State : warning == Summary == $ dim checkpatch origin/drm-tip 284fafeb344b drm/i915: Track hw reported context runtime -:109: WARNING:LINE_SPACING: Missing a bl

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: Ensure no conflicts with BIOS when updating Dbuf

== Series Details == Series: drm/i915: Ensure no conflicts with BIOS when updating Dbuf URL : https://patchwork.freedesktop.org/series/73369/ State : success == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16545_full S

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Track hw reported context runtime (rev6)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev6) URL : https://patchwork.freedesktop.org/series/73499/ State : success == Summary == CI Bug Log - changes from CI_DRM_7948 -> Patchwork_16587 Summary ---

[Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Track hw reported context runtime (rev7)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev7) URL : https://patchwork.freedesktop.org/series/73499/ State : warning == Summary == $ dim checkpatch origin/drm-tip 6b2debda1baa drm/i915: Track hw reported context runtime -:109: WARNING:LINE_SPACING: Missing a bl

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Track hw reported context runtime (rev7)

== Series Details == Series: drm/i915: Track hw reported context runtime (rev7) URL : https://patchwork.freedesktop.org/series/73499/ State : success == Summary == CI Bug Log - changes from CI_DRM_7949 -> Patchwork_16588 Summary ---

[Intel-gfx] [PATCH] drm/i915/gt: Refactor l3cc/mocs availability

On dgfx, we only use l3cc and not mocs, but we share the table of register definitions with Tigerlake (which includes the mocs). This confuses our selftest that verifies that the registers do contain the values in our tables after various events (idling, reset, activity etc). When constructing the

[Intel-gfx] [PATCH] drm/i915: Avoid potential division-by-zero in computing CS timestamp period

Since we use a HW readback or estimation of the CS timestamp frequency, sometimes it may result in 0. Avoid the division-by-zero in computing its reciprocal, the timestamp period. Signed-off-by: Chris Wilson --- drivers/gpu/drm/i915/intel_device_info.c | 18 +++--- 1 file changed, 11

[Intel-gfx] [PATCH] drm/i915: Read rawclk_freq earlier

Read the rawclk_freq during runtime info probing, prior to its first use in computing the CS timestamp frequency. Then store it in the runtime info, and include it in the debug printouts. Closes: https://gitlab.freedesktop.org/drm/intel/issues/834 Signed-off-by: Chris Wilson --- drivers/gpu/drm/

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/selftests: Fix selftest_mocs for DGFX (rev3)

== Series Details == Series: drm/i915/selftests: Fix selftest_mocs for DGFX (rev3) URL : https://patchwork.freedesktop.org/series/73387/ State : success == Summary == CI Bug Log - changes from CI_DRM_7950 -> Patchwork_16589 Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Avoid potential division-by-zero in computing CS timestamp period

== Series Details == Series: drm/i915: Avoid potential division-by-zero in computing CS timestamp period URL : https://patchwork.freedesktop.org/series/73506/ State : success == Summary == CI Bug Log - changes from CI_DRM_7950 -> Patchwork_16590 ===

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Read rawclk_freq earlier

== Series Details == Series: drm/i915: Read rawclk_freq earlier URL : https://patchwork.freedesktop.org/series/73507/ State : success == Summary == CI Bug Log - changes from CI_DRM_7950 -> Patchwork_16591 Summary --- **SUCCESS** N

[Intel-gfx] ✓ Fi.CI.IGT: success for series starting with [1/2] MAINTAINERS: Update drm/i915 bug filing URL

== Series Details == Series: series starting with [1/2] MAINTAINERS: Update drm/i915 bug filing URL URL : https://patchwork.freedesktop.org/series/73371/ State : success == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16546_full ===

Re: [Intel-gfx] kernel 5.5.4: BUG: kernel NULL pointer dereference, address: 000000000000000

On 2/16/20 3:55 PM, Hillf Danton wrote: > > On Sun, 16 Feb 2020 11:33:02 +0100 Toralf Foerster wrote: >> On 2/16/20 4:26 AM, Hillf Danton wrote: >>> Looks like a stray lock counts for the above NULL dereference. >>> >> Hi, the patch applied on top of 5.5.4 breaks the internal display now even >>

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915: pfit/scaler rework prep stuff (rev2)

== Series Details == Series: drm/i915: pfit/scaler rework prep stuff (rev2) URL : https://patchwork.freedesktop.org/series/68409/ State : success == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16547_full Summary -

[Intel-gfx] ✓ Fi.CI.IGT: success for drm: Add support for DP 1.4 Compliance edid corruption test (rev6)

== Series Details == Series: drm: Add support for DP 1.4 Compliance edid corruption test (rev6) URL : https://patchwork.freedesktop.org/series/70530/ State : success == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16548_full ===

Re: [Intel-gfx] [PATCH v3 3/7] drm/exynos: Use drm_encoder_mask()

20. 2. 12. 오전 1:22에 Ville Syrjala 이(가) 쓴 글: > From: Ville Syrjälä > > Replace the hand rolled encoder bitmask thing with drm_encoder_mask() > > Cc: Inki Dae > Cc: Joonyoung Shim > Cc: Seung-Woo Kim > Cc: Kyungmin Park > Acked-by: Thomas Zimmermann > Signed-off-by: Ville Syrjälä Acked-by

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/tgl: Add Wa_1808121037 to tgl.

== Series Details == Series: drm/i915/tgl: Add Wa_1808121037 to tgl. URL : https://patchwork.freedesktop.org/series/73379/ State : failure == Summary == CI Bug Log - changes from CI_DRM_7926_full -> Patchwork_16550_full Summary --- *

Re: [Intel-gfx] [PATCH] Add support for Color encoding YCBCR_BT2020

> -Original Message- > From: Jani Nikula > Sent: Friday, February 14, 2020 4:56 PM > To: Kadiyala, Kishore ; intel- > g...@lists.freedesktop.org > Cc: Kadiyala, Kishore > Subject: Re: [Intel-gfx] [PATCH] Add support for Color encoding YCBCR_BT2020 > > On Fri, 14 Feb 2020, Kishore Kadi

Re: [Intel-gfx] [PATCH v2 5/7] drm/i915: Get first crtc instead of PIPE_A crtc

On 2020-02-11 at 22:55:30 +0530, Anshuman Gupta wrote: > intel_plane_fb_max_stride should return the max stride of > primary plane for first available pipe in intel device info > pipe_mask. > Similarly glk_force_audio_cdclk() should also use the first > available CRTC instead of pipe 'A' crtc to fo