[PATCH 00/24] drm: add extern C guard for the UAPI headers

On 27 April 2016 at 10:47, Russell King - ARM Linux wrote: > On Thu, Apr 21, 2016 at 09:17:13PM +0100, Emil Velikov wrote: >> Dave Airlie pointed out that "polluting" the headers in a manner as seen >> with this series might not be too wise. David H, can we hear your view >> on the topic ? > >

[PATCH] drm/dp: Allow signals to interrupt drm_aux-dev reads/writes

From: Ville Syrjälä Let's be nice and interrupt the dpcd aux-dev reads/writes when there's a signal pending. Much nicer if the user can hit ^C instead of having to sit around waiting for the read/write to finish. time dd if=/dev/drm_dp_aux0 bs=$((1024*1024)) ^C

[PATCH 19/24] drm/sis: add missing include drm.h for the UAPI header

On 27 April 2016 at 00:37, Dave Airlie wrote: > On 22 April 2016 at 18:37, Daniel Vetter wrote: >> On Thu, Apr 21, 2016 at 09:17:32PM +0100, Emil Velikov wrote: >>> Signed-off-by: Emil Velikov >> >> If the extern C stuff falls through, maybe we want to pull this one out >> ahead? > > I've

[GIT PULL] drm-hisilicon-next-2016-04-18 for 4.7

On 27 April 2016 at 07:43, Dave Airlie wrote: > On 19 April 2016 at 19:03, Xinliang Liu wrote: >> Hi Dave, >> >> This is the first pull request from drm-hisilicon and for 4.7. >> >> The patches add new hisilicon drm driver. >> >> The patches were reviewed here: >>

[PATCH v3 0/7] drm: Add fbdev deferred io support to helpers

Den 27.04.2016 21:24, skrev Daniel Vetter: > On Wed, Apr 27, 2016 at 08:16:29PM +0200, Noralf Trønnes wrote: >> This patchset adds fbdev deferred io support to drm_fb_helper and >> drm_fb_cma_helper. >> >> It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage >> through the

[PATCH v2 1/3] dt/bindings: display: Add DT bindings for Mali Display Processors.

On Mon, Apr 25, 2016 at 03:19:22PM +0100, Liviu Dudau wrote: > Add DT bindings documentation for the Mali Display Processor. The bindings > describe the Mali DP500, DP550 and DP650 processors from ARM Ltd. > > Cc: Rob Herring > Cc: Pawel Moll > Cc: Mark Rutland > Cc: Ian

[PATCH v4 04/11] drm: sun4i: Add DT bindings documentation

On Mon, Apr 25, 2016 at 03:22:45PM +0200, Maxime Ripard wrote: > The display pipeline of the Allwinner A10 is involving several loosely > coupled components. > > Add a documentation for the bindings. > > Signed-off-by: Maxime Ripard > --- > .../bindings/display/sunxi/sun4i-drm.txt |

[PATCH 2/2] drm/etnaviv: fix mmap operations for userptr and dma-buf objects

On Wed, Apr 27, 2016 at 02:39:21PM +0200, Lucas Stach wrote: > +static int etnaviv_gem_userptr_mmap_obj(struct etnaviv_gem_object > *etnaviv_obj, > + struct vm_area_struct *vma) > +{ > + return -EPERM; > +} EPERM The prot argument asks for PROT_EXEC but the mapped area

[PATCH v3 3/7] drm/fb-helper: Add fb_deferred_io support

