GPU-DRM-QXL: Move three assignments in qxl_device_init()

On Do, 2016-09-22 at 19:16 +0200, SF Markus Elfring wrote: > > For starters make sure the patches land actually on the list. > > How do you think about to take another look at this update suggestion > also by the usual archive interfaces? > > * https://patchwork.kernel.org/patch/9344521/ > > *

GPU-DRM-TILCDC: Less function calls in tilcdc_convert_slave_node() after error detection

>> The of_node_put() function was called in some cases >> by the tilcdc_convert_slave_node() function during error handling >> even if the passed variable contained a null pointer. >> >> * Adjust jump targets according to the Linux coding style convention. >> >> * Split a condition check for

GPU-DRM-TILCDC: Return directly after a failed kfree_table_init() in tilcdc_convert_slave_node()

> I'll pick this up, but with your permission I change > the commit subject to follow the current convention. I guess that I can accept the integration of this update suggestion also with an adjusted prefix in the commit title. ;-) Regards, Markus

[Bug 97886] radeon r300 vdpau broken

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

[Bug 97886] radeon r300 vdpau broken

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/20160922/108bd7cc/attachment-0001.html>

[PATCH 3/4] GPU-DRM-TILCDC: Less function calls in tilcdc_convert_slave_node() after error detection

On 09/22/16 11:33, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 22 Sep 2016 10:06:50 +0200 > > The of_node_put() function was called in some cases > by the tilcdc_convert_slave_node() function during error handling > even if the passed variable contained a null pointer. > > *

[PATCH 2/4] GPU-DRM-TILCDC: Return directly after a failed kfree_table_init() in tilcdc_convert_slave_node()

On 09/22/16 11:32, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 22 Sep 2016 09:29:23 +0200 > > Return directly after a memory allocation failed in this function > at the beginning. > > Signed-off-by: Markus Elfring > --- > drivers/gpu/drm/tilcdc/tilcdc_slave_compat.c | 2 +- >

[PATCH 1/4] GPU-DRM-TILCDC: Use kmalloc_array() in kfree_table_init()

On 09/22/16 11:31, SF Markus Elfring wrote: > From: Markus Elfring > Date: Thu, 22 Sep 2016 09:05:14 +0200 > > A multiplication for the size determination of a memory allocation > indicated that an array data structure should be processed. > Thus use the corresponding function "kmalloc_array". >

[PATCH 14/14] GPU-DRM-TTM: Mark an array of text strings as "const" in ttm_dma_pool_init()

From: Markus Elfring Date: Thu, 22 Sep 2016 18:46:01 +0200 The local variable "n" was not modified after it was initialized with a few text strings. Thus express this detail also by the data type qualifier "const". Signed-off-by: Markus Elfring ---

[PATCH 13/14] GPU-DRM-TTM: Delete unnecessary variable initialisations in ttm_dma_pool_init()

From: Markus Elfring Date: Thu, 22 Sep 2016 17:37:24 +0200 Two local variables will be set to an appropriate pointer a bit later. Thus omit the explicit initialisation which became unnecessary with a previous update step. Signed-off-by: Markus Elfring ---

[PATCH 12/14] GPU-DRM-TTM: Less function calls in ttm_dma_pool_init() after error detection

From: Markus Elfring Date: Thu, 22 Sep 2016 17:30:52 +0200 The kfree() function was called in up to two cases by the ttm_dma_pool_init() function during error handling even if the passed variable contained a null pointer. Adjust jump targets according to the Linux

[PATCH 1/7] selftest: sync: basic tests for sw_sync framework

Emilio López writes: > These tests are based on the libsync test suite from Android. > This commit lays the ground for future tests, as well as includes > tests for a variety of basic allocation commands. Hi Emilio, Just a few comments on the Makefile. > diff --git

[PATCH 11/14] GPU-DRM-TTM: Return an error code only as a constant in ttm_dma_pool_init()

From: Markus Elfring Date: Thu, 22 Sep 2016 17:17:19 +0200 * Return an error code without storing it in a local variable. * Delete the local variable "ret" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring ---

[PATCH 10/14] GPU-DRM-TTM: Return directly after a failed kobject_init_and_add() in ttm_dma_page_alloc_init()

From: Markus Elfring Date: Thu, 22 Sep 2016 16:24:43 +0200 * Return directly after a call of the function "kobject_init_and_add" failed here. * Delete the jump target "err" which became unnecessary with this refactoring. Signed-off-by: Markus Elfring ---

