On Sun, Aug 21, 2016 at 11:39:22AM +0530, Kamble, Sagar A wrote:
>
>
> On 8/20/2016 1:32 PM, Chris Wilson wrote:
> >On Sat, Aug 20, 2016 at 10:39:25AM +0530, Sagar Arun Kamble wrote:
> >>+ obj = dev_priv->guc.slpc.vma->obj;
> >>+ if (obj) {
> >OOPS.
> Fixed in next series.
> >
> >>+
In the next patch, a few rearrangements are made to make these static.
First, we move them so the changes are not lost in the noise.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_display.c | 239 ++-
1 file changed, 120 insertions(+), 119 deletions(-)
The generic atomic helper likes to skip a prepare_plane_fb() if it
decides that the plane->fb is unchanged. This is wrong for us for a
couple of reasons:
- if the pipe is reconfigured (i.e. a size change) but the framebuffer
is untouched, we still have to flush any rendering prior to the
re
Since an fb may have multiple VMA (due to rotations etc), we need to
wait a vblank and unpin the old VMA not if the fb itself is changed, but
if the underlying VMA is changed.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_display.c | 10 +++---
1 file changed, 7 insertions(+), 3
Just a quick tidy now to make the next patch neater.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_display.c | 43 +---
1 file changed, 25 insertions(+), 18 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_display.c
b/drivers/gpu/drm/i915/intel_
Now that we subclass our request from struct fence, we start using the
common primitives more freely and so avoid hand-rolling routines already
provided for by the helpers.
Signed-off-by: Chris Wilson
---
drivers/gpu/drm/i915/intel_atomic_plane.c | 3 --
drivers/gpu/drm/i915/intel_display.c
With atomic plane states we are able to track an allocation right from
preparation, during use and through to the final free after being
swapped out for a new plane. We can couple the VMA we pin for the
framebuffer (and its rotation) to this lifetime and avoid all the clumsy
lookups in between.
Si
On Sun, Aug 21, 2016 at 02:15:34PM +0100, Chris Wilson wrote:
> intel_cleanup_plane_fb(struct drm_plane *plane,
> struct drm_plane_state *old_state)
> {
> - struct drm_device *dev = plane->dev;
> - struct intel_plane_state *old_intel_state;
> - struct drm_i915_gem
From: Wei Yongjun
Fixes the following sparse warning:
drivers/gpu/drm/i915/intel_hotplug.c:480:6: warning:
symbol 'i915_hpd_poll_init_work' was not declared. Should it be static?
Also move the '{' to new line.
Signed-off-by: Wei Yongjun
---
drivers/gpu/drm/i915/intel_hotplug.c | 3 ++-
1 fi
On 8/21/2016 2:09 PM, Chris Wilson wrote:
On Sun, Aug 21, 2016 at 11:39:22AM +0530, Kamble, Sagar A wrote:
On 8/20/2016 1:32 PM, Chris Wilson wrote:
On Sat, Aug 20, 2016 at 10:39:25AM +0530, Sagar Arun Kamble wrote:
+ obj = dev_priv->guc.slpc.vma->obj;
+ if (obj) {
OOPS.
Fixed
This week's new regressions
+---+---+++
| BugId | Summary | Created on |
Bisect |
+---+---+++
| 97396 | [drm] stuck on bsd
Any comments?
Regards,
Libin
> -Original Message-
> From: libin.y...@linux.intel.com [mailto:libin.y...@linux.intel.com]
> Sent: Thursday, August 18, 2016 2:42 PM
> To: intel-gfx@lists.freedesktop.org; jani.nik...@linux.intel.com;
> ville.syrj...@linux.intel.com; Vetter, Daniel ;
> ti...
Hi Tom,
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on v4.8-rc3 next-20160819]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
[Suggest to use git(>=2.9.0) format-patch --base= (or --base=auto for
convenience) to r
On Fri, Aug 19, 2016 at 11:50:09AM -0600, Jonathan Corbet wrote:
> On Fri, 19 Aug 2016 11:52:15 +1000
> Stephen Rothwell wrote:
>
> > Today's linux-next merge of the jc_docs tree got a conflict in:
> >
> > Documentation/gpu/index.rst
> >
> > between commit:
> >
> > b754b35b089d ("vgaarbite
14 matches
Mail list logo
