Hi all,
New -testing cycle with cool stuff:
- skl wm fixes (Lyude, Matt, Maarten)
- cleanup of kdev/drm_dev/i915_dev handling (David Weinehall)
- make (most) encoders take advantage of atomic states (Maarten)
- MMAP_GTT_VERSION driver param to announce that gtt mmaps are reliable (Chris)
- allow c
On Mon, 2016-08-15 at 19:36 -0300, Paulo Zanoni wrote:
> Ever since I started working on FBC I was already aware that FBC can
> really amplify the FIFO underrun symptoms. On systems where FIFO
> underruns were harmless error messages, enabling FBC would cause the
> underruns to give black screens.
One more thing to add, if allocate the ringbuffer not from stolen memory but
normal memory, issue is gone.
static int intel_alloc_ringbuffer_obj(struct drm_device *dev,
struct intel_ringbuffer *ringbuf)
{
struct drm_i915_gem_object *obj;
obj
== Series Details ==
Series: Enable upfront link training on DDI platforms (rev3)
URL : https://patchwork.freedesktop.org/series/10821/
State : failure
== Summary ==
Series 10821v3 Enable upfront link training on DDI platforms
http://patchwork.freedesktop.org/api/1.0/series/10821/revisions/3/m
On Thu, Sep 01, 2016 at 09:55:10PM +0100, Chris Wilson wrote:
> The error state itself is guarded by a spinlock (admittedly even that is
> overkill for a single pointer!) and doesn't require us to take the
> struct_mutex in the debugfs/sysfs interface. Removing the struct_mutex
> removes one more p
From: Ander Conselvan de Oliveira
Decouple intel_dp_set_link_params() from struct intel_crtc_state. This
will be useful for implementing DP upfront link training.
v2:
* Rebased on atomic state changes (Manasi)
Reviewed-by: Durgadoss R
Signed-off-by: Ander Conselvan de Oliveira
Signed-off-by:
From: Jim Bride
Add the PLL selection code for HSW/BDW/BXT/SKL into a stand-alone function
in order to allow for the implementation of a platform neutral upfront
link training function.
v3:
* Add Hooks for all DDI platforms into this standalone function
v2:
* Change the macro to use dev_priv in
Split out the DisplayPort and HDMI pll setup code into separate
functions and refactor the DP code that calculates the pll
so that it doesn't depend on crtc state.
This will be used for acquiring port pll when doing
upfront link training.
Reviewed-by: Durgadoss R
Signed-off-by: Manasi Navare
---
From: Jim Bride
Split out the DisplayPort and HDMI pll setup code into separate
functions and refactor the DP code does not directly depend on
crtc state, so that the code can be used for upfront link training.
Reviewed-by: Manasi Navare
Signed-off-by: Jim Bride
---
drivers/gpu/drm/i915/intel
From: Durgadoss R
To support USB type C alternate DP mode, the display driver needs to
know the number of lanes required by the DP panel as well as number
of lanes that can be supported by the type-C cable. Sometimes, the
type-C cable may limit the bandwidth even if Panel can support
more lanes.
From: Ander Conselvan de Oliveira
The value of ddi_pll_sel is derived from the selection of shared dpll,
so just calculate the final value when necessary.
v2: Actually remove it from crtc state and delete remaining usages. (CI)
Reviewed-by: Durgadoss R
Signed-off-by: Ander Conselvan de Oliveir
From: Dhinakaran Pandiyan
Wrap the max. vswing check in a separate function.
This makes the clock recovery phase of DP link training cleaner
Signed-off-by: Dhinakaran Pandiyan
---
drivers/gpu/drm/i915/intel_dp_link_training.c | 16
1 file changed, 12 insertions(+), 4 deletions
From: Durgadoss R
Split out of bxt_ddi_pll_select() the logic that calculates the pll
dividers and dpll_hw_state into a new function that doesn't depend on
crtc state. This will be used for enabling the port pll when doing
upfront link training.
v2:
* Refactored code so that bxt_clk_div need not
According to the DisplayPort Spec, in case of Clock Recovery failure
the link training sequence should fall back to the lower link rate
followed by lower lane count until CR succeeds.
On CR success, the sequence proceeds with Channel EQ.
In case of Channel EQ failures, it should fallback to
lower l
Fix the number of tries in channel euqalization link training sequence
according to DP 1.2 Spec. It returns a boolean depending on channel
equalization pass or failure.
Signed-off-by: Dhinakaran Pandiyan
Signed-off-by: Manasi Navare
---
drivers/gpu/drm/i915/intel_dp_link_training.c | 57 +++
While configuring the pipe during modeset, it should loop
starting from max clock and max lane count reducing the
lane count and clock in each iteration until the requested mode
rate is less than or equal to available link BW.
Signed-off-by: Manasi Navare
---
drivers/gpu/drm/i915/intel_dp.c | 9
From: Jim Bride
Add upfront link training to intel_dp_mst_mode_valid() so that we know
topology constraints before we validate the legality of modes to be
checked.
Call the function that loops through the link rates and lane counts
starting from highest supported link rate and lane count for trai
From: Dhinakaran Pandiyan
This function cleans up clock recovery loop in link training compliant
tp Dp Spec 1.2. It tries the clock recovery 5 times for the same voltage
or until max voltage swing is reached and removes the additional non
compliant retries. This function now returns a boolean val
This patch series enables upfront link training on DDI platforms
(SKL/BDW/HSW/BXT) for DP SST and MST.
They are based on some of the patches submitted earlier by
Ander and Durgadoss.
The upfront link training had to be factored out of long pulse
hanlder because of deadlock issues seen on DP MST ca
Split intel_ddi_pre_enable() into encoder type specific versions that
don't depend on crtc_state. The necessary parameters are passed as
function arguments. This split will be necessary for implementing DP
upfront link training.
v3:
* Rebased onto latest kernel (Manasi)
v2:
* Rebased onto kernel v
== Series Details ==
Series: drm/i915: Drop mutex around clearing error state
URL : https://patchwork.freedesktop.org/series/11911/
State : failure
== Summary ==
Series 11911v1 drm/i915: Drop mutex around clearing error state
http://patchwork.freedesktop.org/api/1.0/series/11911/revisions/1/mb
The error state itself is guarded by a spinlock (admittedly even that is
overkill for a single pointer!) and doesn't require us to take the
struct_mutex in the debugfs/sysfs interface. Removing the struct_mutex
removes one more potential blockage when trying to debug a deadlock.
Signed-off-by: Chr
On Thu, Sep 01, 2016 at 05:51:09PM +0100, Dave Gordon wrote:
> The gem_exec_nop test generally works by submitting batches to an
> engine as fast as possible for a fixed time, then finally calling
> gem_sync() to wait for the last submitted batch to complete. The
> time-per-batch is then calculated
On 01/09/16 15:48, Chris Wilson wrote:
On Thu, Sep 01, 2016 at 03:17:44PM +0100, Dave Gordon wrote:
This macro was recently updated to skip testing for non-existent or
uninteresting engines by using ffs() to directly find the next engine of
interest. However, it required the introduction of a ca
The gem_exec_nop test generally works by submitting batches to an engine
as fast as possible for a fixed time, then finally calling gem_sync() to
wait for the last submitted batch to complete. The time-per-batch is
then calculated as the total elapsed time, divided by the total number
of batche
On Thu, Sep 01, 2016 at 03:17:44PM +0100, Dave Gordon wrote:
> This macro was recently updated to skip testing for non-existent or
> uninteresting engines by using ffs() to directly find the next engine of
> interest. However, it required the introduction of a caller-provided
> temporary variable,
On to, 2016-09-01 at 15:17 +0100, Dave Gordon wrote:
> This macro was recently updated to skip testing for non-existent or
> uninteresting engines by using ffs() to directly find the next engine of
> interest. However, it required the introduction of a caller-provided
> temporary variable, which so
This macro was recently updated to skip testing for non-existent or
uninteresting engines by using ffs() to directly find the next engine of
interest. However, it required the introduction of a caller-provided
temporary variable, which some people regard as inelegant. So, this
patch provides anothe
Reviewed-by: Joonas Lahtinen
Regards, Joonas
--
Joonas Lahtinen
Open Source Technology Center
Intel Corporation
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
On to, 2016-09-01 at 15:32 +0300, Joonas Lahtinen wrote:
> On to, 2016-09-01 at 13:27 +0100, Chris Wilson wrote:
> >
> > On Thu, Sep 01, 2016 at 12:20:18PM -, Patchwork wrote:
> > >
> > > Test prime_vgem:
> > > Subgroup basic-fence-flip:
> > > pass -> FAIL
On to, 2016-09-01 at 13:27 +0100, Chris Wilson wrote:
> On Thu, Sep 01, 2016 at 12:20:18PM -, Patchwork wrote:
> > Test prime_vgem:
> > Subgroup basic-fence-flip:
> > pass -> FAIL (fi-bdw-5557u)
> Hmm, this is probably some condition I forgot to drain before
On Thu, Sep 01, 2016 at 12:20:18PM -, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: Use atomic for dev_priv->mm.bsd_engine_dispatch_index
> URL : https://patchwork.freedesktop.org/series/11890/
> State : failure
>
> == Summary ==
>
> Series 11890v1 drm/i915: Use atomic for
== Series Details ==
Series: drm/i915: Use atomic for dev_priv->mm.bsd_engine_dispatch_index
URL : https://patchwork.freedesktop.org/series/11890/
State : failure
== Summary ==
Series 11890v1 drm/i915: Use atomic for dev_priv->mm.bsd_engine_dispatch_index
http://patchwork.freedesktop.org/api/1
On Thu, Sep 01, 2016 at 02:58:21PM +0300, Joonas Lahtinen wrote:
> Use atomic type and operands for dev_priv->mm.bsd_engine_dispatch_index
> to avoid one struct_mutex locking scenario.
>
> Cc: Chris Wilson
> Cc: Imre Deak
> Cc: Zhao Yakui
> Cc: Daniel Vetter
> Signed-off-by: Joonas Lahtinen
Use atomic type and operands for dev_priv->mm.bsd_engine_dispatch_index
to avoid one struct_mutex locking scenario.
Cc: Chris Wilson
Cc: Imre Deak
Cc: Zhao Yakui
Cc: Daniel Vetter
Signed-off-by: Joonas Lahtinen
---
drivers/gpu/drm/i915/i915_drv.h| 2 +-
drivers/gpu/drm/i915/i915
== Series Details ==
Series: Prep. for DP audio MST support (rev8)
URL : https://patchwork.freedesktop.org/series/11129/
State : failure
== Summary ==
Series 11129v8 Prep. for DP audio MST support
http://patchwork.freedesktop.org/api/1.0/series/11129/revisions/8/mbox/
Test kms_cursor_legacy:
On 31/08/16 17:09, Daniel Vetter wrote:
Again move it from the unmaintainable csv into DOC free-form overview
sections.
Cc: Lionel Landwerlin
Signed-off-by: Daniel Vetter
---
Documentation/gpu/drm-kms.rst| 12 +
Documentation/gpu/kms-properties.csv | 5
drivers/gpu/dr
On 31/08/16 17:09, Daniel Vetter wrote:
For both the new degamm/lut/gamma atomic combo, and the old legacy
gamma tables.
Signed-off-by: Daniel Vetter
---
drivers/gpu/drm/Makefile| 2 +-
drivers/gpu/drm/drm_color_mgmt.c| 248
drivers/gpu/
== Series Details ==
Series: drm/i915: read out slice/subslice masks (rev2)
URL : https://patchwork.freedesktop.org/series/33/
State : failure
== Summary ==
Series 33v2 drm/i915: read out slice/subslice masks
http://patchwork.freedesktop.org/api/1.0/series/33/revisions/2/mbox/
Test gem_exec_s
== Series Details ==
Series: More splitting&documenting for drm_crtc.c
URL : https://patchwork.freedesktop.org/series/11834/
State : failure
== Summary ==
Series 11834v1 More splitting&documenting for drm_crtc.c
http://patchwork.freedesktop.org/api/1.0/series/11834/revisions/1/mbox/
Test kms_
The changes in this version are primarily in i915. I have carried over
Takashi's R-B from the previous version and removed Ville's.
From: Pandiyan, Dhinakaran
Sent: Thursday, September 01, 2016 12:50 AM
To: intel-gfx@lists.freedesktop.org
Cc: libin.y...@lin
DP MST provides the capability to send multiple video and audio streams
through a single port. This requires the API's between i915 and audio
drivers to distinguish between multiple audio capable displays that can be
connected to a port. Currently only the port identity is shared in the
APIs. This
42 matches
Mail list logo
