Reviewed-by: Samuel Li
On 2018-11-28 3:20 a.m., Daniel Vetter wrote:
> On Wed, Nov 28, 2018 at 08:17:04AM +0100, Maarten Lankhorst wrote:
>> Op 27-11-18 om 18:34 schreef Daniel Vetter:
>>> KMS drivers really should all be able to restore their display state
>>> on resume without fbcon helping
On Wed, Nov 28, 2018 at 10:02:22AM +0200, Jani Nikula wrote:
> On Tue, 06 Nov 2018, Lucas De Marchi wrote:
> > From: Rodrigo Vivi
> >
> > RANGE makes it longer, but clear. We are also going to add a check for
> > the display part, so make rename to GT.
>
> I also still have my doubts about this
On Wed, Nov 28, 2018 at 03:58:19PM +0200, Mika Kuoppala wrote:
> Chris Wilson writes:
>
> > Mark A0 as the one and only pre-production variant of Kabylake and
> > remove its couple of workarounds, consigning them to the annals of
> > history.
> >
> > Signed-off-by: Chris Wilson
> > Cc: Joonas
On Tue, Nov 27, 2018 at 11:28:38PM -0800, José Roberto de Souza wrote:
> As stated in struct drm_encoder, crtc field should only be used
> by non-atomic drivers.
>
> So here caching the pipe id in intel_psr_enable() what is way more
> simple and efficient than at every call to
>
Regards
Shashank
On 11/27/2018 10:10 PM, Uma Shankar wrote:
This patch adds a DP colorspace property, enabling
userspace to switch to various supported colorspaces.
This will help enable BT2020 along with other colorspaces.
v2: Addressed Maarten and Ville's review comments. Enhanced
the
Regards
Shashank
On 11/27/2018 10:10 PM, Uma Shankar wrote:
This patch adds a HDMI colorspace property, enabling
userspace to switch to various supported colorspaces.
This will help enable BT2020 along with other colorspaces.
v2: Addressed Maarten and Ville's review comments. Enhanced
the
== Series Details ==
Series: HDCP1.4 fixes (rev9)
URL : https://patchwork.freedesktop.org/series/38978/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10932
Summary
---
**SUCCESS**
No regressions
== Series Details ==
Series: drm/i915/selftests: Terminate hangcheck sanitycheck forcibly
URL : https://patchwork.freedesktop.org/series/53165/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
DESCEND objtool
CHK include/generated/compile.h
CC [M]
== Series Details ==
Series: Return only active connectors for get_resources ioctl
URL : https://patchwork.freedesktop.org/series/53163/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10931
Summary
---
On Wed, 2018-11-28 at 14:39 +, Chris Wilson wrote:
> Quoting Stanislav Lisovskiy (2018-11-28 13:52:10)
> > Currently kernel might allocate different connector ids
> > for the same outputs in case of DP MST, which seems to
> > confuse userspace. There are can be different connector
> > ids in
== Series Details ==
Series: Return only active connectors for get_resources ioctl
URL : https://patchwork.freedesktop.org/series/53163/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9e2ef2ea4d7b Return only active connectors for get_resources ioctl
-:41:
== Series Details ==
Series: series starting with [1/2] drm/i915: Add kbl A0 to preproduction
detection list
URL : https://patchwork.freedesktop.org/series/53162/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10930
== Series Details ==
Series: drm/i915/psr: Get pipe id following atomic guidelines
URL : https://patchwork.freedesktop.org/series/53132/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5213_full -> Patchwork_10924_full
Am Dienstag, 27. November 2018, 18:34:24 CET schrieb Daniel Vetter:
> KMS drivers really should all be able to restore their display state
> on resume without fbcon helping out. So make this the default.
>
> Since I'm not entirely foolish, make it only a default, which drivers
> can still
== Series Details ==
Series: drm/i915: Mark up early pre-production Kabylakes
URL : https://patchwork.freedesktop.org/series/53161/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10929
Summary
---
On Wed, Nov 28, 2018 at 02:29:53PM +, Shankar, Uma wrote:
>
>
> >-Original Message-
> >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
> >Brian Starkey
> >Sent: Wednesday, November 28, 2018 5:27 PM
> >To: Shankar, Uma
> >Cc: Syrjala, Ville ;
Quoting Stanislav Lisovskiy (2018-11-28 13:52:10)
> Currently kernel might allocate different connector ids
> for the same outputs in case of DP MST, which seems to
> confuse userspace. There are can be different connector
> ids in the list, which could be assigned to the same
> output, while
== Series Details ==
Series: Return only active connectors for GET_RESOURCES
URL : https://patchwork.freedesktop.org/series/53159/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10928
Summary
---
>-Original Message-
>From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of
>Brian Starkey
>Sent: Wednesday, November 28, 2018 5:27 PM
>To: Shankar, Uma
>Cc: Syrjala, Ville ; jo...@kwiboo.se; intel-
>g...@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
Quoting Patchwork (2018-11-28 14:18:05)
> == Series Details ==
>
> Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
> registers on ring init (rev2)
> URL : https://patchwork.freedesktop.org/series/53154/
> State : success
>
> == Summary ==
>
> CI Bug Log - changes
== Series Details ==
Series: Return only active connectors for GET_RESOURCES
URL : https://patchwork.freedesktop.org/series/53159/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
1b346bba5470 Return only active connectors for GET_RESOURCES
-:39: CHECK:PARENTHESIS_ALIGNMENT:
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init (rev2)
URL : https://patchwork.freedesktop.org/series/53154/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10927
If all else fails and we are stuck eternally waiting for the undying
request, abandon all hope.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/selftests/intel_hangcheck.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git
HDCP1.4 key load process varies between Intel platform to platform.
For Gen9 platforms except BXT and GLK, HDCP1.4 key is loaded using
the GT Driver Mailbox interface. So all GEN9_BC platforms will use
the GT Driver Mailbox interface for HDCP1.4 key load.
v2:
Using the IS_GEN9_BC for filtering
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init (rev2)
URL : https://patchwork.freedesktop.org/series/53154/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/ringbuffer:
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init (rev2)
URL : https://patchwork.freedesktop.org/series/53154/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
82f42511a45b drm/i915/ringbuffer: Clear
>-Original Message-
>From: Brian Starkey [mailto:brian.star...@arm.com]
>Sent: Wednesday, November 28, 2018 5:12 PM
>To: Shankar, Uma
>Cc: intel-gfx@lists.freedesktop.org; dri-de...@lists.freedesktop.org;
>Lankhorst,
>Maarten ; Syrjala, Ville
>;
>Sharma, Shashank ; jo...@kwiboo.se;
Chris Wilson writes:
> Mark A0 as the one and only pre-production variant of Kabylake and
> remove its couple of workarounds, consigning them to the annals of
> history.
>
> Signed-off-by: Chris Wilson
> Cc: Joonas Lahtinen
> Cc: Jani Nikula
> Cc: Rodrigo Vivi
> Cc: Mika Kuoppala
My two
No need to carry kbl preproduction workarounds anymore,
so drop them.
Signed-off-by: Mika Kuoppala
---
drivers/gpu/drm/i915/intel_lrc.c | 12
drivers/gpu/drm/i915/intel_workarounds.c | 5 -
2 files changed, 17 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_lrc.c
Currently kernel might allocate different connector ids
for the same outputs in case of DP MST, which seems to
confuse userspace. There are can be different connector
ids in the list, which could be assigned to the same
output, while being in different states.
This results in issues, like external
It is time to prune kbl preproduction bits from the
driver. Add kbl revision A0 to preproduction hw list.
Signed-off-by: Mika Kuoppala
---
drivers/gpu/drm/i915/i915_drv.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpu/drm/i915/i915_drv.c b/drivers/gpu/drm/i915/i915_drv.c
index
Mark A0 as the one and only pre-production variant of Kabylake and
remove its couple of workarounds, consigning them to the annals of
history.
Signed-off-by: Chris Wilson
Cc: Joonas Lahtinen
Cc: Jani Nikula
Cc: Rodrigo Vivi
Cc: Mika Kuoppala
---
drivers/gpu/drm/i915/i915_drv.c | 1
Currently kernel might allocate different connector ids
for the same outputs in case of DP MST, which seems to
confuse userspace. There are can be different connector
ids in the list, which could be assigned to the same
output, while being in different states.
This results in issues, like external
Currently we face a severe problem on Braswell that manifests as invalid
ppGTT accesses. The code tries to maintain the PDP (page directory
pointers) inside the context in two ways, direct write into the context
and a pipelined LRI update. The direct write into the context is
fundamentally racy as
Quoting Mika Kuoppala (2018-11-28 13:21:41)
> Chris Wilson writes:
> > diff --git a/drivers/gpu/drm/i915/intel_lrc.c
> > b/drivers/gpu/drm/i915/intel_lrc.c
> > index 08fd9b12e4d7..3464058cbfc7 100644
> > --- a/drivers/gpu/drm/i915/intel_lrc.c
> > +++ b/drivers/gpu/drm/i915/intel_lrc.c
> > @@
Hi,
> -Original Message-
> From: Intel-gfx [mailto:intel-gfx-boun...@lists.freedesktop.org] On Behalf Of
> Patchwork
> Sent: keskiviikko 28. marraskuuta 2018 15.20
> To: Chris Wilson
> Cc: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] ✓ Fi.CI.BAT: success for series starting
Chris Wilson writes:
> Currently we allocate a scratch page for each engine, but since we only
> ever write into it for post-sync operations, it is not exposed to
> userspace nor do we care for coherency. As we then do not care about its
> contents, we can use one page for all, reducing our
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init
URL : https://patchwork.freedesktop.org/series/53154/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10926
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init
URL : https://patchwork.freedesktop.org/series/53154/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/ringbuffer: Clear
== Series Details ==
Series: series starting with [1/3] drm/i915/ringbuffer: Clear semaphore sync
registers on ring init
URL : https://patchwork.freedesktop.org/series/53154/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
300cb53c30ed drm/i915/ringbuffer: Clear semaphore sync
Currently we allocate a scratch page for each engine, but since we only
ever write into it for post-sync operations, it is not exposed to
userspace nor do we care for coherency. As we then do not care about its
contents, we can use one page for all, reducing our allocations and
avoid complications
Currently we face a severe problem on Braswell that manifests as invalid
ppGTT accesses. The code tries to maintain the PDP (page directory
pointers) inside the context in two ways, direct write into the context
and a pipelined LRI update. The direct write into the context is
fundamentally racy as
Ensure that the sync registers are cleared every time we restart the
ring to avoid stale values from creeping in from random neutrinos.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_ringbuffer.c | 7 +++
1 file changed, 7 insertions(+)
diff --git
Hi,
On Tue, Nov 27, 2018 at 10:10:40PM +0530, Uma Shankar wrote:
> This patch series creates a new connector property to program
> colorspace to sink devices. Modern sink devices support more
> than 1 type of colorspace like 601, 709, BT2020 etc. This helps
> to switch based on content type which
ci/linux/commits/Manasi-Navare/drm-dsc-Modify-DRM-helper-to-return-complete-DSC-color-depth-capabilities/20181128-095026
base: git://anongit.freedesktop.org/drm-intel for-linux-next
:: branch date: 10 hours ago
:: commit date: 10 hours ago
>> drivers/gpu/drm/i915/intel_vdsc.c:404:22
== Series Details ==
Series: series starting with [CI,v12,01/23] drm/dsc: Modify DRM helper to
return complete DSC color depth capabilities
URL : https://patchwork.freedesktop.org/series/53113/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5212_full -> Patchwork_10923_full
Hi Uma,
On Tue, Nov 27, 2018 at 10:10:42PM +0530, Uma Shankar wrote:
> This patch adds a DP colorspace property, enabling
> userspace to switch to various supported colorspaces.
> This will help enable BT2020 along with other colorspaces.
>
> v2: Addressed Maarten and Ville's review comments.
On Wed, Nov 07, 2018 at 04:05:52PM -0800, José Roberto de Souza wrote:
> When suspending or unloading the driver, it needs to release the
> TC ports so HW can change it state without wait for driver handshake.
According to
https://bugs.freedesktop.org/show_bug.cgi?id=108070#c26
this patch
== Series Details ==
Series: drm: Fix up drm_atomic_state_helper.[hc] extraction
URL : https://patchwork.freedesktop.org/series/53148/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10925 =
== Summary - SUCCESS ==
No regressions found.
External URL:
== Series Details ==
Series: drm/i915/ringbuffer: Clear semaphore sync registers on ring init
URL : https://patchwork.freedesktop.org/series/53112/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5212_full -> Patchwork_10922_full =
== Summary - WARNING ==
Minor unknown
== Series Details ==
Series: drm: Fix up drm_atomic_state_helper.[hc] extraction
URL : https://patchwork.freedesktop.org/series/53148/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
9288282eb7cc drm: Fix up drm_atomic_state_helper.[hc] extraction
-:413:
I've misplaced two functions by accident:
- drm_atomic_helper_duplicate_state is really part of the
resume/suspend/shutdown device-wide helpers.
- drm_atomic_helper_legacy_gamma_set is part of the legacy ioctl
compat helpers.
Move them both back.
Fixes: 9ef8a9dc4b21 ("drm: Extract
== Series Details ==
Series: drm/i915: implement EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT (rev2)
URL : https://patchwork.freedesktop.org/series/49669/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5212_full -> Patchwork_10921_full =
== Summary - WARNING ==
Minor
Hi Dave,
Here's the next pull request for v4.21. :)
drm-misc-next-2018-11-28:
drm-misc-next for v4.21:
Core Changes:
- Merge drm_info.c into drm_debugfs.c
- Complete the fake drm_crtc_commit's hw_done/flip_done sooner.
- Remove deprecated drm_obj_ref/unref functions. All drivers use get/put
Quoting Jani Nikula (2018-11-28 10:02:22)
> On Tue, 06 Nov 2018, Lucas De Marchi wrote:
> > From: Rodrigo Vivi
> >
> > RANGE makes it longer, but clear. We are also going to add a check for
> > the display part, so make rename to GT.
>
> I also still have my doubts about this patch I'm afraid.
Quoting Ho, Kenny (2018-11-27 17:41:17)
> On Tue, Nov 27, 2018 at 4:46 AM Joonas Lahtinen
> wrote:
> > I think a more abstract property "% of GPU (processing power)" might
> > be a more universal approach. One can then implement that through
> > subdividing the resources or timeslicing them,
On Tue, 27 Nov 2018, Manasi Navare wrote:
> From: Matt Atwood
>
> According to DP spec (2.9.3.1 of DP 1.4) if
> EXTENDED_RECEIVER_CAPABILITY_FIELD_PRESENT is set the addresses in DPCD
> 02200h through 0220Fh shall contain the DPRX's true capability. These
> values will match 0h through
On Tue, Nov 27, 2018 at 08:44:14PM -0500, Lyude Paul wrote:
> On Tue, 2018-11-27 at 20:44 +0100, Daniel Vetter wrote:
> > On Tue, Nov 27, 2018 at 12:48:59PM -0500, Lyude Paul wrote:
> > > On Mon, 2018-11-26 at 22:22 +0100, Daniel Vetter wrote:
> > > > On Mon, Nov 26, 2018 at 10:04:21PM +0100,
== Series Details ==
Series: drm/i915/psr: Get pipe id following atomic guidelines
URL : https://patchwork.freedesktop.org/series/53132/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5213 -> Patchwork_10924 =
== Summary - WARNING ==
Minor unknown changes coming with
On Tue, Nov 27, 2018 at 12:38:44PM -0800, Eric Anholt wrote:
> Daniel Vetter writes:
>
> > On Mon, Nov 26, 2018 at 04:36:21PM -0800, Eric Anholt wrote:
> >> Noralf Trønnes writes:
> >> > +static void drm_gem_shmem_vm_close(struct vm_area_struct *vma)
> >> > +{
> >> > +struct
On Wed, Nov 28, 2018 at 08:17:04AM +0100, Maarten Lankhorst wrote:
> Op 27-11-18 om 18:34 schreef Daniel Vetter:
> > KMS drivers really should all be able to restore their display state
> > on resume without fbcon helping out. So make this the default.
> >
> > Since I'm not entirely foolish, make
On Tue, 06 Nov 2018, Lucas De Marchi wrote:
> From: Rodrigo Vivi
>
> RANGE makes it longer, but clear. We are also going to add a check for
> the display part, so make rename to GT.
I also still have my doubts about this patch I'm afraid. I've expressed
the concern before, but here goes again.
101 - 162 of 162 matches
Mail list logo
