[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 10:02:43PM +0200, Daniel Vetter wrote: >On Tue, Oct 11, 2016 at 9:44 PM, Brian Starkey >wrote: >> Hi, >> >> >> On Tue, Oct 11, 2016 at 07:01:33PM +0200, Daniel Vetter wrote: >>> >>> On Tue, Oct 11, 2016 at 6:43 PM, Brian Starkey >>> wrote: Hi Daniel,

[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 9:44 PM, Brian Starkey wrote: > Hi, > > > On Tue, Oct 11, 2016 at 07:01:33PM +0200, Daniel Vetter wrote: >> >> On Tue, Oct 11, 2016 at 6:43 PM, Brian Starkey >> wrote: >>> >>> Hi Daniel, >>> >>> Firstly thanks very much for having a look. >>> >>> >>> On Tue, Oct 11, 2016

[RFC 0/6] Module for tracking/accounting shared memory buffers

On Tue, Oct 11, 2016 at 7:50 PM, Ruchi Kandoi wrote: > This patchstack introduces a new "memtrack" module for tracking and accounting > memory exported to userspace as shared buffers, like dma-buf fds or GEM > handles. btw, I wouldn't care much about the non-dmabuf case.. dri2/flink is kind of

[RFC PATCH 00/11] Introduce writeback connectors

Hi, On Tue, Oct 11, 2016 at 07:01:33PM +0200, Daniel Vetter wrote: >On Tue, Oct 11, 2016 at 6:43 PM, Brian Starkey >wrote: >> Hi Daniel, >> >> Firstly thanks very much for having a look. >> >> >> On Tue, Oct 11, 2016 at 05:43:59PM +0200, Daniel Vetter wrote: >>> >>> On Tue, Oct 11, 2016 at

[Bug 60879] [radeonsi] Tahiti LE: GFX block is not functional, CP is okay

ing this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/00bac1a9/attachment.html>

[REGRESSION v4.7] i915 / drm crash when undocking from DP monitors

Certainly, done and done. The bug is filed at: https://bugs.freedesktop.org/show_bug.cgi?id=98211 Thanks! On Tue, Oct 11, 2016 at 6:55 AM, Jani Nikula wrote: > On Sat, 08 Oct 2016, Vadim Lobanov wrote: >> I'm seeing a repeatable crash on my HP EliteBook 840 G2/2216 when >> booting it while in

[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 03:53:57PM +0100, Brian Starkey wrote: > Hi, > > This RFC series introduces a new connector type: > DRM_MODE_CONNECTOR_WRITEBACK > It is a follow-on from a previous discussion: [1] > > Writeback connectors are used to expose the memory writeback engines > found in some

[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 6:43 PM, Brian Starkey wrote: > Hi Daniel, > > Firstly thanks very much for having a look. > > > On Tue, Oct 11, 2016 at 05:43:59PM +0200, Daniel Vetter wrote: >> >> On Tue, Oct 11, 2016 at 03:53:57PM +0100, Brian Starkey wrote: >>> >>> Hi, >>> >>> This RFC series

[RFC PATCH 02/11] drm/fb-helper: Skip writeback connectors

On Tue, Oct 11, 2016 at 6:47 PM, Brian Starkey wrote: > On Tue, Oct 11, 2016 at 05:44:48PM +0200, Daniel Vetter wrote: >> >> On Tue, Oct 11, 2016 at 03:53:59PM +0100, Brian Starkey wrote: >>> >>> Writeback connectors aren't much use to the fbdev helpers, as they won't >>> show anything to the

[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 6:25 PM, Ville Syrjälä wrote: >> Writeback connector usage: >> -- >> Due to connector routing changes being treated as "full modeset" >> operations, any client which wishes to use a writeback connector >> should include the connector in every

[git pull] drm pull for v4.9

On Tue, Oct 11, 2016 at 2:14 PM, Dave Airlie wrote: > > this email is all in small letters because my gpg key expired so I couldn't > sign the tag, and it's too early in the morning for me to go do gpg stuff. I'm happy that you have found alternative identity management model, but I'm not sure

[Bug 98200] [radeon] kernel hangs during shutdown - drm-next-4.9-/+wip

: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/c1dc3154/attachment.html>

[Intel-gfx] [PATCH v5 06/11] drm/i915: Enable i915 perf stream for Haswell OA unit

v->perf.oa.ops.enable_metric_set = hsw_enable_metric_set; > > + dev_priv->perf.oa.ops.disable_metric_set = > hsw_disable_metric_set; > > + dev_priv->perf.oa.ops.oa_enable = gen7_oa_enable; > > + dev_priv->perf.oa.ops.oa_disable = gen7_oa_disable; > > + dev_priv->perf.oa.ops.update_hw_ctx_id_locked = > > + gen7_update_hw_ctx_id_locked; > > + dev_priv->perf.oa.ops.read = gen7_oa_read; > > + dev_priv->perf.oa.ops.oa_buffer_is_empty = > > + gen7_oa_buffer_is_empty_fop_unlocked; > > + > > + dev_priv->perf.oa.timestamp_frequency = 1250; > Slightly magical. > Not sure how to dymistify this with a comment; it pretty much is just a magic hardware constant detailing the fixed frequency of the HW timestamp counter. I think it's likely not actually specified in the PRMs for < gen 9 considering that I think for all gens prior to SKL the frequency has remained the same. Other software that currently deals with these raw HW timestamps (such as Mesa) actually work in terms of an integer multiplier (80) when scaling HW timestamps to have nanosecond units, and you can derive the frequency from that. Maybe the scalar of 80 is noted in the PRMs somewhere instead of a frequency. Awkwardly once we get to Skylake an integer multiple no longer works, so it's preferable to track the platform differences in terms of a frequency like this. I'll consider noting some of this in a comment. > > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c > b/drivers/gpu/drm/i915/intel_ringbuffer.c > > index 7a74750..22d5ff1 100644 > > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c > > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c > > @@ -2043,8 +2043,14 @@ static int intel_ring_context_pin(struct > i915_gem_context *ctx, > > if (ret) > > goto error; > > > > - ret = i915_vma_pin(ce->state, 0, ctx->ggtt_alignment, > > - PIN_GLOBAL | PIN_HIGH); > > + if (engine->id == RCS) { > > + u64 vma_flags = PIN_GLOBAL | PIN_HIGH; > Maybe move this up a level and reuse for both paths. > Ah yep, > > > + ret = i915_gem_context_pin_legacy_ > rcs_state(engine->i915, > > + ctx, > > + > vma_flags); > > + } else > > + ret = i915_vma_pin(ce->state, 0, > ctx->ggtt_alignment, > > + PIN_GLOBAL | PIN_HIGH); > > if (ret) > > goto error; > > } > I'm travelling this week, but will send out an updated patch when I've had a chance to test the change for initializing the specific_ctx_id on haswell. thanks for the feedback. Regards, - Robert -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/d862e742/attachment-0001.html>

[RFC PATCH 04/11] drm: Add __drm_framebuffer_remove_atomic

On Tue, Oct 11, 2016 at 03:54:01PM +0100, Brian Starkey wrote: > Implement the CRTC/Plane disable functionality of drm_framebuffer_remove > using the atomic API, and use it if possible. > > For atomic drivers, this removes the possibility of several commits when > a framebuffer is in use by more

[RFC PATCH 07/11] drm: Add writeback-connector pixel format properties

On Tue, Oct 11, 2016 at 03:54:04PM +0100, Brian Starkey wrote: > So that userspace can determine what pixel formats are supported for a > writeback connector's framebuffer, add a pixel format list to writeback > connectors. This is in the form of an immutable blob containing an array > of formats,

[RFC PATCH 02/11] drm/fb-helper: Skip writeback connectors

On Tue, Oct 11, 2016 at 05:44:48PM +0200, Daniel Vetter wrote: >On Tue, Oct 11, 2016 at 03:53:59PM +0100, Brian Starkey wrote: >> Writeback connectors aren't much use to the fbdev helpers, as they won't >> show anything to the user. Skip them when looking for candidate output >> configurations. >>

[RFC PATCH 02/11] drm/fb-helper: Skip writeback connectors

On Tue, Oct 11, 2016 at 03:53:59PM +0100, Brian Starkey wrote: > Writeback connectors aren't much use to the fbdev helpers, as they won't > show anything to the user. Skip them when looking for candidate output > configurations. > > Signed-off-by: Brian Starkey > --- >

[RFC PATCH 00/11] Introduce writeback connectors

On Tue, Oct 11, 2016 at 03:53:57PM +0100, Brian Starkey wrote: > Hi, > > This RFC series introduces a new connector type: > DRM_MODE_CONNECTOR_WRITEBACK > It is a follow-on from a previous discussion: [1] > > Writeback connectors are used to expose the memory writeback engines > found in some

[RFC PATCH 00/11] Introduce writeback connectors

Hi Daniel, Firstly thanks very much for having a look. On Tue, Oct 11, 2016 at 05:43:59PM +0200, Daniel Vetter wrote: >On Tue, Oct 11, 2016 at 03:53:57PM +0100, Brian Starkey wrote: >> Hi, >> >> This RFC series introduces a new connector type: >> DRM_MODE_CONNECTOR_WRITEBACK >> It is a

[PATCH 2/9] drm/sun4i: tcon: Move SoC specific quirks to a DT matched data structure

On Fri, Oct 7, 2016 at 4:38 PM, Maxime Ripard wrote: > Hi, > > On Fri, Oct 07, 2016 at 12:06:22AM +0800, Chen-Yu Tsai wrote: >> +struct sun4i_tcon_quirks { >> + boolis_sun5i; /* sun5i has undocumented mux */ >> + boolhas_channel_1; /* a33 does not have channel 1 */ >> +

[PULL] drm-intel-next-fixes

Hi Dave - A big bunch of i915 fixes for drm-next / v4.9 merge window, with more than half of them also cc: stable. We also continue to have more Fixes: annotations for our fixes, which should help the backporters and archeologists. There's also a fix to your v4.8-rc8 backmerge to drm-next,

[REGRESSION v4.7] i915 / drm crash when undocking from DP monitors

On Sat, 08 Oct 2016, Vadim Lobanov wrote: > I'm seeing a repeatable crash on my HP EliteBook 840 G2/2216 when > booting it while in a docking station connected to two external > DisplayPort monitors, undocking, and then either logging out or > shutting down -- regardless of whether I've redocked

[RFC 6/6] drivers: staging: ion: add ION_IOC_TAG ioctl

From: Greg Hackmann ION_IOC_TAG provides a userspace interface for tagging buffers with their memtrack usage after allocation. Signed-off-by: Ruchi Kandoi --- drivers/staging/android/ion/ion-ioctl.c | 17 + drivers/staging/android/uapi/ion.h | 25

[RFC 5/6] memtrack: Add memtrack accounting for forked processes.

When a process is forked, all the buffers are shared with the forked process too. Adds the functionality to add memtrack accounting for the forked processes. Forked process gets a copy of the mapped pages of the parent process. This patch makes sure that the new mapped pages are attributed to the

[RFC 4/6] memtrack: Adds the accounting to keep track of all mmaped/unmapped pages.

Since mmaped pages will be accounted by the PSS, memtrack needs a way to differentiate the total memory that hasn't been accounted for. Signed-off-by: Ruchi Kandoi Signed-off-by: Greg Hackmann --- drivers/misc/memtrack.c | 175 --

[RFC 3/6] dma-buf: add memtrack support

Signed-off-by: Greg Hackmann Signed-off-by: Ruchi Kandoi --- drivers/dma-buf/dma-buf.c | 37 ++ drivers/staging/android/ion/ion.c | 14 + drivers/staging/android/ion/ion_priv.h | 2 ++ include/linux/dma-buf.h| 5

[RFC 2/6] drivers: misc: add memtrack

Shared-buffer allocators like ion or GEM traditionally call into CMA or alloc_pages() to get backing memory, meaning these allocations will not show up in any process's mm counters. But since these allocations are often used for things like graphics buffers that can be extremely large, the user

[RFC 1/6] fs: add installed and uninstalled file_operations

These optional file_operations notify a file implementation when it is installed or uninstalled from a task's fd table. This can be used for accounting of file-backed shared resources like dma-buf. This involves some changes to the __fd_install() and __close_fd() APIs to actually pass along the

[RFC 0/6] Module for tracking/accounting shared memory buffers

This patchstack introduces a new "memtrack" module for tracking and accounting memory exported to userspace as shared buffers, like dma-buf fds or GEM handles. Any process holding a reference to these buffers will keep the kernel from reclaiming its backing pages. mm counters don't provide a

[Intel-gfx] [PATCH 04/10] drm/i915/gen9: Cleanup skl_pipe_wm_active_state

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > This function is a wreck, let's help it get it's life back together > and > cleanup all of the copy pasta here. s/it's/its/ Idea for your next patch series: rename skl_pipe_wm_active_state()'s "i" parameter to something more meaningful.

[PATCH v2 03/10] drm/i915/gen9: Make skl_wm_level per-plane

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > Having skl_wm_level contain all of the watermarks for each plane is > annoying since it prevents us from having any sort of object to > represent a single watermark level, something we take advantage of in > the next commit to cut down on all

[Intel-gfx] [PATCH v2 01/10] drm/i915/skl: Move per-pipe ddb allocations into crtc states

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > First part of cleaning up all of the skl watermark code. This moves > the > structures for storing the ddb allocations of each pipe into > intel_crtc_state, along with moving the structures for storing the > current ddb allocations active on

[Bug 98200] [radeon] kernel hangs during shutdown - drm-next-4.9-/+wip

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/2fc6fa5a/attachment.html>

[Bug 98200] [radeon] kernel hangs during shutdown - drm-next-4.9-/+wip

nee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/1e441212/attachment.html>

[RFC] drm/fb-helper: reject any changes to the fbdev

The current fbdev emulation does not allow to push back changes in width, height or depth to KMS, hence reject any changes with an error. This makes sure that fbdev ioctl's fail properly and user space does not assume that changes succeeded. Signed-off-by: Stefan Agner --- This rejects

[Bug 155711] Aorus X5, Backlight hotkeys non-functional

https://bugzilla.kernel.org/show_bug.cgi?id=155711 --- Comment #11 from seqrteam at gmail.com --- Just a gentle bump on this -- any ideas if it's possible to fix this issue, or if one should be looking elsewhere for help with this (e.g. complaining to NVidia)? Let me know if there is any

[PATCH 1/8] drm: mali-dp: Set the drm->irq_enabled flag to match driver's state.

On Tue, Oct 11, 2016 at 03:26:02PM +0100, Brian Starkey wrote: > From: Liviu Dudau > > Mali DP driver does not use drm_irq_{un,}install() function so the > drm->irq_enabled flag does not get set automatically. > drm_wait_vblank() checks the value of the flag among other functions. > >

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

+Rex to review this. Alex On Sun, Oct 9, 2016 at 3:23 PM, Grazvydas Ignotas wrote: > Currently the driver crashes if smu7_enable_dpm_tasks() returns early, > which it does if DPM is already active. It seems to be better just to > continue anyway, at least I haven't noticed any ill effects. It's

[RFC PATCH 11/11] drm: mali-dp: Add writeback connector

Mali-DP has a memory writeback engine which can be used to write the composition result to a memory buffer. Expose this functionality as a DRM writeback connector on supported hardware. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/Makefile |1 +

[RFC PATCH 10/11] drm: mali-dp: Add support for writeback on DP550/DP650

From: Liviu Dudau Mali-DP display processors are able to write the composition result to a memory buffer via the SE. Add entry points in the HAL for enabling/disabling this feature, and implement support for it on DP650 and DP550. DP500 acts differently and so is omitted

[RFC PATCH 09/11] drm: mali-dp: Add RGB writeback formats for DP550/DP650

Add a layer bit for the SE memory-write, and add it to the pixel format matrix for DP550/DP650. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_hw.c | 28 ++-- drivers/gpu/drm/arm/malidp_hw.h |1 + 2 files changed, 15 insertions(+), 14 deletions(-)

[RFC PATCH 08/11] drm: mali-dp: Rename malidp_input_format

We're going to use the same format list for output formats, so rename everything related to input formats to avoid confusion. Signed-off-by: Brian Starkey Reviewed-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_hw.c | 24 drivers/gpu/drm/arm/malidp_hw.h |

[RFC PATCH 07/11] drm: Add writeback-connector pixel format properties

So that userspace can determine what pixel formats are supported for a writeback connector's framebuffer, add a pixel format list to writeback connectors. This is in the form of an immutable blob containing an array of formats, and an immutable uint holding the array size. Signed-off-by: Brian

[RFC PATCH 06/11] drm: Expose fb_id property for writeback connectors

Expose the framebuffer for writeback connectors to userspace by attaching the fb_id property to them. Signed-off-by: Brian Starkey --- drivers/gpu/drm/drm_atomic.c|9 + drivers/gpu/drm/drm_connector.c |4 2 files changed, 13 insertions(+) diff --git

[RFC PATCH 05/11] drm: Add fb to connector state

Add a framebuffer to the connector state, for use as the output target by writeback connectors. If a framebuffer is in use by a writeback connector when userspace removes it, it is handled by removing the framebuffer from the connector. Signed-off-by: Brian Starkey ---

[RFC PATCH 04/11] drm: Add __drm_framebuffer_remove_atomic

Implement the CRTC/Plane disable functionality of drm_framebuffer_remove using the atomic API, and use it if possible. For atomic drivers, this removes the possibility of several commits when a framebuffer is in use by more than one CRTC/plane. Additionally, this will provide a suitable place to

[RFC PATCH 03/11] drm: Extract CRTC/plane disable from drm_framebuffer_remove

In preparation for adding an atomic version of the disable code, extract the actual disable operation into a separate function. Signed-off-by: Brian Starkey --- drivers/gpu/drm/drm_framebuffer.c | 87 +++-- 1 file changed, 54 insertions(+), 33 deletions(-)

[RFC PATCH 02/11] drm/fb-helper: Skip writeback connectors

Writeback connectors aren't much use to the fbdev helpers, as they won't show anything to the user. Skip them when looking for candidate output configurations. Signed-off-by: Brian Starkey --- drivers/gpu/drm/drm_fb_helper.c |4 1 file changed, 4 insertions(+) diff --git

[RFC PATCH 01/11] drm: Add writeback connector type

Writeback connectors represent writeback engines which can write the CRTC output to a memory framebuffer. Add a writeback connector type, hidden from userspace behind a client cap. They are hidden from non-aware clients so that they do not attempt to use writeback connectors to provide visual

[RFC PATCH 00/11] Introduce writeback connectors

Hi, This RFC series introduces a new connector type: DRM_MODE_CONNECTOR_WRITEBACK It is a follow-on from a previous discussion: [1] Writeback connectors are used to expose the memory writeback engines found in some display controllers, which can write a CRTC's composition result to a memory

[PATCH 8/8] drm: mali-dp: Store internal format and n_planes in plane state

Save a search through the format lists at commit-time by storing the internal format ID and number of planes in our plane state. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_drv.h|3 +++ drivers/gpu/drm/arm/malidp_planes.c | 27 --- 2 files

[PATCH 7/8] drm: mali-dp: Enable alpha blending

Always enable pixel-level alpha blending with the background, so that buffers which include an alpha channel are displayed correctly. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_planes.c | 32 ++-- 1 file changed, 26 insertions(+), 6 deletions(-)

[PATCH 6/8] drm: mali-dp: Refactor plane initialisation

As we add more features, it makes sense to skip all the features not supported by the smart layer together, instead of checking each one individually. Achieve this by refactoring the plane init loop. Signed-off-by: Brian Starkey Acked-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_planes.c |

[PATCH 5/8] arm: mali-dp: Extract mode_config cleanup into malidp_fini

Split out malidp_fini as the opposite of malidp_init. This helps keep the cleanup paths neat and easier to manage. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_drv.c | 12 1 file changed, 8 insertions(+), 4 deletions(-) diff --git

[PATCH 4/8] drm: mali-dp: Add pitch alignment check for planes

Check that the framebuffer pitches are appropriately aligned when checking planes. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_planes.c | 15 ++- 1 file changed, 14 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/arm/malidp_planes.c

[PATCH 3/8] drm: mali-dp: Add pitch alignment check function

Different hardware versions have different requirements when it comes to pitch alignment. Add a function which can be used to check pitch alignment for a device. Signed-off-by: Brian Starkey --- drivers/gpu/drm/arm/malidp_hw.c |3 +++ drivers/gpu/drm/arm/malidp_hw.h |9 + 2

[PATCH 2/8] drm: mali-dp: Clear the config_valid flag before using it in wait_event.

From: Liviu Dudau config_valid variable is used to signal the activation of the CVAL request when the vsync interrupt has fired. malidp_set_and_wait_config_valid() uses the variable in wait_event_interruptible_timeout without clearing it first, so the wait is skipped.

[PATCH 1/8] drm: mali-dp: Set the drm->irq_enabled flag to match driver's state.

From: Liviu Dudau Mali DP driver does not use drm_irq_{un,}install() function so the drm->irq_enabled flag does not get set automatically. drm_wait_vblank() checks the value of the flag among other functions. Signed-off-by: Liviu Dudau --- Hi, This series is a bunch of

[PATCH v4] drm/panel: simple: Add support for AUO t215hvn01

The AUO t215hvn01 is a 21.5" FHD (1920x1080) color TFT LCD panel. This panel is used on the Acer Chromebase 21.5-inch All-in-One (DC221HQ). Link to spec: http://www.udmgroup.com/ftp/T215HVN01.0.pdf v2: fix alphabetical order v3: remove minor revision suffix ".0" and add link to spec v4: add

[Bug 98166] [vulkan, radv] make install regenerates radv_timestamp.h and rebuilds radv_device.lo

: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/0fbe0607/attachment-0001.html>

[Bug 98167] [vulkan, radv] missing libgcrypt and openssl devel results in linker error in libvulkan_common

: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/5d90b44d/attachment.html>

[PATCH] drm/i915: Before pageflip, also wait for shared dmabuf fences.

Am 11.10.2016 um 05:58 schrieb Michel Dänzer: > On 07/10/16 09:34 PM, Mike Lothian wrote: >> This has discussion has gone a little quiet >> >> Was there any agreement about what needed doing to get this working >> for i965/amdgpu? > Christian, do you see anything which could prevent the solution

[Bug 98168] [vulkan, radv] Talos rendering glitches on Ultra settings on Tonga

: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/63331856/attachment.html>

[PATCH] drm/gma500: remove useless comment

Remove useless comment in framebuffer.c. Signed-off-by: Jiang Biao --- drivers/gpu/drm/gma500/framebuffer.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/framebuffer.c b/drivers/gpu/drm/gma500/framebuffer.c index 0fcdce0..3c8aa55 100644 ---

drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7.

t; > regards, > dan carpenter > > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/6319f749/attachment.html>

[Bug 97820] [BDW BYT SKL HSW IVB]Regression] [GPU Hang] with gem_reset_stats ban- and reset-stats- subtests

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/c8c5913a/attachment.html>

[git pull] drm for 4.8

What's the status of the 4.9 merge window pull request? The GPU side is the main remaining pile for this merge window according to linux-next. I'd hate to get a last-minute pull at the end of the week ... Linus

[PATCH] drm/i915: Before pageflip, also wait for shared dmabuf fences.

On 07/10/16 09:34 PM, Mike Lothian wrote: > > This has discussion has gone a little quiet > > Was there any agreement about what needed doing to get this working > for i965/amdgpu? Christian, do you see anything which could prevent the solution I outlined from working? -- Earthling Michel

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On Tue, 11 Oct 2016, "Sun, Jing A" wrote: > It's needed that DRM Driver module could be removed and reloaded after > kernel booting on the projects that I have been working on, and I hope > such module type change could be accepted. Looks like Iwai has similar > change request as well. Would you

[PATCH] drm/amdgpu: use .early_unregister hook to remove DP AUX i2c

On Sun, Oct 9, 2016 at 1:28 PM, Grazvydas Ignotas wrote: > When DisplayPort AUX channel i2c adapter is registered, drm_connector's > kdev member is used as a parent, so we get sysfs structure like: > /drm/card1/card1-DP-2/i2c-12 > Because of that, there is a problem when drm core (and not the

[Bug 98170] [vdpau] Error when calling vdp_output_surface_create

--- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/b71da101/attachment.html>

[PATCH v11 2/4] drm: Add API for capturing frame CRCs

Hello, I have been able to test it on my setup and, after implementing set_crc_source function, I have crc/data and crc/control entries for each of my crtc. "cat /sys/kernel/debug/dri/0/crtc-0/crc/data" is blocking but I'm really sure of my driver implementation... Anyway you could add my ack

[Intel-gfx] [PATCH] drm/i915: Add i915 perf infrastructure

sed the mistake here, just didn't get around to posting the patch. Also applied the notes to not redundantly init some vars, spurious new line, redundant include. Thanks, - Robert -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/1075dc85/attachment.html>

[RFC PATCH 00/11] Introduce writeback connectors

t -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 800 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/5660dc94/attachment-0001.sig>

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

On 11.10.2016 11:33, Jani Nikula wrote: > On Tue, 11 Oct 2016, "Sun, Jing A" wrote: >> It's needed that DRM Driver module could be removed and reloaded after >> kernel booting on the projects that I have been working on, and I hope >> such module type change could be accepted. Looks like Iwai has

[PATCH 2/9] drm/sun4i: tcon: Move SoC specific quirks to a DT matched data structure

lectrons.com -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/c35796a0/attachment.sig>

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

Hi, This patch misses dsi bus un-registration. However I have reviewed two patches of Takashi which solves the same issue more completely [1]. These patches were not accepted neither. [1]: https://lists.freedesktop.org/archives/dri-devel/2016-August/114870.html Regards Andrzej On 11.10.2016

drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7.

-- A non-text attachment was scrubbed... Name: 0001-drm-amd-powerplay-add-array-length-check-to-avoid-bu.patch Type: application/octet-stream Size: 1189 bytes Desc: 0001-drm-amd-powerplay-add-array-length-check-to-avoid-bu.patch URL: <https://lists.freedesktop.org/archives/dri-dev

[PATCH 1/1] gpu: drm: gma500: Use vma_pages()

On Tue, Oct 11, 2016 at 10:15 AM, Daniel Vetter wrote: > On Mon, Oct 10, 2016 at 07:22:47AM +0530, Shyam Saini wrote: >> On Mon, 2016-10-10 at 01:46 +0200, Patrik Jakobsson wrote: >> > On Mon, Oct 10, 2016 at 1:07 AM, Shyam Saini >> > wrote: >> > > >> > > Replace explicit computation of vma page

[PATCH] drm/gma500: remove useless comment

On Tue, Oct 11, 2016 at 02:03:45PM +0800, Jiang Biao wrote: > Remove useless comment in framebuffer.c. > > Signed-off-by: Jiang Biao Applied to drm-misc. -Daniel > --- > drivers/gpu/drm/gma500/framebuffer.c | 1 - > 1 file changed, 1 deletion(-) > > diff --git

[PATCH 1/1] gpu: drm: gma500: Use vma_pages()

On Mon, Oct 10, 2016 at 07:22:47AM +0530, Shyam Saini wrote: > On Mon, 2016-10-10 at 01:46 +0200, Patrik Jakobsson wrote: > > On Mon, Oct 10, 2016 at 1:07 AM, Shyam Saini > > wrote: > > > > > > Replace explicit computation of vma page count by a call to > > > vma_pages() > > Hi, I already have

drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7.

Hello Rex Zhu, This is a semi-automatic email about new static checker warnings. The patch 599a7e9fe1b6: "drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7." from Sep 9, 2016, leads to the following Smatch complaint:

[PULL] topic/drm-misc

Hi Dave, Just flushing out my -misc queue. Slightly important are the prime refcount/unload fixes from Chris. There's also the reservation stuff from Chris still pending, and Sumits hasn't landed that yet. Might get another pull for that, but pls don't hold up the main pull for it ;-) Cheers,

[bug report] drm/amd/powerplay: implement fw related smu interface for iceland.

Hello Rex Zhu, The patch 18aafc59b106: "drm/amd/powerplay: implement fw related smu interface for iceland." from Aug 23, 2016, leads to the following static checker warning: drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/iceland_smc.c:2462 iceland_set_mc_special_registers()

[Bug 98170] [vdpau] Error when calling vdp_output_surface_create

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/3bc3a022/attachment.html>

[PATCH]"drm: change DRM_MIPI_DSI module type from "bool" to "tristate".

Dear Maintainers, It's needed that DRM Driver module could be removed and reloaded after kernel booting on the projects that I have been working on, and I hope such module type change could be accepted. Looks like Iwai has similar change request as well. Would you please review it and let us

[Bug 98146] DRI_PRIME=1 and fullscreen issues

t was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/3a363d5b/attachment-0001.html>

[Bug 98146] DRI_PRIME=1 and fullscreen issues

isplay (5) for last few days. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/b824ed6d/attachment.html>

[Bug 98170] [vdpau] Error when calling vdp_output_surface_create

org/archives/dri-devel/attachments/20161011/fb7f5960/attachment.html>

[Bug 98146] DRI_PRIME=1 and fullscreen issues

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/1e0934df/attachment.html>

[radeon-alex:amd-staging-4.7 5/11] drivers/gpu/drm/amd/amdgpu/dce_virtual.c:662:3: warning: 'connector' may be used uninitialized in this function

: 43764 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161011/f14c6662/attachment-0001.gz>

[Bug 94726] [Tonga] ARK: Survival Evolved crashes on savegame load. Out of Memory

/attachments/20161011/820525c0/attachment.html>

[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

https://bugzilla.kernel.org/show_bug.cgi?id=51381 --- Comment #49 from Teofilis Martisius --- Hi, Ok, I got my laptop fixed and now my BIOS is v2.14 (was 2.06). Nothing changed. I have tested with kernel v4.8. I get same errors as in 4.8-rc4. Please let me know what else can I do to help get

[Bug 95017] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).

https://bugs.freedesktop.org/show_bug.cgi?id=95017 --- Comment #14 from erhard_f at mailbox.org --- It seems the patches to force Radeon cards into PCI-mode (or force it via radeon.agpmode=-1) are no definitive solution. My G4 and G5 Macs hold out longer running X but sooner or later a hard lock