Den 27.04.2016 21:20, skrev Daniel Vetter: > On Wed, Apr 27, 2016 at 08:16:32PM +0200, Noralf Trønnes wrote: >> This adds deferred io support to drm_fb_helper. >> The fbdev framebuffer changes are flushed using the callback >> (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker >>

[PATCH v3 0/7] drm: Add fbdev deferred io support to helpers

On Wed, Apr 27, 2016 at 08:16:29PM +0200, Noralf Trønnes wrote: > This patchset adds fbdev deferred io support to drm_fb_helper and > drm_fb_cma_helper. > > It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage > through the (struct drm_framebuffer_funcs)->dirty callback on

[PATCH v3 6/7] drm/qxl: Use drm_fb_helper deferred_io support

On Wed, Apr 27, 2016 at 08:16:35PM +0200, Noralf Trønnes wrote: > Use the fbdev deferred io support in drm_fb_helper which mirrors the > one qxl has had. > This patch has only been compile tested. > > Signed-off-by: Noralf Trønnes > --- > > Changes since v2: > - The

[PATCH v3 3/7] drm/fb-helper: Add fb_deferred_io support

On Wed, Apr 27, 2016 at 08:16:32PM +0200, Noralf Trønnes wrote: > This adds deferred io support to drm_fb_helper. > The fbdev framebuffer changes are flushed using the callback > (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker > ensuring that it always runs in process context. >

[PATCH 00/12] De-stage Sync File Framework

On Wed, Apr 27, 2016 at 01:27:07PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Hi, > > This patchset sits on top of Sync ABI Rework v13: > > https://www.spinics.net/lists/dri-devel/msg105667.html > > The first eight clean up and prepare sync_file for de-staging. The last four >

[PATCH 12/12] Documentation: add Sync File doc

On Wed, Apr 27, 2016 at 01:27:19PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Add sync_file documentation on dma-buf-sync_file.txt > --- > Documentation/dma-buf-sync_file.txt | 65 > + > 1 file changed, 65 insertions(+) > create mode 100644

i915: screen flicker

On Wed, 27 Apr 2016 20:36:13 +0300 Mihai Donțu wrote: > On Wed, 27 Apr 2016 08:28:20 -0700 Rodrigo Vivi wrote: > > Hi Mihai, > > > > What platform do you have? HSW or BDW? > > I have an i7, Haswell CPU. > > > If you don't know please provide lspci -nn > > I have attached the output of

i915: screen flicker

--- next part -- An embedded and charset-unspecified text was scrubbed... Name: lspci.txt URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/e594bf28/attachment.txt>

[PATCH] drm/omap: check plane size

On Wed, Apr 27, 2016 at 06:30:19PM +0300, Laurent Pinchart wrote: > Hi Tomi, > > (CC'ing Daniel) > > Thank you for the patch. > > On Tuesday 26 Apr 2016 13:16:42 Tomi Valkeinen wrote: > > At the moment we don't check the plane input/output sizes, which can > > lead to DSS HW errors when invalid

[PATCH v3 7/7] drm/udl: Use drm_fb_helper deferred_io support

Use the fbdev deferred io support in drm_fb_helper. The (struct fb_ops *)->fb_{fillrect,copyarea,imageblit} functions will now schedule a worker instead of being flushed directly like it was previously (recorded when in atomic). This patch has only been compile tested. Signed-off-by: Noralf

[PATCH v3 6/7] drm/qxl: Use drm_fb_helper deferred_io support

Use the fbdev deferred io support in drm_fb_helper which mirrors the one qxl has had. This patch has only been compile tested. Signed-off-by: Noralf Trønnes --- Changes since v2: - The drm_clip_rect_{width/height} functions are dropped, so open code it Changes since v1: - Add FIXME about

[PATCH v3 5/7] drm/fb-cma-helper: Add fb_deferred_io support

This adds fbdev deferred io support if CONFIG_FB_DEFERRED_IO is enabled. The driver has to provide a (struct drm_framebuffer_funcs *)->dirty() callback to get notification of fbdev framebuffer changes. If the dirty() hook is set, then fb_deferred_io is set up automatically by the helper. Two

[PATCH v3 4/7] fbdev: fb_defio: Export fb_deferred_io_mmap

Export fb_deferred_io_mmap so drivers can change vma->vm_page_prot. When the framebuffer memory is allocated using dma_alloc_writecombine() instead of vmalloc(), I get cache syncing problems on ARM. This solves it: static int drm_fbdev_cma_deferred_io_mmap(struct fb_info *info,

[PATCH v3 3/7] drm/fb-helper: Add fb_deferred_io support

This adds deferred io support to drm_fb_helper. The fbdev framebuffer changes are flushed using the callback (struct drm_framebuffer *)->funcs->dirty() by a dedicated worker ensuring that it always runs in process context. Signed-off-by: Noralf Trønnes --- Changes since v2: - FB_DEFERRED_IO is

[PATCH v3 2/7] drm/qxl: Change drm_fb_helper_sys_*() calls to sys_*()

Now that drm_fb_helper gets deferred io support, the drm_fb_helper_sys_{fillrect,copyarea,imageblit} functions will schedule a worker that will call the (struct drm_framebuffer *)->funcs->dirty() function. This will break this driver so use the sys_{fillrect,copyarea,imageblit} functions directly.

[PATCH v3 1/7] drm/udl: Change drm_fb_helper_sys_*() calls to sys_*()

Now that drm_fb_helper gets deferred io support, the drm_fb_helper_sys_{fillrect,copyarea,imageblit} functions will schedule a worker that will call the (struct drm_framebuffer *)->funcs->dirty() function. This will break this driver so use the sys_{fillrect,copyarea,imageblit} functions directly.

[PATCH v3 0/7] drm: Add fbdev deferred io support to helpers

This patchset adds fbdev deferred io support to drm_fb_helper and drm_fb_cma_helper. It channels fbdev mmap and fb_{write,fillrect,copyarea,imageblit} damage through the (struct drm_framebuffer_funcs)->dirty callback on the fb_helper framebuffer which will always run in process context. I have

[PATCH v15 8/8] memory: mtk-smi: export mtk_smi_larb_get/put

On 27/04/16 17:05, Philipp Zabel wrote: > To allow building mediatek-drm.ko as a module, the > mtk_smi_larb_get and mtk_smi_larb_put symbols have > to be exported. > > Signed-off-by: Philipp Zabel Signed-off-by: Matthias Brugger > --- > drivers/memory/mtk-smi.c | 2 ++ > 1 file changed, 2

[PATCH 2/2] drm/vmwgfx: Report vmwgfx version to vmware.log

When tracking down a customer issue, it is useful to know exactly which version of the vmwgfx they are using. Since vmware.log is often the only available debug log, report vmwgfx version in there. Signed-off-by: Sinclair Yeh Reviewed-by: Thomas Hellstrom --- drivers/gpu/drm/vmwgfx/.gitignore

[PATCH 1/2] drm/vmwgfx: Add VMWare host messaging capability

This patch adds capabilities for a VMWare guest to send and receive messages from the host, and adds functions to sending log messages to vmware.log and to request device settings that aren't available through the virtual hardware, e.g. certain settings in the VMX file. Signed-off-by: Sinclair

[Bug 86351] HDMI audio garbled output on Radeon R9 280X

https://bugzilla.kernel.org/show_bug.cgi?id=86351 haakobja at gmail.com changed: What|Removed |Added CC||haakobja at gmail.com --- Comment

[PATCH 07/12] drm/rcar-du: Rename async to nonblock.

Hi Maarten, Thank you for the patch. On Tuesday 26 Apr 2016 16:11:40 Maarten Lankhorst wrote: > The async name is deprecated and should be changed to nonblocking. > > Cc: Laurent Pinchart > Signed-off-by: Maarten Lankhorst Acked-by: Laurent Pinchart > --- >

[PATCH] drm/omap: check plane size

Hi Tomi, (CC'ing Daniel) Thank you for the patch. On Tuesday 26 Apr 2016 13:16:42 Tomi Valkeinen wrote: > At the moment we don't check the plane input/output sizes, which can > lead to DSS HW errors when invalid values are given from the userspace. > > Add a check so that the sizes are > 0. >

[ANNOUNCE] libdrm 2.4.68

vel/attachments/20160427/6d62ecf1/attachment.sig>

[Bug 95177] *ERROR* radeon: failed testing IB on ring 5 (-35)

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

[Bug 95177] *ERROR* radeon: failed testing IB on ring 5 (-35)

or the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/8860601c/attachment-0001.html>

[Intel-gfx] RFC: libdrm: Support Iris Graphics 540 & 550 (Skylake GT3e)

. Roland just mentioned this on IRC...I've reviewed and pushed the patch to master. I'm also making a release. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: This is a digitally signed messa

[PATCH 2/2] ARC: [axs10x] Specify reserved memory for frame buffer

Allocation of a frame buffer memory in a special memory region allows bypassing of so-called IO Coherency aperture which is typically set as a range 0x8z-0xAz. I.e. all data traffic to PGU bypasses IO Coherency block and saves its bandwidth for other peripherals. Even though for AXS101 (which

[PATCH 1/2] drm/arcpgu: use dedicated memory area for frame buffer

Now when ARC supports reserved memory areas and per-device coherent DMA allocations we may switch ARC PGU to use of those dedicated areas. One of the benefits we may move frame-buffer area out from IO Coherency aperture and so significantly reduce IOC utilization allowing less demanding

[PATCH 0/2] drm/arcpgu: Get use of dedicated memory area for frame buffer

This mini-series allows to allocate frame buffer memory in desired location. Allocation of a frame buffer memory in a special memory region allows bypassing of so-called IO Coherency aperture which is typically set as a range 0x8z-0xAz. I.e. all data traffic to PGU bypasses IO Coherency block and

[PATCH] drm/ttm: fix kref count mess in ttm_bo_move_to_lru_tail

LGTM Reviewed-by: Thomas Hellstrom On 04/26/2016 06:50 AM, Alex Deucher wrote: > Ping. Any objections? > > > On Wed, Apr 20, 2016 at 1:52 PM, Alex Deucher > wrote: >> From: Flora Cui >> >> Fixes the following scenario: >> >> 1. Page table bo allocated in vram and linked to man->lru. >>

[PATCH] drm/etnaviv: don't move linear memory window on 3D cores without MC2.0

2016-04-21 14:51 GMT+02:00 Lucas Stach : > On cores with MC1.0 the memory window offset is not properly respected > by all engines in the core, leading to different views of the memory > if the offset in non-zero. This causes relocs for those engines to be > wrong and might lead to other subtile

bug in autoloading of imx-ipuv3-crtc

Am Mittwoch, den 27.04.2016, 08:59 +1000 schrieb Dave Airlie: > > I reverted the 4 patches in that series > > > > 407c9eba drm/imx: Remove of_node assignment from ipuv3-crtc driver probe > > 304e6be6 gpu: ipu-v3: Assign of_node of child platform devices to > > corresponding ports > > 99ae78c3 gpu:

[PATCH 04/24] drm/etnaviv: add extern C guard for the UAPI header

2016-04-21 22:17 GMT+02:00 Emil Velikov : > Cc: Christian Gmeiner > Cc: Russell King > Cc: Lucas Stach > Signed-off-by: Emil Velikov Acked-by: Christian Gmeiner > --- > include/uapi/drm/etnaviv_drm.h | 8 > 1 file changed, 8 insertions(+) > > diff

[Intel-gfx] [PATCH 04/35] drm: Forbid legacy MAP functions for DRIVER_MODESET

>> Hm, I thought the referenced commit explained this, but now that I recheck >> it doesn't. I'm not too sure again myself why I thought nouveau needs >> this. The legacy ctx stuff is required because of some old kms nouveau ddx >> that still used that stuff. I thought it also used legacy maps ...

[PATCH v15 8/8] memory: mtk-smi: export mtk_smi_larb_get/put

To allow building mediatek-drm.ko as a module, the mtk_smi_larb_get and mtk_smi_larb_put symbols have to be exported. Signed-off-by: Philipp Zabel --- drivers/memory/mtk-smi.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/memory/mtk-smi.c b/drivers/memory/mtk-smi.c index

[PATCH v15 7/8] clk: mediatek: remove hdmitx_dig_cts from TOP clocks

The hdmitx_dig_cts clock signal is not a child of tvdpll_445p5m, but is routed out of the HDMI PHY module. Signed-off-by: Philipp Zabel Acked-by: Stephen Boyd --- drivers/clk/mediatek/clk-mt8173.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/clk/mediatek/clk-mt8173.c

[PATCH v15 6/8] clk: mediatek: Add hdmi_ref HDMI PHY PLL reference clock output

The configurable hdmi_ref output of the PLL block is derived from the tvdpll_594m clock signal via a configurable PLL post-divider. It is used as the PLL reference input to the HDMI PHY module. Signed-off-by: Philipp Zabel Acked-by: James Liao Acked-by: Stephen Boyd ---

[PATCH v15 5/8] clk: mediatek: make dpi0_sel propagate rate changes

This mux is supposed to select a fitting divider after the PLL is already set to the correct rate. Signed-off-by: Philipp Zabel Acked-by: James Liao Acked-by: Stephen Boyd --- drivers/clk/mediatek/clk-mt8173.c | 6 +- drivers/clk/mediatek/clk-mtk.h| 15 +-- 2 files

[PATCH v15 4/8] drm/mediatek: Add DPI sub driver

From: Jie Qiu Add DPI connector/encoder to support HDMI output via the attached HDMI bridge. Signed-off-by: Jie Qiu Signed-off-by: Philipp Zabel --- drivers/gpu/drm/mediatek/Makefile | 3 +- drivers/gpu/drm/mediatek/mtk_dpi.c | 769

[PATCH v15 3/8] drm/mediatek: Add DSI sub driver

From: CK Hu This patch add a drm encoder/connector driver for the MIPI DSI function block of the Mediatek display subsystem and a phy driver for the MIPI TX D-PHY control module. Signed-off-by: Jitao Shi Signed-off-by: Philipp Zabel --- Changes since v15: - use div_u64 to

[PATCH v15 2/8] drm/mediatek: Add DRM Driver for Mediatek SoC MT8173.

From: CK Hu This patch adds an initial DRM driver for the Mediatek MT8173 DISP subsystem. It currently supports two fixed output streams from the OVL0/OVL1 sources to the DSI0/DPI0 sinks, respectively. Signed-off-by: CK Hu Signed-off-by: YT Shen Signed-off-by: Daniel Kurtz

[PATCH v15 1/8] dt-bindings: drm/mediatek: Add Mediatek display subsystem dts binding

From: CK Hu Add device tree binding documentation for the display subsystem in Mediatek MT8173 SoCs. Signed-off-by: CK Hu Signed-off-by: Philipp Zabel Acked-by: Rob Herring --- .../bindings/display/mediatek/mediatek,disp.txt| 203 +

[PATCH v15 0/8] MT8173 DRM support

Rebased onto drm-next, fixed building as a module, removed the driver unload hook, custom vm_ops, and the dts patch. Changes since v14: - Fixed module build - Select DRM_GEM_CMA_HELPER and use drm_gem_cma_vm_ops - Select MEMORY so that select MTK_SMI works properly - Rebase onto drm-next so

[Bug 93548] Grid Autosport causes a hard system crash

is loading at the end of the qualifications. -- 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/20160427/50f682c6/attachment-0001.html>

[Bug 71789] [r300g] Visuals not found in (default) depth = 24

) / Debian Sid. -- 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/20160427/92d019ff/attachment.html>

[PATCH] drm/msm: Move call to PTR_ERR_OR_ZERO after reassignment

Here, a location is reset to NULL before being passed to PTR_ERR. So, PTR_ERR should be called before its argument is reassigned to NULL. Further to simplify things use PTR_ERR_OR_ZERO instead of PTR_ERR and IS_ERR. Problem found using Coccinelle. Signed-off-by: Vaishali Thakkar ---

[PATCH v4 02/12] mm: migrate: support non-lru movable page migration

We have allowed migration for only LRU pages until now and it was enough to make high-order pages. But recently, embedded system(e.g., webOS, android) uses lots of non-movable pages(e.g., zram, GPU memory) so we have seen several reports about troubles of small high-order allocation. For fixing

[PATCH v4 00/13] Support non-lru page migration

Recently, I got many reports about perfermance degradation in embedded system(Android mobile phone, webOS TV and so on) and easy fork fail. The problem was fragmentation caused by zram and GPU driver mainly. With memory pressure, their pages were spread out all of pageblock and it cannot be

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

On Wed, 27 Apr 2016, Florian Zumbiehl wrote: >> Florian, if you're using drm-intel-nigthly submit a bug at >> https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel >> as component. This way we can track some kind of progress/regress. The FIFO > > Gee ... is there any way without

[PATCH v3 2/2] dt-bindings: imx: ldb: Add ddc-i2c-bus property

Document the ddc-i2c-bus property used by imx-ldb driver to read EDID information via I2C interface. Signed-off-by: Akshay Bhat --- v3: Newly added. Documentation/devicetree/bindings/display/imx/ldb.txt | 1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 1/2] drm/imx: imx-ldb: Add DDC support

From: Steve Longerbeam Add support for reading EDID over Display Data Channel. If no DDC adapter is available, falls back to hardcoded EDID or display-timings node as before. Signed-off-by: Steve Longerbeam Signed-off-by: Akshay Bhat Acked-by: Philipp Zabel ---

[Bug 93767] Glitches with soft shadows and MSAA in Knights of the Old Republic 2

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/8cf7fd6b/attachment.html>

[PATCH] gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading

Am Mittwoch, den 27.04.2016, 08:54 -0500 schrieb Dennis Gilmore: > Thanks Philipp, > > I tested and module loading worked correctly > > Dennis > > On 2016-04-27 03:29, Philipp Zabel wrote: > > If of_node is set before calling platform_device_add, the driver core > > will try to use of: modalias

[PATCH 1/9] drm: Add drm_mode_debug_printmodeline_raw

On Wed, 27 Apr 2016, Tvrtko Ursulin wrote: > From: Tvrtko Ursulin > > Purpose is to enable drivers to print out just the mode > string with their own formatting. Some alternatives that preserve the use of a single printk(), avoiding garbled console output due to races (as discussed on intel-gfx

[Bug 71789] [r300g] Visuals not found in (default) depth = 24

tps://lists.freedesktop.org/archives/dri-devel/attachments/20160427/b4bd19d1/attachment.html>

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

Hi, > Florian, if you're using drm-intel-nigthly submit a bug at > https://bugs.freedesktop.org/enter_bug.cgi?product=DRI, with DRM/intel > as component. This way we can track some kind of progress/regress. The FIFO Gee ... is there any way without "creating an account"? Having to create

[PATCH 2/2] drm/etnaviv: fix mmap operations for userptr and dma-buf objects

Add an indirect object operations call to allow distinct implementations of the mmap operation based on the type of the object. This ensures that the exporter is called to set up the mmap for imported dma-bufs and disallows mapping of userptr objects through the DRM file, as this might lead to

[PATCH 1/2] drm/etnaviv: take etnaviv_gem_obj in etnaviv_gem_mmap_obj

This function will be changed to be called indirectly and this prototype change brings it in line with all the other indirect object calls. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_gem.c | 9 - 1 file changed, 4 insertions(+), 5 deletions(-) diff --git

[PATCH] drm/etnaviv: remove BUG_ON in MMU unmap path

If the MMU map fails caused by an unaligned SG entry, the unmap path is called to undo all already setup SG mappings. When encountering the unaligned SG the unmap path hangs the kernel with a BUG(), while the error is recoverable by just failing the submit that references the faulty object.

[PATCH] drm/gem: support BO freeing without dev->struct_mutex

On Wed, Apr 27, 2016 at 12:58:51PM +0100, Chris Wilson wrote: > On Wed, Apr 27, 2016 at 01:50:00PM +0200, Daniel Vetter wrote: > > Finally all the core gem and a lot of drivers are entirely free of > > dev->struct_mutex depencies, and we can start to have an entirely > > lockless unref path. > >

[PATCH 19/35] drm/imx: Use lockless gem BO free callback

Am Mittwoch, den 27.04.2016, 13:21 +0200 schrieb Daniel Vetter: > On Wed, Apr 27, 2016 at 12:29:34PM +0200, Philipp Zabel wrote: > > Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter: > > > No dev->struct_mutex anywhere to be seen. > > > > > > Cc: Sascha Hauer > > > Cc: Philipp

[pull] radeon and amdgpu drm-fixes-4.6

Hi Dave, A few fixes for 4.6. - revert amdgpu PX commit that was previously reverted on the radeon side - cleaned up version of the NI+ MC update display fix for radeon - TTM kref fix The following changes since commit 18cdfe751f26ffa610f2a7b59775c5cc4c1c9619: Merge branch 'drm-fixes-4.6' of

[PATCH 1/9] drm: Add drm_mode_debug_printmodeline_raw

On 27/04/16 13:35, Jani Nikula wrote: > On Wed, 27 Apr 2016, Tvrtko Ursulin wrote: >> From: Tvrtko Ursulin >> >> Purpose is to enable drivers to print out just the mode >> string with their own formatting. > > Some alternatives that preserve the use of a single printk(), avoiding > garbled

[PATCH] drm/gem: support BO freeing without dev->struct_mutex

Finally all the core gem and a lot of drivers are entirely free of dev->struct_mutex depencies, and we can start to have an entirely lockless unref path. To make sure that no one who touches the core code accidentally breaks existing drivers which still require dev->struct_mutex I've made the

[PATCH 3/3] drm/msm: Nuke dummy fb->dirty callback

It's an optional hook. Cc: Rob Clark Signed-off-by: Daniel Vetter --- drivers/gpu/drm/msm/msm_fb.c | 8 1 file changed, 8 deletions(-) diff --git a/drivers/gpu/drm/msm/msm_fb.c b/drivers/gpu/drm/msm/msm_fb.c index 17e0c9eb1900..672d8b1c2d09 100644 --- a/drivers/gpu/drm/msm/msm_fb.c

[PATCH 2/3] drm/exynos: Nuke dummy fb->dirty callback

It's an optional hook. Might be needed for frontbuffer rendering on manual upload displays, but a simple TODO doesn't explain at all what needs to be done or why. Cc: Inki Dae Signed-off-by: Daniel Vetter --- drivers/gpu/drm/exynos/exynos_drm_fb.c | 11 --- 1 file changed, 11

[PATCH 1/3] drm/rockchip: Use cma gem vm ops

No need to reinvent this little wheel. v2: Like, try to make it compile even. Cc: Mark Yao Signed-off-by: Daniel Vetter --- drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 8 ++-- 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/drivers/gpu/drm/rockchip/rockchip_drm_drv.c

i915: screen flicker

On Wed, 27 Apr 2016, Mihai Donțu wrote: > On Wed, 27 Apr 2016 10:09:32 +0300 Jani Nikula wrote: >> On Wed, 27 Apr 2016, Mihai Donțu wrote: >> > I noticed that since I started using 4.6.0-rcX, my screen flickers once >> > or twice after I stop using my laptop for ~1min or so. Given the >> >

[PATCH] drm/i915: Fix enc_to_dig_port() for MST encoders

For MST encoders, the encoder struct is stored in the intel_dp_mst struct, not a intel_digital_port struct. This fixes issues with hotplugging MST displays that support MST audio, where hotplugging had a surprisingly good chance of accidentally overwriting other parts of the kernel leading to

[PATCH 12/12] Documentation: add Sync File doc

From: Gustavo Padovan Add sync_file documentation on dma-buf-sync_file.txt --- Documentation/dma-buf-sync_file.txt | 65 + 1 file changed, 65 insertions(+) create mode 100644 Documentation/dma-buf-sync_file.txt diff --git

[PATCH 11/12] Documentation: include sync_file into DocBook

From: Gustavo Padovan Add entry in device-drivers.tmpl for sync_file documentation. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/DocBook/device-drivers.tmpl

[PATCH 10/12] dma-buf/sync_file: de-stage sync_file

From: Gustavo Padovan sync_file is useful to connect one or more fences to the file. The file is used by userspace to track fences between drivers that share DMA bufs. Signed-off-by: Gustavo Padovan --- drivers/Kconfig | 2 ++

[PATCH 09/12] dma-buf/sync_file: de-stage sync_file headers

From: Gustavo Padovan Move sync_file headers file to include/ dir. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.h | 4 ++-- drivers/staging/android/sync_debug.c | 2 +-

[PATCH 08/12] staging/android: style fix: alignment to match the open parenthesis

From: Gustavo Padovan Fix checks reported by checkpatch.pl. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync_file.c | 8 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/drivers/staging/android/sync_file.c

[PATCH 07/12] staging/android: improve documentation for sync_file

From: Gustavo Padovan num_fences was missing a colon mark and sync_file_create() now have better description. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync_file.c | 3 ++- drivers/staging/android/sync_file.h | 2 +- 2 files changed, 3

[PATCH 06/12] staging/android: prepare sync_file for de-staging

From: Gustavo Padovan Move its functions and structs to their own file. Also moves function's docs to the .c file. Signed-off-by: Gustavo Padovan --- drivers/staging/android/Makefile | 2 +- drivers/staging/android/sync.c

[PATCH 05/12] staging/android: make sync_file_fdget() static

From: Gustavo Padovan There is no plan in the near future to use this function outside of this file so keep it as static. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 3 +-- drivers/staging/android/sync.h | 1 - 2 files changed, 1

[PATCH 04/12] staging/android: make sync_file_merge() static

From: Gustavo Padovan There is no plan in the near future to use this function outside of this file so keep it as static. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 4 ++-- drivers/staging/android/sync.h | 2 -- 2 files changed, 2

[PATCH 03/12] staging/android: move sync_file functions comments to sync.c

From: Gustavo Padovan To keep comments in line with drivers/dma-buf/ move all sync_file comments to sync.c. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sync.c | 26 +- drivers/staging/android/sync.h | 31

[PATCH 02/12] staging/android: drop sync_file_install() and sync_file_put()

From: Gustavo Padovan These two functions are just wrappers for one line functions, they call fd_install() and fput() respectively, so just get rid of them and use fd_install() and fput() directly for more simplicity. Signed-off-by: Gustavo Padovan ---

[PATCH 01/12] staging/android: remove redundant comments on sync_merge_data

From: Gustavo Padovan struct sync_merge_data already have documentation on top of the struct definition. No need to duplicate it. Signed-off-by: Gustavo Padovan Reviewed-by: Maarten Lankhorst --- drivers/staging/android/uapi/sync.h | 10 +- 1 file

[PATCH 00/12] De-stage Sync File Framework

From: Gustavo Padovan Hi, This patchset sits on top of Sync ABI Rework v13: https://www.spinics.net/lists/dri-devel/msg105667.html The first eight clean up and prepare sync_file for de-staging. The last four patches do the de-staging, moving files to

[PATCH 19/35] drm/imx: Use lockless gem BO free callback

On Wed, Apr 27, 2016 at 12:29:34PM +0200, Philipp Zabel wrote: > Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter: > > No dev->struct_mutex anywhere to be seen. > > > > Cc: Sascha Hauer > > Cc: Philipp Zabel > > Signed-off-by: Daniel Vetter > > --- > >

[PATCH 09/35] drm/gem: support BO freeing without dev->struct_mutex

On Wed, Apr 27, 2016 at 11:31:00AM +0200, Lucas Stach wrote: > Am Dienstag, den 26.04.2016, 19:29 +0200 schrieb Daniel Vetter: > > Finally all the core gem and a lot of drivers are entirely free of > > dev->struct_mutex depencies, and we can start to have an entirely > > lockless unref path. > >

[PATCH v4 00/13] Support non-lru page migration

On Wed, 27 Apr 2016 16:48:13 +0900 Minchan Kim wrote: > Recently, I got many reports about perfermance degradation in embedded > system(Android mobile phone, webOS TV and so on) and easy fork fail. > > The problem was fragmentation caused by zram and GPU driver mainly. > With memory pressure,

[PATCH] drm/gem: support BO freeing without dev->struct_mutex

On Wed, Apr 27, 2016 at 02:12:46PM +0200, Daniel Vetter wrote: > On Wed, Apr 27, 2016 at 12:58:51PM +0100, Chris Wilson wrote: > > On Wed, Apr 27, 2016 at 01:50:00PM +0200, Daniel Vetter wrote: > > > Finally all the core gem and a lot of drivers are entirely free of > > > dev->struct_mutex

[PATCH v2 4/8] drm/fb-helper: Add fb_deferred_io support

On Wed, Apr 27, 2016 at 11:45:31AM +0200, Noralf Trønnes wrote: > > Den 26.04.2016 19:19, skrev Daniel Vetter: > >On Tue, Apr 26, 2016 at 06:24:54PM +0200, Noralf Trønnes wrote: > >>Den 25.04.2016 11:09, skrev Daniel Vetter: > >>>On Sun, Apr 24, 2016 at 10:48:58PM +0200, Noralf Trønnes wrote:

i915: screen flicker

On Wed, 27 Apr 2016 10:09:32 +0300 Jani Nikula wrote: > On Wed, 27 Apr 2016, Mihai Donțu wrote: > > I noticed that since I started using 4.6.0-rcX, my screen flickers once > > or twice after I stop using my laptop for ~1min or so. Given the > > behavior, my prime suspect is the PSR feature that

[Intel-gfx] i951 ERRORs and WARN_ON()s (was: blank screen on boot with i915/DRM_FBDEV_EMULATION)

lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: Digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160427/33053c09/attachment.sig>

[PATCH] drm/gem: support BO freeing without dev->struct_mutex

On Wed, Apr 27, 2016 at 01:50:00PM +0200, Daniel Vetter wrote: > Finally all the core gem and a lot of drivers are entirely free of > dev->struct_mutex depencies, and we can start to have an entirely > lockless unref path. > > To make sure that no one who touches the core code accidentally breaks

[PATCH v14 2/8] drm/mediatek: Add DRM Driver for Mediatek SoC MT8173.

On Wed, Apr 27, 2016 at 12:29:05PM +0200, Philipp Zabel wrote: > Hi Daniel, > > Am Dienstag, den 26.04.2016, 10:48 +0200 schrieb Daniel Vetter: > [...] > > > +static int mtk_drm_unload(struct drm_device *drm) > > > +{ > > > + mtk_drm_kms_deinit(drm); > > > + drm->dev_private = NULL; > > > + > > >

  1   2   >