== Series Details ==
Series: CI: Revert "net/sch_generic: Shut up noise"
URL : https://patchwork.freedesktop.org/series/60699/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8fbf6ed5c78a CI: Revert "net/sch_generic: Shut up noise"
-:32: ERROR:MISSING_SIGN_OFF: Missing Signed-off
This reverts commit a9f840bdd2fd4cb07a669f1c3112b804218b4aba.
But instead tune it down to an error, hopefully that way we can
perhaps capture something ...
Cc: Martin Peres
---
net/sched/sch_generic.c | 9 ++---
1 file changed, 2 insertions(+), 7 deletions(-)
diff --git a/net/sched/sch_gen
== Series Details ==
Series: Reg: igt@kms_pipe_crc_basic@* CRC mismatch test failures
URL : https://patchwork.freedesktop.org/series/60697/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6089 -> Patchwork_13023
Summary
-
On Wednesday, May 15, 2019 5:00:40 PM CEST Chris Wilson wrote:
> Janus, some old patches that may be of use for shutdown prior to kexec.
> -Chris
Hi Chris,
Thanks for sharing.
I'm only not sure why you mentioned kexec. I have an impression someone else
was talking about kexec recently so maybe
This patch fixes the igt@kms_pipe_crc_basic@* test failures due to CRC mismatch
on CI BYT squawks chromebook as reported in:
https://bugs.freedesktop.org/show_bug.cgi?id=103191
These CRC mismatch test failures happen consistently on BYT squawks chromebook
These test failures happen very intermitte
display_pipe_crc_irq_handler() skips the first CRC for all GPUs and the
second CRC for GEN8+ GPUs. The second CRC is invalid even for BYT which
is a GEN7 GPU. So, skip the second CRC even for GEN7 GPUs.
Cc: Jani Nikula
Cc: Tomi Sarvela
Cc: Petri Latvala
Cc: Ville Syrjälä
Cc: Maarten Lankhorst
Hi Daniel,
On 5/10/19 4:34 PM, Daniel Vetter wrote:
On Fri, May 10, 2019 at 01:21:59PM +0800, Lu Baolu wrote:
Forward to i915 mailing list and post the question again so people knows
what are the key concerns.
The background is that Linux community is going to collect and report
the reserved m
== Series Details ==
Series: drm/i915/perf: Refactor oa object to better manage resources (rev3)
URL : https://patchwork.freedesktop.org/series/60176/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6086_full -> Patchwork_13022_full
==
== Series Details ==
Series: series starting with [1/2] drm/i915: Hook into the reboot notifier to
cancel outstanding GPU operations
URL : https://patchwork.freedesktop.org/series/60676/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6086_full -> Patchwork_13021_full
=
Quoting Chris Wilson (2019-05-15 20:57:18)
> Quoting Tvrtko Ursulin (2019-05-15 11:58:20)
> >
> > On 08/05/2019 11:09, Chris Wilson wrote:
> > > + igt_assert_f(load > 0.90,
> > > + "engine %d (class:instance %d:%d) was
> > > found to be only %.
Hi Da.*,
Some more fixes for -next. As predicted more panfrost cleanup.
We also have 4 msm patches that Rob and I figured should just go through -misc
instead of spinning up an msm-fixes branch. If we pooled together all msm fixes
for 5.2, maybe the -fixes branch would have been warranted, but we
Quoting Tvrtko Ursulin (2019-05-15 11:58:20)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > The submit-fence + load_balancing apis allow for us to execute a named
> > pair of engines in parallel; that this by submitting a request to one
> > engine, we can then use the generated submit-fence to s
Quoting Tvrtko Ursulin (2019-05-15 11:49:45)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > Exercise the in-kernel load balancer checking that we can distribute
> > batches across the set of ctx->engines to avoid load.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > tests/Makefile.am
On 2019-05-15 21:45, Ville Syrjälä wrote:
> On Wed, May 15, 2019 at 07:33:10PM +, Jonas Karlman wrote:
>> On 2019-05-15 21:10, Ville Syrjälä wrote:
>>> On Tue, May 14, 2019 at 11:06:23PM +0530, Uma Shankar wrote:
This patch adds a blob property to get HDR metadata
information from use
On Wed, May 15, 2019 at 07:33:10PM +, Jonas Karlman wrote:
> On 2019-05-15 21:10, Ville Syrjälä wrote:
> > On Tue, May 14, 2019 at 11:06:23PM +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
On Tue, May 14, 2019 at 11:06:25PM +0530, Uma Shankar wrote:
> HDR metadata block is introduced in CEA-861.3 spec.
> Parsing the same to get the panel's HDR metadata.
>
> v2: Rebase and added Ville's POC changes to the patch.
>
> v3: No Change
>
> v4: Addressed Shashank's review comments
>
> v5
Quoting Tvrtko Ursulin (2019-05-14 13:57:26)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > Add a new mode for some more stress, submit the all-engines tests
> > simultaneously, a stream per engine.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > tests/i915/gem_exec_whisper.c | 27 ++
Quoting Tvrtko Ursulin (2019-05-15 07:37:18)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > v2: Test each shared context is its own timeline and allows request
> > reordering between shared contexts.
> >
> > Signed-off-by: Chris Wilson
> > Cc: Joonas Lahtinen
> > Cc: Tvrtko Ursulin
> > Cc: M
On 2019-05-15 21:10, Ville Syrjälä wrote:
> On Tue, May 14, 2019 at 11:06:23PM +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.
>>
>> It also implements get() and set() functions f
On Wed, May 15, 2019 at 08:59:37AM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: Patchwork [mailto:patchw...@emeril.freedesktop.org]
> >Sent: Wednesday, May 15, 2019 6:54 AM
> >To: Shankar, Uma
> >Cc: intel-gfx@lists.freedesktop.org
> >Subject: ✗ Fi.CI.IGT: failure for Ad
On Tue, May 14, 2019 at 11:06:34PM +0530, Uma Shankar wrote:
> Added state readout for DRM infoframe and enabled
> state validation for DRM infoframe.
>
> v2: Addressed Ville's review comments and dropped the
> unused drm infoframe read at intel_hdmi_init.
>
> Signed-off-by: Uma Shankar
> ---
>
On Tue, May 14, 2019 at 11:06:31PM +0530, Uma Shankar wrote:
> This patch enables modeset whenever HDR metadata
> needs to be updated to sink.
>
> v2: Addressed Shashank's review comments.
>
> v3: Added Shashank's RB.
>
> v4: Addressed Ville's review comments.
>
> Signed-off-by: Ville Syrjälä
On Tue, May 14, 2019 at 11:06:26PM +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
Quoting Tvrtko Ursulin (2019-05-14 13:41:13)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > Exercise cloning contexts, an extension of merely creating one.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > tests/Makefile.sources | 1 +
> > tests/i915/gem_ctx_clone.c | 460 ++
On Tue, May 14, 2019 at 11:06:23PM +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.
>
> It also implements get() and set() functions for HDR output
> metadata property.The blob data
Quoting Tvrtko Ursulin (2019-05-14 11:15:12)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > Check that the extended create interface accepts setparam.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > tests/i915/gem_ctx_create.c | 225 ++--
> > 1 file changed,
Quoting Chris Wilson (2019-05-15 20:06:45)
> Quoting Tvrtko Ursulin (2019-05-14 13:27:38)
> >
> > On 08/05/2019 11:09, Chris Wilson wrote:
> > > Check that the extended create interface accepts setparam.
> > >
> > > Signed-off-by: Chris Wilson
> > > ---
> > > tests/i915/gem_ctx_create.c | 225
Quoting Tvrtko Ursulin (2019-05-14 13:27:38)
>
> On 08/05/2019 11:09, Chris Wilson wrote:
> > Check that the extended create interface accepts setparam.
> >
> > Signed-off-by: Chris Wilson
> > ---
> > tests/i915/gem_ctx_create.c | 225 ++--
> > 1 file changed,
== Series Details ==
Series: drm/i915/perf: Refactor oa object to better manage resources (rev3)
URL : https://patchwork.freedesktop.org/series/60176/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6086 -> Patchwork_13022
Su
== Series Details ==
Series: series starting with [1/5] drm/i915: Mark semaphores as complete on
unsubmit out if payload was started
URL : https://patchwork.freedesktop.org/series/60671/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6085_full -> Patchwork_13020_full
=
== Series Details ==
Series: drm/i915/perf: Refactor oa object to better manage resources (rev3)
URL : https://patchwork.freedesktop.org/series/60176/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/perf: Refactor oa object to better manage res
== Series Details ==
Series: drm/i915/perf: Refactor oa object to better manage resources (rev3)
URL : https://patchwork.freedesktop.org/series/60176/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
3c6e6cc91331 drm/i915/perf: Refactor oa object to better manage resources
-:1522:
The oa object manages the oa buffer and must be allocated when the user
intends to read performance counter snapshots. This can be achieved by
making the oa object part of the stream object which is allocated when a
stream is opened by the user.
Attributes in the oa object that are gen-specific ar
On Wed, May 15, 2019 at 10:11:34AM +0100, Lionel Landwerlin wrote:
On 14/05/2019 19:14, Umesh Nerlige Ramappa wrote:
On Tue, May 14, 2019 at 10:34:49AM +0100, Lionel Landwerlin wrote:
Hi Umesh,
I just noticed this different between v1 & v2.
My understanding is that if destroy() is called, stre
== Series Details ==
Series: series starting with [1/2] drm/i915: Hook into the reboot notifier to
cancel outstanding GPU operations
URL : https://patchwork.freedesktop.org/series/60676/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6086 -> Patchwork_13021
===
Hi Noralf.
On Wed, May 15, 2019 at 04:51:04PM +0200, Noralf Trønnes wrote:
> Hi Sam,
>
> [looks like Thundebird decided to throw away my reply, so I'll try again]
I guess it awaits moderator approval as the from address was different
from what you otherwise used - I got both mails.
>
> Den 15.0
Janus, some old patches that may be of use for shutdown prior to kexec.
-Chris
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
When the system is being shutdown, we no longer care about the results
of outstanding GPU operations, and so we can cancel them to speed up the
reboot. This helps most if we happen to be stuck waiting for a timeout
to declare the GPU hung.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/i91
Certain monitors, e.g. Dell, do not like it when we reboot with an
active link, leaving them in a confused state where they refuse to
renegotiate the link after the reboot. If we hook into the reboot
notifier, we can switch off any active link before rebooting, leaving
everything in a consistent, h
Hi Sam,
[looks like Thundebird decided to throw away my reply, so I'll try again]
Den 15.05.2019 11.04, skrev Sam Ravnborg:
> Hi Noralf.
>
> I have read through the cahnes a copuple of times not and feel confident
> to add my r-b if the comments are considered.
>
> On Mon, May 06, 2019 at 08:01
Den 15.05.2019 11.09, skrev Sam Ravnborg:
> Hi Noralf.
>
> On Mon, May 06, 2019 at 08:01:35PM +0200, Noralf Trønnes wrote:
>> Move the modeset commit code to drm_client_modeset.
>> No changes except exporting API.
>>
>> v2: Move to drm_client_modeset.c instead of drm_client.c
>>
>> Signed-off-by
On Tue, 02 Apr 2019, Aditya Swarup wrote:
> Adding N & CTS values for 10/12 bit deep color from Appendix C
> table in HDMI 2.0 spec. The correct values for N is not chosen
> automatically by hardware for deep color modes.
>
> v2: Remove redundant code and make it generic.(Jani)
>
> Signed-off-by:
On Wed, 2019-05-15 at 06:43 +0100, Tvrtko Ursulin wrote:
> On 15/05/2019 01:06, Rodrigo Vivi wrote:
> > On Tue, May 14, 2019 at 06:32:01PM +, Summers, Stuart wrote:
> > > On Tue, 2019-05-14 at 17:53 +0100, Chris Wilson wrote:
> > > > Quoting Stuart Summers (2019-05-14 17:46:52)
> > > > > To all
== Series Details ==
Series: series starting with [1/5] drm/i915: Mark semaphores as complete on
unsubmit out if payload was started
URL : https://patchwork.freedesktop.org/series/60671/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6085 -> Patchwork_13020
===
== Series Details ==
Series: series starting with [1/5] drm/i915: Mark semaphores as complete on
unsubmit out if payload was started
URL : https://patchwork.freedesktop.org/series/60671/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
44f76ee8e2e2 drm/i915: Mark semaphores as co
With the disappearance of NEWCLIENT, we no longer need to provide the
priority boost on preemption in order to prevent repeated gazumping,
and we can remove the dead code.
Signed-off-by: Chris Wilson
Cc: Tvrtko Ursulin
---
drivers/gpu/drm/i915/gt/intel_lrc.c | 59 +
Avoid charging us for the presumed busywait if the request was preempted
after successfully using semaphores to reduce inter-engine latency.
v2: Bump the priority to reflect the lack of semaphores now required.
References: ca6e56f654e7 ("drm/i915: Disable semaphore busywaits on saturated
systems
The handling of the no-preemption priority level imposes the restriction
that we need to maintain the implied ordering even though preemption is
disabled. Otherwise we may end up with an AB-BA deadlock across multiple
engine due to a real preemption event reordering the no-preemption
WAITs. To reso
In commit b7404c7ecb38 ("drm/i915: Bump ready tasks ahead of
busywaits"), I tried cutting a corner in order to not install a signal
for each of our dependencies, and only listened to requests on which we
were intending to busywait. The compromise that was made was that
instead of then being able to
Commit 1413b2bc0717 ("drm/i915: Trim NEWCLIENT boosting") had the
intended consequence of not allowing a sequence of work that merely
crossed into a new engine the privilege to be promoted to NEWCLIENT
status. It also had the unintended consequence of actually making
NEWCLIENT effective on heavily
== Series Details ==
Series: Add HDR Metadata Parsing and handling in DRM layer (rev10)
URL : https://patchwork.freedesktop.org/series/25091/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6081_full -> Patchwork_13017_full
S
On 15/05/2019 12:48, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-05-15 12:44:41)
On 10/05/2019 14:31, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-05-08 13:10:51)
From: Tvrtko Ursulin
A new workload command for enabling a load balanced context map (aka
Virtual Engine). Example usa
On Fri 2019-05-10 17:20:15, Daniel Vetter wrote:
> On Fri, May 10, 2019 at 11:28 AM Petr Mladek wrote:
> >
> > On Thu 2019-05-09 22:06:33, Daniel Vetter wrote:
> > > console_trylock, called from within printk, can be called from pretty
> > > much anywhere. Including try_to_wake_up. Note that this
Quoting Tvrtko Ursulin (2019-05-15 12:44:41)
>
> On 10/05/2019 14:31, Chris Wilson wrote:
> > Quoting Tvrtko Ursulin (2019-05-08 13:10:51)
> >> From: Tvrtko Ursulin
> >>
> >> A new workload command for enabling a load balanced context map (aka
> >> Virtual Engine). Example usage:
> >>
> >>B.1
On 10/05/2019 14:31, Chris Wilson wrote:
Quoting Tvrtko Ursulin (2019-05-08 13:10:51)
From: Tvrtko Ursulin
A new workload command for enabling a load balanced context map (aka
Virtual Engine). Example usage:
B.1
This turns on load balancing for context one, assuming it has already been
c
On 08/05/2019 11:09, Chris Wilson wrote:
The submit-fence + load_balancing apis allow for us to execute a named
pair of engines in parallel; that this by submitting a request to one
engine, we can then use the generated submit-fence to submit a second
request to another engine and have it execut
On 08/05/2019 11:09, Chris Wilson wrote:
Exercise the in-kernel load balancer checking that we can distribute
batches across the set of ctx->engines to avoid load.
Signed-off-by: Chris Wilson
---
tests/Makefile.am |1 +
tests/Makefile.sources |1 +
tests/i915/g
On Wed, May 15, 2019 at 3:25 PM Chris Wilson wrote:
>
> Quoting Masahiro Yamada (2019-05-15 05:37:53)
> > The top level Makefile adds -Wall globally:
> >
> > KBUILD_CFLAGS := -Wall -Wundef -Werror=strict-prototypes -Wno-trigraphs
> > \
> >
> > I see two "-Wall" added for compiling under drive
+ Martin for real.
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
> Shankar, Uma
> Sent: keskiviikko 15. toukokuuta 2019 12.00
> To: intel-gfx@lists.freedesktop.org
> Subject: Re: [Intel-gfx] ✗ Fi.CI.IGT: failure for Add HDR Metadata P
== Series Details ==
Series: drm/i915: drop unneeded -Wall addition
URL : https://patchwork.freedesktop.org/series/60652/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6085_full -> Patchwork_13019_full
Summary
---
**
On Wed, May 15, 2019 at 11:33:31AM +0200, Daniel Vetter wrote:
> On Tue, Apr 16, 2019 at 01:36:02PM +0300, Jani Nikula wrote:
> > Signed-off-by: Jani Nikula
> > ---
> > drivers/gpu/drm/i915/Makefile| 1 +
> > drivers/gpu/drm/i915/intel_display.c | 474 +--
> > dr
On Tue, Apr 16, 2019 at 01:36:03PM +0300, Jani Nikula wrote:
> Signed-off-by: Jani Nikula
pipe_config_compare is used both for the atomic_check logic, and the
verifier. I think stuffing it into the verifier code is misplacing it as
much as e.g. stuffing it into intel_atomic_check.c file.
What I'
On Tue, Apr 16, 2019 at 01:36:02PM +0300, Jani Nikula wrote:
> Signed-off-by: Jani Nikula
> ---
> drivers/gpu/drm/i915/Makefile| 1 +
> drivers/gpu/drm/i915/intel_display.c | 474 +--
> drivers/gpu/drm/i915/intel_drv.h | 12 +
> drivers/gpu/drm/i915/intel_ve
Hi Noralf.
I have read through the cahnes a copuple of times not and feel confident
to add my r-b if the comments are considered.
On Mon, May 06, 2019 at 08:01:33PM +0200, Noralf Trønnes wrote:
> It now only contains the modeset so use that directly instead and attach
> a modeset array to drm_cli
Hi Noralf.
On Mon, May 06, 2019 at 08:01:34PM +0200, Noralf Trønnes wrote:
> This makes the necessary changes so the commit code can be moved out to
> drm_client as-is in the next patch. It's split up to ease review.
>
> Signed-off-by: Noralf Trønnes
Reviewed-by: Sam Ravnborg
_
Hi Noralf
On Mon, May 06, 2019 at 08:01:37PM +0200, Noralf Trønnes wrote:
> This prepares the modeset code so it can be moved out as-is in the next
> patch.
>
> v3: Remove stray newline
>
> Signed-off-by: Noralf Trønnes
> Reviewed-by: Maxime Ripard
Reviewed-by: Sam Ravnborg
__
Hi Noralf.
On Mon, May 06, 2019 at 08:01:35PM +0200, Noralf Trønnes wrote:
> Move the modeset commit code to drm_client_modeset.
> No changes except exporting API.
>
> v2: Move to drm_client_modeset.c instead of drm_client.c
>
> Signed-off-by: Noralf Trønnes
Reviewed-by: Sam Ravnborg
Assumes
On 14/05/2019 19:14, Umesh Nerlige Ramappa wrote:
On Tue, May 14, 2019 at 10:34:49AM +0100, Lionel Landwerlin wrote:
Hi Umesh,
I just noticed this different between v1 & v2.
My understanding is that if destroy() is called, stream should be the
same as dev_priv->perf.exclusive_stream.
If it's
>-Original Message-
>From: Patchwork [mailto:patchw...@emeril.freedesktop.org]
>Sent: Wednesday, May 15, 2019 6:54 AM
>To: Shankar, Uma
>Cc: intel-gfx@lists.freedesktop.org
>Subject: ✗ Fi.CI.IGT: failure for Add HDR Metadata Parsing and handling in DRM
>layer
>(rev10)
>
>== Series Detai
On 13/05/2019 20:45, john.c.harri...@intel.com wrote:
From: John Harrison
With virtual engines, it is no longer possible to know which specific
physical engine a given request will be executed on at the time that
request is generated. This means that the request itself must be engine
agnostic
Hi,
On Tue, 2019-05-14 at 16:28 +0200, Daniel Vetter wrote:
> On Tue, May 14, 2019 at 4:13 PM Paul Kocialkowski
> wrote:
> > Hi,
> >
> > On Tue, 2019-05-14 at 13:09 +0200, Daniel Vetter wrote:
> > > On Mon, May 13, 2019 at 7:14 PM Paul Kocialkowski
> > > wrote:
> > > > Hey,
> > > >
> > > > Le
On Wed, May 15, 2019 at 10:37:31AM +0300, Pekka Paalanen wrote:
> On Tue, 14 May 2019 16:34:01 +0200
> Daniel Vetter wrote:
>
> > On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> > >
> > > On Tue, 14 May 2019 13:02:09 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, May 14, 2019
Hi,
On Wed, 2019-05-15 at 10:37 +0300, Pekka Paalanen wrote:
> On Tue, 14 May 2019 16:34:01 +0200
> Daniel Vetter wrote:
>
> > On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> > > On Tue, 14 May 2019 13:02:09 +0200
> > > Daniel Vetter wrote:
> > >
> > > > On Tue, May 14, 2019 at 10:18
On Wed, May 15, 2019 at 09:43:24AM +0200, Paul Kocialkowski wrote:
> Hi,
>
> On Tue, 2019-05-14 at 16:28 +0200, Daniel Vetter wrote:
> > On Tue, May 14, 2019 at 4:13 PM Paul Kocialkowski
> > wrote:
> > > Hi,
> > >
> > > On Tue, 2019-05-14 at 13:09 +0200, Daniel Vetter wrote:
> > > > On Mon, May
Hi Dave & Daniel,
A fix to close a race opportunity between IRQ handler and RCU.
Two fixes that are also stable, disabling FBC on GLK and HSW EDP fastset
correction.
These patches definitely caused conflicts when merged, resolutions should
be all good.
Regards, Joonas
***
drm-intel-next-fixe
On Tue, 14 May 2019, Ville Syrjälä wrote:
> On Tue, May 14, 2019 at 03:13:19PM +0530, Swati Sharma wrote:
>> In this patch, a vfunc read_luts() is introduced to create a hw lut
>> i.e. lut having values read from gamma/degamma registers which will
>> later be used to compare with sw lut to validat
On Tue, 14 May 2019 16:34:01 +0200
Daniel Vetter wrote:
> On Tue, May 14, 2019 at 3:36 PM Pekka Paalanen wrote:
> >
> > On Tue, 14 May 2019 13:02:09 +0200
> > Daniel Vetter wrote:
> >
> > > On Tue, May 14, 2019 at 10:18 AM Ser, Simon wrote:
> > > >
> > > > On Tue, 2019-05-14 at 11:02 +0300
77 matches
Mail list logo
