32 is too many for the likes of kbl, and in order to insert that many
requests into the ring requires us to declare the first few hung --
understandably a slow and unexpected process. Instead, measure the size
of a singe requests and use that to estimate the upper bound on the
chain length we can u
Use the igt_live_test framework for detecting whether an unwanted hang
occurred during test execution, and report failure if it does.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/selftests/intel_lrc.c | 38 --
1 file changed, 35 insertions(+), 3 deletions(-)
diff --g
Finally, now need shards data ;).
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
> Patchwork
> Sent: torstai 21. maaliskuuta 2019 8.34
> To: Ville Syrjala
> Cc: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] ✓ Fi.CI.BAT: succe
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention.
Secondary aspect of this is that we undo the arbitrary fetching and
potential flushing of all pages for a set-domain(.w
://github.com/0day-ci/linux/commits/Bob-Paauwe/drm-i915-ehl-All-EHL-ports-are-combo-phys-v2/20190321-145619
base: git://anongit.freedesktop.org/drm-intel for-linux-next
config: i386-randconfig-x000-201911 (attached as .config)
compiler: gcc-7 (Debian 7.3.0-1) 7.3.0
reproduce:
# save the
The mock_context() function returns NULL on error, it doesn't return
error pointers.
Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
Signed-off-by: Dan Carpenter
---
.../gpu/drm/i915/selftests/i915_gem_context.c | 4 +-
drivers/staging/erofs/unzip_vle.c | 70 +
== Series Details ==
Series: series starting with [1/2] drm/i915/selftests: Calculate maximum ring
size for preemption chain
URL : https://patchwork.freedesktop.org/series/58323/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12541
===
== Series Details ==
Series: drm/i915: Skip object locking around a no-op set-domain ioctl
URL : https://patchwork.freedesktop.org/series/58325/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e968397bb2a0 drm/i915: Skip object locking around a no-op set-domain ioctl
-:15: WARNIN
Dan Carpenter writes:
> The mock_context() function returns NULL on error, it doesn't return
> error pointers.
>
> Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
> Signed-off-by: Dan Carpenter
> ---
> .../gpu/drm/i915/selftests/i915_gem_context.c | 4 +-
> drivers/stagi
== Series Details ==
Series: drm/i915: Skip object locking around a no-op set-domain ioctl
URL : https://patchwork.freedesktop.org/series/58325/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12542
Summary
Quoting Patchwork (2019-03-21 09:04:59)
> == Series Details ==
>
> Series: drm/i915: Skip object locking around a no-op set-domain ioctl
> URL : https://patchwork.freedesktop.org/series/58325/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12542
> ==
Op 20-03-2019 om 19:22 schreef Sean Paul:
> On Tue, Mar 19, 2019 at 01:17:02PM +0100, Maarten Lankhorst wrote:
>> There has unfortunately been a conflict with the following 3 commits:
>>
>> commit e9961ab95af81b8d29054361cd5f0c575102cf87
>> Author: Ayan Kumar Halder
>> Date: Fri Nov 9 17:21:12 2
Quoting Chris Wilson (2019-03-21 08:05:32)
> If we are already in the desired write domain of a set-domain ioctl,
> then there is nothing for us to do and we can quickly return back to
> userspace, avoiding any lock contention.
>
> Secondary aspect of this is that we undo the arbitrary fetching an
Now that we can rotate 64 bpp formats, we need to add the rotation case.
This wasn't caught by CI or me, because the rotated formats were skipping
because the rotated watermarks exceeded the allocation limits.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_pm.c | 3 +++
1 file c
This was missing in the original addition of those formats, but in
PLANE_SIZE description it's mentioned that 8 cpp formats are not
valid with Yf tiling. Reject this case properly.
Signed-off-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_sprite.c | 4 ++--
1 file changed, 2 insertions(+),
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention.
Secondary aspect of this is that we undo the arbitrary fetching and
potential flushing of all pages for a set-domain(.w
Quoting Chris Wilson (2019-03-21 09:11:30)
> Quoting Patchwork (2019-03-21 09:04:59)
> > == Series Details ==
> >
> > Series: drm/i915: Skip object locking around a no-op set-domain ioctl
> > URL : https://patchwork.freedesktop.org/series/58325/
> > State : failure
> >
> > == Summary ==
> >
>
On Thu, Mar 21, 2019 at 10:58:40AM +0200, Mika Kuoppala wrote:
> Dan Carpenter writes:
>
> > The mock_context() function returns NULL on error, it doesn't return
> > error pointers.
> >
> > Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
> > Signed-off-by: Dan Carpenter
>
The mock_context() function returns NULL on error, it doesn't return
error pointers.
Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
Signed-off-by: Dan Carpenter
---
V2: I accidentally sent a bunch of unrelated stuff...
diff --git a/drivers/gpu/drm/i915/selftests/i915_gem_
== Series Details ==
Series: drm/i915/selftests: fix NULL vs IS_ERR() check in mock_context_barrier()
URL : https://patchwork.freedesktop.org/series/58337/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5785 -> Patchwork_12543
===
Quoting Chris Wilson (2019-03-20 11:34:56)
> Use the igt_live_test framework for detecting whether an unwanted hang
> occurred during test execution, and report failure if it does.
>
> Signed-off-by: Chris Wilson
Reviewed-by: Joonas Lahtinen
Regards, Joonas
On Wed, 2019-03-20 at 23:46 +0200, Ville Syrjala wrote:
> +static void cnl_get_dram_timings(struct drm_i915_private *dev_priv,
> +const struct dram_info *dram,
> +struct intel_dram_timings *t)
> +{
> + u32 val;
> +
> + if (
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention. By recognising that the
write_domain is always a subset of the read_domains, and excluding the
no-op case of requiring 0
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention. By recognising that the
write_domain is always a subset of the read_domains, and excluding the
no-op case of requiring 0
Quoting Lionel Landwerlin (2019-03-19 18:39:52)
> Hi all,
>
> There are couple of extensions coming up for our userspace drivers (anv/i965)
> where we need to add additional parameters to execbuf :
>
> - VK_KHR_timeline_semaphore : supplying u64 points together with syncobjs
> [1]
> -
On Wed, 20 Mar 2019, Chris Wilson wrote:
> gcc-4.8 and older dislike the use of __builtin_constant_p() within a
> constant expression context, and so we must use the magical
> __is_constexpr() instead.
>
> For example, with gcc-4.8.5:
> ../drivers/gpu/drm/i915/i915_reg.h:167:27: error: first argum
Dan Carpenter writes:
> The mock_context() function returns NULL on error, it doesn't return
> error pointers.
>
> Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
> Signed-off-by: Dan Carpenter
Reviewed-by: Mika Kuoppala
> ---
> V2: I accidentally sent a bunch of unrela
Quoting Jani Nikula (2019-03-21 09:50:25)
> On Wed, 20 Mar 2019, Chris Wilson wrote:
> > gcc-4.8 and older dislike the use of __builtin_constant_p() within a
> > constant expression context, and so we must use the magical
> > __is_constexpr() instead.
> >
> > For example, with gcc-4.8.5:
> > ../dr
On Wed, Mar 20, 2019 at 03:49:31PM -0700, Matt Roper wrote:
> On Mon, Mar 18, 2019 at 06:13:15PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > With everything else moved out of the way only ilk+
> > remains using _intel_color_check(). Streamline the logic
> > into ilk_color_check().
Quoting Joonas Lahtinen (2019-03-21 09:32:46)
> Quoting Chris Wilson (2019-03-20 11:34:56)
> > Use the igt_live_test framework for detecting whether an unwanted hang
> > occurred during test execution, and report failure if it does.
> >
> > Signed-off-by: Chris Wilson
>
> Reviewed-by: Joonas Lah
On Thu, Mar 21, 2019 at 10:15:46AM +0100, Maarten Lankhorst wrote:
> This was missing in the original addition of those formats, but in
> PLANE_SIZE description it's mentioned that 8 cpp formats are not
> valid with Yf tiling. Reject this case properly.
>
> Signed-off-by: Maarten Lankhorst
> ---
On Thu, Mar 21, 2019 at 10:15:45AM +0100, Maarten Lankhorst wrote:
> Now that we can rotate 64 bpp formats, we need to add the rotation case.
> This wasn't caught by CI or me, because the rotated formats were skipping
> because the rotated watermarks exceeded the allocation limits.
>
> Signed-off-
On Thu, Mar 21, 2019 at 09:34:00AM +, Lisovskiy, Stanislav wrote:
> On Wed, 2019-03-20 at 23:46 +0200, Ville Syrjala wrote:
> > +static void cnl_get_dram_timings(struct drm_i915_private *dev_priv,
> > +const struct dram_info *dram,
> > +
From: Tvrtko Ursulin
IS_IRONLAKE_M can use the already defined intel_device_info.is_mobile for
this platform, so remove the instance of Ironlake's mobile device id from
the header file and replace it with an IS_MOBILE check.
v2:
* Improved commit text. (Chris)
Signed-off-by: Tvrtko Ursulin
Su
Hi Uma,
On Wed, Mar 20, 2019 at 04:18:16PM +0530, Uma Shankar wrote:
> CEA 861.3 spec adds colorimetry data block for HDMI.
> Parsing the block to get the colorimetry data from
> panel.
>
While code which parses these parts (patches 2 and 3) out of EDID
could be useful - it doesn't seem to actua
Hi Uma,
On Wed, Mar 20, 2019 at 04:18:14PM +0530, Uma Shankar wrote:
> This patch adds a blob property to get HDR metadata
> information from userspace. This will be send as part
> of AVI Infoframe to panel.
>
> v2: Rebase and modified the metadata structure elements
> as per Ville's POC changes.
On Wed, Mar 20, 2019 at 04:18:19PM +0530, Uma Shankar wrote:
> Enable Dynamic Range and Mastering Infoframe for HDR
> content, which is defined in CEA 861.3 spec.
>
> The metadata will be computed based on blending
> policy in userspace compositors and passed as a connector
> property blob to driv
Hi,
On Wed, Mar 20, 2019 at 04:18:18PM +0530, Uma Shankar wrote:
> This patch implements get() and set() functions for HDR output
> metadata property.The blob data is received from userspace and
> saved in connector state, the same is returned as blob in get
> property call to userspace.
>
> v2:
Op 21-03-2019 om 11:27 schreef Ville Syrjälä:
> On Thu, Mar 21, 2019 at 10:15:46AM +0100, Maarten Lankhorst wrote:
>> This was missing in the original addition of those formats, but in
>> PLANE_SIZE description it's mentioned that 8 cpp formats are not
>> valid with Yf tiling. Reject this case prop
GuC may send notification messages with payload larger than
single u32. Prepare driver to accept longer messages.
Signed-off-by: Michal Wajdeczko
Cc: Daniele Ceraolo Spurio
Cc: Vinay Belgaumkar
Cc: Michal Winiarski
Cc: Tomasz Lis
---
drivers/gpu/drm/i915/intel_guc.c| 14 +++---
d
Hi,
On Wed, Mar 20, 2019 at 04:18:26PM +0530, Uma Shankar wrote:
> Added the const version of infoframe for DRM metadata
> for HDR.
>
> Signed-off-by: Uma Shankar
Unless there's a strong reason not to, I think this can be squashed
into patch 6.
> ---
> drivers/video/hdmi.c | 63
> +++
== Series Details ==
Series: series starting with [1/2] drm/i915: Add missing scanline case for 8
cpp watermarks.
URL : https://patchwork.freedesktop.org/series/58342/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5787 -> Patchwork_12544
==
== Series Details ==
Series: drm/i915: Skip object locking around a no-op set-domain ioctl (rev4)
URL : https://patchwork.freedesktop.org/series/58325/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f18176be40dd drm/i915: Skip object locking around a no-op set-domain ioctl
-:19:
== Series Details ==
Series: drm/i915/selftests: fix NULL vs IS_ERR() check in
mock_context_barrier() (rev2)
URL : https://patchwork.freedesktop.org/series/58337/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5787 -> Patchwork_12545
===
Op 21-03-2019 om 11:29 schreef Ville Syrjälä:
> On Thu, Mar 21, 2019 at 10:15:45AM +0100, Maarten Lankhorst wrote:
>> Now that we can rotate 64 bpp formats, we need to add the rotation case.
>> This wasn't caught by CI or me, because the rotated formats were skipping
>> because the rotated watermar
== Series Details ==
Series: drm/i915: Skip object locking around a no-op set-domain ioctl (rev4)
URL : https://patchwork.freedesktop.org/series/58325/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5787 -> Patchwork_12546
S
From: Ville Syrjälä
Some monitors apparently forget to mark any mode as preferred in the
EDID. In this particular case we have a very generic looking ID
"PNP Model 0 Serial Number 4" / "LVDS 800x600" so a specific quirk
doesn't seem particularly wise. Also the quirk we have
(EDID_QUIRK_FIRST_DETA
From: Ville Syrjälä
LVDS and eDP have essentially the same code for grabbing the
fixed mode from VBT. Pull that code to a common location.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_dp.c| 11 ++-
drivers/gpu/drm/i915/intel_drv.h | 2 ++
drivers/gpu/drm/i915/inte
From: Ville Syrjälä
Both LVDS and eDP have the same code to look up the preferred mode
from the connector probed_modes list. Move the code to a common
location.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_dp.c| 13 +++--
drivers/gpu/drm/i915/intel_drv.h | 2 ++
d
From: Ville Syrjälä
Utilize drm_mode_match() instead of hand rolling it when
looking for the DRRS downclock mode.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_panel.c | 49 +++---
1 file changed, 24 insertions(+), 25 deletions(-)
diff --git a/drivers/gpu
From: Ville Syrjälä
Rename intel_find_panel_downclock() to intel_panel_edid_downclock_mode()
to make it clear it's looking for the downclock mode in the EDID.
And while at it polish the implementation a bit as well.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_dp.c| 4 +---
From: Ville Syrjälä
DSI has its own convoluted way of grabbing the fixed mode from
the VBT. Change it to follow the path laid out by LVDS/eDP.
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/icl_dsi.c | 14 ++
drivers/gpu/drm/i915/intel_dsi.h | 1 -
drivers/gpu/drm
== Series Details ==
Series: series starting with [1/3] drm/i915: Split Pineview device info into
desktop and mobile (rev2)
URL : https://patchwork.freedesktop.org/series/58123/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
777e1e26f8a9 drm/i915: Split Pineview device info int
== Series Details ==
Series: series starting with [1/3] drm/i915: Split Pineview device info into
desktop and mobile (rev2)
URL : https://patchwork.freedesktop.org/series/58123/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Split Pineview d
Quoting Mika Kuoppala (2019-03-21 10:01:13)
> Dan Carpenter writes:
>
> > The mock_context() function returns NULL on error, it doesn't return
> > error pointers.
> >
> > Fixes: 85fddf0b0027 ("drm/i915: Introduce a context barrier callback")
> > Signed-off-by: Dan Carpenter
>
> Reviewed-by: Mik
== Series Details ==
Series: series starting with [1/2] drm/i915: Turn dram_info.num_channels into a
bitmask (rev3)
URL : https://patchwork.freedesktop.org/series/58299/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5785_full -> Patchwork_12540_full
==
When we return pages to the system, we ensure that they are marked as
being in the CPU domain since any external access is uncontrolled and we
must assume the worst. This means that we need to always flush the pages
on acquisition if we need to use them on the GPU, and from the beginning
have used
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention. By recognising that the
write_domain is always a subset of the read_domains, and excluding the
no-op case of requiring 0
> -Original Message-
> From: Shankar, Uma
> Sent: Wednesday, March 20, 2019 5:19 PM
> To: Kulkarni, Vandita ; intel-
> g...@lists.freedesktop.org
> Cc: Nikula, Jani ; Chauhan, Madhav
>
> Subject: RE: [PATCH 1/2] drm/i915/icl/dsi: Ungate clocks if gated
>
>
>
> >-Original Message---
== Series Details ==
Series: series starting with [1/3] drm/i915: Split Pineview device info into
desktop and mobile (rev2)
URL : https://patchwork.freedesktop.org/series/58123/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5787 -> Patchwork_12547
> -Original Message-
> From: Deak, Imre
> Sent: Wednesday, March 20, 2019 4:38 PM
> To: Kulkarni, Vandita
> Cc: intel-gfx@lists.freedesktop.org; Nikula, Jani
> Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915/icl/dsi: Fix port disable
> sequence
>
> On Wed, Mar 20, 2019 at 03:38:59PM +05
> -Original Message-
> From: Shankar, Uma
> Sent: Wednesday, March 20, 2019 5:32 PM
> To: Deak, Imre ; Kulkarni, Vandita
>
> Cc: Nikula, Jani ; intel-gfx@lists.freedesktop.org
> Subject: RE: [Intel-gfx] [PATCH 2/2] drm/i915/icl/dsi: Fix port disable
> sequence
>
>
>
> >-Original
In later patches, it became apparent that userspace can see a partially
constructed GEM context and begin using it before it was ready, to much
hilarity. Close this window of opportunity by lifting the registration of
the context with userspace (the insertion of the context into the filp's
idr) to
The timeline->name is only used for convenience in pretty printing the
i915_request.fence->ops->get_timeline_name() and it is just as
convenient to pull it from the gem_context directly. The few instances
of its use inside GEM_TRACE() has proven more of a nuisance than
helpful, so not worth saving
Define a mutex for the exclusive use of interacting with the per-file
context-idr, that was previously guarded by struct_mutex. This allows us
to reduce the coverage of struct_mutex, with a view to removing the last
bits coordinating GEM context later. (In the short term, we avoid taking
struct_mut
The user_handle need only be known by userspace for it to lookup the
context via the idr; internally we have no use for it.
Signed-off-by: Chris Wilson
Reviewed-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_debugfs.c | 5 ++--
drivers/gpu/drm/i915/i915_gem_context.c | 23 +++
On 21/03/2019 09:46, Joonas Lahtinen wrote:
Quoting Lionel Landwerlin (2019-03-19 18:39:52)
Hi all,
There are couple of extensions coming up for our userspace drivers (anv/i965)
where we need to add additional parameters to execbuf :
- VK_KHR_timeline_semaphore : supplying u64 points toge
Op 19-03-2019 om 18:20 schreef Chris Wilson:
> Quoting Lionel Landwerlin (2019-03-19 16:39:52)
>> Hi all,
>>
>> There are couple of extensions coming up for our userspace drivers (anv/i965)
>> where we need to add additional parameters to execbuf :
>>
>> - VK_KHR_timeline_semaphore : supplying
Quoting Lionel Landwerlin (2019-03-21 14:08:39)
> Mostly it's just about having the ability to extend it.
> I can't really tell you up front what we're going to need until we do :)
Yup. My takeaway is that the uAPI debugability is something that has
never been taken seriously (-EINVAL!). And that
Quoting Tvrtko Ursulin (2019-03-20 13:13:45)
>
> On 19/03/2019 11:57, Chris Wilson wrote:
> > A usecase arose out of handling context recovery in mesa, whereby they
> > wish to recreate a context with fresh logical state but preserving all
> > other details of the original. Currently, they create
On Wed, 2019-03-20 at 11:48 -0700, Stuart Summers wrote:
> Currently, the subslice_mask runtime parameter is stored as an
> array of subslices per slice. Expand the subslice mask array to
> better match what is presented to userspace through the
> I915_QUERY_TOPOLOGY_INFO ioctl. The index into this
On Thu, 2019-03-21 at 15:24 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Some monitors apparently forget to mark any mode as preferred in the
> EDID. In this particular case we have a very generic looking ID
> "PNP Model 0 Serial Number 4" / "LVDS 800x600" so a specific quirk
> doesn't s
Quoting Tvrtko Ursulin (2019-03-20 15:59:14)
>
> On 19/03/2019 11:57, Chris Wilson wrote:
> > static void execlists_dequeue(struct intel_engine_cs *engine)
> > {
> > struct intel_engine_execlists * const execlists = &engine->execlists;
> > @@ -691,6 +805,37 @@ static void execlists_deque
== Series Details ==
Series: drm/i915/guc: Support for extended GuC notification messages
URL : https://patchwork.freedesktop.org/series/58352/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5788 -> Patchwork_12548
Summary
-
On 21/03/2019 15:00, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-03-20 15:59:14)
On 19/03/2019 11:57, Chris Wilson wrote:
static void execlists_dequeue(struct intel_engine_cs *engine)
{
struct intel_engine_execlists * const execlists = &engine->execlists;
@@ -691,6 +805,37 @
On 21/03/2019 14:38, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-03-20 13:13:45)
On 19/03/2019 11:57, Chris Wilson wrote:
A usecase arose out of handling context recovery in mesa, whereby they
wish to recreate a context with fresh logical state but preserving all
other details of the ori
Quoting Tvrtko Ursulin (2019-03-21 15:13:59)
>
> On 21/03/2019 15:00, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2019-03-20 15:59:14)
> >>
> >> On 19/03/2019 11:57, Chris Wilson wrote:
> >>> +static void virtual_submission_tasklet(unsigned long data)
> >>> +{
> >>> + struct virtual_engine
== Series Details ==
Series: series starting with [1/2] drm/i915: Flush pages on acquisition
URL : https://patchwork.freedesktop.org/series/58357/
State : failure
== Summary ==
Applying: drm/i915: Flush pages on acquisition
Using index info to reconstruct a base tree...
M drivers/gpu/drm
== Series Details ==
Series: series starting with [1/6] drm/i915: Refactor EDID fixed mode search
URL : https://patchwork.freedesktop.org/series/58356/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5788 -> Patchwork_12549
S
Quoting Patchwork (2019-03-21 15:37:25)
> == Series Details ==
>
> Series: series starting with [1/2] drm/i915: Flush pages on acquisition
> URL : https://patchwork.freedesktop.org/series/58357/
> State : failure
>
> == Summary ==
>
> Applying: drm/i915: Flush pages on acquisition
> Using inde
== Series Details ==
Series: series starting with [CI,1/4] drm/i915: Separate GEM context
construction and registration to userspace
URL : https://patchwork.freedesktop.org/series/58361/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Separat
On Thu, Mar 21, 2019 at 12:32:47AM +, Patchwork wrote:
> == Series Details ==
>
> Series: series starting with [CI,1/4] drm/i915: Force 2*96 MHz cdclk on
> glk/cnl when audio power is enabled
> URL : https://patchwork.freedesktop.org/series/58273/
> State : failure
>
> == Summary ==
>
> C
== Series Details ==
Series: series starting with [CI,1/4] drm/i915: Separate GEM context
construction and registration to userspace
URL : https://patchwork.freedesktop.org/series/58361/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5788 -> Patchwork_12551
===
When we return pages to the system, we ensure that they are marked as
being in the CPU domain since any external access is uncontrolled and we
must assume the worst. This means that we need to always flush the pages
on acquisition if we need to use them on the GPU, and from the beginning
have used
If we are already in the desired write domain of a set-domain ioctl,
then there is nothing for us to do and we can quickly return back to
userspace, avoiding any lock contention. By recognising that the
write_domain is always a subset of the read_domains, and excluding the
no-op case of requiring 0
On Thu, 21 Mar 2019 at 13:43, Chris Wilson wrote:
>
> If we are already in the desired write domain of a set-domain ioctl,
> then there is nothing for us to do and we can quickly return back to
> userspace, avoiding any lock contention. By recognising that the
> write_domain is always a subset of
== Series Details ==
Series: series starting with [1/2] drm/i915/selftests: Calculate maximum ring
size for preemption chain
URL : https://patchwork.freedesktop.org/series/58323/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5785_full -> Patchwork_12541_full
=
Hi Da.*,
Here's the first 5.2 PR from -misc. There's a bit of everything in the PR,
enjoy!
drm-misc-next-2019-03-21:
drm-misc-next for 5.2:
UAPI Changes:
- Add Colorspace connector property (Uma)
- fourcc: Several new YUV formats from ARM (Brian & Ayan)
- fourcc: Fix merge conflicts between new
Quoting Ville Syrjala (2019-03-21 13:24:41)
> From: Ville Syrjälä
>
> Both LVDS and eDP have the same code to look up the preferred mode
> from the connector probed_modes list. Move the code to a common
> location.
>
> Signed-off-by: Ville Syrjälä
Reviewed-by: Chris Wilson
-Chris
_
Quoting Ville Syrjala (2019-03-21 13:24:43)
> From: Ville Syrjälä
>
> LVDS and eDP have essentially the same code for grabbing the
> fixed mode from VBT. Pull that code to a common location.
>
> Signed-off-by: Ville Syrjälä
Reviewed-by: Chris Wilson
-Chris
_
Quoting Ville Syrjala (2019-03-21 13:24:46)
> From: Ville Syrjälä
>
> Rename intel_find_panel_downclock() to intel_panel_edid_downclock_mode()
> to make it clear it's looking for the downclock mode in the EDID.
> And while at it polish the implementation a bit as well.
>
> Signed-off-by: Ville S
Quoting Ville Syrjala (2019-03-21 13:24:45)
> From: Ville Syrjälä
>
> Utilize drm_mode_match() instead of hand rolling it when
> looking for the DRRS downclock mode.
>
> Signed-off-by: Ville Syrjälä
> ---
> drivers/gpu/drm/i915/intel_panel.c | 49 +++---
> 1 file change
Quoting Ville Syrjala (2019-03-21 13:24:44)
> From: Ville Syrjälä
>
> DSI has its own convoluted way of grabbing the fixed mode from
> the VBT. Change it to follow the path laid out by LVDS/eDP.
That was scarier than the actual code changes.
> Signed-off-by: Ville Syrjälä
Reviewed-by: Chris W
== Series Details ==
Series: series starting with [1/2] drm/i915: Flush pages on acquisition
URL : https://patchwork.freedesktop.org/series/58367/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
b1808bbb9ff2 drm/i915: Flush pages on acquisition
a231feabd20f drm/i915: Skip object
== Series Details ==
Series: series starting with [1/2] drm/i915: Flush pages on acquisition
URL : https://patchwork.freedesktop.org/series/58367/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Flush pages on acquisition
-drivers/gpu/drm/i915
On Thu, Mar 21, 2019 at 05:23:30PM +, Chris Wilson wrote:
> Quoting Ville Syrjala (2019-03-21 13:24:45)
> > From: Ville Syrjälä
> >
> > Utilize drm_mode_match() instead of hand rolling it when
> > looking for the DRRS downclock mode.
> >
> > Signed-off-by: Ville Syrjälä
> > ---
> > drivers
Adding a call to intel_uc_suspend in i915_gem_suspend, which
is a common point for the suspend/resume and hibernate paths.
This fixes an unbalanced call that causes issues with the CTB
register/deregister.
Cc: Daniele Ceraolo Spurio
Cc: Chris Wilson
Cc: Michal Wajdeczko
Signed-off-by: Sujaritha
It took 35-120sec because some of engines hang up and reset.
I guess too many requests are accumulated for all
prime numbers up to 32 and detected as hangup.
By adding wait, requests are processed on each prime number and not
accumulated. The test runs for 8.5sec.
Change-Id: I0d3732a202fef90d192fb
Quoting Yokoyama, Caz (2019-03-21 17:38:21)
> It took 35-120sec because some of engines hang up and reset.
> I guess too many requests are accumulated for all
> prime numbers up to 32 and detected as hangup.
> By adding wait, requests are processed on each prime number and not
> accumulated. The te
On 3/21/19 10:14 AM, Sujaritha Sundaresan wrote:
Adding a call to intel_uc_suspend in i915_gem_suspend, which
is a common point for the suspend/resume and hibernate paths.
This fixes an unbalanced call that causes issues with the CTB
register/deregister.
Cc: Daniele Ceraolo Spurio
Cc: Chris W
1 - 100 of 206 matches
Mail list logo
