The positions of primary and overlay plane type enums in the kernel were
updated in
drm/doc: Polish for drm_plane.[hc]
So, making the change here as well.
Cc: Daniel Vetter
Signed-off-by: Dhinakaran Pandiyan
---
xf86drmMode.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletion
On 09/19/16 16:33, ville.syrjala at linux.intel.com wrote:
> From: Ville Syrjälä
>
> drm/tilcdc/tilcdc_tfp410.c:385:24: warning: symbol 'tfp410_driver' was not
> declared. Should it be static?
> drm/tilcdc/tilcdc_tfp410.c:395:12: warning: symbol 'tilcdc_tfp410_init' was
> not declared. Should
On Thu, Sep 22, 2016 at 03:11:25PM +0200, SF Markus Elfring wrote:
> > If you restricted yourself to fixing bugs only then you would maybe fix more
> > bugs than you introduce but as it you are making the kernel worse.
>
> Would you like to discuss the statistics for my failure (or success) rate
>
On Thu, Sep 22, 2016 at 2:04 PM, Jyri Sarha wrote:
> On 09/22/16 09:18, Daniel Vetter wrote:
>> On Wed, Sep 21, 2016 at 06:36:28AM -0700, Sean Paul wrote:
>>> Also reorder alphabetically and fix up drm_flip_work header.
>>>
>>> Signed-off-by: Sean Paul
>>
>> Reviewed-by: Daniel Vetter
>>
>
> Pic
On 09/22/16 21:38, SF Markus Elfring wrote:
>>> 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 conve
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/
>
> * h
>> 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 resour
> 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
--
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/ca42a569/attachment.html>
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>
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.
>
> * Adj
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 +-
>
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".
>
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
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 2
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
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma
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 coding style convention.
Signe
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 a/tools/testing/selftests/s
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
---
drivers/gpu/drm/ttm/ttm_page_alloc_dma.c | 5 +
1
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
---
drivers/gpu/drm/ttm/ttm_page_alloc
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.
Signed-off-by: Markus Elfring
-
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 deletions(-)
diff --git a/drivers/gpu/
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 deletions(-)
diff --git a/drivers/
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 deletions(-)
diff --git a/drivers/gpu
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 detected by using the Coccinelle softwa
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 deletions(-)
diff --git a/drivers/gpu/drm/
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 deletions(-)
diff --git a/drivers/gp
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 deletions(-)
diff --git a/drivers/gpu/drm
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 detected by using the Coccinelle softwa
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 labels in ttm_page_pool_free()
> 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 yo
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
> 'tilcdc_atomic_check'
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:
> drivers/gpu/drm/tilcdc/tilcdc_tfp410.c:3
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] [drm:drm_helper_probe_single_connector_modes_mer
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
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
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
inde
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
--- a
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 100644
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
Signed-of
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 |
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
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 e
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
> "while(!fence_i
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
>> devfreq_get_devfreq_by_ph
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 probin
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!).
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 th
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 obje
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 (2016-0
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
> 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 ov
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 s
es/dri-devel/attachments/20160922/b11f88f8/attachment.html>
Am 22.09.2016 um 14:26 schrieb Daniel Vetter:
> 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
On Thu, Sep 22, 2016 at 01:28:37PM +0200, Daniel Vetter wrote:
>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 pick
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, but
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++) {
>>
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
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 fi
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 a/drivers/gpu/d
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 a/drivers/gpu/drm/
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 a/drivers/gpu/drm/
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 ++---
drivers/gpu/drm/omapdrm/displays/connector-dv
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 omap_video_timings
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
---
driv
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 +++
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
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 +-
drivers/gpu/drm/omap
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 +-
...
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 +--
drive
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 a/drivers/gpu
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 --
drivers/gpu/drm/omapdrm/dss/dis
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 a/drivers/gpu/
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
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
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
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 +-
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 +-
driv
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 +-
drivers
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
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 +-
dri
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 videm
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
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 R
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
2016-09-22 Christian König :
> Am 22.09.2016 um 09:44 schrieb Gustavo Padovan:
> > Hi Christian,
> >
> > 2016-09-21 Christian König :
> >
> > > Am 21.09.2016 um 13:36 schrieb Gustavo Padovan:
> > > > From: Gustavo Padovan
> > > >
> > > > If the fences in the fence_array signal on the fence_a
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
CC
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 --git a/include/video/d
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 pi
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 d
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 thi
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/216afa6d/attachment.html>
xt part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/e179e6fd/attachment.html>
the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/64d40334/attachment-0001.html>
-- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/139d1073/attachment.html>
--- next part --
An HTML attachment was scrubbed...
URL:
<https://lists.freedesktop.org/archives/dri-devel/attachments/20160922/3161331e/attachment.html>
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 h
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 are
ls fences 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>
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, but essentially I think it is a perfectly valid
>> requirement to have multipl
1 - 100 of 156 matches
Mail list logo
