Howdy,
I have a thinkpad P70 with debian testing and 4.11.6 kernel.
A recent-ish upgrade broke something and now I'm getting loads of spam
in my Xorg.log
[ 5031.435] (WW) modeset(0): flip queue failed: Invalid argument
[ 5031.435] (WW) modeset(0): Page flip failed: Invalid argument
[ 5031.435]
Hey,
Op 03-07-17 om 12:19 schreef Abdiel Janulgue:
> When descending thru debugfs directory. Doing this tends to
> takes forever. CRC pipe read tests for this are already
> covered under kms_pipe_crc_basic.
>
> v2: Be more verbose that the check is meant for the crtc control data
>
> Signed-off-by
Hello,
Found that there is a BDW GPU hang bug with iommu enabled in free desktop
Bugzilla since two years ago, and it is still not closed:
https://bugs.freedesktop.org/show_bug.cgi?id=89360
The last duplicated issue is 99964 which was reproduced with linux-4.10. Does
anyone know if linux-4.11
2017년 07월 05일 00:18에 Daniel Vetter 이(가) 쓴 글:
> From: Thierry Reding
>
> The FB helper core now supports deferred setup, so the driver's custom
> implementation can be removed.
Reviewed-by: Inki Dae
Tested-by: Inki Dae
Thanks,
Inki Dae
>
> v2: Drop NULL check, drm_fb_helper_hotplug_event h
== Series Details ==
Series: series starting with [1/4] drm/i915/cnl: Introduce initial Cannonlake
Workarounds.
URL : https://patchwork.freedesktop.org/series/26881/
State : success
== Summary ==
Series 26881v1 Series without cover letter
https://patchwork.freedesktop.org/api/1.0/series/26881
== Series Details ==
Series: x86/gpu: CNL uses the same GMS values as SKL
URL : https://patchwork.freedesktop.org/series/26880/
State : success
== Summary ==
Series 26880v1 x86/gpu: CNL uses the same GMS values as SKL
https://patchwork.freedesktop.org/api/1.0/series/26880/revisions/1/mbox/
Te
On 04/07/17 09:09, Chris Wilson wrote:
Triggering a GPU reset for one engine affects another, notably
corrupting the context status buffer (CSB) effectively losing track of
inflight requests.
Adding a few printks:
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
ind
== Series Details ==
Series: drm/i915/cnl: Add force wake for gen10+.
URL : https://patchwork.freedesktop.org/series/26879/
State : success
== Summary ==
Series 26879v1 drm/i915/cnl: Add force wake for gen10+.
https://patchwork.freedesktop.org/api/1.0/series/26879/revisions/1/mbox/
Test gem_e
WA to disable replay buffer destination buffer arbitration optimization.
Same Wa on previous platforms has a different name:
WaToEnableHwFixForPushConstHWBug
Signed-off-by: Rodrigo Vivi
Reviewed-by: Mika Kuoppala
---
drivers/gpu/drm/i915/intel_engine_cs.c | 4
1 file changed, 4 insertion
This bit enables hardware that will change the approximation used for distances
calculations for AA wide lines so that they are rendered more accurately.
The default value for this bit leaves the legacy behavior. There is no good
reason to not enable the new approximation except if comparing to pr
WA forTDS handle reallocation getting dropped by SDE,
which may result in PS attribute corruption.
Disable enhanced SBE vertex caching in COMMON_SLICE_CHICKEN2 offset.
v2: Make it until B0 as spec tells. (by Mika).
Signed-off-by: Rodrigo Vivi
Reviewed-by: Mika Kuoppala
---
drivers/gpu/drm/i91
Let's inherit workarounds from previous platforms that
according to wa_database and BSpec are still valid for
Cannonlake.
v2: Add missed workarounds.
v3: Rebase
v4: Remove bad chunk that was added to rc6 disable. (Ander)
Also remove A0 W/a that are not needed anymore.
v5: Rebase on top of CFL.
From: Paulo Zanoni
So don't forget to reserve its stolen memory bits.
v2: Add ack and remove "TODO" from commit message.
Signed-off-by: Paulo Zanoni
Signed-off-by: Rodrigo Vivi
Acked-by: Thomas Gleixner
---
arch/x86/kernel/early-quirks.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/a
By spec there is no change on force wake registers
for Cannonlake. Let's reuse gen9 one.
v2: Adding missing case for the write part. (Tvrtko)
v3: Rebase on recent tree.
v4: Make it for gen9+ instead adding gen10 only. (by Joonas).
Cc: Tvrtko Ursulin
Signed-off-by: Rodrigo Vivi
Reviewed-by: Joon
Hi Oscar,
I had missed this patch here, but noticed now that I was refreshing
and testing more cnl tests before re-submitting them.
First of all I believe we need to remove the A0 w/a. I don't believe
we will ever see one. So I'm removing all A0 exclusive W/a from the
patches as well.
I also gav
== Series Details ==
Series: vfio: ABI for mdev display dma-buf operation (rev2)
URL : https://patchwork.freedesktop.org/series/26786/
State : success
== Summary ==
Series 26786v2 vfio: ABI for mdev display dma-buf operation
https://patchwork.freedesktop.org/api/1.0/series/26786/revisions/2/mb
Add VFIO_DEVICE_QUERY_GFX_PLANE ioctl command to let user mode query and
get the plan and its related information.
The dma-buf's life cycle is handled by user mode and tracked by kernel.
The returned fd in struct vfio_device_query_gfx_plane can be a new
fd or an old fd of a re-exported dma-buf. Ho
v9->v10:
1) remove dma-buf management
2) refine the ABI API VFIO_DEVICE_QUERY_GFX_PLANE
3) track the dma-buf create and release in kernel mode
v8->v9:
1) refine the dma-buf ioctl definition
2) add a lock to protect the dmabuf list
3) move drm format change to a separate patch
4) codes cleanup
v7
Patch pushed to libdrm master.
On Fri, Jun 30, 2017 at 2:28 PM, Rodrigo Vivi wrote:
> No functional change. Just organizing the code
> so it gets clear for future platforms.
>
> Paulo deserves credits becuase he was the one
> that just noticed this IS_9XX was in the wrong position
> after CNL pat
On Wed, 2017-07-05 at 11:04 +0300, Paul Kocialkowski wrote:
> When a CRC comparison error occurs, it is quite useful to get a dump
> of both the frame obtained from the chamelium and the reference in
> order
> to compare them.
>
> This implements the frame dump, with a configurable path that enabl
yep, makes total sense and you were right... no timeout..
Reviewed-by: Rodrigo Vivi
On Fri, Jun 30, 2017 at 5:29 AM, Imre Deak wrote:
> On Thu, Jun 29, 2017 at 01:06:01PM -0700, Rodrigo Vivi wrote:
>> This patch makes sense and seems the right thing to do...
>>
>> However removing the sanitize
On Wed, Jul 5, 2017 at 1:12 PM, Chris Wilson
wrote:
> the drm_file parameter is unused, so remove it.
>
> Signed-off-by: Chris Wilson
> Cc: Dave Airlie
> ---
> drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 ++
> drivers/gpu/drm/drm_syncobj.c | 8 +++-
> include/drm/drm_syncobj.h
On Wed, 2017-07-05 at 11:04 +0300, Paul Kocialkowski wrote:
> This introduces a chamelium_write_frame_to_png function that saves a
> Chamelium frame dump to a png file. This should be useful when a
> frame
> comparison with a reference fails.
>
> Signed-off-by: Paul Kocialkowski
> ---
> lib/igt_
NAK. You're right that these don't actually give us any advantage over
just using CRCs and are just slower, however I left these tests in here
moreso just so we had something to actually test the frame dumping
functions so that we could avoid regressing them by accident since
we're the only users o
On Wed, 2017-07-05 at 16:34 -0400, Lyude Paul wrote:
> So a couple of notes here that will make it a lot easier for me to
> review these in the future
>
> * When you're doing a new revision of a patch series, it's helpful
> to
> keep it in the same email thread as the original v1 so it's easie
So a couple of notes here that will make it a lot easier for me to
review these in the future
* When you're doing a new revision of a patch series, it's helpful to
keep it in the same email thread as the original v1 so it's easier
to keep track of in people's mail clients (as well as avoidi
== Series Details ==
Series: drm: Remove unused drm_file parameter to drm_syncobj_replace_fence()
URL : https://patchwork.freedesktop.org/series/26868/
State : success
== Summary ==
Series 26868v1 drm: Remove unused drm_file parameter to
drm_syncobj_replace_fence()
https://patchwork.freedeskt
On Wed, Jul 05, 2017 at 10:09:21AM +0200, Peter Rosin wrote:
> On 2017-07-05 08:08, Daniel Vetter wrote:
> > On Tue, Jul 04, 2017 at 12:36:56PM +0200, Peter Rosin wrote:
> >> Hi!
> >>
> >> While trying to get CLUT support for the atmel_hlcdc driver, and
> >> specifically for the emulated fbdev inte
On Wed, Jul 05, 2017 at 04:49:00PM +0100, Chris Wilson wrote:
> The last user of these (i915.ko) no longer does. We can slim down the
> core GEM object by removing the unused 8 bytes.
>
> Signed-off-by: Chris Wilson
Time to celebrate!
Applied, thanks.
-Daniel
> ---
> include/drm/drm_gem.h | 1
On Wed, Jul 05, 2017 at 12:08:15PM +0200, Maarten Lankhorst wrote:
> Op 04-07-17 om 17:18 schreef Daniel Vetter:
> > We could probably hit this already with our current async fbdev init,
> > but it's much easier to hit this with the new deferred fbdev setup
> > that I'm working on polishing.
> >
>
the drm_file parameter is unused, so remove it.
Signed-off-by: Chris Wilson
Cc: Dave Airlie
---
drivers/gpu/drm/amd/amdgpu/amdgpu_cs.c | 6 ++
drivers/gpu/drm/drm_syncobj.c | 8 +++-
include/drm/drm_syncobj.h | 3 +--
3 files changed, 6 insertions(+), 11 deletions(
On Wed, Jul 05, 2017 at 06:25:30PM +, Navare, Manasi D wrote:
> On Fri, Jun 30, 2017 at 09:33:48AM -0700, Manasi Navare wrote:
> > This patch fixes the DP AUX CH timeouts observed during CI IGT tests
> > thus fixing the CI failures. This is done by adding a quirk for a
> > particular PCI devi
On Fri, Jun 30, 2017 at 09:33:48AM -0700, Manasi Navare wrote:
> This patch fixes the DP AUX CH timeouts observed during CI IGT tests
> thus fixing the CI failures. This is done by adding a quirk for a
> particular PCI device that requires the panel power cycle delay (T12)
> to be set to 800ms w
On 2017-07-05 08:08, Daniel Vetter wrote:
> On Tue, Jul 04, 2017 at 12:36:56PM +0200, Peter Rosin wrote:
>> Hi!
>>
>> While trying to get CLUT support for the atmel_hlcdc driver, and
>> specifically for the emulated fbdev interface, I received some
>> push-back that my feeble in-driver attempts sho
== Series Details ==
Series: drm/i915: Only free the oldest stale object before a fresh allocation
URL : https://patchwork.freedesktop.org/series/26864/
State : success
== Summary ==
Series 26864v1 drm/i915: Only free the oldest stale object before a fresh
allocation
https://patchwork.freedes
Inspired by Tvrtko's critique of the reaping of the stale contexts
before allocating a new one, also limit the freed object reaping to the
oldest stale object before allocating a fresh object. Unlike contexts,
objects may have radically different sizes of backing storage, but
similar to contexts, w
== Series Details ==
Series: drm: Remove pending_read_domains and pending_write_domain
URL : https://patchwork.freedesktop.org/series/26860/
State : success
== Summary ==
Series 26860v1 drm: Remove pending_read_domains and pending_write_domain
https://patchwork.freedesktop.org/api/1.0/series/2
The last user of these (i915.ko) no longer does. We can slim down the
core GEM object by removing the unused 8 bytes.
Signed-off-by: Chris Wilson
---
include/drm/drm_gem.h | 15 ---
1 file changed, 15 deletions(-)
diff --git a/include/drm/drm_gem.h b/include/drm/drm_gem.h
index 663d
Quoting Matthew Auld (2017-07-03 15:14:58)
> v2: mock test page support configurations and add MI_STORE_DWORD test
>
> v3: run all mockable huge page tests on all platforms via the mock_device
Another thought is to have multiple objects in the ppgtt, to avoid any
issues hidden by effectively alwa
On 05/07/2017 15:26, Chris Wilson wrote:
Currently, we move all unreferenced contexts to an RCU free list and
then onto a worker for eventual reaping. To compensate against this
growing into a long list with frequent allocations starving the system
of available memory, before we allocate a new c
On 05/07/2017 15:26, Chris Wilson wrote:
Before we create a new context, we try and reap all the stale contexts
(i.e. those that are freed but waiting for a worker to come and return
their allocations to the system). Before we do this, we retire all
requests so that we clear any inflight no long
== Series Details ==
Series: Fixed16.16 wrapper cleanup & wm optimization (rev4)
URL : https://patchwork.freedesktop.org/series/25692/
State : success
== Summary ==
Series 25692v4 Fixed16.16 wrapper cleanup & wm optimization
https://patchwork.freedesktop.org/api/1.0/series/25692/revisions/4/mb
== Series Details ==
Series: series starting with [1/4] drm/i915: Check new context against
kernel_context after reporting an error
URL : https://patchwork.freedesktop.org/series/26854/
State : success
== Summary ==
Series 26854v1 Series without cover letter
https://patchwork.freedesktop.org/
On Wed, Jul 05, 2017 at 01:03:46PM +0300, Jani Nikula wrote:
> On Tue, 04 Jul 2017, David Weinehall wrote:
> > This reverts commit ae25eceab616d16a07bcaa434b84463d58a3bdc3.
> >
> > The introduction of dynamic backlight control causes
> > Lenovo ThinkPad X1 Carbon 4th Gen to boot to a black screen;
From: "Kumar, Mahesh"
GEN > 9 require transition WM to be programmed if IPC is enabled.
This patch calculates & enable transition WM for supported platforms.
If transition WM is enabled, Plane read requests are sent at high
priority until filling above the transition watermark, then the
requests
From: "Kumar, Mahesh"
This patch adds IPC support for platforms. This patch enables IPC
only for BXT/KBL platform as for SKL recommendation is to keep it disabled.
IPC (Isochronous Priority Control) is the hardware feature, which
dynamically controls the memory read priority of Display.
When IPC
From: "Kumar, Mahesh"
CNL:A & CNL:B have same workaround as KBL to increase wm level latency
by 4us if IPC is enabled.
Signed-off-by: Mahesh Kumar
---
drivers/gpu/drm/i915/intel_pm.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers
From: "Kumar, Mahesh"
IF IPC is enabled LINETIME_WM value should be half of calculated value
line time = ROUNDDOWN(1/2 * Calculated Line Time)
Earlier code was rounding-up the value, But updated Bspec says we should
take the ROUNDDOWN. This patch corrects that as well.
Signed-off-by: Mahesh Ku
From: "Kumar, Mahesh"
use same cpp value in different phase of plane WM caluclation.
Signed-off-by: Mahesh Kumar
Reviewed-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_pm.c | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drive
From: "Kumar, Mahesh"
height of plane was require to swap width/height in case of 90/270
rotation. Now src structure contains already swapped values, So we
don't have to calculate height of the plane.
Signed-off-by: Mahesh Kumar
Reviewed-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/intel_pm
From: "Kumar, Mahesh"
This patch make naming of fixed-point wrappers consistent
operation__<1st operand>_<2nd operand>
also shorten the name for fixed_16_16 to fixed16
s/u32_to_fixed_16_16/u32_to_fixed16
s/fixed_16_16_to_u32/fixed16_to_u32
s/fixed_16_16_to_u32_round_up/fixed16_to_u32_round_up
s/
From: "Kumar, Mahesh"
Plane configuration parameters doesn't change for each WM-level
calculation. Currently we compute same parameters 8 times for each
wm-level.
This patch optimizes it by calculating these parameters in beginning
& reuse during each level-wm calculation.
Signed-off-by: Mahesh
From: "Kumar, Mahesh"
This patch introduce addition wrapper for fixed point 16.16 operations.
Which will be used by later patches to avoid direct member variables
access of fixed_16_16_t structure.
add_fixed16 : takes 2 fixed_16_16_t variable & returns fixed_16_16_t
add_fixed16_u32 : takes fixed
From: "Kumar, Mahesh"
This patch combines fixed_16_16_div & fixed_16_16_div_u64 wrappers.
And new fixed_16_16_div wrapper always performs division operation in
u64 internally, to avoid any data loss which was happening in earlier
version of wrapper.
earlier wrapper was converting u32 to fixed16 i
This series Include patches for:
clean fixed16.16 naming & make them consistent
optimize wm calculation code
enable/Implement trans wm calculation
Changes Since V1:
- Split fixed16 cleanup code in more logical patches (Maarten)
- make intel_compute_linetime_wm function st
From: "Kumar, Mahesh"
This patch creates a new function for clamping u64 to fixed16.
And make use of this function in other fixed16 wrappers.
Signed-off-by: Mahesh Kumar
Reviewed-by: Maarten Lankhorst
---
drivers/gpu/drm/i915/i915_drv.h | 28
1 file changed, 12 in
We need to reap the stale contexts for all new contexts, be they created
by user in i915_gem_context_ioctl or from opening a new file in
i915_gem_context_open. Both paths may be called very frequently
accumulating many stale contexts before any worker has a chance to run
and free their memory.
Fix
Before we create a new context, we try and reap all the stale contexts
(i.e. those that are freed but waiting for a worker to come and return
their allocations to the system). Before we do this, we retire all
requests so that we clear any inflight no longer used contexts (who are
only being kept al
Currently, we move all unreferenced contexts to an RCU free list and
then onto a worker for eventual reaping. To compensate against this
growing into a long list with frequent allocations starving the system
of available memory, before we allocate a new context we reap all the
stale contexts. This
Avoid any pointer dereference in inspecting a potential PTR_ERR by
checking for the error pointer before checking for an invalid context.
Signed-off-by: Chris Wilson
Reviewed-by: Tvrtko Ursulin
---
drivers/gpu/drm/i915/i915_gem_context.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-
Quoting Tvrtko Ursulin (2017-07-05 14:50:57)
>
> On 05/07/2017 14:18, Chris Wilson wrote:
> > We need to reap the stale contexts for all new contexts, be they created
> > by user in i915_gem_context_ioctl or from opening a new file in
> > i915_gem_context_open. Both paths may be called very freque
On 05/07/2017 14:18, Chris Wilson wrote:
We need to reap the stale contexts for all new contexts, be they created
by user in i915_gem_context_ioctl or from opening a new file in
i915_gem_context_open. Both paths may be called very frequently
accumulating many stale contexts before any worker has
On 05/07/2017 14:18, Chris Wilson wrote:
Avoid any pointer dereference in inspecting a potential PTR_ERR by
checking for the error pointer before checking for an invalid context.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_gem_context.c | 5 ++---
1 file changed, 2 insertions(
== Series Details ==
Series: series starting with [1/2] drm/i915: Check new context against
kernel_context after reporting an error
URL : https://patchwork.freedesktop.org/series/26851/
State : success
== Summary ==
Series 26851v1 Series without cover letter
https://patchwork.freedesktop.org/
On 27/06/2017 09:02, Tvrtko Ursulin wrote:
On 26/06/2017 17:09, Daniel Vetter wrote:
On Fri, Jun 23, 2017 at 12:31:39PM +0100, Tvrtko Ursulin wrote:
From: Tvrtko Ursulin
Small series which saves test execution time by removing the
redundant tests.
Tvrtko Ursulin (4):
igt: Remove defaul
We need to reap the stale contexts for all new contexts, be they created
by user in i915_gem_context_ioctl or from opening a new file in
i915_gem_context_open. Both paths may be called very frequently
accumulating many stale contexts before any worker has a chance to run
and free their memory.
Fix
Avoid any pointer dereference in inspecting a potential PTR_ERR by
checking for the error pointer before checking for an invalid context.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i915_gem_context.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/gpu/d
== Series Details ==
Series: drm/i915/selftests: Exercise independence of per-engine resets
URL : https://patchwork.freedesktop.org/series/26849/
State : success
== Summary ==
Series 26849v1 drm/i915/selftests: Exercise independence of per-engine resets
https://patchwork.freedesktop.org/api/1.
On Wed, Jul 05, 2017 at 11:46:14AM +0300, Laurent Pinchart wrote:
> Hi Ville,
>
> On Tuesday 04 Jul 2017 15:44:02 Ville Syrjälä wrote:
> > On Tue, Jul 04, 2017 at 01:56:07PM +0200, Andrzej Hajda wrote:
> > > On 03.07.2017 21:19, ville.syrj...@linux.intel.com wrote:
> > >> From: Ville Syrjälä
> >
If all goes well, resetting one engine should not affect the operation of
any others. So to test this, we setup a continuous stream of requests
onto to each of the "innocent" engines whilst constantly resetting our
target engine.
Signed-off-by: Chris Wilson
Cc: Mika Kuoppala
Cc: Michel Thierry
On Wed, Jul 05, 2017 at 03:49:51PM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 7/5/2017 3:46 PM, Ville Syrjälä wrote:
> > On Wed, Jul 05, 2017 at 08:48:40AM +0530, Sharma, Shashank wrote:
> >> Regards
> >>
> >> Shashank
> >>
> >>
> >> On 7/4/2017 9:26 PM, Ville Syrjälä wrote:
Op 04-07-17 om 17:18 schreef Daniel Vetter:
> FB helper code falls back to a 1024x768 mode if no outputs are connected
> or don't report back any modes upon initialization. This can be annoying
> because outputs that are added to FB helper later on can't be used with
> FB helper if they don't suppo
Regards
Shashank
On 7/5/2017 3:46 PM, Ville Syrjälä wrote:
On Wed, Jul 05, 2017 at 08:48:40AM +0530, Sharma, Shashank wrote:
Regards
Shashank
On 7/4/2017 9:26 PM, Ville Syrjälä wrote:
On Tue, Jul 04, 2017 at 07:41:51PM +0530, Shashank Sharma wrote:
YCBCR420 modes are supported only on HD
On 03/07/2017 11:14, Chris Wilson wrote:
Many years ago, long before requests, we tried doing this. We never
quite got it right, but now with requests we have the tracking to do the
job properly!
Add a few words on the benefits in certain use cases/benchmarks.
One of the stall points for ge
On Wed, Jul 05, 2017 at 08:48:40AM +0530, Sharma, Shashank wrote:
> Regards
>
> Shashank
>
>
> On 7/4/2017 9:26 PM, Ville Syrjälä wrote:
> > On Tue, Jul 04, 2017 at 07:41:51PM +0530, Shashank Sharma wrote:
> >> YCBCR420 modes are supported only on HDMI 2.0 capable sources.
> >> This patch adds a
On Wed, Jul 05, 2017 at 12:09:19PM +0530, Mahesh Kumar wrote:
> Hi,
>
>
> On Tuesday 04 July 2017 08:11 PM, Ville Syrjälä wrote:
> > On Mon, Jul 03, 2017 at 09:28:00PM +0530, Mahesh Kumar wrote:
> >> Hi,
> >>
> >>
> >> On Monday 03 July 2017 07:32 PM, Ville Syrjälä wrote:
> >>> On Sat, Jul 01, 20
Op 04-07-17 om 17:18 schreef Daniel Vetter:
> We could probably hit this already with our current async fbdev init,
> but it's much easier to hit this with the new deferred fbdev setup
> that I'm working on polishing.
>
> Cc: Maarten Lankhorst
> Reported-by: Maarten Lankhorst
> Signed-off-by: Dan
On Tue, 04 Jul 2017, David Weinehall wrote:
> This reverts commit ae25eceab616d16a07bcaa434b84463d58a3bdc3.
>
> The introduction of dynamic backlight control causes
> Lenovo ThinkPad X1 Carbon 4th Gen to boot to a black screen;
> presumably the backlight is off.
Oh, I thought reverting just this
== Series Details ==
Series: drm/i915: Only skip updating execobject.offset after error
URL : https://patchwork.freedesktop.org/series/26847/
State : success
== Summary ==
Series 26847v1 drm/i915: Only skip updating execobject.offset after error
https://patchwork.freedesktop.org/api/1.0/series
I was being overly paranoid in not updating the execobject.offset after
performing the fallback copy where we set reloc.presumed_offset to -1.
The thinking was to ensure that a subsequent NORELOC execbuf would be
forced to process the invalid relocations. However this is overkill so
long as we *onl
Hi Ville,
On Tuesday 04 Jul 2017 15:44:02 Ville Syrjälä wrote:
> On Tue, Jul 04, 2017 at 01:56:07PM +0200, Andrzej Hajda wrote:
> > On 03.07.2017 21:19, ville.syrj...@linux.intel.com wrote:
> >> From: Ville Syrjälä
> >>
> >> Appedix F of HDMI 2.0 says that some HDMI sink may fail to switch from
When a CRC comparison error occurs, it is quite useful to get a dump
of both the frame obtained from the chamelium and the reference in order
to compare them.
This implements the frame dump, with a configurable path that enables
the use of this feature.
Signed-off-by: Paul Kocialkowski
---
lib/
The frame dump tests provide no additional functionality over CRC tests
and are considerably slower. Thus, these tests should be considered as
poorer duplicates and removed.
Signed-off-by: Paul Kocialkowski
---
tests/chamelium.c | 53 -
1 file
This introduces a chamelium_write_frame_to_png function that saves a
Chamelium frame dump to a png file. This should be useful when a frame
comparison with a reference fails.
Signed-off-by: Paul Kocialkowski
---
lib/igt_chamelium.c | 40
lib/igt_chamelium
This introduces CRC calculation for reference frames, instead of using
hardcoded values for them. The rendering of reference frames may differ
from machine to machine, especially due to font rendering, and the
frame itself may change with subsequent IGT changes.
These differences would cause the C
85 matches
Mail list logo
