[PATCH 1/2] meson: set proper pkg-config version for libdrm_freedreno

[Dylan Baker]

Copy and paste error from exynos.

Signed-off-by: Dylan Baker 
---
 freedreno/meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/freedreno/meson.build b/freedreno/meson.build
index b4035e1..de6a413 100644
--- a/freedreno/meson.build
+++ b/freedreno/meson.build
@@ -64,7 +64,7 @@ pkg.generate(
   name : 'libdrm_freedreno',
   libraries : libdrm_freedreno,
   subdirs : ['.', 'libdrm', 'freedreno'],
-  version : '0.7',
+  version : meson.project_version(),
   requires_private : 'libdrm',
   description : 'Userspace interface to freedreno kernel DRM services',
 )
-- 
git-series 0.9.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH 2/2] meson: set the minimum version correctly

[Dylan Baker]

Currently we ask for 0.42, but we actually require 0.43 because we pass
file objects as arguments to tests. If someone needs version 0.42 it
wouldn't be hard, just a lot of replacing files() with strings.

Signed-off-by: Dylan Baker 
---
 meson.build | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/meson.build b/meson.build
index 0556608..d7a50cf 100644
--- a/meson.build
+++ b/meson.build
@@ -23,7 +23,7 @@ project(
   ['c'],
   version : '2.4.89',
   license : 'MIT',
-  meson_version : '>= 0.42',
+  meson_version : '>= 0.43',
   default_options : ['buildtype=debugoptimized', 'c_std=gnu99'],
 )
 
-- 
git-series 0.9.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[PATCH 0/2] Small fixes for the meson build

[Dylan Baker]

Here's a few things I've caught as I've started trying to add the meson
build to our CI system.

Dylan Baker (2):
  meson: set proper pkg-config version for libdrm_freedreno
  meson: set the minimum version correctly

 freedreno/meson.build | 2 +-
 meson.build   | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

base-commit: fd9bcb73e9c5a01085069b37c2f5e04300a9b4d4
-- 
git-series 0.9.1
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 101003] segfault with ideas test of glmark2

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=101003

--- Comment #5 from James Burton  ---
Seeing the same problem on Ubuntu 16.04 LTS with the 4.13.0-26-generic kernel.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104345] Playing video hangs X-Server with showing scrambled picture, sound still playing.

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104345

--- Comment #6 from bernhardu  ---
Created attachment 136709
  --> https://bugs.freedesktop.org/attachment.cgi?id=136709=edit
kernel output captured from the serial line. (4.14.10+lockdep)

Attaching another example with a vanilla kernel 4.14.10 with lockdep enabled.

Shows again such "GPU fault detected:"
followed by a "task amdgpu_cs:0:1014 blocked for more than 120 seconds.

I might add that it may be related to one or more suspend and resume cycles.

Is there anything I can attach or test to make
identification of the issue easier?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 198123] Console is the wrong color at boot with radeon 6670

[bugzilla-daemon]

https://bugzilla.kernel.org/show_bug.cgi?id=198123

--- Comment #15 from Deposite Pirate (dpir...@metalpunks.info) ---
As for me, the latest patch on top of HEAD doesn't fix the issue. But maybe I
ought to have applied Michel Dänzer's first patch too?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

[Bug 104463] RX 460 fan speed 100%

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104463

--- Comment #1 from Dmitry  ---
pwmconfig and Radeon GPU Profile adjust only one of the two coolers.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PATCH v2 2/2] drm: rcar-du: lvds: Fix LVDS startup on R-Car gen2

[Sergei Shtylyov]

On 1/13/2018 2:10 AM, Laurent Pinchart wrote:


From: Sergei Shtylyov 

According to the latest revision 2.00 of the R-Car gen2 manual, the LVDS
must be enabled and the bias crcuit enabled after the LVDS I/O pins are
enabled, not before. Fix the gen2 LVDS startup sequence accordingly.

While at it, also fix the comment preceding the first LVDCR0 write that
still talks about hardcoding the LVDS mode 0.


   Please do this in a separate commit then...


