dri-devel July 2017

dri-devel@lists.freedesktop.org

212 participants
1542 discussions

[Bug 100242] radeon buffer allocation failure during startup of Factorio
by bugzilla-daemon＠freedesktop.org 03 Jul '17

03 Jul '17

https://bugs.freedesktop.org/show_bug.cgi?id=100242 Bug ID: 100242 Summary: radeon buffer allocation failure during startup of Factorio Product: Mesa Version: git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 Assignee: dri-devel(a)lists.freedesktop.org Reporter: tnmailinglists(a)gmail.com QA Contact: dri-devel(a)lists.freedesktop.org Created attachment 130277 --> https://bugs.freedesktop.org/attachment.cgi?id=130277&action=edit terminal output when running the executable The game Factorio crashes during startup with the following message printed on the CLI: radeon: Failed to allocate a buffer: radeon: size : 268435456 bytes radeon: alignment : 16384 bytes radeon: domains : 4 radeon: flags : 20 The crash occurs during the pre-game loading procedure, before reaching the main menu, at the same spot every time. I'm on Lubuntu 16.10 using the up-to-date drivers provided by https://launchpad.net/~oibaf/+archive/ubuntu/graphics-drivers , my GPU is a Radeon HD 4670 with AGP. I believe this is a driver issue since the game starts up normally with 16.10's default drivers (12.0.6). I unfortunately cannot provide a specific date or build for when this behavior started occurring, but it has been happening for several months. Of note is that the demo version provided by the developer on their website does not have this problem and starts up fine. Attached are the terminal output, an strace and a gdb bt log. -- You are receiving this mail because: You are the assignee for the bug.

1 13

[PATCH] drm: ttm: virtio-gpu: dma-buf: Constify ttm_place structures.
by Arvind Yadav 03 Jul '17

03 Jul '17