[PATCH 09/14] GPU-DRM-TTM: Return directly after a failed kzalloc() in ttm_dma_page_alloc_init()

From: Markus Elfring Date: Thu, 22 Sep 2016 16:16:36 +0200 * Return directly after a memory allocation failed in this function at the beginning. * Delete the explicit initialisation for the local variable "ret" which became unnecessary with this refactoring.

[PATCH 08/14] GPU-DRM-TTM: Rename a jump label in ttm_dma_pool_shrink_scan()

From: Markus Elfring Date: Thu, 22 Sep 2016 16:02:36 +0200 Adjust a jump label according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 07/14] GPU-DRM-TTM: Rename jump labels in ttm_dma_page_pool_free()

From: Markus Elfring Date: Thu, 22 Sep 2016 15:32:32 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 9 - 1 file changed, 4 insertions(+), 5

[PATCH 06/14] GPU-DRM-TTM: Rename a jump label in ttm_dma_pool_alloc_new_pages()

From: Markus Elfring Date: Thu, 22 Sep 2016 14:54:12 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 05/14] GPU-DRM-TTM: Use kmalloc_array() in two more functions

From: Markus Elfring Date: Thu, 22 Sep 2016 14:48:39 +0200 * Multiplications for the size determination of memory allocations indicated that array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 04/14] GPU-DRM-TTM: Rename a jump label in ttm_page_pool_get_pages()

From: Markus Elfring Date: Thu, 22 Sep 2016 14:36:47 +0200 Adjust a jump label according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc.c | 4 ++-- 1 file changed, 2 insertions(+), 2

[PATCH 03/14] GPU-DRM-TTM: Rename jump labels in ttm_page_pool_free()

From: Markus Elfring Date: Thu, 22 Sep 2016 14:30:12 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc.c | 10 -- 1 file changed, 4 insertions(+), 6

[PATCH 02/14] GPU-DRM-TTM: Rename a jump label in ttm_alloc_new_pages()

From: Markus Elfring Date: Thu, 22 Sep 2016 14:16:05 +0200 Adjust jump labels according to the current Linux coding style convention. Signed-off-by: Markus Elfring --- drivers/gpu/drm/ttm/ttm_page_alloc.c | 6 +++--- 1 file changed, 3 insertions(+), 3

[PATCH 01/14] GPU-DRM-TTM: Use kmalloc_array() in two functions

From: Markus Elfring Date: Thu, 22 Sep 2016 14:00:31 +0200 * Multiplications for the size determination of memory allocations indicated that array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was

[PATCH 00/14] GPU-DRM-TTM: Fine-tuning for several function implementations

From: Markus Elfring Date: Thu, 22 Sep 2016 19:00:01 +0200 Several update suggestions were taken into account from static source code analysis. Markus Elfring (14): Use kmalloc_array() in two functions Rename a jump label in ttm_alloc_new_pages() Rename jump

GPU-DRM-QXL: Move three assignments in qxl_device_init()

> For starters make sure the patches land actually on the list. How do you think about to take another look at this update suggestion also by the usual archive interfaces? * https://patchwork.kernel.org/patch/9344521/ * https://lkml.kernel.org/r/ > Only the cover letter arrived here. Would

[PATCH] drm/tilcdc: mark tilcdc_atomic_check() static

Thank, But I already have this too: http://www.spinics.net/lists/kernel/msg2340400.html Best regards, Jyri On 09/21/16 08:14, Baoyou Xie wrote: > We get 1 warning when building kernel with W=1: > drivers/gpu/drm/tilcdc/tilcdc_drv.c:64:5: warning: no previous prototype for >

[PATCH] drm/tilcdc: add missing header dependencies

Thanks, But I have got this already: https://lists.freedesktop.org/archives/dri-devel/2016-September/117900.html I will send a pull request soon. Best regards, Jyri On 09/21/16 08:12, Baoyou Xie wrote: > We get 4 warnings when building kernel with W=1: >

[ADV7393] DRM Encoder Slave or DRM Bridge

Hi Tomi, Now with the adv7393 driver in place, I was getting following error. After debugging found out that this is due to the “.interlace= true” in display timings “drivers\gpu\drm\omapdrm\displays\connector-analog-tv.c”. [ 14.564872]

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

