On Tue, 4 Sep 2018, Daniel Vetter wrote:
> On Tue, Sep 4, 2018 at 1:41 AM, Dave Airlie wrote:
> >>
> >> I've seen that you dropped this patch:
> >> https://patchwork.kernel.org/patch/10445393/
> >>
> >> Is that patch correct or incorrect? In case it is incorrect, do you have
> >> an idea how
May be different then, because my bug
https://bugs.freedesktop.org/show_bug.cgi?id=107784 is with git userspace no
older than a few days, and displayport is broken whatever the screen resolution.
I did manually bisect the kernel and found the faulty commit though, I guess
the guys in amd are now
On Tue, 4 Sep 2018, Daniel Vetter wrote:
> On Tue, Sep 4, 2018 at 7:04 PM, Mikulas Patocka wrote:
> >
> >
> > On Tue, 4 Sep 2018, Daniel Vetter wrote:
> >
> >> On Tue, Sep 4, 2018 at 1:41 AM, Dave Airlie wrote:
> >> >>
> >> >> I've seen that you dropped this patch:
> >> >>
https://bugs.freedesktop.org/show_bug.cgi?id=105251
--- Comment #49 from Andrey Grodzovsky ---
(In reply to CheatCodesOfLife from comment #48)
> Created attachment 141425 [details]
> logs and trace
>
> Hi,
>
> I have applied the patch, ran through the process and attached the logs. The
> file
On Tue, Sep 4, 2018 at 9:05 PM, Mikulas Patocka wrote:
>
>
> On Tue, 4 Sep 2018, Daniel Vetter wrote:
>
>> With kms you need logind or someone like that who orchestrates the vt
>> switching and makes sure you can read/write other people's stuff.
>
> BTW. I'm just wondering how is this 'master
https://bugs.freedesktop.org/show_bug.cgi?id=107825
Bug ID: 107825
Summary: *ERROR* Couldn't read Speaker Allocation Data Block:
-2
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status:
Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
wrote:
On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter wrote:
On Tue, Sep 4, 2018 at 3:33 PM, Bas Nieuwenhuizen
wrote:
On Tue, Sep 4, 2018 at 3:04 PM Daniel Vetter wrote:
On Tue, Sep 04, 2018 at
Am 04.09.2018 um 20:00 schrieb Bas Nieuwenhuizen:
On Tue, Sep 4, 2018 at 7:57 PM Bas Nieuwenhuizen
wrote:
On Tue, Sep 4, 2018 at 7:48 PM Christian König
wrote:
Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
wrote:
On Tue, Sep 4, 2018 at
On Tue, Sep 4, 2018 at 7:57 PM, Bas Nieuwenhuizen
wrote:
> On Tue, Sep 4, 2018 at 7:48 PM Christian König
> wrote:
>>
>> Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
>> > On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
>> > wrote:
>> >> On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter wrote:
>>
On Tue, 4 Sep 2018, Daniel Vetter wrote:
> With kms you need logind or someone like that who orchestrates the vt
> switching and makes sure you can read/write other people's stuff.
BTW. I'm just wondering how is this 'master mode' security working at all.
The user start Xserver under the
On Tue, Sep 4, 2018 at 8:31 PM, Bas Nieuwenhuizen
wrote:
> On Tue, Sep 4, 2018 at 8:27 PM Daniel Vetter wrote:
>>
>> On Tue, Sep 4, 2018 at 7:57 PM, Bas Nieuwenhuizen
>> wrote:
>> > On Tue, Sep 4, 2018 at 7:48 PM Christian König
>> > wrote:
>> >>
>> >> Am 04.09.2018 um 18:37 schrieb Daniel
On Tue, Sep 4, 2018 at 9:28 PM Daniel Vetter wrote:
>
> On Tue, Sep 4, 2018 at 8:31 PM, Bas Nieuwenhuizen
> wrote:
> > On Tue, Sep 4, 2018 at 8:27 PM Daniel Vetter wrote:
> >>
> >> On Tue, Sep 4, 2018 at 7:57 PM, Bas Nieuwenhuizen
> >> wrote:
> >> > On Tue, Sep 4, 2018 at 7:48 PM Christian
https://bugs.freedesktop.org/show_bug.cgi?id=104362
--- Comment #8 from Andrey Grodzovsky ---
We can try and check the gfx command buffer for latest commands and CUs status
-
Clone and build our open source register analyzer from here -
https://cgit.freedesktop.org/amd/umr/
After hang happens
On Tue, Sep 4, 2018 at 7:48 PM Christian König
wrote:
>
> Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
> > On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
> > wrote:
> >> On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter wrote:
> >>> On Tue, Sep 4, 2018 at 3:33 PM, Bas Nieuwenhuizen
> >>> wrote:
https://bugs.freedesktop.org/show_bug.cgi?id=107213
--- Comment #12 from Sylvain BERTRAND ---
May be different then, because my bug
https://bugs.freedesktop.org/show_bug.cgi?id=107784 is with git userspace no
older than a few days, and displayport is broken whatever the screen
resolution.
I did
On Tue, Sep 4, 2018 at 8:27 PM Daniel Vetter wrote:
>
> On Tue, Sep 4, 2018 at 7:57 PM, Bas Nieuwenhuizen
> wrote:
> > On Tue, Sep 4, 2018 at 7:48 PM Christian König
> > wrote:
> >>
> >> Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
> >> > On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
> >>
https://bugs.freedesktop.org/show_bug.cgi?id=105046
--- Comment #19 from Michael Zapf ---
On my office PC with 4K monitor, the issue is now also gone. That is, I have no
more evidence of that resolution reset on any of my computers.
--
You are receiving this mail because:
You are the assignee
On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
wrote:
> On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter wrote:
>>
>> On Tue, Sep 4, 2018 at 3:33 PM, Bas Nieuwenhuizen
>> wrote:
>> > On Tue, Sep 4, 2018 at 3:04 PM Daniel Vetter wrote:
>> >>
>> >> On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas
Quoting Daniel Vetter (2018-09-04 14:08:12)
> On Tue, Sep 04, 2018 at 12:57:19PM +0100, Chris Wilson wrote:
> > The ioctl arguments are under control of the user and as such we should
> > resist any temptation to flood the kernel logs with their errors.
> > Relegate the DRM_ERROR to a DRM_DEBUG so
https://bugs.freedesktop.org/show_bug.cgi?id=107826
Bug ID: 107826
Summary: amdgpu-pro ubuntu 18.30: Missing xserver modesetting
package (--px install)
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=107826
qnerd changed:
What|Removed |Added
Summary|amdgpu-pro ubuntu 18.30:|amdgpu-pro 18.30: Missing
On Tue, Sep 4, 2018 at 7:57 PM Bas Nieuwenhuizen
wrote:
>
> On Tue, Sep 4, 2018 at 7:48 PM Christian König
> wrote:
> >
> > Am 04.09.2018 um 18:37 schrieb Daniel Vetter:
> > > On Tue, Sep 4, 2018 at 5:52 PM, Bas Nieuwenhuizen
> > > wrote:
> > >> On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter
On Tue, Sep 4, 2018 at 7:04 PM, Mikulas Patocka wrote:
>
>
> On Tue, 4 Sep 2018, Daniel Vetter wrote:
>
>> On Tue, Sep 4, 2018 at 1:41 AM, Dave Airlie wrote:
>> >>
>> >> I've seen that you dropped this patch:
>> >> https://patchwork.kernel.org/patch/10445393/
>> >>
>> >> Is that patch correct or
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #8 from Alan W. Irwin ---
Created attachment 141451
--> https://bugs.freedesktop.org/attachment.cgi?id=141451=edit
tarball containing kern.log, syslog, and dmesg output
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=106671
--- Comment #9 from Alan W. Irwin ---
We (there are two of us using this machine) just got yet another kernel lockup
(no remote access possible with ssh, direct keyboard not working), but this is
a case when we were remotely accessing this box
On Tuesday, 2018-09-04 14:49:07 +0200, Daniel Vetter wrote:
> Looks much neater on the gitlab UI, e.g. on my personal libdrm fork:
>
> https://gitlab.freedesktop.org/danvet/drm
>
> Signed-off-by: Daniel Vetter
Acked-by: Eric Engestrom
> ---
> CONTRIBUTING => CONTRIBUTING.rst | 0
> README
https://bugzilla.kernel.org/show_bug.cgi?id=200531
Barry G (ba...@grussling.com) changed:
What|Removed |Added
CC||ba...@grussling.com
---
Hi Jernej,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on sunxi/sunxi/for-next]
[also build test WARNING on v4.19-rc2 next-20180831]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Tue, Sep 4, 2018 at 4:43 PM Daniel Vetter wrote:
>
> On Tue, Sep 4, 2018 at 3:33 PM, Bas Nieuwenhuizen
> wrote:
> > On Tue, Sep 4, 2018 at 3:04 PM Daniel Vetter wrote:
> >>
> >> On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
> >> > On Tue, Sep 4, 2018 at 2:26 PM Daniel
Hi Bjorn and Linus
Thanks for the comments.
Based on this, since we want to remove the dev/phone dependency but
retain the driver + panel dependency on the compatible string, while
addressing Philip's comments, I shall rename the string as
"truly,nt35597-2K-display".
Let me know if there
On 2018年09月04日 17:20, Christian König wrote:
Am 04.09.2018 um 11:00 schrieb zhoucm1:
On 2018年09月04日 16:42, Christian König wrote:
Am 04.09.2018 um 10:27 schrieb zhoucm1:
On 2018年09月04日 16:05, Christian König wrote:
Am 04.09.2018 um 09:53 schrieb zhoucm1:
[SNIP]
How about this idea:
On 2018-08-29 10:49, Sean Paul wrote:
From: Sean Paul
The atomic_check is a bit too aggressive with respect to planes which
leave the active area. This caused a bunch of log spew when the cursor
got to the edge of the screen and stopped it from going all the way.
This patch removes the
On Tue, Sep 04, 2018 at 09:36:01PM +0200, Bas Nieuwenhuizen wrote:
> On Tue, Sep 4, 2018 at 9:28 PM Daniel Vetter wrote:
> >
> > On Tue, Sep 4, 2018 at 8:31 PM, Bas Nieuwenhuizen
> > wrote:
> > > On Tue, Sep 4, 2018 at 8:27 PM Daniel Vetter wrote:
> > >>
> > >> On Tue, Sep 4, 2018 at 7:57 PM,
On Tue, Mar 27, 2018 at 5:15 PM, Thomas Hellstrom wrote:
> On 03/27/2018 05:08 PM, Ville Syrjälä wrote:
>>
>> On Tue, Mar 27, 2018 at 04:26:17PM +0200, Thomas Hellstrom wrote:
>>>
>>> Use the correct helper and also return early on helper
>>> success rather than on helper failure.
>>>
>>> Also
Since this is handling user provided bpp and depth, we need to sanity
check and propagate the EINVAL back rather than assume what the insane
client intended and fill the logs with DRM_ERROR.
Signed-off-by: Chris Wilson
Cc: Daniel Vetter
Cc: Ville Syrjälä
---
So I am presuming that
On Tue, Sep 04, 2018 at 09:53:19PM +0100, Chris Wilson wrote:
> Since this is handling user provided bpp and depth, we need to sanity
> check and propagate the EINVAL back rather than assume what the insane
> client intended and fill the logs with DRM_ERROR.
>
> Signed-off-by: Chris Wilson
> Cc:
https://bugs.freedesktop.org/show_bug.cgi?id=107781
--- Comment #8 from Alex Findler ---
med@sorceress:~ 0> uname -av
Linux sorceress 4.18.5med+ #1 SMP Tue Sep 4 17:42:26 CEST 2018 x86_64 x86_64
x86_64 GNU/Linux
So far, so good. I booted with these kernel options:
On Tue, 4 Sep 2018 at 03:00, Thomas Hellstrom wrote:
>
> On 09/03/2018 06:33 PM, Daniel Vetter wrote:
> > On Mon, Sep 03, 2018 at 11:16:29AM +0200, Thomas Hellstrom wrote:
> >> On 08/31/2018 05:30 PM, Thomas Hellstrom wrote:
> >>> On 08/31/2018 05:27 PM, Emil Velikov wrote:
> On 31 August
On 2018-08-31 09:08, Sean Paul wrote:
On Tue, Aug 28, 2018 at 05:40:01PM -0700, Jeykumar Sankaran wrote:
Strip down the support for topology enums. It
can be replaced with simple hw count checks.
Changes in v4:
...
Signed-off-by: Jeykumar Sankaran
---
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--- Comment #39 from djip.per...@free.fr ---
test last patch with kernel 4.18.5...
It works...
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=105880
--- Comment #40 from djip.per...@free.fr ---
Created attachment 141452
--> https://bugs.freedesktop.org/attachment.cgi?id=141452=edit
dmesg from kernel 4.18.5 with patch 141163
on AMD Kabini A6-1450...
--
You are receiving this mail
On Mon, Sep 03, 2018 at 06:54:31PM +0200, Daniel Vetter wrote:
> This leaves all the commit/check and state handling in drm_atomic.c,
> while pulling all the uapi glue and the huge ioctl itself into a
> seprate file.
>
> This seems to almost perfectly split the rather big drm_atomic.c file
> into
On 2018-08-31 07:56, Sean Paul wrote:
On Tue, Aug 28, 2018 at 05:39:59PM -0700, Jeykumar Sankaran wrote:
Prep changes for state based resource management.
Moves all the hw block tracking for the crtc to the state
object.
Changes in v4...
Signed-off-by: Jeykumar Sankaran
---
On 4 September 2018 at 13:19, Daniel Vetter wrote:
> On Mon, Sep 03, 2018 at 06:38:44PM +0100, Emil Velikov wrote:
>> On 3 September 2018 at 17:54, Daniel Vetter wrote:
>>
>> > -Hide legacy cruft better
>> > -
>> > -
>> > -Way back DRM supported only drivers which
"crtc->helper_private" is not initialized by the QXL driver and thus the
"crtc_funcs->disable" call would crash (resulting in suspend failure).
Fix this by converting the suspend/resume functions to use the
drm_mode_config_helper_* helpers.
Tested system sleep with QEMU 3.0 using "echo mem >
On Tue, Sep 4, 2018 at 3:12 PM, Christian König
wrote:
> Am 04.09.2018 um 15:03 schrieb Daniel Vetter:
>>
>> On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
>>>
>>> On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
On Tue, Sep 04, 2018 at 12:44:19PM +0200,
On Tue, Sep 4, 2018 at 3:45 PM, Thomas Hellstrom wrote:
> On 09/03/2018 06:54 PM, Daniel Vetter wrote:
>>
>> The idea behind allowing drivers to override legacy ioctls (instead of
>> using the generic implementations unconditionally) is to handle bugs
>> in old driver-specific userspace. Like
Hi Laurent,
On Tue, Sep 4, 2018 at 2:10 PM Laurent Pinchart
wrote:
> The LVDS encoders in the D3 and E3 SoCs differ significantly from those
> in the other R-Car Gen3 family members:
>
> - The LVDS PLL architecture is more complex and requires computing PLL
> parameters manually.
> - The PLL
Hi Laurent, Geert,
On Tue, Sep 04, 2018 at 04:32:32PM +0200, Geert Uytterhoeven wrote:
> On Tue, Sep 4, 2018 at 2:10 PM Laurent Pinchart
> wrote:
> > From: Takeshi Kihara
> >
> > Add device nodes for I2C ch{0,1,2,3,4,5,6,7} to R-Car E3 R8A77990 device
> > tree.
> >
> > Signed-off-by: Takeshi
Am 04.09.2018 um 14:22 schrieb Daniel Stone:
Hi,
On Tue, 4 Sep 2018 at 11:44, Christian König
wrote:
Am 04.09.2018 um 12:15 schrieb Daniel Stone:
Right. The conclusion, after people went through and started sorting
out the kinds of formats for which they would _actually_ export real
colour
On Tue, Sep 4, 2018 at 11:02 AM, Michel Dänzer wrote:
> On 2018-09-04 3:05 p.m., Ilia Mirkin wrote:
>> On Tue, Sep 4, 2018 at 4:00 AM, Michel Dänzer wrote:
>>> On 2018-09-03 7:07 p.m., Ilia Mirkin wrote:
On Mon, Sep 3, 2018 at 12:45 PM, Daniel Vetter wrote:
> On Mon, Sep 03, 2018 at
Hi Michał,
I love your patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc2 next-20180831]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Am 04.09.2018 um 14:26 schrieb Daniel Vetter:
On Tue, Sep 04, 2018 at 12:44:19PM +0200, Christian König wrote:
Am 04.09.2018 um 12:15 schrieb Daniel Stone:
Hi,
On Tue, 4 Sep 2018 at 11:05, Daniel Vetter wrote:
On Tue, Sep 4, 2018 at 3:00 AM, Bas Nieuwenhuizen
wrote:
+/* The chip this is
On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
> On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
> >
> > On Tue, Sep 04, 2018 at 12:44:19PM +0200, Christian König wrote:
> > > Am 04.09.2018 um 12:15 schrieb Daniel Stone:
> > > > Hi,
> > > >
> > > > On Tue, 4 Sep 2018 at
On Thu, Aug 30, 2018 at 01:09:37PM +0200, Heiko Stuebner wrote:
> The rk3188 has 2 vops not using iommus which only output directly
> to a rgb interface per vop. So all other output modes like hdmi
> are provided by external brige chips.
>
> Signed-off-by: Heiko Stuebner
> ---
> This depends on
On Tue, Sep 4, 2018 at 2:10 PM Laurent Pinchart
wrote:
> From: Takeshi Kihara
>
> Add device nodes for I2C ch{0,1,2,3,4,5,6,7} to R-Car E3 R8A77990 device
> tree.
>
> Signed-off-by: Takeshi Kihara
> Signed-off-by: Jacopo Mondi
My
Reviewed-by: Geert Uytterhoeven
Tested-by: Geert
On Tue, Sep 4, 2018 at 3:33 PM, Bas Nieuwenhuizen
wrote:
> On Tue, Sep 4, 2018 at 3:04 PM Daniel Vetter wrote:
>>
>> On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
>> > On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
>> > >
>> > > On Tue, Sep 04, 2018 at 12:44:19PM
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #5 from Jan Burgmeier ---
Created attachment 141447
--> https://bugs.freedesktop.org/attachment.cgi?id=141447=edit
dmesg after setting mode to auto
--
You are receiving this mail because:
You are the assignee for the
Hi Daniel,
FYI, the error/warning still remains.
tree: git://anongit.freedesktop.org/drm/drm-tip drm-tip
head: 1b18cb66428cffa748719cf900b2decac3690029
commit: 7928ca5cc786fdc0269342f1b9e22c2af939b989 [144/320] RFC: debugobjects:
capture stack traces at _init() time
config:
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.20-wip
head: 6abc0c8f8cf3e0c47707b01f027f9f9b9aa75646
commit: dd73043534515c1b8bf31f78f0e9945f5d95e0e6 [165/258] drm/amd/display:
implement DPMS DTN test v2
config: i386-randconfig-j3-201835 (attached as .config)
compiler: gcc-4.9
Am 04.09.2018 um 15:17 schrieb Daniel Vetter:
On Tue, Sep 4, 2018 at 3:12 PM, Christian König
wrote:
Am 04.09.2018 um 15:03 schrieb Daniel Vetter:
On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
On Tue, Sep 04, 2018 at
On 09/03/2018 06:54 PM, Daniel Vetter wrote:
The idea behind allowing drivers to override legacy ioctls (instead of
using the generic implementations unconditionally) is to handle bugs
in old driver-specific userspace. Like e.g. vmw_kms_set_config does,
to work around some vmwgfx userspace not
On Tue, 4 Sep 2018 13:30:30 +0200
Pavel Machek wrote:
> I'd say this is still quite valueable, and it might be worth fixing,
> rather then removing completely.
I agree. Perhaps we should have a 00-DESCRIPTION file in each
directory, and each file could start with a:
DESCRIPTION:
and then
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #3 from Jan Burgmeier ---
Created attachment 141445
--> https://bugs.freedesktop.org/attachment.cgi?id=141445=edit
xrandr output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #4 from Jan Burgmeier ---
Created attachment 141446
--> https://bugs.freedesktop.org/attachment.cgi?id=141446=edit
dmesg after setting mode to 1400x1050
--
You are receiving this mail because:
You are the assignee for the
Looks much neater on the gitlab UI, e.g. on my personal libdrm fork:
https://gitlab.freedesktop.org/danvet/drm
Signed-off-by: Daniel Vetter
---
CONTRIBUTING => CONTRIBUTING.rst | 0
README => README.rst | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename CONTRIBUTING =>
Op 04-09-18 om 15:50 schreef Ville Syrjälä:
> On Tue, Sep 04, 2018 at 02:47:51PM +0200, Maarten Lankhorst wrote:
>> Op 30-08-18 om 16:24 schreef Stanislav Lisovskiy:
>>> PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
>>> specification.
>>>
>>> v2: Edited commit message, removed
On Tue, Sep 04, 2018 at 02:47:51PM +0200, Maarten Lankhorst wrote:
> Op 30-08-18 om 16:24 schreef Stanislav Lisovskiy:
> > PLANE_CTL_FORMAT_AYUV is already supported, according to hardware
> > specification.
> >
> > v2: Edited commit message, removed redundant whitespaces.
> >
> > v3: Fixed
On Tue, Sep 04, 2018 at 03:52:51PM +0200, Maarten Lankhorst wrote:
> Op 04-09-18 om 15:50 schreef Ville Syrjälä:
> > On Tue, Sep 04, 2018 at 02:47:51PM +0200, Maarten Lankhorst wrote:
> >> Op 30-08-18 om 16:24 schreef Stanislav Lisovskiy:
> >>> PLANE_CTL_FORMAT_AYUV is already supported, according
On Tue, Sep 4, 2018 at 4:00 AM, Michel Dänzer wrote:
> On 2018-09-03 7:07 p.m., Ilia Mirkin wrote:
>> On Mon, Sep 3, 2018 at 12:45 PM, Daniel Vetter wrote:
>>> On Mon, Sep 03, 2018 at 12:57:54PM +0200, Gerd Hoffmann wrote:
Userspace on big endian machhines typically expects the ADDFB ioctl
On Tue, Sep 4, 2018 at 3:04 PM Daniel Vetter wrote:
>
> On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
> > On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
> > >
> > > On Tue, Sep 04, 2018 at 12:44:19PM +0200, Christian König wrote:
> > > > Am 04.09.2018 um 12:15 schrieb
On Tue, Sep 04, 2018 at 12:57:19PM +0100, Chris Wilson wrote:
> The ioctl arguments are under control of the user and as such we should
> resist any temptation to flood the kernel logs with their errors.
> Relegate the DRM_ERROR to a DRM_DEBUG so the user has to opt into
> hearing of their own
On Tue, Sep 04, 2018 at 09:45:05AM +0530, Souptick Joarder wrote:
> We have introduce new return type vm_fault_t for
> fault handler. Update the document for the same.
>
> Signed-off-by: Souptick Joarder
> ---
> v2: Revert spaces added in v1
Thanks, applied to drm-misc-next.
-Daniel
>
>
Am 04.09.2018 um 15:03 schrieb Daniel Vetter:
On Tue, Sep 04, 2018 at 02:33:02PM +0200, Bas Nieuwenhuizen wrote:
On Tue, Sep 4, 2018 at 2:26 PM Daniel Vetter wrote:
On Tue, Sep 04, 2018 at 12:44:19PM +0200, Christian König wrote:
Am 04.09.2018 um 12:15 schrieb Daniel Stone:
Hi,
On Tue, 4
https://bugs.freedesktop.org/show_bug.cgi?id=107823
Bug ID: 107823
Summary: [amdgpu/displayport] Blackscreen on native resolution
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #1 from Jan Burgmeier ---
Created attachment 141443
--> https://bugs.freedesktop.org/attachment.cgi?id=141443=edit
lspci -vv output
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=107823
--- Comment #2 from Jan Burgmeier ---
Created attachment 141444
--> https://bugs.freedesktop.org/attachment.cgi?id=141444=edit
/proc/cpuinfo
--
You are receiving this mail because:
You are the assignee for the
On 2018-09-04 3:05 p.m., Ilia Mirkin wrote:
> On Tue, Sep 4, 2018 at 4:00 AM, Michel Dänzer wrote:
>> On 2018-09-03 7:07 p.m., Ilia Mirkin wrote:
>>> On Mon, Sep 3, 2018 at 12:45 PM, Daniel Vetter wrote:
On Mon, Sep 03, 2018 at 12:57:54PM +0200, Gerd Hoffmann wrote:
> Userspace on big
From: Colin Ian King
Don't populate the array vsoff on the stack but instead make it
static. Makes the object code smaller by 67 bytes:
Before:
textdata bss dec hex filename
5753 112 0586516e9 .../nouveau/nvkm/subdev/bios/dp.o
After:
textdata
Hi Jernej,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on sunxi/sunxi/for-next]
[also build test WARNING on v4.19-rc2 next-20180831]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Evan,
FYI, the error/warning still remains.
tree: git://people.freedesktop.org/~agd5f/linux.git drm-next-4.20-wip
head: 6abc0c8f8cf3e0c47707b01f027f9f9b9aa75646
commit: d617d4d73043bc4cbc316a7a1b4370fa5bc26a31 [99/258] drm/amd/powerplay:
new interfaces for overdrive vega20 sclk and mclk
The ioctl arguments are under control of the user and as such we should
resist any temptation to flood the kernel logs with their errors.
Relegate the DRM_ERROR to a DRM_DEBUG so the user has to opt into
hearing of their own mistakes. (One day we will have a small ringbuffer
attached to the task,
The R8A77990 (E3) platform has one RGB output and two LVDS outputs
connected to the DU. Add the DT nodes for the DU, LVDS encoders and
supporting VSP and FCP.
Signed-off-by: Laurent Pinchart
---
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 167 ++
1 file changed, 167
The THC63LVD1024 is restricted to a pixel clock frequency in the range
of 8 to 135 MHz. Implement the bridge .mode_valid() operation
accordingly.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/bridge/thc63lvd1024.c | 18 ++
1 file changed, 18 insertions(+)
diff --git
All Gen3 SoCs supported so far have a fixed association between DPAD0
and DU channels, which led to hardcoding that association when writing
the corresponding hardware register. The D3 and E3 will break that
mechanism as DPAD0 can be dynamically connected to either DU0 or DU1.
Make DPAD0 routing
From: Kieran Bingham
The r8a77995 D3 platform has 2 LVDS channels connected to the DU.
Signed-off-by: Kieran Bingham
[uli: moved lvds* into the soc node, added PM domains, resets]
Signed-off-by: Ulrich Hecht
Reviewed-by: Laurent Pinchart
---
arch/arm64/boot/dts/renesas/r8a77995.dtsi | 56
The LVDS encoders in the D3 and E3 SoCs differ significantly from those
in the other R-Car Gen3 family members:
- The LVDS PLL architecture is more complex and requires computing PLL
parameters manually.
- The PLL uses external clocks as inputs, which need to be retrieved
from DT.
- In
Document the E3 (r8a77990) SoC in the R-Car DU bindings.
Signed-off-by: Laurent Pinchart
---
Documentation/devicetree/bindings/display/renesas,du.txt | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/devicetree/bindings/display/renesas,du.txt
The rcar_du_crtc_get() function is always immediately followed by a call
to rcar_du_crtc_setup(). Call the later from the former to simplify the
code, and add a comment to explain how the get and put calls are
balanced.
Signed-off-by: Laurent Pinchart
---
drivers/gpu/drm/rcar-du/rcar_du_crtc.c
From: Ulrich Hecht
Adds LVDS decoder, HDMI encoder and connector for the Draak board.
The LVDS0 and LVDS1 encoders can use the DU_DOTCLKIN0, DU_DOTCLKIN1 and
EXTAL externals clocks. Two of them are provided to the SoC on the Draak
board, hook them up in DT.
Signed-off-by: Ulrich Hecht
The E3 (r8a77990) supports two LVDS channels. Extend the binding to
support them.
Signed-off-by: Laurent Pinchart
---
Documentation/devicetree/bindings/display/bridge/renesas,lvds.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
On the D3 and E3 SoCs, the LVDS encoder can derive its internal pixel
clock from an externally supplied clock, either through the EXTAL pin or
through one of the DU_DOTCLKINx pins. Add corresponding clocks to the DT
bindings.
To retain backward compatibility with DT that don't specify the
On selected SoCs, the DU can use the clock output by the LVDS encoder
PLL as its input dot clock. This feature is optional, but on the D3 and
E3 SoC it is often the only way to obtain a precise dot clock frequency,
as the other available clocks (CPG-generated clock and external clock)
usually have
DSYSR is a DU channel register that also contains group fields. It is
thus written to by both the group and CRTC code, using read-update-write
sequences. As the register isn't initialized explicitly at startup time,
this can lead to invalid or otherwise unexpected values being written to
some of
The official way to stop the display is to clear the display enable
(DEN) bit in the DSYSR register, but that operates at a group level and
affects the two channels in the group. To disable channels selectively,
the driver uses TV sync mode that stops display operation on the channel
and turns
From: Ulrich Hecht
Add support for the R-Car D3 (R8A77995) and E3 (R8A77990) SoCs to the
R-Car DU driver. The two SoCs instantiate compatible DUs, so a single
information structure is enough.
Signed-off-by: Ulrich Hecht
[Add support for R8A77990]
Signed-off-by: Laurent Pinchart
---
From: Takeshi Kihara
Add device nodes for I2C ch{0,1,2,3,4,5,6,7} to R-Car E3 R8A77990 device
tree.
Signed-off-by: Takeshi Kihara
Signed-off-by: Jacopo Mondi
---
arch/arm64/boot/dts/renesas/r8a77990.dtsi | 123 ++
1 file changed, 123 insertions(+)
diff --git
Hello everybody,
This patch series adds display support for the D3 and E3 SoCs, and in
particular the Draak and Ebisu boards.
The code is based on Ulrich's "[PROTO][PATCH 00/10] R-Car D3 LVDS/HDMI support
(with PLL)" series previously posted to the dri-devel and linux-renesas-soc
mailing lists.
Add the LVDS decoder, HDMI encoder, VGA encoder and HDMI and VGA
connectors, and wire up the display-related nodes with clocks, pinmux
and regulators.
The LVDS0 and LVDS1 encoders can use the DU_DOTCLKIN0, DU_DOTCLKIN1 and
EXTAL externals clocks. Two of them are provided to the SoC on the Ebisu
On Mon, Sep 03, 2018 at 06:38:44PM +0100, Emil Velikov wrote:
> On 3 September 2018 at 17:54, Daniel Vetter wrote:
>
> > -Hide legacy cruft better
> > -
> > -
> > -Way back DRM supported only drivers which shadow-attached to PCI devices
> > with
> > -userspace or fbdev
1 - 100 of 173 matches
Mail list logo
