messages from 2023-10-17 00:46:48 to 2023-10-19 11:40:40 UTC [more...]
[Intel-gfx] [PATCH v3 1/3] pwm: make it possible to apply pwm changes in atomic context
2023-10-19 10:51 UTC (3+ messages)
[Intel-gfx] [PULL] drm-misc-next
2023-10-19 11:40 UTC
[Intel-gfx] [CI] PR for new GuC v70.13.1
2023-10-19 11:39 UTC (3+ messages)
[Intel-gfx] [PATCH v3] drm/i915/display: Reset message bus after each read/write operation
2023-10-19 11:38 UTC (8+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/display: Reset message bus after each read/write operation (rev4)
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/display: Reset message bus after each read/write operation (rev5)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH v2] debugobjects: stop accessing objects after releasing spinlock
2023-10-19 10:31 UTC (3+ messages)
[Intel-gfx] [PATCH v4 0/2] display device info as a separate debugfs entry
2023-10-19 9:32 UTC (9+ messages)
` [Intel-gfx] [PATCH v4 1/2] drm/i915/display: debugfs entry to list display capabilities
` [Intel-gfx] [PATCH v4 2/2] drm/i915: remove display device info from i915 capabilities
` [Intel-gfx] ✗ Fi.CI.BUILD: warning for display device info as a separate debugfs entry (rev6)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH v2 0/9] drm/i915: Replace kmap_atomic() with kmap_local_page()
2023-10-19 9:02 UTC (10+ messages)
` [Intel-gfx] [PATCH v2 9/9] drm/i915: Use kmap_local_page() in gem/i915_gem_execbuffer.c
[Intel-gfx] [PATCH v2] drm/i915/mtl: Don't set PIPE_CONTROL_FLUSH_L3
2023-10-19 8:14 UTC (7+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/mtl: Don't set PIPE_CONTROL_FLUSH_L3 (rev5)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH 0/2] Cleanup a few functions in C10/C20 handling
2023-10-19 2:21 UTC (5+ messages)
` [Intel-gfx] [PATCH 1/2] drm/i915/display: Abstract C10/C20 pll hw readout
` [Intel-gfx] [PATCH 2/2] drm/i915/display: Abstract C10/C20 pll calculation
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Cleanup a few functions in C10/C20 handling
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH 0/2] drm/i915/lnl: Assign correct phys
2023-10-19 1:45 UTC (5+ messages)
` [Intel-gfx] [PATCH 1/2] drm/i915/lnl: Extend C10/C20 phy
` [Intel-gfx] [PATCH 2/2] drm/i915/lnl: Fix check for TC phy
` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/lnl: Assign correct phys
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH v7c 00/24] fix DRM_USE_DYNAMIC_DEBUG=y regression
2023-10-18 23:59 UTC (26+ messages)
` [Intel-gfx] [PATCH v7c 01/24] test-dyndbg: fixup CLASSMAP usage error
` [Intel-gfx] [PATCH v7c 02/24] dyndbg: reword "class unknown, " to "class:_UNKNOWN_"
` [Intel-gfx] [PATCH v7c 03/24] dyndbg: make ddebug_class_param union members same size
` [Intel-gfx] [PATCH v7c 04/24] dyndbg: replace classmap list with a vector
` [Intel-gfx] [PATCH v7c 05/24] dyndbg: ddebug_apply_class_bitmap - add module arg, select on it
` [Intel-gfx] [PATCH v7c 06/24] dyndbg: split param_set_dyndbg_classes to module/wrapper fns
` [Intel-gfx] [PATCH v7c 07/24] dyndbg: drop NUM_TYPE_ARRAY
` [Intel-gfx] [PATCH v7c 08/24] dyndbg: reduce verbose/debug clutter
` [Intel-gfx] [PATCH v7c 09/24] dyndbg: silence debugs with no-change updates
` [Intel-gfx] [PATCH v7c 10/24] dyndbg: tighten ddebug_class_name() 1st arg type
` [Intel-gfx] [PATCH v7c 11/24] dyndbg: tighten fn-sig of ddebug_apply_class_bitmap
` [Intel-gfx] [PATCH v7c 12/24] dyndbg: reduce verbose=3 messages in ddebug_add_module
` [Intel-gfx] [PATCH v7c 13/24] dyndbg-API: remove DD_CLASS_TYPE_(DISJOINT|LEVEL)_NAMES and code
` [Intel-gfx] [PATCH v7c 14/24] dyndbg-API: fix CONFIG_DRM_USE_DYNAMIC_DEBUG regression
` [Intel-gfx] [PATCH v7c 15/24] dyndbg: refactor ddebug_classparam_clamp_input
` [Intel-gfx] [PATCH v7c 16/24] dyndbg-API: promote DYNDBG_CLASSMAP_PARAM to API
` [Intel-gfx] [PATCH v7c 17/24] dyndbg-doc: add classmap info to howto
` [Intel-gfx] [PATCH v7c 18/24] dyndbg: reserve flag bit _DPRINTK_FLAGS_PREFIX_CACHED
` [Intel-gfx] [PATCH v7c 19/24] dyndbg: add _DPRINTK_FLAGS_INCL_LOOKUP
` [Intel-gfx] [PATCH v7c 20/24] dyndbg: refactor *dynamic_emit_prefix
` [Intel-gfx] [PATCH v7c 21/24] dyndbg: change WARN_ON to WARN_ON_ONCE
` [Intel-gfx] [PATCH v7c 22/24] drm: use correct ccflags-y spelling
` [Intel-gfx] [PATCH v7c 23/24] drm-drivers: DRM_CLASSMAP_USE in 2nd batch of drivers, helpers
` [Intel-gfx] [PATCH v7c 24/24] drm: restore CONFIG_DRM_USE_DYNAMIC_DEBUG un-BROKEN
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for fix DRM_USE_DYNAMIC_DEBUG=y regression (rev4)
[Intel-gfx] [PATCH 0/4] drm/i915/mst: MST modeset sequence fixes
2023-10-18 23:42 UTC (7+ messages)
` [Intel-gfx] [PATCH 1/4] drm/i915/mst: Swap TRANSCONF vs. FECSTALL_DIS_DPTSTREAM_DPTTG disable
` [Intel-gfx] [PATCH 2/4] drm/i915/mst: Disable transcoder before deleting the payload
` [Intel-gfx] [PATCH 3/4] drm/i915/mst: Clear ACT just before triggering payload allocation
` [Intel-gfx] [PATCH 4/4] drm/i915/mst: Always write CHICKEN_TRANS
` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/mst: MST modeset sequence fixes
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs
2023-10-18 23:17 UTC (2+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Add bigjoiner force enable option to debugfs (rev4)
[Intel-gfx] [PATCH] drm/i915/mtl: Add Wa_14019821291
2023-10-18 23:08 UTC (5+ messages)
` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for "
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH] drm/i915/mtl: Support HBR3 rate with C10 phy and eDP in MTL
2023-10-18 22:52 UTC (3+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for "
[Intel-gfx] [PATCH v3] drm/i915: Flush WC GGTT only on required platforms
2023-10-18 21:54 UTC (6+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Flush WC GGTT only on required platforms (rev9)
[Intel-gfx] [rft, PATCH v1 0/2] drm/i915/dsi: An attempt to get rid of IOSF GPIO on VLV
2023-10-18 21:23 UTC (7+ messages)
` [Intel-gfx] [PATCH v1 1/2] drm/i915/dsi: Extract common soc_gpio_exec() helper
` [Intel-gfx] [PATCH v1 2/2] drm/i915/dsi: Replace poking of VLV GPIOs behind the driver's back
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: An attempt to get rid of IOSF GPIO on VLV
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] PR for new GuC v70.13.1
2023-10-18 19:07 UTC
[Intel-gfx] [PATCH] drm/i915/display: Use dma_fence interfaces instead of i915_sw_fence
2023-10-18 17:59 UTC (8+ messages)
[Intel-gfx] [PATCH v5 0/3] Resolve suspend-resume racing with GuC destroy-context-worker
2023-10-18 16:15 UTC (3+ messages)
` [Intel-gfx] [PATCH v5 2/3] drm/i915/guc: Close deregister-context race against CT-loss
[Intel-gfx] [PATCH v12 0/4] Apply Wa_16018031267 / Wa_16018063123
2023-10-18 13:39 UTC (14+ messages)
` [Intel-gfx] [PATCH v12 1/4] drm/i915: Enable NULL PTE support for vm scratch
` [Intel-gfx] [PATCH v12 2/4] drm/i915: Reserve some kernel space per vm
` [Intel-gfx] [PATCH v12 3/4] drm/i915: Add WABB blit for Wa_16018031267 / Wa_16018063123
` [Intel-gfx] [PATCH v12 4/4] drm/i915: Set copy engine arbitration "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Apply Wa_16018031267 / Wa_16018063123 (rev5)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH v2] drm/i915: Prevent potential null-ptr-deref in engine_init_common
2023-10-18 11:38 UTC (4+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Prevent potential null-ptr-deref in engine_init_common (rev6)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH] drm/i915/mtl: Remove the 'force_probe' requirement for Meteor Lake
2023-10-18 4:38 UTC (2+ messages)
[Intel-gfx] [PATCH v17 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines
2023-10-18 4:18 UTC (21+ messages)
` [Intel-gfx] [PATCH v17 1/7] drm/i915: Add GuC TLB Invalidation device info flags
` [Intel-gfx] [PATCH v17 2/7] drm/i915/guc: Add CT size delay helper
` [Intel-gfx] [PATCH v17 3/7] drm/i915: Define and use GuC and CTB TLB invalidation routines
` [Intel-gfx] [PATCH v17 4/7] drm/i915: No TLB invalidation on suspended GT
` [Intel-gfx] [PATCH v17 5/7] drm/i915: No TLB invalidation on wedged GT
` [Intel-gfx] [PATCH v17 6/7] drm/i915/gt: Increase sleep in gt_tlb selftest sanitycheck
` [Intel-gfx] [PATCH v17 7/7] drm/i915: Enable GuC TLB invalidations for MTL
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] linux-next: manual merge of the drm-misc tree with the asm-generic tree
2023-10-18 1:46 UTC (2+ messages)
[Intel-gfx] [PATCH] drm/i915/quirk: Add quirk for devices with incorrect PWM frequency
2023-10-18 0:32 UTC (3+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH v3 0/1] display device info as a separate debugfs entry
2023-10-17 21:47 UTC (3+ messages)
` [Intel-gfx] [PATCH v3 1/1] drm/i915/display: debugfs entry to list display capabilities
` [Intel-gfx] ✗ Fi.CI.BAT: failure for display device info as a separate debugfs entry (rev5)
[Intel-gfx] [PATCH v2 0/2] display device info as a separate debugfs entry
2023-10-17 20:55 UTC (4+ messages)
` [Intel-gfx] [PATCH v2 1/2] drm/i915/display: debugfs entry to list display capabilities
` [Intel-gfx] [PATCH v2 2/2] drm/i915: remove display device info from i915 capabilities
[Intel-gfx] [PATCH] drm/i915/mtl: Don't set PIPE_CONTROL_FLUSH_L3
2023-10-17 18:42 UTC (9+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/mtl: Don't set PIPE_CONTROL_FLUSH_L3 (rev4)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH 0/4] drm/i915: DPLL code cleanups
2023-10-17 16:36 UTC (3+ messages)
` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: DPLL code cleanups (rev4)
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH v16 0/7] drm/i915: Define and use GuC and CTB TLB invalidation routines
2023-10-17 15:31 UTC (22+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev2)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev3)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✓ Fi.CI.BAT: success "
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev4)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev5)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev6)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev7)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Define and use GuC and CTB TLB invalidation routines (rev8)
` [Intel-gfx] ✗ Fi.CI.SPARSE: "
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH 00/10] drm/i915/spi: spi access for discrete graphics
2023-10-17 14:46 UTC (7+ messages)
` [Intel-gfx] [PATCH 06/10] drm/i915/spi: spi register with mtd
[Intel-gfx] [PATCH v1 0/2] display device info as a separate debugfs entry
2023-10-17 12:19 UTC (6+ messages)
` [Intel-gfx] [PATCH v1 1/2] drm/i915/display: display device info "
` [Intel-gfx] [PATCH v1 2/2] drm/i915: remove display device info from i915 capabilities
` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for display device info as a separate debugfs entry (rev3)
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH] drm/i915: Add bigjoiner force enable option to debugfs
2023-10-17 9:49 UTC (2+ messages)
[Intel-gfx] [PATCH v7 0/6] Panel replay phase1 implementation
2023-10-17 8:22 UTC (4+ messages)
` [Intel-gfx] [PATCH v7 4/6] drm/i915/panelreplay: Enable panel replay dpcd initialization for DP
[Intel-gfx] [PATCH] drm/i915/mtl: avoid stringop-overflow warning
2023-10-17 5:27 UTC (5+ messages)
` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for drm/i915/mtl: avoid stringop-overflow warning (rev3)
` [Intel-gfx] ✗ Fi.CI.BAT: failure "
[Intel-gfx] [PATCH] drm/i915/gvt: Optimize mmio_offset_compare() for efficiency
2023-10-17 5:00 UTC (3+ messages)
` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/gvt: Optimize mmio_offset_compare() for efficiency (rev3)
` [Intel-gfx] ✗ Fi.CI.IGT: failure "
[Intel-gfx] [PATCH] drm/i915: Move the g45 PEG band gap HPD workaround to the HPD code
2023-10-17 1:53 UTC (2+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915: Move the g45 PEG band gap HPD workaround to the HPD code (rev4)
[Intel-gfx] [PATCH] drm/i915/bios: Clamp VBT HDMI level shift on BDW
2023-10-17 1:18 UTC (2+ messages)
` [Intel-gfx] ✗ Fi.CI.BAT: failure for drm/i915/bios: Clamp VBT HDMI level shift on BDW (rev3)
page: next (older) | prev (newer) | latest
- recent:[subjects (threaded)|topics (new)|topics (active)]
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).