The grass looks like in a cell shading game, (wrong shader applied?) -- You are receiving this mail because: You are on the CC list for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/2016

GPU-DRM-QXL: Move three assignments in qxl_device_init()

On Do, 2016-09-22 at 15:11 +0200, SF Markus Elfring wrote: > > Guys, please stop accepting patches from Markus! > > I would appreciate a bit more explanation for this request. For starters make sure the patches land actually on the list. Only the cover letter arrived here. cheers, Gerd

[PATCH] drivers: drm: nouveau: Fix brace coding style error

Fixed a coding style issue. Else should follow brace. Signed-off-by: David Archuleta Jr. --- drivers/gpu/drm/nouveau/nouveau_display.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_display.c b/drivers/gpu/drm/nouveau/nouveau_display.c

[PATCH v2 4/4] drm/exynos: g2d: beautify probing message

Apply some 'make-up' in g2d_probe(). Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/exynos/exynos_drm_g2d.c b/drivers/gpu/drm/exynos/exynos_drm_g2d.c index 73cd83f..410d170 100644 ---

[PATCH v2 3/4] drm/exynos: mixer: simplify loop in vp_win_reset()

A simple while loop should do the same here. Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_mixer.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/exynos/exynos_mixer.c b/drivers/gpu/drm/exynos/exynos_mixer.c index c3dad66..4f39d6b

[PATCH v2 2/4] drm/exynos: mixer: configure layers once in mixer_atomic_flush()

Only manipulate the MXR_CFG and MXR_LAYER_CFG registers once in mixer_cfg_layer(). Trigger this via atomic flush. Changes in v2: - issue mixer_cfg_layer() in mixer_disable() - rename fields as suggested by Andrzej - added docu to mixer context struct - simplify mixer_win_reset() as well

[PATCH v2 1/4] drm/exynos: mixer: convert booleans to flags in mixer context

The mixer context struct already has a 'flags' field, so we can use it to store the 'interlace', 'vp_enabled' and 'has_sclk' booleans. We use the non-atomic helper functions to access these bits. Reviewed-by: Andrzej Hajda Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_mixer.c

[PATCH v2 0/4] drm/exynos: mixer: small optimisations

Hello, here's v2 of this patchset. I've added two other 'cosmetic' patches as well. Anyway, I have fixed up the second patch and integrated Andrzej's suggestions. First patch is unmodified except for the Reviewed-By tag. With best wishes, Tobias Tobias Jakobi (4): drm/exynos: mixer: convert

[PATCH] dma-buf/fence-array: get signaled state when signaling is disabled

Am 22.09.2016 um 16:11 schrieb Christian König: > Am 22.09.2016 um 13:16 schrieb Gustavo Padovan: >> 2016-09-22 Christian König : >> >>> Dropping the rest of the patch, cause that really doesn't make sense >>> any >>> more. >>> >>> Am 22.09.2016 um 12:40 schrieb Gustavo Padovan: > E.g. for

[PATCH] dma-buf/fence-array: get signaled state when signaling is disabled

Am 22.09.2016 um 13:16 schrieb Gustavo Padovan: > 2016-09-22 Christian König : > >> Dropping the rest of the patch, cause that really doesn't make sense any >> more. >> >> Am 22.09.2016 um 12:40 schrieb Gustavo Padovan: E.g. for example it is illegal to do something like >

drm/exynos: probe deferral for sub drivers

Hey Andrzej, Andrzej Hajda wrote: > On 21.09.2016 00:07, Tobias Jakobi wrote: >> Hello, >> >> I'm currently facing the following problem. >> >> I want to use a devfreq device in one of the Exynos sub drivers, namely >> the G2D sub driver. My current approach is to use >>

drm/exynos: probe deferral for sub drivers

On 21.09.2016 00:07, Tobias Jakobi wrote: > Hello, > > I'm currently facing the following problem. > > I want to use a devfreq device in one of the Exynos sub drivers, namely > the G2D sub driver. My current approach is to use > devfreq_get_devfreq_by_phandle() in g2d_probe(). But at the G2D

[PATCH] drm: Convert prime dma-buf <-> handle to rhashtable

Currently we use a linear walk to lookup a handle and return a dma-buf, and vice versa. A long overdue TODO task is to convert that to a hashtable. Since the initial implementation of dma-buf/prime, we now have resizeable hashtables we can use (and now a future task is to RCU enable the lookup!).

