From: Bob Paauwe
The WA specifies that we need to toggle a SDE chicken bit on and then
off as the final step in preparation for s0ix entry.
Bspec: 33450
Bspec: 8402
However, something is happening after we toggle the bit that causes
the WA to be invalidated. This makes dispcnlunit1_cp_x
On 2020.10.28 11:18:45 +, Vivi, Rodrigo wrote:
>
> I'm actually pulling it off. I had bypassed dim, considering this was an old
> issue with our email decoder,
> but it happens that
>
> $ git show 401ccfa87856 | grep Fixes
> Fixes: e6ba76480299 (drm/i915: Remove i915->kernel_context)
>
> A
On 2020.10.28 11:18:45 +, Vivi, Rodrigo wrote:
>
>
> On Oct 27, 2020, at 1:46 PM, Rodrigo Vivi wrote:
>
> On Tue, Oct 27, 2020 at 11:17:40AM +0800, Zhenyu Wang wrote:
>
>
> Hi,
>
> Here's first gvt fixes for 5.10 which includes more vGPU
> suspend/resume f
== Series Details ==
Series: drm: Quieten [zero] EDID carping
URL : https://patchwork.freedesktop.org/series/83218/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9221_full -> Patchwork_18810_full
Summary
---
**FAILUR
Hi Dave and Daniel,
Only 3 patches on this first round. I had blocked a few patches
because CI results were strange and I had blocked GVT pull request
for having a bad-formatted commit message. So we might see a bigger
number of patches next week.
Thanks,
Rodrigo.
drm-intel-fixes-2020-10-29:
- F
Hi Daniel,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-exynos/exynos-drm-next
tegra-drm/drm/tegra/for-next linus/master v5.10-rc1 next-20201029]
[If your patch is applied to the wrong git tree, kindly
tlb_nr_tbl' [-Werror=implicit-function-declaration]
320 | need_swiotlb = !!swiotlb_nr_tbl();
| ^~
Caused by commit
ee5d2a8e549e ("drm/ttm: wire up the new pool as default one v2")
I have used the drm-misc tree from next-20201029 for t
== Series Details ==
Series: drm: Quieten [zero] EDID carping
URL : https://patchwork.freedesktop.org/series/83218/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9221 -> Patchwork_18810
Summary
---
**SUCCESS**
No
@Anshuman Gupta All the failures are addressed and re-reported.
Lakshmi.
-Original Message-
From: Anshuman Gupta
Sent: Thursday, October 29, 2020 1:38 AM
To: Vudum, Lakshminarayana
Cc: intel-gfx@lists.freedesktop.org; Shankar, Uma
Subject: Re: ✗ Fi.CI.IGT: failure for HDCP 2.2 and HDC
> -Original Message-
> From: Intel-gfx On Behalf Of
> Lucas De Marchi
> Sent: Monday, October 26, 2020 9:46 PM
> To: intel-gfx@lists.freedesktop.org
> Subject: [Intel-gfx] [PATCH 3/3] drm/i915: remove some debug-only registers
> from MCHBAR
>
> GT_PERF_STATUS and RP_STATE_LIMITS were a
On Tue, 2020-10-27 at 16:45 -0700, José Roberto de Souza wrote:
> Add the calculations to set plane selective fetch registers depending
> in the value of the area damaged.
> It is still using the whole plane area as damaged but that will
> change
> in next patches.
>
> v2:
> - fixed new_plane_stat
We have a few displays in CI that always report their EDID as a bunch of
zeroes. This is consistent behaviour, so one assumes intentional
indication of an "absent" EDID. Flagging these consistent warnings
detracts from CI.
One option would be to ignore the zero EDIDs as intentional behaviour,
but
== Series Details ==
Series: drm: Remove SCATTERLIST_MAX_SEGMENT
URL : https://patchwork.freedesktop.org/series/83203/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9220_full -> Patchwork_18807_full
Summary
---
**FAI
== Series Details ==
Series: series starting with [v4,1/6] drm/i915/dp: Some reshuffling in
mode_valid as prep for bigjoiner modes
URL : https://patchwork.freedesktop.org/series/83212/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9221 -> Patchwork_18809
=
== Series Details ==
Series: series starting with [v4,1/6] drm/i915/dp: Some reshuffling in
mode_valid as prep for bigjoiner modes
URL : https://patchwork.freedesktop.org/series/83212/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e90405311347 drm/i915/dp: Some reshuffling in
No functional changes here. Just pass intel_atomic_state
along with crtc_state to certain atomic_check functions.
This will lay the foundation for adding bigjoiner master/slave
states in atomic check.
v2:
* More prep with intel_atomic_state (Ville)
Cc: Ville Syrjälä
Signed-off-by: Manasi Navare
From: Maarten Lankhorst
With bigjoiner, there will be 2 pipes driving 2 halves of 1 transcoder,
because of this, we need a pipe_mode for various calculations, including
for example watermarks, plane clipping, etc.
v8:
* Add pipe_mode in readout in verify_crtc_state (Ville)
v7:
* Remove redundant
No functional changes, create a separate intel_encoder_get_config()
function that calls encoder->get_config hook.
This is needed so that later we can add beigjoienr related
readout here.
Signed-off-by: Manasi Navare
---
drivers/gpu/drm/i915/display/intel_display.c | 12 +---
1 file chang
From: Maarten Lankhorst
Small changes to intel_dp_mode_valid(), allow listing modes that
can only be supported in the bigjoiner configuration, which is
not supported yet.
v12:
* slice_count logic simplify (Ville)
* Fix unnecessary changes in downstream_mode_valid (Ville)
v11:
* Make intel_dp_can
No functional changes, to align with previous cleanups pass
intel_atomic_state instead of drm_atomic_state.
Also pass this intel_atomic_state with crtc_state to
some of the atomic_check functions.
Signed-off-by: Manasi Navare
---
drivers/gpu/drm/i915/display/intel_display.c | 14 +++---
No functional changes. This patch just moves some mode checks
around to prepare for adding bigjoiner related mode validation
Cc: Ville Syrjälä
Signed-off-by: Manasi Navare
Reviewed-by: Ville Syrjälä
---
drivers/gpu/drm/i915/display/intel_dp.c | 12 ++--
1 file changed, 6 insertions(+),
Am 29.10.20 um 11:14 schrieb Daniel Vetter:
> So ever since syzbot discovered fbcon, we have solid proof that it's
> full of bugs. And often the solution is to just delete code and remove
> features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code").
>
> Now the problem is that most mode
Am 29.10.20 um 11:14 schrieb Daniel Vetter:
> Every since
>
> commit 6104c37094e729f3d4ce65797002112735d49cd1
> Author: Daniel Vetter
> Date: Tue Aug 1 17:32:07 2017 +0200
>
> fbcon: Make fbcon a built-time depency for fbdev
>
> these are no longer distinct loadable modules, so exportin
On Thu, Oct 29, 2020 at 7:20 PM Jason Gunthorpe wrote:
>
> On Wed, Oct 28, 2020 at 08:49:11PM +0100, Daniel Vetter wrote:
> > On Wed, Oct 28, 2020 at 04:15:26PM -0300, Jason Gunthorpe wrote:
> > > Since commit 9a40401cfa13 ("lib/scatterlist: Do not limit max_segment to
> > > PAGE_ALIGNED values")
On Wed, Oct 28, 2020 at 08:49:11PM +0100, Daniel Vetter wrote:
> On Wed, Oct 28, 2020 at 04:15:26PM -0300, Jason Gunthorpe wrote:
> > Since commit 9a40401cfa13 ("lib/scatterlist: Do not limit max_segment to
> > PAGE_ALIGNED values") the max_segment input to sg_alloc_table_from_pages()
> > does not
== Series Details ==
Series: HDCP 2.2 and HDCP 1.4 Gen12 DP MST support (rev2)
URL : https://patchwork.freedesktop.org/series/82998/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9206_full -> Patchwork_18788_full
Summary
--
== Series Details ==
Series: HDCP 2.2 and HDCP 1.4 Gen12 DP MST support (rev2)
URL : https://patchwork.freedesktop.org/series/82998/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9206_full -> Patchwork_18788_full
Summary
--
Hi Dave, Daniel,
Here's the first round of fixes for drm-misc
Maxime
drm-misc-fixes-2020-10-29:
First round of drm-misc-fixes with a couple of leftovers from
drm-misc-fixes next.
Some reset fixes for the mantix panel, some fixes for a scaler issue on
sun4i, many kernel-doc fixes and various fix
== Series Details ==
Series: drm: Remove SCATTERLIST_MAX_SEGMENT
URL : https://patchwork.freedesktop.org/series/83203/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9220 -> Patchwork_18807
Summary
---
**SUCCESS**
== Series Details ==
Series: drm/i915: Remove unused variable ret
URL : https://patchwork.freedesktop.org/series/83204/
State : failure
== Summary ==
Applying: drm/i915: Remove unused variable ret
Using index info to reconstruct a base tree...
M drivers/gpu/drm/i915/i915_debugfs.c
Fallin
== Series Details ==
Series: series starting with fbcon: Disable accelerated scrolling (rev3)
URL : https://patchwork.freedesktop.org/series/83194/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9218_full -> Patchwork_18806_full
=
== Series Details ==
Series: drm: Remove SCATTERLIST_MAX_SEGMENT
URL : https://patchwork.freedesktop.org/series/83203/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
66f5f63cc749 drm: Remove SCATTERLIST_MAX_SEGMENT
-:101: WARNING:FROM_SIGN_OFF_MISMATCH: From:/Signed-off-by: emai
From: Thomas Gleixner
CONFIG_PREEMPT_COUNT is now unconditionally enabled and will be
removed. Cleanup the leftovers before doing so.
Signed-off-by: Thomas Gleixner
Cc: Jani Nikula
Cc: Joonas Lahtinen
Cc: Rodrigo Vivi
Cc: David Airlie
Cc: Daniel Vetter
Cc: intel-gfx@lists.freedesktop.org
C
On Wed, Oct 28, 2020 at 02:07:12PM -0700, José Roberto de Souza wrote:
> After commit 00e5deb5c4f5 ("drm/i915: Fix encoder lookup during PSR
> atomic check") dig_port was not being used but while fixing it I
> realized that would be better to mark all CRTCs that has a eDP
> connector as needing to
On Thu, Oct 29, 2020 at 04:01:23PM +, Chris Wilson wrote:
> Quoting Ville Syrjälä (2020-10-29 14:07:46)
> > On Thu, Oct 29, 2020 at 11:00:30AM +, Chris Wilson wrote:
> > > We have a few displays in CI that always report their EDID as a bunch of
> > > zeroes. This is consistent behavioud, so
Quoting Ville Syrjälä (2020-10-29 14:07:46)
> On Thu, Oct 29, 2020 at 11:00:30AM +, Chris Wilson wrote:
> > We have a few displays in CI that always report their EDID as a bunch of
> > zeroes. This is consistent behavioud, so one assumes intentional
> > indication of an "absent" EDID. Let us tr
== Series Details ==
Series: series starting with fbcon: Disable accelerated scrolling (rev3)
URL : https://patchwork.freedesktop.org/series/83194/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9218 -> Patchwork_18806
Summa
== Series Details ==
Series: series starting with fbcon: Disable accelerated scrolling (rev3)
URL : https://patchwork.freedesktop.org/series/83194/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
363efbc2f463 fbcon: Disable accelerated scrolling
-:8: ERROR:GIT_COMMIT_ID: Please u
== Series Details ==
Series: series starting with fbcon: Disable accelerated scrolling (rev2)
URL : https://patchwork.freedesktop.org/series/83194/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9217 -> Patchwork_18805
Summa
On Thu, Oct 29, 2020 at 11:00:30AM +, Chris Wilson wrote:
> We have a few displays in CI that always report their EDID as a bunch of
> zeroes. This is consistent behavioud, so one assumes intentional
> indication of an "absent" EDID. Let us treat is as such by silently
> reporting the zero edid
== Series Details ==
Series: series starting with [1/3] fbcon: Disable accelerated scrolling
URL : https://patchwork.freedesktop.org/series/83194/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_9216_full -> Patchwork_18803_full
==
tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Daniel-Vetter/fbcon-Disable-accelerated-scrolling/20201029-181618
base: git://anongit.freedeskt
Since commit 9a40401cfa13 ("lib/scatterlist: Do not limit max_segment to
PAGE_ALIGNED values") the max_segment input to sg_alloc_table_from_pages()
does not have to be any special value. The new algorithm will always
create something less than what the user provides. Thus eliminate this
confusing c
This patch fixes below warnings reported by coccicheck
./drivers/gpu/drm/i915/i915_debugfs.c:789:5-8: Unneeded variable: "ret". Return
"0" on line 1012
Reported-by: Hulk Robot
Signed-off-by: Zou Wei
---
drivers/gpu/drm/i915/i915_debugfs.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-
These are leftovers from 13aff184ed9f ("drm/qxl: remove dead qxl fbdev
emulation code").
v2: Somehow these structs provided the struct qxl_device pre-decl,
reorder the header to not anger compilers.
Acked-by: Gerd Hoffmann
Signed-off-by: Daniel Vetter
Cc: Dave Airlie
Cc: Gerd Hoffmann
Cc: vir
== Series Details ==
Series: series starting with fbcon: Disable accelerated scrolling (rev2)
URL : https://patchwork.freedesktop.org/series/83194/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
ca2b9ab33821 fbcon: Disable accelerated scrolling
-:8: ERROR:GIT_COMMIT_ID: Please u
On Thu, Oct 29, 2020 at 10:18:45AM +0800, Zou Wei wrote:
> This patch fixes below warnings reported by coccicheck
>
> ./drivers/gpu/drm/i915/i915_debugfs.c:789:5-8: Unneeded variable: "ret".
> Return "0" on line 1012
>
> Reported-by: Hulk Robot
> Signed-off-by: Zou Wei
Thanks. Applied.
> ---
So ever since syzbot discovered fbcon, we have solid proof that it's
full of bugs. And often the solution is to just delete code and remove
features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code").
Now the problem is that most modern-ish drivers really only treat
fbcon as an dumb kernel
the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url:
https://github.com/0day-ci/linux/commits/Daniel-Vetter/fbcon-Disable-accelerated-scrolling/20201029-181618
b
I use an open source DVR called MythTV. I've just swapped from using
nvidia graphics to intel graphics. Generally it's working great, but
I've run into one thing I used to do with the old system that I cannot
find out how to achieve with the new.
MythTV doesn't currently entirely handle starti
== Series Details ==
Series: drm: Silence zero EDID carping
URL : https://patchwork.freedesktop.org/series/83199/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9216 -> Patchwork_18804
Summary
---
**SUCCESS**
No re
== Series Details ==
Series: series starting with [1/3] fbcon: Disable accelerated scrolling
URL : https://patchwork.freedesktop.org/series/83194/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_9216 -> Patchwork_18803
Summar
== Series Details ==
Series: series starting with [1/3] fbcon: Disable accelerated scrolling
URL : https://patchwork.freedesktop.org/series/83194/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
83d868107d69 fbcon: Disable accelerated scrolling
-:8: ERROR:GIT_COMMIT_ID: Please us
On Thu, Oct 29, 2020 at 11:14:28AM +0100, Daniel Vetter wrote:
> These are leftovers from 13aff184ed9f ("drm/qxl: remove dead qxl fbdev
> emulation code").
Acked-by: Gerd Hoffmann
___
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists
We have a few displays in CI that always report their EDID as a bunch of
zeroes. This is consistent behavioud, so one assumes intentional
indication of an "absent" EDID. Let us treat is as such by silently
reporting the zero edid using connector->null_edid_counter, leaving the
loud carp to EDID tha
These are leftovers from 13aff184ed9f ("drm/qxl: remove dead qxl fbdev
emulation code").
Signed-off-by: Daniel Vetter
Cc: Dave Airlie
Cc: Gerd Hoffmann
Cc: virtualizat...@lists.linux-foundation.org
Cc: spice-de...@lists.freedesktop.org
---
drivers/gpu/drm/qxl/qxl_drv.h | 14 --
1 f
Every since
commit 6104c37094e729f3d4ce65797002112735d49cd1
Author: Daniel Vetter
Date: Tue Aug 1 17:32:07 2017 +0200
fbcon: Make fbcon a built-time depency for fbdev
these are no longer distinct loadable modules, so exporting symbols is
kinda pointless.
Signed-off-by: Daniel Vetter
Cc:
So ever since syzbot discovered fbcon, we have solid proof that it's
full of bugs. And often the solution is to just delete code and remove
features, e.g. 50145474f6ef ("fbcon: remove soft scrollback code").
Now the problem is that most modern-ish drivers really only treat
fbcon as an dumb kernel
Hi Lakshmi,
Below HDCP over DP-MST patchwork series has unrelated failures from GEM and
display side as well.
Similar series i had sent earlier on tryboat it was passing
https://patchwork.freedesktop.org/series/82919/
Could you please let us know if below INCOMPLETE and DMESG-WARN are already
kno
On Wed, 28 Oct 2020, Lee Shawn C wrote:
> After boot into kernel. Driver configured ddc pin mapping based on
> predefined table in parse_ddi_port(). Now driver configure rkl
> ddc pin mapping depends on icp_ddc_pin_map[]. Then this table will
> give incorrect gmbus port number to cause HDMI can't
On Wed, 28 Oct 2020, Chris Wilson wrote:
> Quoting Stephen Rothwell (2020-10-28 21:28:23)
>> Hi all,
>>
>> Commit
>>
>> d13208a88f41 ("lockdep: Fix nr_unused_locks")
>>
>> is missing a Signed-off-by from its author.
>>
>> Also, the author's email name is missing the leading 'P'.
>
> And it s
61 matches
Mail list logo