Fixes: 90374b5c25c9 ("drm/rcar-du: Add internal LVDS encoder support")


   You forgot to specify the other commit this one fixes -- I mean the 
comment fix.



Signed-off-by: Sergei Shtylyov 
Reviewed-by: Laurent Pinchart 
[Set the mode and input at the same time as the BEN and LVEN bits]
Tested-by: Laurent Pinchart 
Signed-off-by: Laurent Pinchart 
---
  drivers/gpu/drm/rcar-du/rcar_du_lvdsenc.c | 14 +++---
  1 file changed, 7 insertions(+), 7 deletions(-)

Hi Sergei,

For your convenience (and if you agree with bundling mode setup with the first
write as explained in my review of patch 1/2), here's the updated version of
patch 2/2 that I have taken in my development branch. If you're fine with it
I'll keep it, otherwise we can continue the review discussion.


   As I said, I don't know how to interpret the note 3 in either manual.

[...]

MBR, Sergei
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PATCH 1/2] drm: rcar-du: lvds: fix LVDS startup on R-Car gen3

[Sergei Shtylyov]

On 1/13/2018 1:15 AM, Laurent Pinchart wrote:


According to the latest revisions of the R-Car gen3 manual, the LVDS mode
must be set before the LVDS I/O pins are enabled, not after --  fix  the
gen3 LVDS startup sequence accordingly...

While  at it,  also fix the comment  preceding the first LVDCR0 write in
the R-Car gen2 startup code that still talks about hardcoding the LVDS
mode 0...


How about fixing that in patch 2/2 that touches the Gen2 initialization
sequence ? I think I'd even go as far as squashing both patches, I don't
think there's a need to split them.


Fixes: e947eccbeba4 ("drm: rcar-du: Add support for LVDS mode selection")
Signed-off-by: Sergei Shtylyov 


Is this really needed ? Does it fix a problem you've experienced, or is it
theoretical only ? The mode shouldn't matter before the LVDS internal logic
is turned on. Unless there's a real issue I'm not sure we should make the
code more complex.


Furthermore the datasheet states

"3. This refers to settings other than those that are concerned with LVDS-IF
startup. These items may be set while waiting for the conditions of step 6 to
be met."


   Ah, I hadn't paid much attention to this note. Howeve, it seems quite 
vague to me... and there's no condition in step 6. ;-)



Doesn't this mean that the mode and input selector don't have to be set as the
very first step, but can be programmed at any point before starting the LVDS
encoder through the PWD bit (on Gen3) or the PLLON bit (on Gen2) ?


   Frankly speaking, I don't know how to interpret that note...

[...]

MBR, Sergei
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

Re: [PATCH 1/2] drm: rcar-du: lvds: fix LVDS startup on R-Car gen3

[Sergei Shtylyov]

Hello!

On 1/13/2018 12:51 AM, Laurent Pinchart wrote:


On Friday, 12 January 2018 22:12:04 EET Sergei Shtylyov wrote:

According to the latest revisions of the R-Car gen3 manual, the LVDS mode
must be set before the LVDS I/O pins are enabled, not after --  fix  the
gen3 LVDS startup sequence accordingly...

While  at it,  also fix the comment  preceding the first LVDCR0 write in
the R-Car gen2 startup code that still talks about hardcoding the LVDS
mode 0...


How about fixing that in patch 2/2 that touches the Gen2 initialization
sequence ? I think I'd even go as far as squashing both patches, I don't think
there's a need to split them.


   No. Fixing both issues with 1 patch was intentional because they both were 
introduced by the same commit (see Fixes:).



Fixes: e947eccbeba4 ("drm: rcar-du: Add support for LVDS mode selection")
Signed-off-by: Sergei Shtylyov 


Is this really needed ? Does it fix a problem you've experienced, or is it
theoretical only ?


   No, just another check against the manual - there were some patches in the 
history of this file that did the same thing (sync to the manual). See e.g.


https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=85e8f8d175caa6a39f4c4e11dd4d0ab038f43324


The mode shouldn't matter before the LVDS internal logic is
turned on. Unless there's a real issue I'm not sure we should make the code
more complex.


   Up to you, of course...

[...]

MBR,Sergei
___
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel