On 4/7/2022 4:12 PM, Rob Clark wrote:
On Thu, Apr 7, 2022 at 3:59 PM Abhinav Kumar wrote:
Hi Rob and Daniel
On 4/7/2022 3:51 PM, Rob Clark wrote:
On Wed, Apr 6, 2022 at 6:27 PM Jessica Zhang wrote:
On 3/31/2022 8:20 AM, Daniel Vetter wrote:
The stuff never really worked, and leads
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address (rev2)
URL : https://patchwork.freedesktop.org/series/102428/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11479_full -> Patchwork_22833_full
== Series Details ==
Series: Update to GuC v70
URL : https://patchwork.freedesktop.org/series/102430/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11479_full -> Patchwork_22832_full
Summary
---
**SUCCESS**
No
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address (rev2)
URL : https://patchwork.freedesktop.org/series/102428/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11479 -> Patchwork_22833
== Series Details ==
Series: drm/i915/uncore: Warn only if unclaimed access remains flagged
URL : https://patchwork.freedesktop.org/series/102424/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11479_full -> Patchwork_22830_full
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address (rev2)
URL : https://patchwork.freedesktop.org/series/102428/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address (rev2)
URL : https://patchwork.freedesktop.org/series/102428/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
29958f7974ac drm/dp: Factor out a function to probe a
On Sat, Apr 09, 2022 at 01:47:21AM +0300, Almahallawy, Khaled wrote:
> On Fri, 2022-04-08 at 20:21 +0300, Imre Deak wrote:
> > Factor out from drm_dp_dpcd_read() a function to probe a DPCD address
> > with a 1-byte read access. This will be needed by the next patch
> > doing a
> > read from an
Some ADLP DP link configuration at least with multiple LTTPRs expects
the first DPCD access during the LTTPR/DPCD detection after hotplug to
be a read from the LTTPR range starting with
DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV. The side effect of
this read is to put each LTTPR into the
On Fri, 2022-04-08 at 20:21 +0300, Imre Deak wrote:
> Factor out from drm_dp_dpcd_read() a function to probe a DPCD address
> with a 1-byte read access. This will be needed by the next patch
> doing a
> read from an LTTPR address, which must happen without the preceding
> wake-up read in
== Series Details ==
Series: Update to GuC v70
URL : https://patchwork.freedesktop.org/series/102430/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11479 -> Patchwork_22832
Summary
---
**WARNING**
Minor unknown
== Series Details ==
Series: Update to GuC v70
URL : https://patchwork.freedesktop.org/series/102430/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
== Series Details ==
Series: Update to GuC v70
URL : https://patchwork.freedesktop.org/series/102430/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ca0a801b1dda drm/i915/guc: Update context registration to new GuC API
-:418: WARNING:IF_0: Consider removing the code enclosed by
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address
URL : https://patchwork.freedesktop.org/series/102428/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11479 -> Patchwork_22831
Op 07-04-2022 om 15:37 schreef Juha-Pekka Heikkila:
> Reviewed-by: Juha-Pekka Heikkila
>
> On 4.4.2022 16.38, Imre Deak wrote:
>> From: Mika Kahola
>>
>> DG2 clear color render compression uses Tile4 layout. Therefore, we need
>> to define a new format modifier for uAPI to support clear color
== Series Details ==
Series: series starting with [v2,1/2] drm/dp: Factor out a function to probe a
DPCD address
URL : https://patchwork.freedesktop.org/series/102428/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be
== Series Details ==
Series: drm/i915/uncore: Warn only if unclaimed access remains flagged
URL : https://patchwork.freedesktop.org/series/102424/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11479 -> Patchwork_22830
Issues are related to following (just filed #5614)
https://gitlab.freedesktop.org/drm/intel/-/issues/636
[CI][DRMTIP]igt@kms_flip@2x-flip-vs-suspend - dmesg-warn - WARNING: CPU: \d
PID: \d+ at drivers/misc/mei/hbm.c:\d+ mei_hbm_dispatch\+.*
https://gitlab.freedesktop.org/drm/intel/-/issues/5614
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
(rev2)
URL : https://patchwork.freedesktop.org/series/102352/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22829_full
On Fri, Apr 08, 2022 at 06:47:48PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
> (rev2)
> URL : https://patchwork.freedesktop.org/series/102352/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
(rev2)
URL : https://patchwork.freedesktop.org/series/102352/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22829_full
From: John Harrison
Update to the latest GuC firmware release.
Signed-off-by: John Harrison
---
drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c | 32
1 file changed, 16 insertions(+), 16 deletions(-)
diff --git a/drivers/gpu/drm/i915/gt/uc/intel_uc_fw.c
From: John Harrison
The latest GuC firmware drops the individual scheduling policy update
H2G commands in favour of a single KLV based H2G. So, change the
update wrappers accordingly.
Unfortunately, the API changes also mean losing the ability to set any
scheduling policy values during context
From: John Harrison
The latest GuC firmware drops the context descriptor pool in favour of
passing all creation data in the create H2G. It also greatly simplifies
the work queue and removes the process descriptor used for multi-LRC
submission. So, remove all mention of LRC and process
From: John Harrison
Update to the latest GuC firmware release.
Note that this includes some significant backwards breaking API
changes. One is about context registration - the descriptor pool is
gone, all parameters are passed via the CTB instead. The second is
about scheduling policy updates -
On Fri, Apr 08, 2022 at 06:59:07PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> > On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > > Currently skl_pcode_try_request function doesn't
> > > properly handle return value it gets
On Fri, 2022-04-08 at 15:52 +0300, Stanislav Lisovskiy wrote:
> If ret isn't zero, it is almost for sure ETIMEDOUT, because
> we use it in wait_for macro which does continuous retries
> until timeout is reached. If we still ran out of time and
> retries, we most likely would be interested in
On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > Currently skl_pcode_try_request function doesn't
> > properly handle return value it gets from
> > snb_pcode_rw, but treats status != 0 as success,
> >
Some ADLP DP link configuration at least with multiple LTTPRs expects
the first DPCD access during the LTTPR/DPCD detection after hotplug to
be a read from the LTTPR range starting with
DP_LT_TUNABLE_PHY_REPEATER_FIELD_DATA_STRUCTURE_REV. The side effect of
this read is to put each LTTPR into the
Factor out from drm_dp_dpcd_read() a function to probe a DPCD address
with a 1-byte read access. This will be needed by the next patch doing a
read from an LTTPR address, which must happen without the preceding
wake-up read in drm_dp_dpcd_read().
v2: Add a probe function instead of exporting
== Series Details ==
Series: drm/i915/display: Fix warnings about PSR lock not held (rev4)
URL : https://patchwork.freedesktop.org/series/102298/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22828_full
On Fri, Apr 08, 2022 at 09:48:37AM -0700, Lucas De Marchi wrote:
> Commit 4b276ed3c7ac ("drm/i915/uncore: Warn on previous unclaimed
> accesses") tried to improve our report of unclaimed register access,
> however it unveiled cases that were not previously causing any harm.
>
> Downgrade the
Commit 4b276ed3c7ac ("drm/i915/uncore: Warn on previous unclaimed
accesses") tried to improve our report of unclaimed register access,
however it unveiled cases that were not previously causing any harm.
Downgrade the first message to debug so we can still see them and
eventually fix, but don't
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
(rev2)
URL : https://patchwork.freedesktop.org/series/102352/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22829
On Fri, Apr 08, 2022 at 06:46:00PM +0300, Ville Syrjälä wrote:
> On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> > Currently skl_pcode_try_request function doesn't
> > properly handle return value it gets from
> > snb_pcode_rw, but treats status != 0 as success,
> >
== Series Details ==
Series: drm/i915/display: Fix warnings about PSR lock not held (rev4)
URL : https://patchwork.freedesktop.org/series/102298/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22828
On Fri, Apr 08, 2022 at 03:51:59PM +0300, Stanislav Lisovskiy wrote:
> Currently skl_pcode_try_request function doesn't
> properly handle return value it gets from
> snb_pcode_rw, but treats status != 0 as success,
> returning true, which basically doesn't allow
> to use retry/timeout mechanisms
On Fri-08-04-2022 08:32 pm, Harry Wentland wrote:
On 2022-04-08 02:53, Bhanuprakash Modem wrote:
It's useful to know the connector's max supported bpc for IGT
testing. Expose it via a debugfs file on the connector "output_bpc".
Example: cat /sys/kernel/debug/dri/0/DP-1/output_bpc
Cc: Jani
On Fri-08-04-2022 08:33 pm, Harry Wentland wrote:
On 2022-04-08 02:53, Bhanuprakash Modem wrote:
As drm_connector already have the display_info, instead of creating
"output_bpc" debugfs in vendor specific driver, move the logic to
the drm layer.
This patch will also move "Current" bpc to the
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477_full -> Patchwork_22827_full
Summary
---
On Fri, 8 Apr 2022 at 12:29, Tvrtko Ursulin
wrote:
>
>
> On 08/04/2022 10:50, Dave Airlie wrote:
> > On Fri, 8 Apr 2022 at 18:25, Tvrtko Ursulin
> > wrote:
> >>
> >>
> >> On 08/04/2022 08:58, Daniel Vetter wrote:
> >>> On Thu, Apr 07, 2022 at 04:16:27PM +0100, Tvrtko Ursulin wrote:
> From:
On Fri, Apr 08, 2022 at 01:44:44PM +0100, Tvrtko Ursulin wrote:
On 05/04/2022 01:11, Lucas De Marchi wrote:
Since gen6 we use FPGA_DBG register to detect unclaimed MMIO registers.
This register is in the display engine IP and can only ever detect
unclaimed accesses to registers in this area.
On Thu, Apr 07, 2022 at 09:07:19PM +0300, Jani Nikula wrote:
> On Tue, 05 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Dump the panel PNPID and name from the VBT.
> >
> > Signed-off-by: Ville Syrjälä
> > ---
> > drivers/gpu/drm/i915/display/intel_bios.c | 24
On Thu, Apr 07, 2022 at 08:55:29PM +0300, Jani Nikula wrote:
> On Wed, 06 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Apparently when the VBT panel_type==0xff we should trawl through
> > the PNPID table and check for a match against the EDID. If a
> > match is found the index
On 3/14/22 19:20, Ramalingam C wrote:
From: Chris Wilson
Even though the initial protocontext we load onto HW has the register
cleared, by the time we save it into the default image, BB_OFFSET has
had the enable bit set. Reclear BB_OFFSET for each new context.
Testcase:
On 3/14/22 19:20, Ramalingam C wrote:
From: Chris Wilson
Ensure that we always signal the semaphore when timing out, so that if it
happens to be stuck waiting for the semaphore we will quickly recover
without having to wait for a reset.
Reported-by: CQ Tang
Signed-off-by: Chris Wilson
Cc:
On 3/14/22 19:20, Ramalingam C wrote:
From: Chris Wilson
When testing whether we can get the GPU to leak information about
non-privileged state, we first need to ensure that the output buffer is
set to a known value as the HW may opt to skip the write into memory for
a non-privileged read of
On 3/14/22 19:20, Ramalingam C wrote:
From: Chris Wilson
In order to keep the context image parser simple, we assume that all
commands follow a similar format. A few, especially not MI commands on
the render engines, have fixed lengths not encoded in a length field.
This caused us to
== Series Details ==
Series: drm/i915/display: Fix warnings about PSR lock not held (rev4)
URL : https://patchwork.freedesktop.org/series/102298/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22828
Issue is related to
https://gitlab.freedesktop.org/drm/intel/-/issues/5602
All tests - *ERROR* Scratch setup failed, DEBUG_LOCKS_WARN_ON(lock->magic !=
lock)
Lakshmi.
From: Souza, Jose
Sent: Thursday, April 7, 2022 2:05 PM
To: intel-gfx@lists.freedesktop.org; Vudum, Lakshminarayana
Subject:
Regression is related to https://gitlab.freedesktop.org/drm/intel/-/issues/5602
All tests - *ERROR* Scratch setup failed, DEBUG_LOCKS_WARN_ON(lock->magic !=
lock)
Lakshmi.
-Original Message-
From: Roper, Matthew D
Sent: Thursday, April 7, 2022 4:15 PM
To:
On Thu, Apr 07, 2022 at 08:49:00PM +0300, Jani Nikula wrote:
> On Tue, 05 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Make the panel type code a bit more abstract along the
> > lines of the source of the panel type. For the moment
> > we have three classes: OpRegion, VBT,
On Thu, Apr 07, 2022 at 08:23:03PM +0300, Jani Nikula wrote:
> On Tue, 05 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Parsing the panel specific data from VBT is currently happening
> > too early. Split the whole thing into global vs. panel specific
> > parts so that we can
Hi Jani:
Thanks so much for the help. Can you generate a new tag on drm-intel-next? I
noticed that there was one patch moving the DMC related registers into
display/intel_dmc_regs.h, which is not included in the latest tag on
drm-intel-next.
Guess it would be better that I can change this
On Thu, Apr 07, 2022 at 08:07:24PM +0300, Jani Nikula wrote:
> On Wed, 06 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > We need to start parsing stuff from the tail end of the LFP data block.
> > This is made awkward by the fact that the fp_timing table has variable
> > size. So
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22827
Summary
---
**SUCCESS**
On Thu, Apr 07, 2022 at 07:21:44PM +0300, Jani Nikula wrote:
> On Tue, 05 Apr 2022, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Reorder things so that we can parse the entier LFP data block
>
> *entire
>
> > in one go. For now we just stick to parsing the DTD from it.
> >
> > Also fix
== Series Details ==
Series: Fix issues in skl_pcode_request
URL : https://patchwork.freedesktop.org/series/102410/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
6934e112b8f9 drm/i915: Fix skl_pcode_try_request function
-:25: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped
== Series Details ==
Series: Expose max and current bpc via debugfs
URL : https://patchwork.freedesktop.org/series/102390/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11477 -> Patchwork_22825
Summary
---
== Series Details ==
Series: drm/i915: fix i915_gem_object_wait_moving_fence
URL : https://patchwork.freedesktop.org/series/102396/
State : failure
== Summary ==
Applying: drm/i915: fix i915_gem_object_wait_moving_fence
Using index info to reconstruct a base tree...
M
Hi Bhanuprakash,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip next-20220408]
[cannot apply to drm/drm-next v5.18-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note
== Series Details ==
Series: Expose max and current bpc via debugfs
URL : https://patchwork.freedesktop.org/series/102390/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: 0.5.1 (Ubuntu: 0.5.1-2)
Fast mode used, each commit won't be checked separately.
If ret isn't zero, it is almost for sure ETIMEDOUT, because
we use it in wait_for macro which does continuous retries
until timeout is reached. If we still ran out of time and
retries, we most likely would be interested in getting status,
to understand what was the actual error propagated from
Currently skl_pcode_try_request function doesn't
properly handle return value it gets from
snb_pcode_rw, but treats status != 0 as success,
returning true, which basically doesn't allow
to use retry/timeout mechanisms if PCode happens
to be busy and returns EGAIN or some other status
code not
Couple of crucial fixes for skl_pcode_request function.
1) Correctly handle the error and do retires until timeout
2) Return PCode request status, when failure happens
Stanislav Lisovskiy (2):
drm/i915: Fix skl_pcode_try_request function
drm/i915: Swap ret and status returned from
On 05/04/2022 01:11, Lucas De Marchi wrote:
Since gen6 we use FPGA_DBG register to detect unclaimed MMIO registers.
This register is in the display engine IP and can only ever detect
unclaimed accesses to registers in this area. However sometimes there
are reports of this triggering for
On 17/03/2022 18:56, Alan Previn wrote:
Update GuC ADS size allocation to include space for
the lists of error state capture register descriptors.
Then, populate GuC ADS with the lists of registers we want
GuC to report back to host on engine reset events. This list
should include global,
On 08/04/2022 10:48, Matthew Auld wrote:
On 08/04/2022 09:59, Christian König wrote:
Am 08.04.22 um 10:42 schrieb Matthew Auld:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that
On Thu, 7 Apr 2022 at 14:00, Alexander Usyskin
wrote:
>
> From: Tomas Winkler
>
> GSC requires more operational memory than available on chip.
> Reserve 4M of LMEM for GSC operation. The memory is provided to the
> GSC as struct resource to the auxiliary data of the child device.
>
>
On Mon-04-04-2022 09:11 pm, Daniel Vetter wrote:
On Mon, Apr 04, 2022 at 01:46:23PM +0300, Jani Nikula wrote:
On Mon, 04 Apr 2022, "Modem, Bhanuprakash" wrote:
On Fri-01-04-2022 06:10 pm, Jani Nikula wrote:
On Tue, 29 Mar 2022, Bhanuprakash Modem wrote:
This new debugfs will expose the
On 08/04/2022 10:50, Dave Airlie wrote:
On Fri, 8 Apr 2022 at 18:25, Tvrtko Ursulin
wrote:
On 08/04/2022 08:58, Daniel Vetter wrote:
On Thu, Apr 07, 2022 at 04:16:27PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Inherit submitter nice at point of request submission to account for
On Fri, 08 Apr 2022, cgel@gmail.com wrote:
> From: Lv Ruyi
>
> There are some spelling mistakes in the comments. Fix it.
Please prefer splitting by driver. This isn't even split by subsystem. I
presume there are very few maintainers willing to pick this up as it is.
BR,
Jani.
>
>
On Fri, 08 Apr 2022, Christian König wrote:
> Am 08.04.22 um 11:05 schrieb Jani Nikula:
>> On Thu, 07 Apr 2022, "Christian König"
>> wrote:
>>> That should now be handled by the common dma_resv framework.
>>>
>>> Signed-off-by: Christian König
>>> Reviewed-by: Daniel Vetter
>>> Cc:
On Fri, 8 Apr 2022 at 18:25, Tvrtko Ursulin
wrote:
>
>
> On 08/04/2022 08:58, Daniel Vetter wrote:
> > On Thu, Apr 07, 2022 at 04:16:27PM +0100, Tvrtko Ursulin wrote:
> >> From: Tvrtko Ursulin
> >>
> >> Inherit submitter nice at point of request submission to account for long
> >> running
On 08/04/2022 09:59, Christian König wrote:
Am 08.04.22 um 10:42 schrieb Matthew Auld:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the pin_map() for the
On 07/04/2022 21:49, John Harrison wrote:
On 4/7/2022 08:49, Tvrtko Ursulin wrote:
On 03/06/2021 17:48, Matthew Brost wrote:
From: John Harrison
The meaning of 'default' for the enable_guc module parameter has been
updated to accurately reflect what is supported on current platforms.
So
On Fri, 8 Apr 2022 at 11:27, Christian König wrote:
>
> Am 08.04.22 um 11:05 schrieb Jani Nikula:
> > On Thu, 07 Apr 2022, "Christian König"
> > wrote:
> >> That should now be handled by the common dma_resv framework.
> >>
> >> Signed-off-by: Christian König
> >> Reviewed-by: Daniel Vetter
>
Am 08.04.22 um 11:23 schrieb Tvrtko Ursulin:
On 08/04/2022 10:12, Christian König wrote:
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
On 07/04/2022 17:45, Matthew Auld wrote:
All of CI is just failing with the following, which prevents
loading of
the module:
i915 :03:00.0: [drm]
On Fri, Apr 08, 2022 at 09:42:05AM +0100, Matthew Auld wrote:
> All of CI is just failing with the following, which prevents loading of
> the module:
>
> i915 :03:00.0: [drm] *ERROR* Scratch setup failed
>
> Best guess is that this comes from the pin_map() for the scratch page,
> which
On 08/04/2022 10:12, Christian König wrote:
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
On 07/04/2022 17:45, Matthew Auld wrote:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is
Am 08.04.22 um 11:08 schrieb Tvrtko Ursulin:
On 07/04/2022 17:45, Matthew Auld wrote:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the pin_map() for the
On Thu, Apr 07, 2022 at 10:32:11PM +0300, Jani Nikula wrote:
> On Thu, 07 Apr 2022, Imre Deak wrote:
> > The next patch needs a way to read a DPCD register without the preceding
> > wake-up read in drm_dp_dpcd_read(). Export drm_dp_dpcd_access() to allow
> > this.
>
> I think I'd rather you
On 07/04/2022 17:45, Matthew Auld wrote:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the pin_map() for the scratch page,
which does an
On Thu, 07 Apr 2022, "Christian König" wrote:
> That should now be handled by the common dma_resv framework.
>
> Signed-off-by: Christian König
> Reviewed-by: Daniel Vetter
> Cc: intel-gfx@lists.freedesktop.org
So, where are the i915 maintainer acks for merging this (and the other
patches in
On 4/5/22 17:08, Ramalingam C wrote:
When emit_pte doesn't update any PTE with return value as 0, interpret
it as -EINVAL.
v2:
Add missing goto [Thomas]
Signed-off-by: Ramalingam C
---
drivers/gpu/drm/i915/gt/intel_migrate.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
On 28/03/2022 12:18, Petri Latvala wrote:
On Mon, Mar 28, 2022 at 11:08:59AM +0100, Matthew Auld wrote:
From: CQ Tang
On some systems lmem can be as large as 16G, which seems to trigger
various CI timeouts, and in the best case just takes a long time. For
the purposes of the test we should
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the pin_map() for the scratch page,
which does an i915_gem_object_wait_moving_fence() somewhere. It looks
like this now
On 07/04/2022 17:49, Christian König wrote:
Am 07.04.22 um 18:45 schrieb Matthew Auld:
I guess this was missed in the conversion or something.
Fixes: 7bc80a5462c3 ("dma-buf: add enum dma_resv_usage v4")
Signed-off-by: Matthew Auld
Cc: Christian König
Cc: Daniel Vetter
My best guess is
On 08/04/2022 08:58, Daniel Vetter wrote:
On Thu, Apr 07, 2022 at 04:16:27PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Inherit submitter nice at point of request submission to account for long
running processes getting either externally or self re-niced.
This accounts for the
On 08/04/2022 06:00, Lucas De Marchi wrote:
On Thu, Apr 07, 2022 at 05:45:32PM +0100, Matthew Auld wrote:
All of CI is just failing with the following, which prevents loading of
the module:
i915 :03:00.0: [drm] *ERROR* Scratch setup failed
Best guess is that this comes from the
On Fri, 08 Apr 2022, Jani Nikula wrote:
> On Mon, 04 Apr 2022, Imre Deak wrote:
>> This is a rebased version of patches 15-17 of [1], adding DG2 display
>> engine support for decompressing render and media compressed
>> framebuffers.
>>
>> The dependency patches from [1] should be merged already
On Thu, Apr 07, 2022 at 04:16:27PM +0100, Tvrtko Ursulin wrote:
> From: Tvrtko Ursulin
>
> Inherit submitter nice at point of request submission to account for long
> running processes getting either externally or self re-niced.
>
> This accounts for the current processing landscape where
On Mon, 04 Apr 2022, Imre Deak wrote:
> This is a rebased version of patches 15-17 of [1], adding DG2 display
> engine support for decompressing render and media compressed
> framebuffers.
>
> The dependency patches from [1] should be merged already to drm-tip.
>
> It addresses the review
== Series Details ==
Series: drm/dp: Don't rewrite link config when setting phy CTS test pattern
with LTTPR
URL : https://patchwork.freedesktop.org/series/102385/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11474 -> Patchwork_22824
On Tue, Apr 05, 2022 at 11:03:18PM +0200, Daniel Vetter wrote:
> Hi all,
>
> Finally got around to respin this. Changes:
> - Bunch more acks and r-b, still not yet all patches.
> - one tiny fix for a bisect issue, end result was all fine
> - I dropped the last to patches to make registered_fb
== Series Details ==
Series: drm/i915/display: Fix warnings about PSR lock not held (rev3)
URL : https://patchwork.freedesktop.org/series/102298/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22818
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
URL : https://patchwork.freedesktop.org/series/102352/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22819
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
URL : https://patchwork.freedesktop.org/series/102352/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22819
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
URL : https://patchwork.freedesktop.org/series/102352/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22819
== Series Details ==
Series: drm/i915: Sunset igpu legacy mmap support based on GRAPHICS_VER_FULL
URL : https://patchwork.freedesktop.org/series/102352/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_11472 -> Patchwork_22819
1 - 100 of 106 matches
Mail list logo
