On Mon, Aug 11, 2025 at 09:46:55AM +0300, Lee, Shawn C wrote:
> On Fri, Aug 08, 2025 at 09:40:00AM +, Imre Deak C wrote:
> >On Fri, Aug 08, 2025 at 09:16:02AM +, Lee Shawn C wrote:
> >> While performing HDMI compliance testing, test equipment may request
> >> different bpc output for signa
== Series Details ==
Series: drm/i915/bo: remove unnecessary include
URL : https://patchwork.freedesktop.org/series/152954/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_17000 -> Patchwork_152954v1
Summary
---
**SUCC
Hi Tvrtko,
On Wed, Aug 13, 2025 at 10:43:30PM +0100, Tvrtko Ursulin wrote:
> Hi Dave, Sima,
>
> Two display fixes for the RC cycle this week - one for FBC and one for PSR
> handling.
The following commits in drm-intel-next are for stable, so should be
also sent for -rc:
6cb52cba474b drm/i915/ic
== Series Details ==
Series: dma-buf/fence-chain: Speed up processing of rearmed callbacks
URL : https://patchwork.freedesktop.org/series/152941/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_17000 -> Patchwork_152941v1
Sum
Hi Dave and Sima,
Here goes our first round for 6.17 fixes.
The SRIOV setting for VF LMEM BAR size is critical and will cause
trouble for people using SRIOV if not there. But we couldn't send
it earlier because the dependency on PCI patches that just landed
in the last merge-window:
https://lore
Hi,
On Wed, Aug 13, 2025 at 10:04:22AM +, Kandpal, Suraj wrote:
> > > > };
> > >
> > > I still don't like that. This really doesn't belong here. If anything,
> > > the drm_connector for writeback belongs to drm_crtc.
> >
> > Why? We already have generic HDMI field inside drm_connector. I am r
== Series Details ==
Series: drm/i915/audio: drop irq enabled check from LPE audio setup (rev2)
URL : https://patchwork.freedesktop.org/series/152409/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_16998 -> Patchwork_152409v2
== Series Details ==
Series: drm/i915/active: Use try_cmpxchg64() in __active_lookup() (rev2)
URL : https://patchwork.freedesktop.org/series/152185/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_16998 -> Patchwork_152185v2
intel_bo.c doesn't need intel_display_types.h for anything. Remove.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/display/intel_bo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_bo.c
b/drivers/gpu/drm/i915/display/intel_bo.c
index
On 14.08.25 10:16, Janusz Krzysztofik wrote:
> When first user starts waiting on a not yet signaled fence of a chain
> link, a dma_fence_chain callback is added to a user fence of that link.
> When the user fence of that chain link is then signaled, the chain is
> traversed in search for a first
On Wed, 13 Aug 2025, Gustavo Sousa wrote:
> Quoting Jani Nikula (2025-08-06 13:55:01-03:00)
>>Switch to passing struct intel_display to all the macros that use
>>__to_intel_display(), and once that's done, remove __to_intel_display().
>>
>>We'll still need to get rid of struct intel_display usage
On Thu, 14 Aug 2025, "Hogander, Jouni" wrote:
> On Tue, 2025-08-05 at 14:56 +0300, Jani Nikula wrote:
>> Commit 8d9908e8fe9c ("drm/i915/display: remove small micro-
>> optimizations
>> in irq handling") not only removed the optimizations, it also enabled
>> wakeref asserts for the GEN11_GU_MISC_II
On Tue, 05 Aug 2025, Jani Nikula wrote:
> On Tue, 08 Jul 2025, Rodrigo Vivi wrote:
>> On Tue, Jul 08, 2025 at 04:38:18PM +0200, Jason A. Donenfeld wrote:
>>> Hi,
>>>
>>> I'm seeing this splat on 6.16-rc5. i7-11850H.
>>
>> Hi Jason,
>>
>> Could you please file a bug in our gitlab/issues so we can
When first user starts waiting on a not yet signaled fence of a chain
link, a dma_fence_chain callback is added to a user fence of that link.
When the user fence of that chain link is then signaled, the chain is
traversed in search for a first not signaled link and the callback is
rearmed on a user
Userspace may build dma_fence chains of arbitrary length step by step,
e.g. via drm_syncobj IOCTLs, and each step may start waiting on a chain
link it has added. Adjust the wait_* selftests to cover such extreme use
cases.
Having that done, don't enable signaling on each chain link when building
Test cases that create threads around __wait_fence_chains() function now
pass info about the whole chain to those threads as an argument, with no
hint on which fence of the chain to wait on. That decision is hard coded
into the __wait_fence_chains() function which always selects the tail of
the ch
CI results indicate excessive time spent on processing of wait_backward
selftest. For easy comparison, report processing time of each wait_* test
case.
Suggested-by: Chris Wilson
Signed-off-by: Janusz Krzysztofik
---
drivers/dma-buf/st-dma-fence-chain.c | 15 +++
1 file changed, 15
CI results indicate excessive time spent on processing of wait_backward
selftest. The test case enables signaling on each link of a 4096 links
long chain, then signals those links one after another in reverse order.
That scanario corresponds to user space potentially building a dma_fence
chain of
On Fri, 2025-08-01 at 15:28 +0300, Jani Nikula wrote:
> There shouldn't be anything requiring irqs to be enabled at the point of
> LPE audio setup. Regardless, we've never hit the warning, as irqs are
> always enabled at the time LPE audio is initialized. Drop the
> superfluous warning, and the dep
Hi Dave, Sima,
here's the first PR from drm-misc-next for the kernel's upcoming
v6.18. There are the usual fixes. There is a number of new hardware
supported by bridge and panel. We a new driver for Rockchip NPUs.
Best regards
Thomas
drm-misc-next-2025-08-14:
drm-misc-next for v6.18:
UAPI Chang
> -Original Message-
> From: Intel-xe On Behalf Of Jani
> Nikula
> Sent: Tuesday, 5 August 2025 12.18
> To: intel-gfx@lists.freedesktop.org; intel...@lists.freedesktop.org
> Cc: Nikula, Jani
> Subject: [PATCH 02/12] drm/i915: add vlv_clock_get_czclk()
>
> Add vlv_clock_get_czclk() helpe
On Tue, 2025-08-05 at 14:56 +0300, Jani Nikula wrote:
> Commit 8d9908e8fe9c ("drm/i915/display: remove small micro-
> optimizations
> in irq handling") not only removed the optimizations, it also enabled
> wakeref asserts for the GEN11_GU_MISC_IIR access. Silence the asserts
> by
> wrapping the acc
22 matches
Mail list logo
