== Series Details ==
Series: series starting with locking/lockdep: restore cross-release checks
(rev3)
URL : https://patchwork.freedesktop.org/series/51923/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5095 -> Patchwork_10738 =
== Summary - FAILURE ==
Serious unknown c
On 06/11/2018 21:51, Lucas De Marchi wrote:
This is the second version of the series trying to make GEN checks
more similar. These or roughly the changes from v1:
- We don't have a single macro receiving 2 or 3 parameters. Now there
is GT_GEN_RANGE(), and GT_GEN(). The firs is the conversion
From: Colin Ian King
Trivial fix to spelling mistake in DRM_INFO message
Signed-off-by: Colin Ian King
---
drivers/gpu/drm/i915/intel_csr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/intel_csr.c b/drivers/gpu/drm/i915/intel_csr.c
index fc7bd21fa586
On 06/11/2018 04:13, Ankit Navik wrote:
drm/i915: Context aware user agnostic EU/Slice/Sub-slice control within kernel
Current GPU configuration code for i915 does not allow us to change
EU/Slice/Sub-slice configuration dynamically. Its done only once while context
is created.
While particular
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
8da27d26559f drm/i915/icl: Fix combo PHY uninit
-:19: ERROR:BAD_SIGN_OFF: Unrecognized email addre
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/icl: Fix combo PHY uninit
Okay!
Commit: drm/i915/cnl+: Move t
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10739 =
== Summary - FAILURE ==
Serious unknown changes coming with Patch
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10739 =
== Summary - FAILURE ==
Serious unknown changes coming with Patch
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10739 =
== Summary - SUCCESS ==
No regressions found.
External URL:
h
== Series Details ==
Series: drm/i915/icl: Fix combo PHY HW context loss (rev2)
URL : https://patchwork.freedesktop.org/series/51970/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10739 =
== Summary - SUCCESS ==
No regressions found.
External URL:
h
== Series Details ==
Series: series starting with [v5,1/2] drm/i915/skl: Rework MOCS tables to keep
common part in a define
URL : https://patchwork.freedesktop.org/series/52108/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10740 =
== Summary - SUCCESS ==
== Series Details ==
Series: mm, drm/i915: Mark pinned shmemfs pages as unevictable (rev7)
URL : https://patchwork.freedesktop.org/series/25337/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
cbea68073add mm, drm/i915: mark pinned shmemfs pages as unevictable
-:161: CHECK:AVOID_
Hey Dave,
First pull for drm-next this cycle. There's been a lot of changes, so I
hope I recorded everything from the changelog correctly.
drm-misc-next-2018-11-07:
drm-misc-next for v4.21, part 1:
UAPI Changes:
- Add syncobj timeline support to drm.
Cross-subsystem Changes:
- Remove shared fen
== Series Details ==
Series: mm, drm/i915: Mark pinned shmemfs pages as unevictable (rev7)
URL : https://patchwork.freedesktop.org/series/25337/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10741 =
== Summary - SUCCESS ==
No regressions found.
Exter
== Series Details ==
Series: drm/i915: fix subslice mask array size
URL : https://patchwork.freedesktop.org/series/52110/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10742 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_10742 nee
== Series Details ==
Series: drm/i915: Rename full ppgtt configuration to be more generic (rev6)
URL : https://patchwork.freedesktop.org/series/49021/
State : failure
== Summary ==
Applying: drm/i915: Make 48bit full ppgtt configuration generic (v7)
Using index info to reconstruct a base tree.
== Series Details ==
Series: series starting with [v4,1/4] drm/i915/psr: Use intel_psr_exit() in
intel_psr_disable_source()
URL : https://patchwork.freedesktop.org/series/52113/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10743 =
== Summary - SUCCESS ==
== Series Details ==
Series: series starting with [1/3] drm/atomic: Use explicit old crtc state in
drm_atomic_add_affected_planes() (rev2)
URL : https://patchwork.freedesktop.org/series/51894/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e5ec4f59a037 drm/atomic: Use explicit
== Series Details ==
Series: series starting with [1/3] drm/atomic: Use explicit old crtc state in
drm_atomic_add_affected_planes() (rev2)
URL : https://patchwork.freedesktop.org/series/51894/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10745 =
== Summa
== Series Details ==
Series: drm/i915: HPD IRQ storm detection fixes (rev5)
URL : https://patchwork.freedesktop.org/series/51556/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: Fix possible race in intel_dp_add_mst_connector()
Okay!
Commit:
== Series Details ==
Series: drm/i915: HPD IRQ storm detection fixes (rev5)
URL : https://patchwork.freedesktop.org/series/51556/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096 -> Patchwork_10746 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https
== Series Details ==
Series: Make GEN macros more similar (rev2)
URL : https://patchwork.freedesktop.org/series/51860/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
d15504ef1f13 Revert "drm/i915: Kill GEN_FOREVER"
322b4c9622f1 drm/i915: Rename IS_GEN to GT_RANGE
0bbf4afc4405 dr
== Series Details ==
Series: Make GEN macros more similar (rev2)
URL : https://patchwork.freedesktop.org/series/51860/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: Revert "drm/i915: Kill GEN_FOREVER"
-drivers/gpu/drm/i915/selftests/../i915_drv.h:3705
== Series Details ==
Series: Forward Error Correction (rev7)
URL : https://patchwork.freedesktop.org/series/47848/
State : failure
== Summary ==
Applying: i915/dp/fec: Add fec_enable to the crtc state.
error: sha1 information is lacking or useless (drivers/gpu/drm/i915/intel_dp.c).
error: coul
== Series Details ==
Series: drm/dp_mst: Add some atomic state iterator macros
URL : https://patchwork.freedesktop.org/series/52130/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f9a06ea3b5c0 drm/dp_mst: Add some atomic state iterator macros
-:7: WARNING:COMMIT_MESSAGE: Missing
== Series Details ==
Series: drm/dp_mst: Add some atomic state iterator macros
URL : https://patchwork.freedesktop.org/series/52130/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/dp_mst: Add some atomic state iterator macros
Okay!
Commit: drm/dp_
== Series Details ==
Series: Make GEN macros more similar (rev2)
URL : https://patchwork.freedesktop.org/series/51860/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10747 =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_10747 need t
== Series Details ==
Series: drm/dp_mst: Improve VCPI helpers, use in nouveau (rev3)
URL : https://patchwork.freedesktop.org/series/51412/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
fefd28281a84 drm/dp_mst: Add some atomic state iterator macros
-:7: WARNING:COMMIT_MESSAGE: M
== Series Details ==
Series: drm/dp_mst: Improve VCPI helpers, use in nouveau (rev3)
URL : https://patchwork.freedesktop.org/series/51412/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/dp_mst: Add some atomic state iterator macros
Okay!
Commit: d
== Series Details ==
Series: drm/dp_mst: Add some atomic state iterator macros
URL : https://patchwork.freedesktop.org/series/52130/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10749 =
== Summary - SUCCESS ==
No regressions found.
External URL:
ht
== Series Details ==
Series: drm/dp_mst: Improve VCPI helpers, use in nouveau (rev3)
URL : https://patchwork.freedesktop.org/series/51412/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10750 =
== Summary - SUCCESS ==
No regressions found.
External UR
Quoting Zhenyu Wang (2018-11-07 04:31:37)
>
> Hi,
>
> Here's re-generated -fixes pull for 4.20. Mostly on fixing
> possible guest arbitrary update of GGTT entries, with one mask
> fix for chicken register, and with one to fix eDP warning in guest.
>
> Thanks.
Pulled. Thanks for re-spinning.
Re
On Mon, Nov 05, 2018 at 09:43:05AM +, Chris Wilson wrote:
> Exercising the gpu reloc path strenuously revealed an issue where the
> updated relocations (from MI_STORE_DWORD_IMM) were not being observed
> upon execution. After some experiments with adding pipecontrols (a lot
> of pipecontrols (3
== Series Details ==
Series: drm/i915/csr: fix spelling mistake "firmare" -> "firmware"
URL : https://patchwork.freedesktop.org/series/52153/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10751 =
== Summary - FAILURE ==
Serious unknown changes coming wi
Quoting Ville Syrjälä (2018-11-07 15:04:24)
> On Mon, Nov 05, 2018 at 09:43:05AM +, Chris Wilson wrote:
> > Exercising the gpu reloc path strenuously revealed an issue where the
> > updated relocations (from MI_STORE_DWORD_IMM) were not being observed
> > upon execution. After some experiments
== Series Details ==
Series: mm, drm/i915: Mark pinned shmemfs pages as unevictable (rev7)
URL : https://patchwork.freedesktop.org/series/25337/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5096_full -> Patchwork_10741_full =
== Summary - FAILURE ==
Serious unknown chan
The MOCS tables are going to be very similar across platforms.
To reduce the amount of copied code, this patch rips the common part and
puts it into a definition valid for all gen9 platforms.
v2: Made defines for or-ing flags. Renamed macros from MOCS_TABLE
to MOCS_ENTRIES. (Joonas)
Signed-o
The table has been unified across OSes to minimize virtualization overhead.
The MOCS table is now published as part of bspec, and versioned. Entries
are supposed to never be modified, but new ones can be added. Adding
entries increases table version. The patch includes version 1 entries.
Meaning
When cross release was originally merged we've hit a bunch of lockdep
splats around the 2 kthread completions. In all cases they are because
totally independent uses of kthread are mixed up by lockdep into the
same locking class, creating artificial deadlocks.
Fix this by converting kthread code i
This reverts the following commits:
commit 527187d28569 ("locking/lockdep: Remove cross-release leftovers")
commit dba04eb76df9 ("locking/Documentation: Remove stale
crossrelease_fullstack parameter")
commit e966eaeeb623 ("locking/lockdep: Remove the cross-release locking checks")
commit 44318d5b
dma-fence is a completion on steriods, which also allows hardware to
directly sync work among each another. It's supposed to be deadlock
free, so let's try to make sure that holds at least for the cpu-only
interactions and waits.
It's a bit much #ifdef, but I figured for the single case it's not
w
cross-release annotations will need some serious amounts of vetting
before they can be enabled by default, or we'll just annoy everyone.
Instead split it into a separate option, which for now stays disabled
by default even if you enable overall lockdep.
Cc: Andrew Morton
Cc: Ingo Molnar
Cc: Mas
i915_request_wait is simply our i915-optimized version of
dma_fence_wait. They both use the exact same code. To help lockdep
discovering all the dependencies, annotate it.
v2: We do opportunistic retiring of dma-fences while holding
struct_mutex. The recursion this causes is intentional, and we do
We need to make sure implementations don't cheat and don't have a
possible schedule/blocking point deeply burried where review can't
catch it.
I'm not sure whether this is the best way to make sure all the
might_sleep() callsites trigger, and it's a bit ugly in the code flow.
But it gets the job d
reservations have an optimized fastpath that bypasses dma_fence_wait(),
make sure we still catch all dependencies in lockdep.
To avoid lockdep complaining about recursion on the fake
dma_fence_wait lock we use the dma_fence_might_sleep annotation.
Cc: Sumit Semwal
Cc: linux-me...@vger.kernel.org
Only way to convince our CI to enable stuff that's new and defaulting
to off. Obviously not for merging.
Signed-off-by: Daniel Vetter
---
lib/Kconfig.debug | 1 +
1 file changed, 1 insertion(+)
diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
index 6074fa3463ac..deba9af0f418 100644
--- a/lib/
Just a bit of paranoia, since if we start pushing this deep into
callchains it's hard to spot all places where an mmu notifier
implementation might fail when it's not allowed to.
Cc: Andrew Morton
Cc: Michal Hocko
Cc: "Christian König"
Cc: David Rientjes
Cc: Daniel Vetter
Cc: "Jérôme Glisse"
This is a similar idea to the fs_reclaim fake lockdep lock. It's
fairly easy to provoke a specific notifier to be run on a specific
range: Just prep it, and then munmap() it.
A bit harder, but still doable, is to provoke the mmu notifiers for
all the various callchains that might lead to them. But
This reverts commit cb92173d1f0474784c6171a9d3fdbbca0ee53554.
This commit tries to shut up lockdep complaining about a
lockdep_assert_held check in the AP cpuhp bringup threads, while the
lock is actually held by the BP thread. Which is all kinda correct,
since BP does wait for all the AP threads
In i915 we also have i915_sw_fence, as some kind of super fence. Since
those include dma-fences (it's the main use really, aside from
chaining them for the scheduler) they're relevant for any lockdep
cycles involving dma_fence.
But i915_sw_fence is also really tough to properly annonate:
- Most of
This was originally added in 7e7844226f10 ("lockdep: allow to disable
reclaim lockup detection") but a git log -G "GFP_NOLOCKDEP" indicates
it was never used.
Cc: Andrew Morton
Cc: Vlastimil Babka
Cc: Michal Hocko
Cc: Mel Gorman
Cc: Daniel Vetter
Cc: "Levin, Alexander (Sasha Levin)"
Cc: Mike
Quoting Colin King (2018-11-07 10:22:11)
> From: Colin Ian King
>
> Trivial fix to spelling mistake in DRM_INFO message
>
> Signed-off-by: Colin Ian King
Thank you for the spelling correction, applied.
-Chris
___
Intel-gfx mailing list
Intel-gfx@list
Quoting Andrew Morton (2018-11-06 18:12:11)
> On Tue, 6 Nov 2018 13:23:24 + Chris Wilson
> wrote:
>
> > From: Kuo-Hsin Yang
> >
> > The i915 driver uses shmemfs to allocate backing storage for gem
> > objects. These shmemfs pages can be pinned (increased ref count) by
> > shmem_read_mappi
== Series Details ==
Series: series starting with [v5,1/2] drm/i915/skl: Rework MOCS tables to keep
common part in a define
URL : https://patchwork.freedesktop.org/series/52108/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10752 =
== Summary - SUCCESS ==
== Series Details ==
Series: series starting with [v6,1/2] drm/i915/skl: Rework MOCS tables to keep
common part in a define
URL : https://patchwork.freedesktop.org/series/52165/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097 -> Patchwork_10753 =
== Summary - SUCCESS ==
== Series Details ==
Series: drm/i915: fix subslice mask array size
URL : https://patchwork.freedesktop.org/series/52110/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096_full -> Patchwork_10742_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork
Unfortunately drm_dp_get_mst_branch_device which is called from both
drm_dp_mst_handle_down_rep and drm_dp_mst_handle_up_rep seem to rely
on that mgr->mst_primary is not NULL, which seem to be wrong as it can be
cleared with simultaneous mode set, if probing fails or in other case.
mgr->lock mutex
== Series Details ==
Series: series starting with [1/3] drm/atomic: Use explicit old crtc state in
drm_atomic_add_affected_planes() (rev2)
URL : https://patchwork.freedesktop.org/series/51894/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096_full -> Patchwork_10745_full =
On Wed, Oct 10, 2018 at 04:50:50PM -0700, Matt Roper wrote:
> Some display controllers can be programmed to present non-black colors
> for pixels not covered by any plane (or pixels covered by the
> transparent regions of higher planes). Compositors that want a UI with
> a solid color background c
== Series Details ==
Series: series starting with [01/13] locking/lockdep: restore cross-release
checks
URL : https://patchwork.freedesktop.org/series/52167/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
a0ec0a02fec5 locking/lockdep: restore cross-release checks
-:9: WARNING:C
On 10/24/18 6:49 PM, Rodrigo Vivi wrote:
> On Fri, Oct 12, 2018 at 11:42:32AM -0700, Radhakrishna Sripada wrote:
>> At times 12bpc HDMI cannot be driven due to faulty cables, dongles
>> level shifters etc. To workaround them we may need to drive the output
>> at a lower bpc. Currently the user spac
== Series Details ==
Series: series starting with [01/13] locking/lockdep: restore cross-release
checks
URL : https://patchwork.freedesktop.org/series/52167/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: locking/lockdep: restore cross-release checks
== Series Details ==
Series: series starting with [01/13] locking/lockdep: restore cross-release
checks
URL : https://patchwork.freedesktop.org/series/52167/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5098 -> Patchwork_10754 =
== Summary - FAILURE ==
Serious unknown
== Series Details ==
Series: drm: Check if primary mst is null
URL : https://patchwork.freedesktop.org/series/52174/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
f8a61b5fe3ea drm: Check if primary mst is null
-:10: WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit descri
On Wed, Nov 07, 2018 at 06:11:30PM +0200, Stanislav Lisovskiy wrote:
> Unfortunately drm_dp_get_mst_branch_device which is called from both
> drm_dp_mst_handle_down_rep and drm_dp_mst_handle_up_rep seem to rely
> on that mgr->mst_primary is not NULL, which seem to be wrong as it can be
> cleared wi
From: Ville Syrjälä
We no longer change LSPCON into PCON mode if it boots up in
LS mode. This was broken by some code shuffling in
commit 96e35598cead ("drm/i915: Check LSPCON vendor OUI").
I actually can't see a reason why that code shuffling had
to be done. The commit msg notes it but doesn't
== Series Details ==
Series: drm: Check if primary mst is null
URL : https://patchwork.freedesktop.org/series/52174/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5098 -> Patchwork_10755 =
== Summary - SUCCESS ==
No regressions found.
External URL:
https://patchwork.
== Series Details ==
Series: series starting with [1/3] drm/atomic: Use explicit old crtc state in
drm_atomic_add_affected_planes() (rev2)
URL : https://patchwork.freedesktop.org/series/51894/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096_full -> Patchwork_10745_full =
On Wed, Nov 07, 2018 at 04:56:00PM +, Kazlauskas, Nicholas wrote:
> On 10/24/18 6:49 PM, Rodrigo Vivi wrote:
> > On Fri, Oct 12, 2018 at 11:42:32AM -0700, Radhakrishna Sripada wrote:
> >> At times 12bpc HDMI cannot be driven due to faulty cables, dongles
> >> level shifters etc. To workaround t
On 11/7/18 1:10 PM, Rodrigo Vivi wrote:
> On Wed, Nov 07, 2018 at 04:56:00PM +, Kazlauskas, Nicholas wrote:
>> On 10/24/18 6:49 PM, Rodrigo Vivi wrote:
>>> On Fri, Oct 12, 2018 at 11:42:32AM -0700, Radhakrishna Sripada wrote:
At times 12bpc HDMI cannot be driven due to faulty cables, dongl
== Series Details ==
Series: drm/i915: Switch LSPCON to PCON mode if it's in LS mode
URL : https://patchwork.freedesktop.org/series/52178/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5099 -> Patchwork_10756 =
== Summary - SUCCESS ==
No regressions found.
External UR
On Thu, Nov 01, 2018 at 11:13:50AM -0700, Rodrigo Vivi wrote:
> On Thu, Nov 01, 2018 at 05:17:36PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Remove the "sizes are 0 based" stuff that is not even true for the
> > scaler.
> >
> > v2: Rebase
> >
> > Signed-off-by: Ville Syrjälä
From: Ville Syrjälä
Due to the constant alpha we're going to have to program two of
the the tree keying registers anyway, so might as well always
program all three.
And parametrize the plane constant alpha define while at it.
v2: Rebase due to input CSC
Signed-off-by: Ville Syrjälä
---
drive
From: Ville Syrjälä
Some observations about the plane registers:
- the control register will self-arm if the plane is not already
enabled, thus we want to write it as close to (or ideally after)
the surface register
- tileoff/linoff/offset/aux_offset are self-arming as well so we want
them
From: Ville Syrjälä
We memset(0) the entire watermark struct the start, so there's no
need to clear things later on.
v2: Rebase due to some stale w/a removal
Signed-off-by: Ville Syrjälä
---
drivers/gpu/drm/i915/intel_pm.c | 16
1 file changed, 4 insertions(+), 12 deletions(-
== Series Details ==
Series: drm/i915: HPD IRQ storm detection fixes (rev5)
URL : https://patchwork.freedesktop.org/series/51556/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5096_full -> Patchwork_10746_full =
== Summary - WARNING ==
Minor unknown changes coming with P
From: Ville Syrjälä
On SKL+ the plane WM/BUF_CFG registers are a proper part of each
plane's register set. That means accessing them will cancel any
pending plane update, and we would need a PLANE_SURF register write
to arm the wm/ddb change as well.
To avoid all the problems with that let's jus
On Fri, Nov 02, 2018 at 08:22:00PM +0200, Imre Deak wrote:
> To enable DC5/6 power well 2 has to be disabled as for previous
> platforms, so fix things up.
>
> Bspec: 4234
> Fixes: 67ca07e7ac10 ("drm/i915/icl: Add power well support")
> Cc: Animesh Manna
> Cc: Paulo Zanoni
> Cc: Ville Syrjälä
>
On Tue, Nov 06, 2018 at 04:30:16PM -0500, Lyude Paul wrote:
> Unfortunately, it seems that the HPD IRQ storm problem from the early
> days of Intel GPUs was never entirely solved, only mostly. Within the
> last couple of days, I got a bug report from one of our customers who
> had been having issue
On Thu, Nov 01, 2018 at 05:05:54PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> If we don't need the PS_PWR_GATE write when programming the
> pipe scaler I don't see why we'd need it for plane scalers either.
> Just remove it.
>
> Signed-off-by: Ville Syrjälä
Reviewed-by: Rodrigo Viv
== Series Details ==
Series: drm/i915: Program SKL+ watermarks/ddb more carefully (rev6)
URL : https://patchwork.freedesktop.org/series/51878/
State : failure
== Summary ==
Applying: drm/i915: Nuke posting reads from plane update/disable funcs
error: sha1 information is lacking or useless
(dr
On Thu, Nov 01, 2018 at 05:05:55PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Due to the constant alpha we're going to have to program two of
> the the tree keying registers anyway, so might as well always
> program all three.
>
> And parametrize the plane constant alpha define while
Thanks for noticing this one! With the changes that Ville mentioned in their
response:
Reviewed-by: Lyude Paul
If you need me to push this for you; poke me here or on IRC
On Wed, 2018-11-07 at 18:11 +0200, Stanislav Lisovskiy wrote:
> Unfortunately drm_dp_get_mst_branch_device which is called f
On Thu, Nov 01, 2018 at 05:05:56PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> On skl+ the scaler (when enabled) will take care of the plane output
> position. Make the code less ugly by just setting crtc_x/y to 0
> when the scaler is enabled.
>
> Signed-off-by: Ville Syrjälä
Reviewe
We shouldn't consider an encoder inactive if it doesn't have a CRTC
linked, but has virtual MST encoders with a crtc linked. Fix this.
Also we should not sanitize the mapping for MST encoders, as it's always
their primary encoder (which could be even in SST mode) whose active
state determines if w
Check for reserved register field values and conflicting
transcoder->port mappings (both MST and non-MST mappings or multiple SST
mappings).
This is also needed for the next patch to determine if a port is in MST
mode during sanitization after HW readout.
Cc: Paulo Zanoni
Cc: Ville Syrjälä
Cc:
On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:
> Hey Dave,
>
> First pull for drm-next this cycle. There's been a lot of changes, so I
> hope I recorded everything from the changelog correctly.
>
> drm-misc-next-2018-11-07:
> drm-misc-next for v4.21, part 1:
>
> UAPI Changes:
On Wed, Nov 07, 2018 at 09:18:16PM +0100, Daniel Vetter wrote:
> On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:
> > Hey Dave,
> >
> > First pull for drm-next this cycle. There's been a lot of changes, so I
> > hope I recorded everything from the changelog correctly.
> >
> > dr
On Wed, Nov 7, 2018 at 9:29 PM Sean Paul wrote:
>
> On Wed, Nov 07, 2018 at 09:18:16PM +0100, Daniel Vetter wrote:
> > On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:
> > > Hey Dave,
> > >
> > > First pull for drm-next this cycle. There's been a lot of changes, so I
> > > hope I
On Fri, Nov 02, 2018 at 11:54:51PM +, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/icl: Fix power well 2 wrt. DC-off toggling order
> URL : https://patchwork.freedesktop.org/series/51971/
> State : success
Thanks for the review, pushed to -dinq.
>
> == Summary ==
>
> = CI
On Tue, 2018-11-06 at 18:06 +0200, Imre Deak wrote:
> BSpec says to clear the comp init HW flag too during combo PHY
> uninit,
> so do that. The lack of this could badly interact with the PHY reinit
> after a DC6/9 transition at least, where (after a follow-up patch
> fixing
> the init code) we'd s
== Series Details ==
Series: series starting with [1/2] drm/i915/ddi: Add more sanity check to the
encoder HW readout
URL : https://patchwork.freedesktop.org/series/52187/
State : failure
== Summary ==
= CI Bug Log - changes from CI_DRM_5100 -> Patchwork_10758 =
== Summary - FAILURE ==
Se
On Tue, 2018-11-06 at 18:06 +0200, Imre Deak wrote:
> Similarly to the GEN9_LP DPIO PHY code keep the CNL+ combo PHY code
> in a
> separate file.
>
> No functional change.
>
> v2:
> - Use SPDX license tag instead of boilerplate. (Rodrigo)
>
> Suggested-by: Ville Syrjälä
> Cc: Paulo Zanoni
> Cc
On Tue, 2018-11-06 at 18:06 +0200, Imre Deak wrote:
> Verify on CNL, ICL that the combo PHY HW state stayed intact after
> PHY
> initialization.
>
> v2:
> - Print 'Port X' as we do elsewhere instead of 'Port-X'. (Jose)
>
> Cc: Paulo Zanoni
> Cc: Ville Syrjälä
Reviewed-by: José Roberto de Souza
On Tue, 2018-11-06 at 18:06 +0200, Imre Deak wrote:
> On ICL DMC/PCODE retains the HW context only for port A across DC
> transitions, for the other port B combo PHY, it doesn't. So we need
> to
> do this manually after exiting from DC6. Do the reinit even after
> exiting from DC5, it won't hurt si
On Wed, Nov 07, 2018 at 09:31:51PM +0100, Daniel Vetter wrote:
> On Wed, Nov 7, 2018 at 9:29 PM Sean Paul wrote:
> >
> > On Wed, Nov 07, 2018 at 09:18:16PM +0100, Daniel Vetter wrote:
> > > On Wed, Nov 07, 2018 at 12:58:56PM +0100, Maarten Lankhorst wrote:
> > > > Hey Dave,
> > > >
> > > > First p
Hi Dave,
First fixes pull for 4.20, some NULL protection for sun4i.
drm-misc-fixes-2018-11-07:
- sun4i: tcon->panel NULL deref protections (Giulio)
Cc: Giulio Benetti
Cheers, Sean
The following changes since commit 651022382c7f8da46cb4872a545ee1da6d097d2a:
Linux 4.20-rc1 (2018-11-04 15:3
On Wed, Nov 07, 2018 at 11:55:27AM -0800, Rodrigo Vivi wrote:
> On Thu, Nov 01, 2018 at 05:05:55PM +0200, Ville Syrjala wrote:
> > From: Ville Syrjälä
> >
> > Due to the constant alpha we're going to have to program two of
> > the the tree keying registers anyway, so might as well always
> > prog
On Tue, Nov 06, 2018 at 08:21:14PM -0500, Lyude Paul wrote:
> There has been a TODO waiting for quite a long time in
> drm_dp_mst_topology.c:
>
> /* We cannot rely on port->vcpi.num_slots to update
>* topology_state->avail_slots as the port may not exist if the parent
>* bran
== Series Details ==
Series: Make GEN macros more similar (rev2)
URL : https://patchwork.freedesktop.org/series/51860/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_5097_full -> Patchwork_10747_full =
== Summary - WARNING ==
Minor unknown changes coming with Patchwork_10
1 - 100 of 161 matches
Mail list logo
