Hi all,
After merging the drm-misc tree, today's linux-next build (powerpc
allyesconfig) failed like this:
kernel/dma/contiguous.c:19:10: fatal error: asm/dma-contiguous.h: No such file
or directory
#include
^~
Caused by commit
4f2a8f5898ec ("drm: Add ASPEED
Hi Vivek,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on next-20190404]
[cannot apply to v5.1-rc3]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
On Thu, 2019-04-04 at 17:32 -0700, Souza, Jose wrote:
> On Thu, 2019-04-04 at 17:22 -0700, Dhinakaran Pandiyan wrote:
> > On Wed, 2019-04-03 at 16:35 -0700, José Roberto de Souza wrote:
> > > Even when driver is reloaded and hits this scenario the PSR mutex
> > > should be initialized, otherwise
On Thu, Mar 14, 2019 at 2:11 PM Souza, Jose wrote:
>
> Maybe rename the commit message to "drm/i915/ehl: Inherit ICELAKE
> conditional code"?
>
> Also there a few important places that this patch and this series is
> missing:
>
>
> diff --git a/drivers/gpu/drm/i915/i915_drv.c
>
On Wed, 2019-04-03 at 16:35 -0700, José Roberto de Souza wrote:
> Just moving it to reduce the tabs and avoid break code lines.
> No behavior changes intended here.
>
> Signed-off-by: José Roberto de Souza
> ---
> drivers/gpu/drm/i915/i915_irq.c | 63 +++--
> 1 file
On Thu, 2019-04-04 at 17:22 -0700, Dhinakaran Pandiyan wrote:
> On Wed, 2019-04-03 at 16:35 -0700, José Roberto de Souza wrote:
> > Even when driver is reloaded and hits this scenario the PSR mutex
> > should be initialized, otherwise reading PSR debugfs status will
> > execute mutex_lock() over a
On Wed, 2019-04-03 at 16:35 -0700, José Roberto de Souza wrote:
> Even when driver is reloaded and hits this scenario the PSR mutex
> should be initialized, otherwise reading PSR debugfs status will
> execute mutex_lock() over a mutex that was not initialized.
>
> Cc: Dhinakaran Pandiyan
> Cc:
== Series Details ==
Series: drm/i915/ehl: Add support for DPLL4 (v2)
URL : https://patchwork.freedesktop.org/series/59029/
State : failure
== Summary ==
CALLscripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
CC
== Series Details ==
Series: Trivial comments and small changes
URL : https://patchwork.freedesktop.org/series/59027/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5875 -> Patchwork_12688
Summary
---
**SUCCESS**
On Thu, 2019-03-28 at 23:05 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> i965+ have an interpolate 10bit LUT mode. Let's expose that so
> that we can actually enjoy real 10bpc.
>
> Signed-off-by: Ville Syrjälä
LGTM
Reviewed-by: Radhakrishna Sripada
> ---
>
This patch adds support for DPLL4 on EHL that include the
following restrictions:
- DPLL4 cannot be used with DDIA (combo port A internal eDP usage).
DPLL4 can be used with other DDIs, including DDID
(combo port A external usage).
- DPLL4 cannot be enabled when DC5 or DC6 are enabled.
- The
== Series Details ==
Series: drm/i915: Fixup kerneldoc for intel_cdclk_needs_cd2x_update
URL : https://patchwork.freedesktop.org/series/58988/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5869_full -> Patchwork_12681_full
On Thu, Apr 04, 2019 at 12:25:56PM -0700, Souza, Jose wrote:
> On Wed, 2019-04-03 at 17:27 -0700, Rodrigo Vivi wrote:
> > On Wed, Apr 03, 2019 at 04:35:35PM -0700, José Roberto de Souza
> > wrote:
> > > Even when driver is reloaded and hits this scenario the PSR mutex
> > > should be initialized,
At some point the spec was changed and we never updated the numbers to
match it. Let's try once more to keep them in sync.
Signed-off-by: Lucas De Marchi
---
drivers/gpu/drm/i915/intel_runtime_pm.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
I was fixing a pm thing that ended up not being needed. So, just get the
small/trivial changes out.
No change in behavior.
Lucas De Marchi (3):
drm/i915/icl: fix step numbers in icl_display_core_init()
drm/i915: reorder if chain to have last gen first
drm/i915: do not mix workaround with
Separate the two comments: one is a workaround and the other is a sanity
check. We could just compare != 1, but let's treat them differently due
to having different meaning.
Signed-off-by: Lucas De Marchi
---
drivers/gpu/drm/i915/intel_pm.c | 10 ++
1 file changed, 6 insertions(+), 4
Reorder if/else so we check for gen >= 11 first, similar to most of
other checks in the driver.
Signed-off-by: Lucas De Marchi
---
drivers/gpu/drm/i915/intel_pm.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_pm.c
== Series Details ==
Series: drm/i915/gvt: Prevent use-after-free in ppgtt_free_all_spt()
URL : https://patchwork.freedesktop.org/series/58985/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5869_full -> Patchwork_12680_full
On Thu, 2019-04-04 at 14:51 -0700, Rodrigo Vivi wrote:
> On Thu, Apr 04, 2019 at 02:41:26PM -0700, Pandiyan, Dhinakaran wrote:
> > On Thu, 2019-04-04 at 14:20 -0700, Rodrigo Vivi wrote:
> > > On Thu, Apr 04, 2019 at 12:40:34PM -0700, Souza, Jose wrote:
> > > > On Wed, 2019-04-03 at 17:31 -0700,
== Series Details ==
Series: drm/i915: the great header refactoring, part one
URL : https://patchwork.freedesktop.org/series/59022/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5875 -> Patchwork_12687
Summary
---
On Thu, 2019-04-04 at 14:41 -0700, Dhinakaran Pandiyan wrote:
> On Thu, 2019-04-04 at 14:20 -0700, Rodrigo Vivi wrote:
> > On Thu, Apr 04, 2019 at 12:40:34PM -0700, Souza, Jose wrote:
> > > On Wed, 2019-04-03 at 17:31 -0700, Rodrigo Vivi wrote:
> > > > On Wed, Apr 03, 2019 at 04:35:38PM -0700,
On Wed, 2019-04-03 at 17:29 -0700, Rodrigo Vivi wrote:
> On Wed, Apr 03, 2019 at 04:35:36PM -0700, José Roberto de Souza wrote:
> > This interlaced restriction applies to all gens, not only to Haswell.
>
> I believe this came from VLV times and I doubt we would be
> impacted by it ever, but
== Series Details ==
Series: drm/i915: the great header refactoring, part one
URL : https://patchwork.freedesktop.org/series/59022/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915: make intel_frontbuffer.h self-contained
On Thu, Apr 04, 2019 at 02:41:26PM -0700, Pandiyan, Dhinakaran wrote:
> On Thu, 2019-04-04 at 14:20 -0700, Rodrigo Vivi wrote:
> > On Thu, Apr 04, 2019 at 12:40:34PM -0700, Souza, Jose wrote:
> > > On Wed, 2019-04-03 at 17:31 -0700, Rodrigo Vivi wrote:
> > > > On Wed, Apr 03, 2019 at 04:35:38PM
== Series Details ==
Series: drm/i915: the great header refactoring, part one
URL : https://patchwork.freedesktop.org/series/59022/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
e3273176ce64 drm/i915: make intel_frontbuffer.h self-contained
9173569bc454 drm/i915: extract
On Thu, 2019-04-04 at 14:20 -0700, Rodrigo Vivi wrote:
> On Thu, Apr 04, 2019 at 12:40:34PM -0700, Souza, Jose wrote:
> > On Wed, 2019-04-03 at 17:31 -0700, Rodrigo Vivi wrote:
> > > On Wed, Apr 03, 2019 at 04:35:38PM -0700, José Roberto de Souza
> > > wrote:
> > > > PSR is only supported in eDP
Quoting Jani Nikula (2019-04-04 22:14:24)
> intel_drv.h has grown out of proportions, and turned into a dumping
> ground. Way back when it was useful to have only a handful of headers,
> but we're long past that.
>
> Start splitting off per-module headers. The basic principles:
>
> * Make the
Quoting Jani Nikula (2019-04-04 22:14:31)
> diff --git a/drivers/gpu/drm/i915/i915_suspend.c
> b/drivers/gpu/drm/i915/i915_suspend.c
> index d2f2a9c2fabd..eec48d856adb 100644
> --- a/drivers/gpu/drm/i915/i915_suspend.c
> +++ b/drivers/gpu/drm/i915/i915_suspend.c
> @@ -24,9 +24,12 @@
> *
On Fri, 05 Apr 2019, Jani Nikula wrote:
> It used to be handy that we only had a couple of headers, but over time
> intel_drv.h has become unwieldy. Extract declarations to a separate
> header file corresponding to the implementation module, clarifying the
> modularity of the
On Thu, Apr 04, 2019 at 12:40:34PM -0700, Souza, Jose wrote:
> On Wed, 2019-04-03 at 17:31 -0700, Rodrigo Vivi wrote:
> > On Wed, Apr 03, 2019 at 04:35:38PM -0700, José Roberto de Souza
> > wrote:
> > > PSR is only supported in eDP transcoder and there is only one
> > > instance of it, so lets
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
While transitioning to having better clarity between the modules, it's
desirable to have the function name prefixes reflect the
module. Functions in intel_foo.c should be prefixed intel_foo_.
Expose only one CDCLK init/uninit function from intel_cdclk.c instead of
one per platform. Obviously this
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
It used to be handy that we only had a couple of headers, but over time
intel_drv.h has become unwieldy. Extract declarations to a separate
header file corresponding to the implementation module, clarifying the
modularity of the driver.
Ensure the new header is self-contained, and do so with
intel_drv.h has grown out of proportions, and turned into a dumping
ground. Way back when it was useful to have only a handful of headers,
but we're long past that.
Start splitting off per-module headers. The basic principles:
* Make the new headers self-contained (i.e. can be compiled without
This will be helpful in the follow-up work. No functional changes.
Signed-off-by: Jani Nikula
---
drivers/gpu/drm/i915/Makefile.header-test | 1 +
drivers/gpu/drm/i915/i915_drv.h | 11 ++-
drivers/gpu/drm/i915/intel_frontbuffer.h | 10 ++
3 files changed, 13
== Series Details ==
Series: tests/i915/gem_madvise.c: Add more mappings
URL : https://patchwork.freedesktop.org/series/59021/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5875 -> IGTPW_2790
Summary
---
**SUCCESS**
== Series Details ==
Series: series starting with [1/7] drm/i915/psr: Update PSR2 SU corruption
workaround comment (rev2)
URL : https://patchwork.freedesktop.org/series/58974/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5875 -> Patchwork_12686
On Tue, Apr 02, 2019 at 11:22:22PM -0700, Aditya Swarup wrote:
> From: Clinton Taylor
>
> v2: Fix commit msg to reflect why issue occurs(Jani)
> Set GCP_COLOR_INDICATION only when we set 10/12 bit deep color.
>
> Changing settings from 10/12 bit deep color to 8 bit(& vice versa)
> doesn't work
== Series Details ==
Series: series starting with [1/7] drm/i915/psr: Update PSR2 SU corruption
workaround comment (rev2)
URL : https://patchwork.freedesktop.org/series/58974/
State : warning
== Summary ==
$ dim sparse origin/drm-tip
Sparse version: v0.5.2
Commit: drm/i915/psr: Update PSR2
== Series Details ==
Series: series starting with [1/7] drm/i915/psr: Update PSR2 SU corruption
workaround comment (rev2)
URL : https://patchwork.freedesktop.org/series/58974/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
73fa7ed439e6 drm/i915/psr: Update PSR2 SU corruption
On Tue, Apr 02, 2019 at 11:22:22PM -0700, Aditya Swarup wrote:
> From: Clinton Taylor
>
> v2: Fix commit msg to reflect why issue occurs(Jani)
> Set GCP_COLOR_INDICATION only when we set 10/12 bit deep color.
>
> Changing settings from 10/12 bit deep color to 8 bit(& vice versa)
> doesn't work
Check madvise versus more memory mappings.
Suggested-by: Chris Wilson
Signed-off-by: Antonio Argenziano
---
tests/i915/gem_madvise.c | 115 ++-
1 file changed, 76 insertions(+), 39 deletions(-)
diff --git a/tests/i915/gem_madvise.c
On Thu, Apr 04, 2019 at 01:36:25PM +0530, Vandita Kulkarni wrote:
> Mipi dsi programs the transcoder timings as part of
> encoder enable sequence, with dual link or single link
> in consideration. Hence add get transcoder timings as
> part of the encoder's get_config function.
>
> Signed-off-by:
Hi Da.*,
So this one is a blockbuster!
We've got 1 new gpu, 1 new display controller, 2 new panels, 4 new ioctls, and 1
new encoder.
Everything seems to check out on my side of the world, please pull.
drm-misc-next-2019-04-04:
drm-misc-next for 5.2:
UAPI Changes:
-syncobj: Add
On Wed, 2019-04-03 at 17:31 -0700, Rodrigo Vivi wrote:
> On Wed, Apr 03, 2019 at 04:35:38PM -0700, José Roberto de Souza
> wrote:
> > PSR is only supported in eDP transcoder and there is only one
> > instance of it, so lets drop all of this code.
>
> Is this sentence true? I mean, in the way it
On Wed, 2019-04-03 at 17:27 -0700, Rodrigo Vivi wrote:
> On Wed, Apr 03, 2019 at 04:35:35PM -0700, José Roberto de Souza
> wrote:
> > Even when driver is reloaded and hits this scenario the PSR mutex
> > should be initialized, otherwise reading PSR debugfs status will
> > execute mutex_lock() over
== Series Details ==
Series: drm/i915/dp: On link train failure on eDP, retry with max params first
(rev2)
URL : https://patchwork.freedesktop.org/series/58975/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5874 -> Patchwork_12685
== Series Details ==
Series: drm/i915/dp: On link train failure on eDP, retry with max params first
(rev2)
URL : https://patchwork.freedesktop.org/series/58975/
State : warning
== Summary ==
$ dim checkpatch origin/drm-tip
58de6f859ee4 drm/i915/dp: On link train failure on eDP, retry with
== Series Details ==
Series: Fix mipi dsi pipe_config mismatch for icl (rev2)
URL : https://patchwork.freedesktop.org/series/58990/
State : failure
== Summary ==
Applying: drm/i915: Fix pipe config timing mismatch warnings
Applying: drm/i915: gen11_dsi_get_pixel_fmt can be static
error: sha1
On Thu, 04 Apr 2019, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915: add Makefile magic for testing headers are self-contained
> (rev4)
> URL : https://patchwork.freedesktop.org/series/58938/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_5863_full ->
== Series Details ==
Series: drm/i915: Fix context IDs not released on driver hot unbind
URL : https://patchwork.freedesktop.org/series/58996/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_5871 -> Patchwork_12683
Summary
On Thu, 2019-03-28 at 23:05 +0200, Ville Syrjala wrote:
> From: Ville Syrjälä
>
> Just so we don't leave gen2/3 out in the cold let's advertize the
> legacy LUT via the GAMMA_LUT/GAMMA_LUT_SIZE props. Without the
> GAMMA_LUT prop we can't actually load a LUT using the atomic ioctl
> (in
== Series Details ==
Series: drm/i915: Be precise in types for i915_gem_busy (rev2)
URL : https://patchwork.freedesktop.org/series/58993/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5871 -> Patchwork_12682
Summary
Hi Dave and Daniel,
Here goes drm-intel-fixes-2019-04-04:
Only one fix for DSC (backoff after drm_modeset_lock deadlock)
and GVT's fixes including vGPU display plane size calculation,
shadow mm pin count, error recovery path for workload create
and one kerneldoc fix.
Thanks,
Rodrigo.
The
Certain eDP panels fail to link train with optimized settings for
link rate and lane count and need the max link parameters to be used
for link training to pass.
So in on link training failure for eDP, retry the link training
with max link parameters first since this tends to fix link
failures on
Hi Vandita,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on v5.1-rc3 next-20190404]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https
Fixes: bab7d9431d53 ("drm/i915: Fix pipe config mismatch for bpp, output
format")
Signed-off-by: kbuild test robot
---
icl_dsi.c |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/icl_dsi.c b/drivers/gpu/drm/i915/icl_dsi.c
index 69cd6b2..163dc54 100644
On Thu, 04 Apr 2019, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-04-04 11:50:14)
>> On Thu, 2019-04-04 at 11:43 +0100, Chris Wilson wrote:
>> > Quoting Janusz Krzysztofik (2019-04-04 11:40:24)
>> > > On Thu, 2019-04-04 at 11:28 +0100, Chris Wilson wrote:
>> > > > Quoting Janusz
== Series Details ==
Series: series starting with [1/2] drm/i915: add Makefile magic for testing
headers are self-contained
URL : https://patchwork.freedesktop.org/series/58963/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5865_full -> Patchwork_12676_full
On Thu, Apr 04, 2019 at 08:33:57AM +0100, Chris Wilson wrote:
> drivers/gpu/drm/i915/intel_cdclk.c:2116: warning: Function parameter or
> member 'dev_priv' not described in 'intel_cdclk_needs_cd2x_update'
>
> Signed-off-by: Chris Wilson
> Cc: Ville Syrjälä
> Cc: Abhay Kumar
> Cc: Imre Deak
== Series Details ==
Series: drm/i915: add immutable zpos plane properties (rev2)
URL : https://patchwork.freedesktop.org/series/58761/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5865_full -> Patchwork_12675_full
== Series Details ==
Series: drm/i915: add immutable zpos plane properties (rev2)
URL : https://patchwork.freedesktop.org/series/58761/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5865_full -> Patchwork_12675_full
On 28/03/2019 11:49, Chris Wilson wrote:
We only need the warning once, not for the several thousand relocations
we try. The current execbuf implementation will set all presumed_offset
to -1 so this loop should quit on the first entry if we hit the
pagefault, but for the sake of completeness
== Series Details ==
Series: drm/i915: Fixup kerneldoc for intel_cdclk_needs_cd2x_update
URL : https://patchwork.freedesktop.org/series/58988/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5869 -> Patchwork_12681
Summary
On 04/04/2019 11:19, Chris Wilson wrote:
Mixing u8 and -1u together leads to zero-extended integer expansion, and
comparing 0x00ff against 0x, causing us to report a mixed
uabi-class request as not busy.
The input flag is a u8, and we want to generate a u32 uABI response,
mark our
Quoting Janusz Krzysztofik (2019-04-04 11:50:14)
> On Thu, 2019-04-04 at 11:43 +0100, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2019-04-04 11:40:24)
> > > On Thu, 2019-04-04 at 11:28 +0100, Chris Wilson wrote:
> > > > Quoting Janusz Krzysztofik (2019-04-04 11:24:45)
> > > > > From:
On Thu, 2019-04-04 at 11:43 +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-04-04 11:40:24)
> > On Thu, 2019-04-04 at 11:28 +0100, Chris Wilson wrote:
> > > Quoting Janusz Krzysztofik (2019-04-04 11:24:45)
> > > > From: Janusz Krzysztofik
> > > >
> > > > In case the driver gets
Quoting Janusz Krzysztofik (2019-04-04 11:40:24)
> On Thu, 2019-04-04 at 11:28 +0100, Chris Wilson wrote:
> > Quoting Janusz Krzysztofik (2019-04-04 11:24:45)
> > > From: Janusz Krzysztofik
> > >
> > > In case the driver gets unbound while a device is open, kernel
> > > panic
> > > may be forced
On Thu, 2019-04-04 at 11:28 +0100, Chris Wilson wrote:
> Quoting Janusz Krzysztofik (2019-04-04 11:24:45)
> > From: Janusz Krzysztofik
> >
> > In case the driver gets unbound while a device is open, kernel
> > panic
> > may be forced if a list of allocated context IDs is not empty.
> >
> > When
Quoting Janusz Krzysztofik (2019-04-04 11:24:45)
> From: Janusz Krzysztofik
>
> In case the driver gets unbound while a device is open, kernel panic
> may be forced if a list of allocated context IDs is not empty.
>
> When a device is open, the list may happen to be not empty because a
>
From: Janusz Krzysztofik
In case the driver gets unbound while a device is open, kernel panic
may be forced if a list of allocated context IDs is not empty.
When a device is open, the list may happen to be not empty because a
context ID, once allocated by a context ID allocator to a context
Mixing u8 and -1u together leads to zero-extended integer expansion, and
comparing 0x00ff against 0x, causing us to report a mixed
uabi-class request as not busy.
The input flag is a u8, and we want to generate a u32 uABI response,
mark our functions so.
Fixes: c8b502422bfe
Mixing u8 and -1u together leads to zero-extended integer expansion, and
comparing 0x00ff against 0x, causing us to report a mixed
uabi-class request as not busy.
The input flag is a u8, and we want to generate a u32 uABI response,
mark our functions so.
Fixes: c8b502422bfe
Mipi dsi programs the transcoder timings as part of
encoder enable sequence, with dual link or single link
in consideration. Hence add get transcoder timings as
part of the encoder's get_config function.
Signed-off-by: Vandita Kulkarni
---
drivers/gpu/drm/i915/icl_dsi.c | 51
In case of dual link mode, the mode clock that we get
from the VBT is halved.
Signed-off-by: Vandita Kulkarni
---
drivers/gpu/drm/i915/icl_dsi.c | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/icl_dsi.c b/drivers/gpu/drm/i915/icl_dsi.c
index
This is series fixes the WARN_ON that we see due to
pipe_config mismatch on mipi dsi for icl.
Only DSI0 trancoder regs are read even in case of dual link mode
as the values programmed for DSI0 and DSI1 transcoder registers
are same.
Vandita Kulkarni (3):
drm/i915: Fix pipe config timing
Read back the pixel fomrat register and get the bpp.
Signed-off-by: Vandita Kulkarni
---
drivers/gpu/drm/i915/icl_dsi.c | 28
1 file changed, 28 insertions(+)
diff --git a/drivers/gpu/drm/i915/icl_dsi.c b/drivers/gpu/drm/i915/icl_dsi.c
index db6bc3d..69cd6b2 100644
== Series Details ==
Series: drm/i915/gvt: Prevent use-after-free in ppgtt_free_all_spt()
URL : https://patchwork.freedesktop.org/series/58985/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_5869 -> Patchwork_12680
Summary
Quoting Zhenyu Wang (2019-04-04 08:48:34)
> On 2019.04.04 08:30:56 +0100, Chris Wilson wrote:
> > ppgtt_free_all_spt() iterates the radixtree as it is deleting it,
> > forgoing all protection against the leaves being freed in the process
> > (leaving the iter pointing into the void).
> >
> > A
1 - 100 of 108 matches
Mail list logo
