== Series Details ==
Series: drm/i915/display: Prevent double YUV range correction on HDR planes
(rev2)
URL : https://patchwork.freedesktop.org/series/84966/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489_full -> Patchwork_19152_full
==
== Series Details ==
Series: series starting with [1/2] i915/perf: Move gen specific OA formats to
single array
URL : https://patchwork.freedesktop.org/series/84978/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489_full -> Patchwork_19151_full
==
== Series Details ==
Series: Add support for DP-HDMI2.1 PCON (rev7)
URL : https://patchwork.freedesktop.org/series/82098/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489 -> Patchwork_19153
Summary
---
**SUCCESS**
== Series Details ==
Series: Add support for DP-HDMI2.1 PCON (rev7)
URL : https://patchwork.freedesktop.org/series/82098/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
+./drivers/gpu/drm/amd/amdg
== Series Details ==
Series: Add support for DP-HDMI2.1 PCON (rev7)
URL : https://patchwork.freedesktop.org/series/82098/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b643098d366f drm/edid: Add additional HFVSDB fields for HDMI2.1
-:61: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Si
If PCON has capability to convert RGB->YUV colorspace and also
to 444->420 downsampling then for any YUV420 only mode, we can
let the PCON do all the conversion.
v2: As suggested by Uma Shankar, considered case for colorspace
BT709 and BT2020, and default to BT609. Also appended dir
'display' in c
When a source supporting DSC1.1 is connected to DSC1.2 HDMI2.1 sink
via DP HDMI2.1 PCON, the PCON can be configured to decode the
DSC1.1 compressed stream and encode to DSC1.2. It then sends the
DSC1.2 compressed stream to the HDMI2.1 sink.
This patch configures the PCON for DSC1.1 to DSC1.2 encod
This patch adds support to read and store the DSC capabilities of the
HDMI2.1 PCon encoder. It also adds a new field to store these caps,
The caps are read during dfp update and can later be used to get the
PPS parameters for PCON-HDMI2.1 sink pair. Which inturn will be used
to take a call to overr
The DP-HDMI2.1 PCON spec provides way for a source to set PPS
parameters: slice height, slice width and bits_per_pixel, based on
the HDMI2.1 sink capabilities. The DSC encoder of the PCON will
respect these parameters, while preparing the 128 byte PPS.
This patch adds helper functions to calculate
This patch adds functions to start FRL training for an HDMI2.1 sink,
connected via a PCON as a DP branch device.
This patch also adds a new structure for storing frl training related
data, when FRL training is completed.
v2: As suggested by Uma Shankar:
-renamed couple of variables for better clar
From: Swati Sharma
In this patch enables support for detecting link failures between
PCON and HDMI sink in i915 driver. HDMI link loss indication to
upstream DP source is indicated via IRQ_HPD. This is followed by
reading of HDMI link configuration status (HDMI_TX_LINK_ACTIVE_STATUS).
If the PCON
This patch calls functions to check FRL training requirements
for an HDMI2.1 sink, when connected through PCON.
The call is made before the DP link training. In case FRL is not
required or failure during FRL training, the TMDS mode is selected
for the pcon.
v2: moved check_frl_training() just afte
HDMI2.1 PCON advertises Max FRL bandwidth supported by the PCON.
This patch captures this in dfp cap structure in intel_dp and uses
this to prune connector modes that cannot be supported by the PCON
and FRL bandwidth.
v2: Addressed review comments from Uma Shankar:
-tweaked the comparison of targ
DP Specification for DP2.0 to HDMI2.1 Pcon specifies support for conversion
of colorspace from RGB to YCbCr.
https://groups.vesa.org/wg/DP/document/previewpdf/15651
This patch adds the relavant registers and helper functions to
get the capability and set the color conversion bits for rgb->ycbcr
co
From: Swati Sharma
There are specific DPCDs defined for detecting link failures between
the PCON and HDMI sink and check the link status. In case of link
failure, PCON will communicate the same using an IRQ_HPD to source.
HDMI sink would have indicated the same to PCON using SCDC interrupt
mechan
This patch adds registers for getting DSC encoder capability for
a HDMI2.1 PCon. It also addes helper functions to configure
DSC between the PCON and HDMI2.1 sink.
v2: Corrected offset for DSC encoder bpc and minor changes.
Also added helper functions for getting pcon dsc encoder capabilities
as s
This patch adds support for configuring a PCON device,
connected as a DP branched device to enable FRL Link training
with a HDMI2.1 + sink.
v2: Fixed typos and addressed other review comments from Uma Shankar.
-changed the commit message for better clarity (Uma Shankar)
-removed unnecessary argume
This patch parses HFVSDB fields for DSC1.2 capabilities of an
HDMI2.1 sink. These fields are required by a source to understand the
DSC capability of the sink, to set appropriate PPS parameters,
before transmitting compressed data stream.
v2: Addressed following issues as suggested by Uma Shankar:
From: Swati Sharma
The HDMI2.1 extends HFVSDB (HDMI Forum Vendor Specific
Data block) to have fields related to newly defined methods of FRL
(Fixed Rate Link) levels, number of lanes supported, DSC Color bit
depth, VRR min/max, FVA (Fast Vactive), ALLM etc.
This patch adds the new HFVSDB fields
From: Swati Sharma
This patch parses MAX_FRL field to get the MAX rate in Gbps that
the HDMI 2.1 panel can support in FRL mode. Source need this
field to determine the optimal rate between the source and sink
during FRL training.
v2: Fixed minor bugs, and removed extra wrapper function (Uma Shan
This patch series attempts to add support for a DP-HDMI2.1 Protocol
Convertor. The VESA spec for the HDMI2.1 PCON are proposed in Errata
E5 to DisplayPort_v2.0:
https://vesa.org/join-vesamemberships/member-downloads/?action=stamp&fileid=42299
The details are mentioned in:
VESA DP-to-HDMI PCON Speci
== Series Details ==
Series: drm/i915: Fix mismatch between misplaced vma check and vma insert
URL : https://patchwork.freedesktop.org/series/84975/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9489_full -> Patchwork_19150_full
Hello Wilson,
Appreciate your code review feedback and apologize for the late replying.
I have made those modification as below and the change will reflect in the next
version. (v10)
Best regards,
Sean
1.
> So this is dead code then?
> If the recommendation is not to enable it, and you don't
== Series Details ==
Series: drm/i915/gt: Track the overall awake/busy time
URL : https://patchwork.freedesktop.org/series/84964/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9488_full -> Patchwork_19148_full
Summary
-
Hi Daniel,
Thank you for the patch.
On Fri, Oct 23, 2020 at 02:21:25PM +0200, Daniel Vetter wrote:
> Ends right after drm_atomic_helper_commit_hw_done(), absolutely
> nothing fancy going on here.
>
> Signed-off-by: Daniel Vetter
> Cc: Laurent Pinchart
> Cc: Kieran Bingham
> Cc: linux-renesas-
== Series Details ==
Series: drm/i915/display: Prevent double YUV range correction on HDR planes
(rev2)
URL : https://patchwork.freedesktop.org/series/84966/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489 -> Patchwork_19152
> -Original Message-
> From: Chris Wilson
> Sent: Tuesday, December 15, 2020 2:02 PM
> To: Tang, CQ ; intel-gfx@lists.freedesktop.org
> Cc: stable@
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced
> vma check and vma insert
>
> Quoting Tang, CQ (2020-12-15 2
== Series Details ==
Series: drm/i915/display: Prevent double YUV range correction on HDR planes
(rev2)
URL : https://patchwork.freedesktop.org/series/84966/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
c3629bb8e645 drm/i915/display: Prevent double YUV range correction on HDR
== Series Details ==
Series: series starting with [1/2] i915/perf: Move gen specific OA formats to
single array
URL : https://patchwork.freedesktop.org/series/84978/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489 -> Patchwork_19151
== Series Details ==
Series: series starting with [1/2] i915/perf: Move gen specific OA formats to
single array
URL : https://patchwork.freedesktop.org/series/84978/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
60f0353cf872 i915/perf: Move gen specific OA formats to single ar
== Series Details ==
Series: series starting with [1/4] dma-buf: Remove kmap kerneldoc vestiges
(rev3)
URL : https://patchwork.freedesktop.org/series/84849/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9488_full -> Patchwork_19147_full
===
On Tue, Dec 15, 2020 at 1:01 PM Ville Syrjälä
wrote:
>
> On Mon, Dec 14, 2020 at 10:57:03PM +, Shankar, Uma wrote:
> >
> >
> > > -Original Message-
> > > From: andrescj via sendgmr
> > >
> > > On Behalf Of Andres Calderon Jaramillo
> > > Sent: Tuesday, December 15, 2020 3:50 AM
> > >
== Series Details ==
Series: drm/i915: Fix mismatch between misplaced vma check and vma insert
URL : https://patchwork.freedesktop.org/series/84975/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9489 -> Patchwork_19150
Summ
== Series Details ==
Series: drm/i915/gem: Drop free_work for GEM contexts (rev3)
URL : https://patchwork.freedesktop.org/series/83537/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9488_full -> Patchwork_19146_full
Summary
> -Original Message-
> From: Chris Wilson
> Sent: Tuesday, December 15, 2020 2:02 PM
> To: Tang, CQ ; intel-gfx@lists.freedesktop.org
> Cc: stable@
> Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix mismatch between misplaced
> vma check and vma insert
>
> Quoting Tang, CQ (2020-12-15 2
Quoting Tang, CQ (2020-12-15 21:50:53)
>
>
> > -Original Message-
> > From: Chris Wilson
> > Sent: Tuesday, December 15, 2020 12:31 PM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Chris Wilson ; Tang, CQ ;
> > sta...@vger.kernel.org
> > Subject: [PATCH] drm/i915: Fix mismatch between
Quoting Daniele Ceraolo Spurio (2020-12-15 21:51:13)
>
>
> On 12/14/2020 6:15 PM, Chris Wilson wrote:
> > Primarily used by selftests, but also by runtime debugging of engine
> > w/a, is a routine to create a temporarily bound buffer for readback.
> > Almagamate the duplicated routines into one.
With full-ppgtt, userspace has complete control over their GTT. Verify
that we can place an object at the very beginning and the very end of
our GTT.
Signed-off-by: Chris Wilson
---
tests/i915/gem_softpin.c | 63
1 file changed, 63 insertions(+)
diff --g
On 12/14/2020 6:15 PM, Chris Wilson wrote:
Primarily used by selftests, but also by runtime debugging of engine
w/a, is a routine to create a temporarily bound buffer for readback.
Almagamate the duplicated routines into one.
Suggested-by: Daniele Ceraolo Spurio
Signed-off-by: Chris Wilson
> -Original Message-
> From: Chris Wilson
> Sent: Tuesday, December 15, 2020 12:31 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: Chris Wilson ; Tang, CQ ;
> sta...@vger.kernel.org
> Subject: [PATCH] drm/i915: Fix mismatch between misplaced vma check and
> vma insert
>
> When inserting
When defining OA formats for TGL, some formats were left out. Add them
back and clean up the uapi comments to reflect available formats.
Signed-off-by: Umesh Nerlige Ramappa
---
drivers/gpu/drm/i915/i915_perf.c | 12 +---
include/uapi/drm/i915_drm.h | 24 ++--
2
Variations in OA formats in the different gens has led to creation of
several sparse arrays to store the formats.
Move oa formats into a single array and add the supported range of
platforms for the oa formats.
Signed-off-by: Umesh Nerlige Ramappa
---
drivers/gpu/drm/i915/i915_perf.c | 56
> -Original Message-
> From: Chris Wilson
> Sent: Tuesday, December 15, 2020 1:07 PM
> To: intel-gfx@lists.freedesktop.org
> Cc: igt-...@lists.freedesktop.org; Chris Wilson ;
> Tang, CQ
> Subject: [PATCH i-g-t 1/2] i915/gem_exec_params: Assert a 4G object does
> _not_ fit without 48b
>
== Series Details ==
Series: drm/i915/display: Prevent double YUV range correction on HDR planes
URL : https://patchwork.freedesktop.org/series/84966/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9488 -> Patchwork_19149
Su
Without opting into 48B addressing, objects are strictly limited to
being placed only the first (4G - 4K). This is to avoid an issue with
stateless 32b addressing being unable to access the last 32b page.
Assert that we do indeed fail to fit in a 4G object without setting the
EXEC_OBJECT_SUPPORTS_4
With full-ppgtt, userspacew has complete control over their GTT. Verify
that we can place an object at the very beginning and the very end of
our GTT.
Signed-off-by: Chris Wilson
---
tests/i915/gem_softpin.c | 45
1 file changed, 45 insertions(+)
diff --
Without opting into 48B addressing, objects are strictly limited to
being placed only the first (4G - 4K). This is to avoid an issue with
stateless 32b addressing being unable to access the last 32b page.
Assert that we do indeed fail to fit in a 4G object without setting the
EXEC_OBJECT_SUPPORTS_4
With full-ppgtt, userspacew has complete control over their GTT. Verify
that we can place an object at the very beginning and the very end of
our GTT.
Signed-off-by: Chris Wilson
---
tests/i915/gem_softpin.c | 45
1 file changed, 45 insertions(+)
diff --
== Series Details ==
Series: drm/i915/display: Prevent double YUV range correction on HDR planes
URL : https://patchwork.freedesktop.org/series/84966/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
7f602d3a40e4 drm/i915/display: Prevent double YUV range correction on HDR planes
== Series Details ==
Series: drm/i915/gt: Track the overall awake/busy time
URL : https://patchwork.freedesktop.org/series/84964/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9488 -> Patchwork_19148
Summary
---
**SU
From: Andres Calderon Jaramillo
Prevent the ICL HDR plane pipeline from performing YUV color range
correction twice when the input is in limited range.
Before this patch the following could happen: user space gives us a YUV
buffer in limited range; per the pipeline in [1], the plane would first
When inserting a VMA, we restrict the placement to the low 4G unless the
caller opts into using the full range. This was done to allow usersapce
the opportunity to transition slowly from a 32b address space, and to
avoid breaking inherent 32b assumptions of some commands.
However, for insert we li
== Series Details ==
Series: drm/i915/backlight: RFC cache backlight power state
URL : https://patchwork.freedesktop.org/series/84954/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9486_full -> Patchwork_19144_full
Summary
On Tue, Dec 15, 2020 at 03:06:30PM -0500, Andres Calderon Jaramillo wrote:
> On Tue, Dec 15, 2020 at 1:01 PM Ville Syrjälä
> wrote:
> >
> > On Mon, Dec 14, 2020 at 10:57:03PM +, Shankar, Uma wrote:
> > >
> > >
> > > > -Original Message-
> > > > From: andrescj via sendgmr
> > > >
> >
== Series Details ==
Series: series starting with [1/4] dma-buf: Remove kmap kerneldoc vestiges
(rev3)
URL : https://patchwork.freedesktop.org/series/84849/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9488 -> Patchwork_19147
=
On 12/15/20 10:13 AM, Chris Wilson wrote:
> Quoting t...@redhat.com (2020-12-15 14:41:01)
>> From: Tom Rix
>>
>> See Documentation/core-api/printk-formats.rst.
>> h should no longer be used in the format specifier for printk.
> It's understood by format_decode().
> * 'h', 'l', or 'L' for integer
== Series Details ==
Series: series starting with [1/4] dma-buf: Remove kmap kerneldoc vestiges
(rev3)
URL : https://patchwork.freedesktop.org/series/84849/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
403e03068940 dma-buf: Remove kmap kerneldoc vestiges
-:115: WARNING:FROM_S
== Series Details ==
Series: drm/i915/gem: Drop free_work for GEM contexts (rev3)
URL : https://patchwork.freedesktop.org/series/83537/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9488 -> Patchwork_19146
Summary
---
Quoting t...@redhat.com (2020-12-15 14:41:01)
> From: Tom Rix
>
> See Documentation/core-api/printk-formats.rst.
> h should no longer be used in the format specifier for printk.
It's understood by format_decode().
* 'h', 'l', or 'L' for integer fields
At least reference commit cbacb5ab0aa0 ("do
On Mon, Dec 14, 2020 at 10:57:03PM +, Shankar, Uma wrote:
>
>
> > -Original Message-
> > From: andrescj via sendgmr
> >
> > On Behalf Of Andres Calderon Jaramillo
> > Sent: Tuesday, December 15, 2020 3:50 AM
> > To: intel-gfx@lists.freedesktop.org
> > Cc: Shankar, Uma ; Venkatesh Re
Quoting Mika Kuoppala (2020-12-15 17:09:39)
> Chris Wilson writes:
>
> > We assume that the contents of the HWSP are lost across suspend, and so
> > upon resume we must restore critical values such as the timeline seqno.
> > Keep track of every timeline allocated that uses the HWSP as its storage
Chris Wilson writes:
> We assume that the contents of the HWSP are lost across suspend, and so
> upon resume we must restore critical values such as the timeline seqno.
> Keep track of every timeline allocated that uses the HWSP as its storage
> and so we can then reset all seqno values by walkin
== Series Details ==
Series: drm/i915: remove h from printk format specifier
URL : https://patchwork.freedesktop.org/series/84958/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9487 -> Patchwork_19145
Summary
---
**F
On Thu, 2020-12-10 at 20:25 +0100, Thomas Gleixner wrote:
> Using the interrupt affinity mask for checking locality is not really
> working well on architectures which support effective affinity masks.
>
> The affinity mask is either the system wide default or set by user
> space,
> but the archit
On Thu, 2020-12-10 at 20:25 +0100, Thomas Gleixner wrote:
> No driver has any business with the internals of an interrupt
> descriptor. Storing a pointer to it just to use yet another helper at
> the
> actual usage site to retrieve the affinity mask is creative at best.
> Just
> because C does not
On 03.12.20 22:30, Alex Deucher wrote:
> On Tue, Sep 29, 2020 at 4:04 PM Alex Deucher wrote:
>>
>> On Tue, Sep 29, 2020 at 8:31 AM Jan Kiszka wrote:
>>>
>>> On 10.09.20 20:18, Deucher, Alexander wrote:
[AMD Public Use]
> -Original Message-
> From: amd-gfx On B
On Tue, Dec 15, 2020 at 02:04:31PM +0100, Thomas Zimmermann wrote:
> Hi Dave and Daniel,
>
> here's this week's PR for drm-misc-next-fixes. IIRC the radeon fix is
> already in drm-misc-next.
Pulled, and also your previous -next pull which got stuck somewhere.
Thanks, Daniel
>
> Best regards
>
== Series Details ==
Series: drm/i915/backlight: RFC cache backlight power state
URL : https://patchwork.freedesktop.org/series/84954/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9486 -> Patchwork_19144
Summary
---
On Tue, Dec 15, 2020 at 03:43:00PM +, Souza, Jose wrote:
> On Tue, 2020-12-15 at 16:44 +0200, Ville Syrjälä wrote:
> > On Mon, Dec 14, 2020 at 09:49:08AM -0800, José Roberto de Souza wrote:
> > > Much more clear to read one function call than four lines doing this
> > > conversion.
> > >
> > >
Quoting Chris Wilson (2020-12-15 15:44:56)
> Since we wake the GT up before executing a request, and go to sleep as
> soon as it is retired, the GT wake time not only represents how long the
> device is powered up, but also provides a summary, albeit an overestimate,
> of the device runtime (i.e. t
Since we wake the GT up before executing a request, and go to sleep as
soon as it is retired, the GT wake time not only represents how long the
device is powered up, but also provides a summary, albeit an overestimate,
of the device runtime (i.e. the rc0 time to compare against rc6 time).
v2: s/bu
On Tue, 2020-12-15 at 16:44 +0200, Ville Syrjälä wrote:
> On Mon, Dec 14, 2020 at 09:49:08AM -0800, José Roberto de Souza wrote:
> > Much more clear to read one function call than four lines doing this
> > conversion.
> >
> > Cc: dri-de...@lists.freedesktop.org
> > Cc: Gwan-gyeong Mun
> > Signed-
The free_list and worker was introduced in commit 5f09a9c8ab6b ("drm/i915:
Allow contexts to be unreferenced locklessly"), but subsequently made
redundant by the removal of the last sleeping lock in commit 2935ed5339c4
("drm/i915: Remove logical HW ID"). As we can now free the GEM context
immediate
On Mon, Dec 14, 2020 at 09:49:08AM -0800, José Roberto de Souza wrote:
> Much more clear to read one function call than four lines doing this
> conversion.
>
> Cc: dri-de...@lists.freedesktop.org
> Cc: Gwan-gyeong Mun
> Signed-off-by: José Roberto de Souza
> ---
> drivers/gpu/drm/drm_rect.c | 1
From: Tom Rix
See Documentation/core-api/printk-formats.rst.
h should no longer be used in the format specifier for printk.
Signed-off-by: Tom Rix
---
drivers/gpu/drm/i915/gt/intel_sseu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/gt/intel_sseu.c
On Mon, 2020-12-14 at 19:42 +, Patchwork wrote:
Patch Details
Series: doc: Fix build of documentation after i915 file rename
URL:https://patchwork.freedesktop.org/series/84914/
State: failure
Details:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_19140/index.html
CI Bug Log -
Am 14.12.20 um 17:01 schrieb Daniel Vetter:
On Mon, Dec 14, 2020 at 11:33:10AM +0100, Christian König wrote:
Am 11.12.20 um 16:58 schrieb Daniel Vetter:
Also try to clarify a bit when dma_buf_begin/end_cpu_access should
be called.
Signed-off-by: Daniel Vetter
Cc: Thomas Zimmermann
Cc: Sumit
Am 14.12.20 um 18:16 schrieb Daniel Vetter:
At least amdgpu and i915 do, so lets just document this as the rule.
v2: Works better with less typos (intel-gfx-ci)
Signed-off-by: Daniel Vetter
Cc: Thomas Zimmermann
Cc: Sumit Semwal
Cc: "Christian König"
Cc: linux-me...@vger.kernel.org
Cc: lina
This is RFC proposal to cache the backlight power state in order
to avoid accessing pps register every time while brightness or bl_power
attributes of class intel_backlight is being changed.
Signed-off-by: Anshuman Gupta
---
.../gpu/drm/i915/display/intel_display_types.h | 1 +
drivers/gpu/drm/
On 14/12/2020 10:08, Chris Wilson wrote:
Since we wake the GT up before executing a request, and go to sleep as
soon as it is retired, the GT wake time not only represents how long the
device is powered up, but also provides a summary, albeit an overestimate,
of the device runtime (i.e. the rc0
Quoting José Roberto de Souza (2020-12-14 18:54:40)
> Commit 70a2b431c364 ("drm/i915/gt: Rename lrc.c to
> execlists_submission.c") renamed intel_lrc.c to
> intel_execlists_submission.c but forgot to update i915.rst.
>
> Fixes: 70a2b431c364 ("drm/i915/gt: Rename lrc.c to execlists_submission.c")
>
On Tue, 2020-12-15 at 12:52 +, Mun, Gwan-gyeong wrote:
> On Mon, 2020-12-14 at 09:49 -0800, José Roberto de Souza wrote:
> > Much more clear to read one function call than four lines doing this
> > conversion.
> >
> > Cc: dri-de...@lists.freedesktop.org
> > Cc: Gwan-gyeong Mun
> > Signed-off-
On Tue, 2020-12-15 at 13:02 +, Mun, Gwan-gyeong wrote:
> On Mon, 2020-12-14 at 09:49 -0800, José Roberto de Souza wrote:
> > Now using plane damage clips property to calcualte the damaged area.
> > Selective fetch only supports one region to be fetched so software
> > needs to calculate a bound
Hi Dave and Daniel,
here's this week's PR for drm-misc-next-fixes. IIRC the radeon fix is
already in drm-misc-next.
Best regards
Thomas
drm-misc-next-fixes-2020-12-15:
Short summary of fixes pull (less than what git shortlog provides):
* dma-buf: Fix docs
* mxsfb: Silence invalid error messag
On Mon, 2020-12-14 at 09:49 -0800, José Roberto de Souza wrote:
> Now using plane damage clips property to calcualte the damaged area.
> Selective fetch only supports one region to be fetched so software
> needs to calculate a bounding box around all damage clips.
>
> Now that we are not complete
On Mon, 2020-12-14 at 09:49 -0800, José Roberto de Souza wrote:
> Much more clear to read one function call than four lines doing this
> conversion.
>
> Cc: dri-de...@lists.freedesktop.org
> Cc: Gwan-gyeong Mun
> Signed-off-by: José Roberto de Souza
> ---
> drivers/gpu/drm/drm_rect.c | 15 +
== Series Details ==
Series: Multi DSB instance support
URL : https://patchwork.freedesktop.org/series/84934/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9482_full -> Patchwork_19143_full
Summary
---
**SUCCESS**
On 15/12/2020 09:47, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2020-12-15 09:41:09)
On 14/12/2020 20:44, Chris Wilson wrote:
Check that timeslices for an oversaturated system (where there is more
work than can be supported by a single engine) are evenly distributed
between the clients.
Si
Quoting Tvrtko Ursulin (2020-12-15 09:41:09)
>
> On 14/12/2020 20:44, Chris Wilson wrote:
> > Check that timeslices for an oversaturated system (where there is more
> > work than can be supported by a single engine) are evenly distributed
> > between the clients.
> >
> > Signed-off-by: Chris Wils
On 14/12/2020 20:59, Chris Wilson wrote:
Refactor the allocation such that we utilise just enough memory pressure
to invoke the shrinker, and just enough processes to spread across the
CPUs and contend on the shrinker.
v2: Reduce over-allocation from mem_size/2 to mem_size/8, and 9
processes p
On 14/12/2020 20:44, Chris Wilson wrote:
Check that timeslices for an oversaturated system (where there is more
work than can be supported by a single engine) are evenly distributed
between the clients.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
tests/i915/gem_exec_schedule.c | 179
== Series Details ==
Series: Multi DSB instance support
URL : https://patchwork.freedesktop.org/series/84934/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9482 -> Patchwork_19143
Summary
---
**SUCCESS**
No regres
== Series Details ==
Series: Multi DSB instance support
URL : https://patchwork.freedesktop.org/series/84934/
State : warning
== Summary ==
$ make htmldocs 2>&1 > /dev/null | grep i915
./drivers/gpu/drm/i915/display/intel_dsb.c:94: warning: Function parameter or
member 'id' not described in '
== Series Details ==
Series: Multi DSB instance support
URL : https://patchwork.freedesktop.org/series/84934/
State : warning
== Summary ==
$ dim sparse --fast origin/drm-tip
Sparse version: v0.6.2
Fast mode used, each commit won't be checked separately.
-
+drivers/gpu/drm/i915/gt/intel_reset.
== Series Details ==
Series: Multi DSB instance support
URL : https://patchwork.freedesktop.org/series/84934/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
5408c90cf097 drm/i915/dsb: multi dsb instance support in prepare() and cleanup()
-:8: WARNING:COMMIT_MESSAGE: Missing comm
95 matches
Mail list logo
