Re: [Intel-gfx] [PATCH] ALSA: hda: fix general protection fault in azx_runtime_idle

On Fri, 12 Nov 2021 13:27:34 +0100, Kai Vehmanen wrote: > > Hi, > > On Fri, 12 Nov 2021, Takashi Iwai wrote: > > > On Thu, 11 Nov 2021 18:39:36 +0100, Kai Vehmanen wrote: > > > And later > > > [ 54.770701] Enabling runtime PM for inactive device (:00:1f.3) > > > with active children > >

[Intel-gfx] ✓ Fi.CI.IGT: success for drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2)

== Series Details == Series: drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2) URL : https://patchwork.freedesktop.org/series/96750/ State : success == Summary == CI Bug Log - changes from CI_DRM_10878_full -> Patchwork_21583_full

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2)

== Series Details == Series: drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2) URL : https://patchwork.freedesktop.org/series/96750/ State : success == Summary == CI Bug Log - changes from CI_DRM_10878 -> Patchwork_21583 Summary

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2)

== Series Details == Series: drm/i915/dsi: let HW maintain the HS-TRAIL timing (rev2) URL : https://patchwork.freedesktop.org/series/96750/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function

[Intel-gfx] [PATCH v2] drm/i915/dsi: let HW maintain the HS-TRAIL timing

This change is to avoid over-specification of the TEOT timing parameter, which is derived from software in current design. Supposed that THS-TRAIL and THS-EXIT have the minimum values, i.e., 60 and 100 in ns. If SW is overriding the HW default, the TEOT value becomes 150 ns, approximately

Re: [Intel-gfx] Can't drive 4K monitor at full resolution over DP

Thanks, Jani, here's the bug report: https://gitlab.freedesktop.org/drm/intel/-/issues/4531 On Sun, Nov 14, 2021 at 2:50 AM Saarinen, Jani wrote: > Hi Bryan. > Can you file new bug: > https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs > > Br, > > Jani Saarinen > Intel

[Intel-gfx] Commit a22c074fd1dd52a8b41dd6789220409b64093e9c broke Intel Corporation HD Graphics (rev 08)

[Now sent from a subscribed address] Hi, Upgrading an Acer Chromebook C740 from a stable 5.14.18 to a 5.15.2 kernel leads to a hang/crash very early during startup. With 5.15.2, the kernel fails before any video output and bootup continues to the recovery kernel. Bisecting points to commit

[Intel-gfx] ✗ Fi.CI.IGT: failure for drm/i915/ttm: Async migration (rev4)

== Series Details == Series: drm/i915/ttm: Async migration (rev4) URL : https://patchwork.freedesktop.org/series/96798/ State : failure == Summary == CI Bug Log - changes from CI_DRM_10878_full -> Patchwork_21582_full Summary ---

[Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915/ttm: Async migration (rev4)

== Series Details == Series: drm/i915/ttm: Async migration (rev4) URL : https://patchwork.freedesktop.org/series/96798/ State : success == Summary == CI Bug Log - changes from CI_DRM_10878 -> Patchwork_21582 Summary --- **SUCCESS**

[Intel-gfx] ✗ Fi.CI.DOCS: warning for drm/i915/ttm: Async migration (rev4)

== Series Details == Series: drm/i915/ttm: Async migration (rev4) URL : https://patchwork.freedesktop.org/series/96798/ State : warning == Summary == $ make htmldocs 2>&1 > /dev/null | grep i915 ./drivers/gpu/drm/i915/display/intel_fbc.c:635: warning: Excess function parameter 'i915'

[Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915/ttm: Async migration (rev4)

== Series Details == Series: drm/i915/ttm: Async migration (rev4) URL : https://patchwork.freedesktop.org/series/96798/ State : warning == Summary == $ dim sparse --fast origin/drm-tip Sparse version: v0.6.2 Fast mode used, each commit won't be checked separately. -

[Intel-gfx] [PATCH v3 6/6] drm/i915/ttm: Update i915_gem_obj_copy_ttm() to be asynchronous

Update the copy function i915_gem_obj_copy_ttm() to be asynchronous for future users and update the only current user to sync the objects as needed after this function. Signed-off-by: Thomas Hellström --- drivers/gpu/drm/i915/gem/i915_gem_ttm_move.c | 40 ++--

[Intel-gfx] [PATCH v3 5/6] drm/i915/ttm: Implement asynchronous TTM moves

Don't wait sync while migrating, but rather make the GPU blit await the dependencies and add a moving fence to the object. This also enables asynchronous VRAM management in that on eviction, rather than waiting for the moving fence to expire before freeing VRAM, it is freed immediately and the

[Intel-gfx] [PATCH v3 3/6] drm/i915/ttm: Move the i915_gem_obj_copy_ttm() function

Move the i915_gem_obj_copy_ttm() function to i915_gem_ttm_move.h. This will help keep a number of functions static when introducing async moves. Signed-off-by: Thomas Hellström --- drivers/gpu/drm/i915/gem/i915_gem_ttm.c | 47 --- drivers/gpu/drm/i915/gem/i915_gem_ttm.h |

[Intel-gfx] [PATCH v3 4/6] drm/i915/ttm: Break refcounting loops at device region unref time

There is an interesting refcounting loop: struct intel_memory_region has a struct ttm_resource_manager, ttm_resource_manager->move may hold a reference to i915_request, i915_request may hold a reference to intel_context, intel_context may hold a reference to drm_i915_gem_object,

[Intel-gfx] [PATCH v3 1/6] drm/i915: Add functions to set/get moving fence

From: Maarten Lankhorst We want to get rid of i915_vma tracking to simplify the code and lifetimes. Add a way to set/put the moving fence, in preparation for removing the tracking. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/i915/gem/i915_gem_object.c | 37 ++

[Intel-gfx] [PATCH v3 2/6] drm/i915: Add support for asynchronous moving fence waiting

From: Maarten Lankhorst For now, we will only allow async migration when TTM is used, so the paths we care about are related to TTM. The mmap path is handled by having the fence in ttm_bo->moving, when pinning, the binding only becomes available after the moving fence is signaled, and pinning a

[Intel-gfx] [PATCH v3 0/6] drm/i915/ttm: Async migration

This patch series deals with async migration and async vram management. It still leaves an important part out, which is async unbinding which will reduce latency further, at least when trying to migrate already active objects. Patches 1/6 and 2/6 deal with accessing and waiting for the TTM moving

Re: [Intel-gfx] Can't drive 4K monitor at full resolution over DP

Hi Bryan. Can you file new bug: https://gitlab.freedesktop.org/drm/intel/-/wikis/How-to-file-i915-bugs Br, Jani Saarinen Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo > -Original Message- > From: Intel-gfx On Behalf Of Bryan > O'Sullivan > Sent: sunnuntai 14.