[PATCH] drm/i2c: tda998x: don't register the connector

On Thu, Sep 22, 2016 at 02:38:45PM +0100, Brian Starkey wrote: > However, without patching all three drivers in the same commit, there > would always be some breakage. HDLCD and Mali-DP call > drm_dev_register() before binding the components - this was needed to > work with tda998x, which needed

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

Am 22.09.2016 um 15:05 schrieb Daniel Vetter: > On Thu, Sep 22, 2016 at 2:44 PM, Christian König > wrote: >>> - explicit fencing: Userspace passes around distinct fence objects for >>> any work going on on the gpu. The kernel doesn't insert any stall of >>> it's own (except for moving buffer

[pull] radeon and amdgpu drm-next-4.9

Hi Dave, Last set of radeon and amdgpu changes for 4.9. This is mostly just the powerplay cleanup for dGPUs. Beyond that, just misc code cleanups and bug fixes. The following changes since commit af1f85ddecfa341e684db950c34a1813d36750db: drm/ttm: remove cpu_address member from ttm_tt

[PATCH] drm/i2c: tda998x: don't register the connector

Hi Sean, On Thu, Sep 22, 2016 at 04:22:40AM -0700, Sean Paul wrote: >On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux > wrote: >> On Thu, Sep 22, 2016 at 11:39:18AM +0100, Brian Starkey wrote: >>> Actually, could you please hold off picking this up? We need to make >>> changes in mali-dp

GPU-DRM-QXL: Move three assignments in qxl_device_init()

> Guys, please stop accepting patches from Markus! I would appreciate a bit more explanation for this request. > Markus, you always introduce bugs. I find the wording "always" exaggerated. It can also happen that I make another programming mistake occasionally. > I have asked you over and

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

On Thu, Sep 22, 2016 at 2:44 PM, Christian König wrote: >> - explicit fencing: Userspace passes around distinct fence objects for >> any work going on on the gpu. The kernel doesn't insert any stall of >> it's own (except for moving buffer objects around ofc). This is what >> Android. This also

[Bug 94900] HD6950 GPU lockup loop with various steam games (octodad[always], saints row 4[always], dead island[always], grid autosport[sometimes])

es/dri-devel/attachments/20160922/b11f88f8/attachment.html>

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

On Thu, Sep 22, 2016 at 12:55 PM, Christian König wrote: > Am 22.09.2016 um 08:36 schrieb Daniel Vetter: >> >> On Wed, Sep 21, 2016 at 06:23:35PM +0200, Christian König wrote: >>> >>> For a quick workaround I suggest to just serialize all accesses to BO >>> shared >>> with different drivers,

[PATCH] drm/udl: Fix for the X server screen update v2

On 19.09.2016 23:12, Daniel Vetter wrote: > On Mon, Sep 19, 2016 at 8:27 PM, poma wrote: >> @@ -122,14 +126,14 @@ int udl_handle_damage(struct udl_framebuffer *fb, int >> x, int y, >> return 0; >> cmd = urb->transfer_buffer; >> >> - for (i = y; i < height ; i++) {

[PATCH] dma-buf/fence-array: get signaled state when signaling is disabled

2016-09-22 Christian König : > Dropping the rest of the patch, cause that really doesn't make sense any > more. > > Am 22.09.2016 um 12:40 schrieb Gustavo Padovan: > > > E.g. for example it is illegal to do something like > > > >"while(!fence_is_signaled(f)) sleep();" without enabling signaling

[PATCH v2 23/23] drm/omap: panel-lgphilips-lb035q02: Add note for incorrect data drive edge and DE level

According to the datasheet of the panel, both data, DEN and sync signals are expected to be driven on the falling edge of the DOTCLK. The DE is active low according to the documentation. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/panel-lgphilips-lb035q02.c | 5 + 1

[PATCH v2 22/23] drm/omap: panel-sharp-ls037v7dw01: Add note for incorrect data drive edge

According to the datasheet of the panel, both data, DEN and sync signals are expected to be driven on the falling edge of the DOTCLK. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/panel-sharp-ls037v7dw01.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v2 21/23] drm/omap: panel-tpo-td028ttec1: Add note for incorrect sync drive edge

According to the datasheet of the panel, both data, DEN and sync signals are expected to be driven on the falling edge of the DOTCLK. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/panel-tpo-td028ttec1.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v2 20/23] drm/omap: panel-tpo-td043mtea1: Add note for incorrect sync drive edge

According to the datasheet of the panel, both data, DEN and sync signals are expected to be driven on the falling edge of the DOTCLK. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/panel-tpo-td043mtea1.c | 4 1 file changed, 4 insertions(+) diff --git

[PATCH v2 19/23] drm/omap: Use consistent name for struct videomode

Use 'vm' to refer to a struct videomode instead of 'p', 't', 'timings' or something else. The code will be easier to follow if we use consistent names. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 26 ++---

[PATCH v2 18/23] drm/omap: Replace struct omap_video_timings with videomode

omap_video_timings can be replaced with the generic videomode in omapdrm and the omap_video_timings can be removed. This patch will replace the omap_video_timings with videomode. With the change we no longer need the functions to convert to/from videomode and drm_display_mode to

[PATCH v2 17/23] drm/omap: Change the types of struct omap_video_timings members

omap_video_timings struct have the same members as struct videomode, but their types are different. As first step change the types of the omap_video_timings struct members to match their counterpart in struct videomode to catch any type cast related issues. Signed-off-by: Peter Ujfalusi ---

[PATCH v2 16/23] drm/omap: omap_display_timings: Use display_flags for sync edge

In preparation to move the stack to use the generic videmode struct for display timing information use display_flags for sync edge. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 5 ++--- drivers/gpu/drm/omapdrm/displays/encoder-tfp410.c | 5

[PATCH v2 15/23] drm/omap: omap_display_timings: Use display_flags for pixel data edge

In preparation to move the stack to use the generic videmode struct for display timing information use display_flags for pixel data edge. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 3 +-- drivers/gpu/drm/omapdrm/displays/encoder-tfp410.c

[PATCH v2 14/23] drm/omap: omap_display_timings: Use display_flags for double_pixel mode

In preparation to move the stack to use the generic videmode struct for display timing information use display_flags for double_pixel mode. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/dss/dispc.c | 6 +++--- drivers/gpu/drm/omapdrm/dss/hdmi4.c | 2 +-

[PATCH v2 13/23] drm/omap: omap_display_timings: Use display_flags for DE level

In preparation to move the stack to use the generic videmode struct for display timing information use display_flags for DE level. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 4 ++-- drivers/gpu/drm/omapdrm/displays/encoder-tfp410.c | 2 +-

[PATCH v2 12/23] drm/omap: omap_display_timings: Use display_flags for h/vsync level

In preparation to move the stack to use the generic videmode struct for display timing information use display_flags for h/vsync level. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 3 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 4 +--

[PATCH v2 11/23] drm/omap: dispc: Simplify _dispc_mgr_set_lcd_timings() parameters

Instead of passing the omap_video_timings structure's members individually, use the pointer to the struct. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/dss/dispc.c | 38 ++--- 1 file changed, 14 insertions(+), 24 deletions(-) diff --git

[PATCH v2 10/23] drm/omap: omap_display_timings: Use display_flags for interlace mode

Remove the interlace member and add display_flags to omap_video_timings to configure the interlace mode. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-hdmi.c | 2 --

[PATCH v2 09/23] drm/omap: HDMI5: Use pointer to cfg->v_fc_config.timings in hdmi_core_video_config

By using a pointer to the omap_mode_timings struct we can unwrap lines to make the code easier to follow. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/dss/hdmi5_core.c | 47 ++-- 1 file changed, 20 insertions(+), 27 deletions(-) diff --git

[PATCH v2 08/23] drm/omap: omap_display_timings: rename vbp to vback_porch

In preparation to move the stack to use the generic videmode struct for display timing information rename the vbp member to vback_porch. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c| 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c

[PATCH v2 07/23] drm/omap: omap_display_timings: rename vfp to vfront_porch

In preparation to move the stack to use the generic videmode struct for display timing information rename the vfp member to vfront_porch. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c| 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c

[PATCH v2 06/23] drm/omap: omap_display_timings: rename vsw to vsync_len

In preparation to move the stack to use the generic videmode struct for display timing information rename the vsw member to vsync_len. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c

[PATCH v2 05/23] drm/omap: omap_display_timings: rename hbp to hback_porch

In preparation to move the stack to use the generic videmode struct for display timing information rename the hbp member to hback_porch. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c| 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 2 +-

[PATCH v2 04/23] drm/omap: omap_display_timings: rename hfp to hfront_porch

In preparation to move the stack to use the generic videmode struct for display timing information rename the hfp member to hfront_porch. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 2 +-

[PATCH v2 03/23] drm/omap: omap_display_timings: rename hsw to hsync_len

In preparation to move the stack to use the generic videmode struct for display timing information rename the hsw member to hsync_len. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 2 +-

[PATCH v2 02/23] drm/omap: omap_display_timings: rename y_res to vactive

In preparation to move the stack to use the generic videmode struct for display timing information rename the y_res member to vactive. Signed-off-by: Peter Ujfalusi --- drivers/gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c

[PATCH v2 01/23] drm/omap: omap_display_timings: rename x_res to hactive

In preparation to move the stack to use the generic videmode struct for display timing information rename the x_res member to hactive. Signed-off-by: Peter Ujfalusi --- .../gpu/drm/omapdrm/displays/connector-analog-tv.c | 2 +- drivers/gpu/drm/omapdrm/displays/connector-dvi.c | 2 +-

[PATCH v2 00/23] drm/omap: Convert to use videomode from omap_video_timings

Hi, Changes since v1: - separated the patches from the sync drive edge selection series [1] - commit messages updated as per Tomi's comments - other comments from Tomi for patch 10 (was 13) and 11 (was 14) addressed also The following series will convert the omapdrm stack to use the generic

[PATCH 2/4] GPU-DRM-TILCDC: Return directly after a failed kfree_table_init() in tilcdc_convert_slave_node()

This one is actually a bug fix... But finding bug fixes in this series is like looking for kernels of edible corn in piles of monkey poop. Also, classic "One Err" bug. regards, dan carpenter

[Bug 172421] radeon: allow to set the TMDS frequency by a special kernel parameter

https://bugzilla.kernel.org/show_bug.cgi?id=172421 --- Comment #12 from Elmar Stellnberger --- Today I approached to try out the dual-link feature of the DVI-port. First I had verified with AOC that my u2868pqu monitor in deed supports dual-link over DVI. Then I connected the DVI output of my

[PATCH] drm/i2c: tda998x: don't register the connector

On Thu, Sep 22, 2016 at 05:32:35AM -0700, Sean Paul wrote: > On Thu, Sep 22, 2016 at 5:09 AM, Russell King - ARM Linux > wrote: > > On Thu, Sep 22, 2016 at 04:22:40AM -0700, Sean Paul wrote: > >> On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux > >> wrote: > >> > On Thu, Sep 22, 2016 at

[PATCH v2 3/3] video: of: display_timing: Add support for syncclk-active property

Configure the DISPLAY_FLAGS_SYNC_POSEDGE/NEGEDGE flags according to the binding document. If the syncclk-active is present in DT, configure the flags accordingly, if it is omitted it means that the SYNC edge is following the pixdata configuration. Signed-off-by: Peter Ujfalusi CC: Rob Herring

[PATCH v2 2/3] video: display_timing: Add flags to select the edge when the sync is driven

The sync can be - and for some panels it must be - driven on different edge then the data. Signed-off-by: Peter Ujfalusi CC: Rob Herring CC: Mark Rutland CC: devicetree at vger.kernel.org --- include/video/display_timing.h | 4 1 file changed, 4 insertions(+) diff

[PATCH v2 1/3] dt-bindings: display: display-timing: Add property to configure sync drive edge

There are display panels which demands that the sync signal is driven on different edge than the pixel data. With the syncclk-active property we can specify the clk edge to be used to drive the sync signal. When the property is missing it indicates that the sync is driven on the same edge as the

[PATCH v2 0/3] video: of: Drive edge selection for sync

Hi, Changes since v1: - separated the code changes from the omap/drm videomode conversion patches - the DT bindings document is now explicitly states that the drive edge is referring to the pixel clock Since we have several panels under omapdrm/displays/ where the data drive edge is set to be

[PATCH] drm/i2c: tda998x: don't register the connector

On Thu, Sep 22, 2016 at 1:22 PM, Sean Paul wrote: > On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux > wrote: >> On Thu, Sep 22, 2016 at 11:39:18AM +0100, Brian Starkey wrote: >>> Actually, could you please hold off picking this up? We need to make >>> changes in mali-dp and hdlcd or

[Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes

bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/216afa6d/attachment.html>

[Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes

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

[Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes

ext part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/64d40334/attachment-0001.html>

[Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes

art -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/139d1073/attachment.html>

[Bug 97896] RADEON DisplayPort - Monitor shows out of range in some modes

--- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/3161331e/attachment.html>

[PATCH] drm/i2c: tda998x: don't register the connector

On Thu, Sep 22, 2016 at 04:22:40AM -0700, Sean Paul wrote: > On Thu, Sep 22, 2016 at 3:51 AM, Russell King - ARM Linux > wrote: > > On Thu, Sep 22, 2016 at 11:39:18AM +0100, Brian Starkey wrote: > >> Actually, could you please hold off picking this up? We need to make > >> changes in mali-dp and

[PATCH 2/4] GPU-DRM-QXL: Move three assignments in qxl_device_init()

Guys, please stop accepting patches from Markus! Markus, you always introduce bugs. I have asked you over and over to stop sending "cleanup patches" because you are not careful. If you restricted yourself to fixing bugs only then you would maybe fix more bugs than you introduce but as it you

[PATCH] dma-buf/fence-array: get signaled state when signaling is disabled

nces on their own. Regards, Christian. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/3a486b47/attachment-0001.html>

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

ave posted a few? If so, I will upload one early next week (I will be away over the weekend). -- You are receiving this mail because: You are on the CC list for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/cc2625bf/attachment.html>

[PATCH 2/2] drm: Don't swallow error codes in drm_dev_alloc()

On Thu, Sep 22, 2016 at 11:47 AM, Eric Engestrom wrote: > On Wed, Sep 21, 2016 at 04:59:19PM +0200, Tom Gundersen wrote: >> There are many reasons other than ENOMEM that drm_dev_init() can >> fail. Return ERR_PTR rather than NULL to be able to distinguish >> these in the caller. >> >>

[PATCH 1/2] drm: Distinguish no name from ENOMEM in set_unique()

On Thu, Sep 22, 2016 at 8:28 AM, Emil Velikov wrote: > On 21 September 2016 at 15:59, Tom Gundersen wrote: >> If passing name == NULL to drm_drv_set_unique() we now get -ENOMEM >> as kstrdup() returns NULL. Instead check for this explicitly and >> return -EINVAL if no name is provided. >> >>

[PATCH] drm/i2c: tda998x: don't register the connector

On Thu, Sep 22, 2016 at 11:39:18AM +0100, Brian Starkey wrote: > Actually, could you please hold off picking this up? We need to make > changes in mali-dp and hdlcd or this will mess up their registration. > I will send those patches later today, but better if this all goes in > together (whenever

[PATCH] drm/imx: hide an unused label

The imx_drm_bind function causes a warning in linux-next when CONFIG_DRM_FBDEV_EMULATION is not set: drivers/gpu/drm/imx/imx-drm-core.c: In function 'imx_drm_bind': drivers/gpu/drm/imx/imx-drm-core.c:441:1: error: label 'err_unbind' defined but not used [-Werror=unused-label] I don't understand

[PATCH 14/14] GPU-DRM-TTM: Mark an array of text strings as "const" in ttm_dma_pool_init()

On Thu, 2016-09-22 at 19:46 +0200, SF Markus Elfring wrote: > The local variable "n" was not modified after it was initialized with > a few text strings. > Thus express this detail also by the data type qualifier "const". [] > diff --git a/drivers/gpu/drm/ttm/ttm_page_alloc_dma.c >

[PATCH] drm/i2c: tda998x: don't register the connector

Thanks Russell, it's most appreciated. On Wed, Sep 21, 2016 at 05:28:03PM +0100, Russell King - ARM Linux wrote: >On Wed, Sep 21, 2016 at 09:57:38AM +0100, Brian Starkey wrote: >> Hi Russell, >> >> Are you in a position to be able to test this now? > >Normally, I'd say no, because I'd normally

[PATCH 1/7] selftest: sync: basic tests for sw_sync framework

Hi Michael, El 22/09/16 a las 06:43, Michael Ellerman escribió: > Emilio López writes: >> +CFLAGS += -I../../../../include/uapi/ > > Please don't include the unprocessed uapi headers, they are not meant to > be directly included in userspace programs. > > They even say so: > >

[Bug 94984] XCom2 crashes with SIGSEGV on radeonsi

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

  1   2   >