ttm_place are not supposed to change at runtime. All functions working with ttm_place provided by <drm/ttm/ttm_placement.h> work with const ttm_place. So mark the non-const structs as const. File size before: text data bss dec hex filename 2315 184 0 2499 9c3 drivers/gpu/drm/virtio/virtgpu_ttm.o File size After adding 'const': text data bss dec hex filename 2347 152 0 2499 9c3 drivers/gpu/drm/virtio/virtgpu_ttm.o Signed-off-by: Arvind Yadav <arvind.yadav.cs(a)gmail.com> --- drivers/gpu/drm/virtio/virtgpu_ttm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/virtio/virtgpu_ttm.c b/drivers/gpu/drm/virtio/virtgpu_ttm.c index 4e8e27d..012d5bc 100644 --- a/drivers/gpu/drm/virtio/virtgpu_ttm.c +++ b/drivers/gpu/drm/virtio/virtgpu_ttm.c @@ -234,7 +234,7 @@ static int virtio_gpu_init_mem_type(struct ttm_bo_device *bdev, uint32_t type, static void virtio_gpu_evict_flags(struct ttm_buffer_object *bo, struct ttm_placement *placement) { - static struct ttm_place placements = { + static const struct ttm_place placements = { .fpfn = 0, .lpfn = 0, .flags = TTM_PL_MASK_CACHING | TTM_PL_FLAG_SYSTEM, -- 2.7.4

2 1

[PATCH 1/2] drm/vmwgfx: Drop drm_vblank_cleanup
by Daniel Vetter 03 Jul '17

03 Jul '17

Again stopping the vblank before uninstalling the irq handler is kinda the wrong way round, but the fb_off stuff should take care of disabling the dsiplay at least in most cases. So drop the drm_vblank_cleanup code since it's not really doing anything, it looks all cargo-culted. v2: Appease gcc better. v3: Simplify code (Sean Paul) Cc: Sinclair Yeh <syeh(a)vmware.com> Cc: Thomas Hellstrom <thellstrom(a)vmware.com> Reviewed-by: Sean Paul <seanpaul(a)chromium.org> Reviewed-by: Thomas Hellstrom <thellstrom(a)vmware.com> Signed-off-by: Daniel Vetter <daniel.vetter(a)intel.com> --- drivers/gpu/drm/vmwgfx/vmwgfx_kms.c | 8 ++------ drivers/gpu/drm/vmwgfx/vmwgfx_kms.h | 2 -- drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 4 ---- drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 9 --------- drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 27 +-------------------------- 5 files changed, 3 insertions(+), 47 deletions(-) diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c index 3d94ea67a825..1cd67b10a0d9 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.c @@ -1658,7 +1658,7 @@ int vmw_kms_init(struct vmw_private *dev_priv) int vmw_kms_close(struct vmw_private *dev_priv) { - int ret; + int ret = 0; /* * Docs says we should take the lock before calling this function @@ -1666,11 +1666,7 @@ int vmw_kms_close(struct vmw_private *dev_priv) * drm_encoder_cleanup which takes the lock we deadlock. */ drm_mode_config_cleanup(dev_priv->dev); - if (dev_priv->active_display_unit == vmw_du_screen_object) - ret = vmw_kms_sou_close_display(dev_priv); - else if (dev_priv->active_display_unit == vmw_du_screen_target) - ret = vmw_kms_stdu_close_display(dev_priv); - else + if (dev_priv->active_display_unit == vmw_du_legacy) ret = vmw_kms_ldu_close_display(dev_priv); return ret; diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.h b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.h index 5f8d678ae675..ff9c8389ff21 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_kms.h +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_kms.h @@ -390,7 +390,6 @@ int vmw_kms_update_proxy(struct vmw_resource *res, * Screen Objects display functions - vmwgfx_scrn.c */ int vmw_kms_sou_init_display(struct vmw_private *dev_priv); -int vmw_kms_sou_close_display(struct vmw_private *dev_priv); int vmw_kms_sou_do_surface_dirty(struct vmw_private *dev_priv, struct vmw_framebuffer *framebuffer, struct drm_clip_rect *clips, @@ -418,7 +417,6 @@ int vmw_kms_sou_readback(struct vmw_private *dev_priv, * Screen Target Display Unit functions - vmwgfx_stdu.c */ int vmw_kms_stdu_init_display(struct vmw_private *dev_priv); -int vmw_kms_stdu_close_display(struct vmw_private *dev_priv); int vmw_kms_stdu_surface_dirty(struct vmw_private *dev_priv, struct vmw_framebuffer *framebuffer, struct drm_clip_rect *clips, diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c index d3987bcf53f8..449ed4fba0f2 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c @@ -582,13 +582,9 @@ int vmw_kms_ldu_init_display(struct vmw_private *dev_priv) int vmw_kms_ldu_close_display(struct vmw_private *dev_priv) { - struct drm_device *dev = dev_priv->dev; - if (!dev_priv->ldu_priv) return -ENOSYS; - drm_vblank_cleanup(dev); - BUG_ON(!list_empty(&dev_priv->ldu_priv->active)); kfree(dev_priv->ldu_priv); diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c b/drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c index 8d7dc9def7c2..3b917c9b0c21 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c @@ -746,15 +746,6 @@ int vmw_kms_sou_init_display(struct vmw_private *dev_priv) return 0; } -int vmw_kms_sou_close_display(struct vmw_private *dev_priv) -{ - struct drm_device *dev = dev_priv->dev; - - drm_vblank_cleanup(dev); - - return 0; -} - static int do_dmabuf_define_gmrfb(struct vmw_private *dev_priv, struct vmw_framebuffer *framebuffer) { diff --git a/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c b/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c index 50be1f034f9e..6aecba6cd5e2 100644 --- a/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c +++ b/drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c @@ -1651,36 +1651,11 @@ int vmw_kms_stdu_init_display(struct vmw_private *dev_priv) if (unlikely(ret != 0)) { DRM_ERROR("Failed to initialize STDU %d", i); - goto err_vblank_cleanup; + return ret; } } DRM_INFO("Screen Target Display device initialized\n"); return 0; - -err_vblank_cleanup: - drm_vblank_cleanup(dev); - return ret; -} - - - -/** - * vmw_kms_stdu_close_display - Cleans up after vmw_kms_stdu_init_display - * - * @dev_priv: VMW DRM device - * - * Frees up any resources allocated by vmw_kms_stdu_init_display - * - * RETURNS: - * 0 on success - */ -int vmw_kms_stdu_close_display(struct vmw_private *dev_priv) -{ - struct drm_device *dev = dev_priv->dev; - - drm_vblank_cleanup(dev); - - return 0; } -- 2.11.0

3 3

[PATCH] drm/bochs: switch fb_ops over to use drm_fb_helper_cfb helpers
by Mark Cave-Ayland 03 Jul '17

03 Jul '17

The current drm_fb_helper_sys helpers referenced in fb_ops assume that the video memory is in system RAM. This is not the case for sparc which uses direct physical memory accesses for IO memory and causes the bochs_drm module to panic immediately upon startup as it tries to initialise the framebuffer. Switching fb_ops over to use the drm_fb_helper_cfb helpers ensures that the correct accesses are used on sparc, fixing the panic and allowing the bochs_drm module to function under qemu-system-sparc64. Signed-off-by: Mark Cave-Ayland <mark.cave-ayland(a)ilande.co.uk> --- drivers/gpu/drm/bochs/bochs_fbdev.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/drivers/gpu/drm/bochs/bochs_fbdev.c b/drivers/gpu/drm/bochs/bochs_fbdev.c index 932a769..d3a75c2 100644 --- a/drivers/gpu/drm/bochs/bochs_fbdev.c +++ b/drivers/gpu/drm/bochs/bochs_fbdev.c @@ -23,9 +23,9 @@ static int bochsfb_mmap(struct fb_info *info, static struct fb_ops bochsfb_ops = { .owner = THIS_MODULE, DRM_FB_HELPER_DEFAULT_OPS, - .fb_fillrect = drm_fb_helper_sys_fillrect, - .fb_copyarea = drm_fb_helper_sys_copyarea, - .fb_imageblit = drm_fb_helper_sys_imageblit, + .fb_fillrect = drm_fb_helper_cfb_fillrect, + .fb_copyarea = drm_fb_helper_cfb_copyarea, + .fb_imageblit = drm_fb_helper_cfb_imageblit, .fb_mmap = bochsfb_mmap, }; -- 1.7.10.4

3 4

[PATCH v4 0/6] STM32 DSI HOST
by Philippe CORNU 03 Jul '17

03 Jul '17

Version 4: - bridge/synopsis/dw-mipi-dsi.c: Add panel-bridge support (-45 lines, but no so easy to do) and is_panel_bridge for a better clean up, add stm copyright/remove dpms_mode/remove drm_of.h/improve clk management/add mode_valid (thanks to comments of Archit Taneja), use "DesignWare" instead of "Designware (thanks to comments of Neil Armstrong) - bridge/synopsis/Kconfig: Remove help section to hide it in menuconfig (thanks to comments of Archit Taneja) - include/drm/bridge/dw_mipi_dsi.h: Remove drmP.h (thanks to comments of Archit Taneja) - bindings/display/bridge/dw_mipi_dsi.txt: Improve optional property explanations (thanks to comments of Neil Armstrong) - stm/ltdc.c: Add is_panel_bridge for a better clean up/remove drm_encoder_helper_add() (thanks to comments of Eric Anholt) - stm/dw_mipi_dsi-stm.c: remove math64.h/use DRM_WARN/remove warnings (thanks to comments of Archit Taneja), minor alignment fix (thanks to comments of Neil Armstrong) - bindings/display/st,stm32-ltdc.txt: use graph binding in the example/improve ports usage doc (thanks to comments of Rob Herring), use "DSI" instead of "dsi" where relevant (thanks to comments of Neil Armstrong) Version 3: - stm/ltdc: Use panel-bridge (-170 lines), thanks to comments of Eric Anholt, Boris Brezillon, Archit Taneja & Andrzej Hajda. - Synopsys dsi: Add dw_mipi_dsi.h (forgotten in v2), thanks to comments of Neil Armstrong. - Synopsys dsi/dw-mipi-dsi.c: add dw_mipi_dsi_dphy_init() & dw_mipi_dsi_dphy_enable() to better manage DW phy-dedicated regs, remove dw_mipi_dsi_mode enum, remove stm32 patch for lpm, remove pllref (manage in the vendor phy) thanks to comments of Archit Taneja. Add mode_flags to phy parameters to better adjust lane mbps according to dsi burst and non burst modes todos in caps. - stm/dw_mipi_dsi-stm.c: Add pllref management. - dt-bindings/display/stm: Split dt-bindings patch in two (parent node removal/ dsi), add required nodes (port & panel/bridge), updates thanks to comments of Rob Herring. - dt-bindings/display/Synopsys dsi: remove port as part of the vendor documentation, add panel/bridge node, update dt-bindings thanks to comments of Rob Herring. - Add more people from Hisilicon & Rockchip. Version 2: - Add a generic Synopsys DesignWare MIPI DSI bridge driver following comments from Neil Armstrong & Archit Taneja. - Use drm_of_find_panel_or_bridge() thanks to Eric Anholt comments - Update dt-bindings thanks to Rob Herring comments Version 1: - Initial commit The purpose of this set of patches is to add the mipi dsi host driver to the stm32 family. This mipi dsi host driver is based on the Rockchip version of the Synopsys Designware mipi dsi driver (rockchip/dw-mipi-dsi.c) modified for the stm32 family: - replace Rockchip digital & phy specific extensions with stm32's ones. - add a bridge Philippe CORNU (6): drm/stm: ltdc: Add panel-bridge support dt-bindings: display: Add Synopsys DW MIPI DSI DRM bridge driver drm/bridge/synopsys: Add MIPI DSI host controller bridge dt-bindings: display: stm32: remove st-display-subsystem parent node requirement dt-bindings: display: stm32: Add DSI host driver drm/stm: Add STM32 DSI host driver .../bindings/display/bridge/dw_mipi_dsi.txt | 30 + .../devicetree/bindings/display/st,stm32-ltdc.txt | 105 ++- drivers/gpu/drm/bridge/synopsys/Kconfig | 6 + drivers/gpu/drm/bridge/synopsys/Makefile | 2 + drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c | 976 +++++++++++++++++++++ drivers/gpu/drm/stm/Kconfig | 9 +- drivers/gpu/drm/stm/Makefile | 2 + drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 352 ++++++++ drivers/gpu/drm/stm/ltdc.c | 211 +---- drivers/gpu/drm/stm/ltdc.h | 3 +- include/drm/bridge/dw_mipi_dsi.h | 39 + 11 files changed, 1555 insertions(+), 180 deletions(-) create mode 100644 Documentation/devicetree/bindings/display/bridge/dw_mipi_dsi.txt create mode 100644 drivers/gpu/drm/bridge/synopsys/dw-mipi-dsi.c create mode 100644 drivers/gpu/drm/stm/dw_mipi_dsi-stm.c create mode 100644 include/drm/bridge/dw_mipi_dsi.h -- 1.9.1

5 21

[PATCH 0/8] Cleanup CRTC .enable()/.disable() cargo-cult
by Laurent Pinchart 03 Jul '17

03 Jul '17

Hello, The atomic helpers favour the .enable() and .atomic_disable() CRTC helper operations, but still support the legacy .prepare(), .commit(), .disable() and .dpms() operations. Some drivers have been updated, but most still use various combination of new and legacy operations, leading to confusion among new developers when they read the code. To avoid cargo-cult use of the legacy operations, this patch series mass-updates all atomic drivers to use the new CRTC atomic helper operations. In addition, patch 7/8 adds an old state pointer argument to the CRTC .enable() helper operation, and rename it to .atomic_enable() for consistency with .atomic_disable(). These two changes could have been split in separate patch, but as they are simple and touch the same large number of files, keeping the two changes as one is simpler and less error-prone. The patches are based on top of the drm-misc-next branch and have been compile-tested only except for rcar-du-drm that has been tested on real hardware. Given the high risk of conflicts I would like to get them merged as soon as possible (after, of course, proper review and testing). Laurent Pinchart (8): drm: arcpgu: Remove CRTC .commit() helper operation drm: arcpgu: Remove CRTC .prepare() helper operation drm: qxl: Remove unused CRTC .dpms() helper operation drm: qxl: Replace CRTC .commit() helper operation with .enable() drm: vmwgfx: Remove unneeded CRTC .prepare() helper operation drm: vmwgfx: Replace CRTC .commit() helper operation with .enable() drm: Add old state pointer to CRTC .enable() helper function drm: Convert atomic drivers from CRTC .disable() to .atomic_disable() drivers/gpu/drm/arc/arcpgu_crtc.c | 12 ++++---- drivers/gpu/drm/arm/hdlcd_crtc.c | 10 ++++--- drivers/gpu/drm/arm/malidp_crtc.c | 10 ++++--- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 10 ++++--- drivers/gpu/drm/drm_atomic_helper.c | 7 +++-- drivers/gpu/drm/drm_simple_kms_helper.c | 10 ++++--- drivers/gpu/drm/exynos/exynos_drm_crtc.c | 10 ++++--- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 5 ++-- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 10 ++++--- drivers/gpu/drm/hisilicon/kirin/kirin_drm_ade.c | 10 ++++--- drivers/gpu/drm/imx/ipuv3-crtc.c | 5 ++-- drivers/gpu/drm/mediatek/mtk_drm_crtc.c | 10 ++++--- drivers/gpu/drm/meson/meson_crtc.c | 10 ++++--- drivers/gpu/drm/msm/mdp/mdp4/mdp4_crtc.c | 10 ++++--- drivers/gpu/drm/msm/mdp/mdp5/mdp5_crtc.c | 10 ++++--- drivers/gpu/drm/omapdrm/omap_crtc.c | 10 ++++--- drivers/gpu/drm/qxl/qxl_display.c | 15 ++++------ drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 10 ++++--- drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 10 ++++--- drivers/gpu/drm/sti/sti_crtc.c | 10 ++++--- drivers/gpu/drm/stm/ltdc.c | 10 ++++--- drivers/gpu/drm/sun4i/sun4i_crtc.c | 10 ++++--- drivers/gpu/drm/tegra/dc.c | 10 ++++--- drivers/gpu/drm/tilcdc/tilcdc_crtc.c | 16 +++++++++-- drivers/gpu/drm/vc4/vc4_crtc.c | 10 ++++--- drivers/gpu/drm/virtio/virtgpu_display.c | 10 ++++--- drivers/gpu/drm/vmwgfx/vmwgfx_ldu.c | 27 ++++++------------ drivers/gpu/drm/vmwgfx/vmwgfx_scrn.c | 14 +++++---- drivers/gpu/drm/vmwgfx/vmwgfx_stdu.c | 10 ++++--- drivers/gpu/drm/zte/zx_vou.c | 10 ++++--- include/drm/drm_modeset_helper_vtables.h | 38 +++++++++++++------------ 31 files changed, 204 insertions(+), 155 deletions(-) -- Regards, Laurent Pinchart

14 50

[PATCH] drm/atomic: Add missing drm_atomic_state_clear to atomic_remove_fb
by Maarten Lankhorst 03 Jul '17

03 Jul '17

Signed-off-by: Maarten Lankhorst <maarten.lankhorst(a)linux.intel.com> --- drivers/gpu/drm/drm_framebuffer.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/drm_framebuffer.c b/drivers/gpu/drm/drm_framebuffer.c index fc8ef42203ec..b3ef4f1c2630 100644 --- a/drivers/gpu/drm/drm_framebuffer.c +++ b/drivers/gpu/drm/drm_framebuffer.c @@ -832,6 +832,7 @@ static int atomic_remove_fb(struct drm_framebuffer *fb) drm_atomic_clean_old_fb(dev, plane_mask, ret); if (ret == -EDEADLK) { + drm_atomic_state_clear(state); drm_modeset_backoff(&ctx); goto retry; } -- 2.11.0

3 5

[PATCH 00/21] drm/etnaviv: support performance counters
by Christian Gmeiner 03 Jul '17

03 Jul '17

In a perfect world we would be able to read GPU registers of interest via the command stream with a 'read-register' command/package. For perf counters it is a must to read them synchronized with the GPU to put the values in relation to a draw command. As Vivante GPUs do not provide this functionality we need to emulate it in software. We need to support three different kind of perf register types: 1) normal register This is the easierst case where we can simply read the register and we are done. 2) debug register We need to configure the mux register and then read the debug register value. 3) pipeline register We need to 'iterate' over all pixel pipes and sum up the values. The 'iteration' is done by select the pipe of interest via HI_CLOCK_CONTROL_DEBUG_PIXEL_PIPE. There is also need to configure the mux register. Allowing the userspace to do it all by its own feels quite error prone and not future-proof. Thats why the kernel exports all performance domains and their signals to the userspace via two new ioctls. So the kernel knows all performance counters and how to sample them. At the moment all performacne domains and signals get exported to all gpu pipe types, but that can be changed in follow-up patches. struct drm_etnaviv_gem_submit was extended to include so-called performance monitor requests (pmrs). A request defines what domain and signal should be sampled (pre/post draw cmdbuffer) and where to store the result. The whole series can be found here: https://github.com/austriancoder/linux/tree/perfmon Happy reviewing! Christian Gmeiner (21): drm/etnaviv: add infrastructure to query perf counter drm/etnaviv: add uapi for perfmon feature drm/etnaviv: add internal representation of perfmon_request drm/etnaviv: extend etnaviv_gpu_cmdbuf_new(..) with nr_pmrs drm/etnaviv: add performance monitor request validation drm/etnaviv: copy pmrs from userspace drm/etnaviv: add performance monitor request processing drm/etnaviv: add 'sync point' support drm/etnaviv: clear alloced event drm/etnaviv: use 'sync points' for performance monitor requests drm/etnaviv: add HI perf domain drm/etnaviv: add PE perf domain drm/etnaviv: add SH perf domain drm/etnaviv: add PA perf domain drm/etnaviv: add SE perf domain drm/etnaviv: add RA perf domain drm/etnaviv: add TX perf domain drm/etnaviv: add MC perf domain drm/etnaviv: need to disable clock gating when doing profiling drm/etnaviv: enable debug registers on demand drm/etnaviv: submit supports performance monitor requests drivers/gpu/drm/etnaviv/Makefile | 3 +- drivers/gpu/drm/etnaviv/etnaviv_buffer.c | 36 +++ drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.c | 13 +- drivers/gpu/drm/etnaviv/etnaviv_cmdbuf.h | 6 +- drivers/gpu/drm/etnaviv/etnaviv_drv.c | 39 ++- drivers/gpu/drm/etnaviv/etnaviv_drv.h | 1 + drivers/gpu/drm/etnaviv/etnaviv_gem_submit.c | 68 +++- drivers/gpu/drm/etnaviv/etnaviv_gpu.c | 151 ++++++++- drivers/gpu/drm/etnaviv/etnaviv_gpu.h | 6 + drivers/gpu/drm/etnaviv/etnaviv_perfmon.c | 447 +++++++++++++++++++++++++++ drivers/gpu/drm/etnaviv/etnaviv_perfmon.h | 48 +++ include/uapi/drm/etnaviv_drm.h | 40 ++- 12 files changed, 836 insertions(+), 22 deletions(-) create mode 100644 drivers/gpu/drm/etnaviv/etnaviv_perfmon.c create mode 100644 drivers/gpu/drm/etnaviv/etnaviv_perfmon.h -- 2.9.4

2 20

[PATCH] drm/udl: dma-buf: Constify dma_buf_ops structures.
by Arvind Yadav 03 Jul '17

03 Jul '17

dma_buf_ops are not supposed to change at runtime. All functions working with dma_buf_ops provided by <linux/dma-buf.h> work with const dma_buf_ops. So mark the non-const structs as const. File size before: text data bss dec hex filename 2002 112 0 2114 842 drivers/gpu/drm/udl/udl_dmabuf.o File size After adding 'const': text data bss dec hex filename 2114 0 0 2114 842 drivers/gpu/drm/udl/udl_dmabuf.o Signed-off-by: Arvind Yadav <arvind.yadav.cs(a)gmail.com> --- drivers/gpu/drm/udl/udl_dmabuf.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/udl/udl_dmabuf.c b/drivers/gpu/drm/udl/udl_dmabuf.c index ed0e636..61a5a5f 100644 --- a/drivers/gpu/drm/udl/udl_dmabuf.c +++ b/drivers/gpu/drm/udl/udl_dmabuf.c @@ -186,7 +186,7 @@ static int udl_dmabuf_mmap(struct dma_buf *dma_buf, return -EINVAL; } -static struct dma_buf_ops udl_dmabuf_ops = { +static const struct dma_buf_ops udl_dmabuf_ops = { .attach = udl_attach_dma_buf, .detach = udl_detach_dma_buf, .map_dma_buf = udl_map_dma_buf, -- 2.7.4

2 1

[PATCH v4 0/6] drm: add asynchrounous plane update
by Gustavo Padovan 03 Jul '17

03 Jul '17

From: Gustavo Padovan <gustavo.padovan(a)collabora.com> Hi, Follow up after Daniel's comments. Here I move the common async code to drm_atomic_helper.c. i915 and msm now have to call the drm_atomic_helper_async_check() themselves. Please review! Thanks. Gustavo Gustavo Padovan (6): drm/atomic: initial support for asynchronous plane update drm/i915: update cursors asynchronously through atomic drm/i915: remove intel_cursor_plane_funcs drm/msm: update cursors asynchronously through atomic drm/msm: remove mdp5_cursor_plane_funcs drm/vc4: update cursors asynchronously through atomic drivers/gpu/drm/drm_atomic_helper.c | 122 +++++++++++++++++++++ drivers/gpu/drm/i915/intel_atomic_plane.c | 73 +++++++++++++ drivers/gpu/drm/i915/intel_display.c | 163 +++++----------------------- drivers/gpu/drm/msm/mdp/mdp5/mdp5_plane.c | 175 +++++++++++------------------- drivers/gpu/drm/msm/msm_atomic.c | 9 ++ drivers/gpu/drm/vc4/vc4_kms.c | 20 ++++ drivers/gpu/drm/vc4/vc4_plane.c | 128 +++++++++------------- include/drm/drm_atomic.h | 2 + include/drm/drm_atomic_helper.h | 4 + include/drm/drm_modeset_helper_vtables.h | 50 +++++++++ 10 files changed, 423 insertions(+), 323 deletions(-) -- 2.9.4

2 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel July 2017