Re: [PATCH v2 13/23] drm/zte: Stop consulting plane->fb

On Thu, Mar 22, 2018 at 07:40:03PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > We want to get rid of plane->fb on atomic drivers. Stop looking at it. Would it be more precise to use "plane->crtc" in both subject and commit log? Other than that: Acked-by: Shawn Guo > > v2: Use old_

Re: [PATCH v4 0/8] cgroup private data and DRM/i915 integration

Quoting Matt Roper (2018-03-23 17:46:16) > On Fri, Mar 23, 2018 at 02:15:38PM +0200, Joonas Lahtinen wrote: > > Quoting Matt Roper (2018-03-17 02:08:57) > > > This is the fourth iteration of the work previously posted here: > > > (v1) > > > https://lists.freedesktop.org/archives/intel-gfx/2018-J

Re: [Intel-gfx] [RFC] splitting dri-devel to drm core and drivers lists?

On Mon, Mar 26, 2018 at 09:42:52AM +0300, Joonas Lahtinen wrote: > Quoting Daniel Vetter (2018-03-23 18:39:04) > > On Fri, Mar 23, 2018 at 06:22:46PM +0200, Jani Nikula wrote: > > > There was some discussion on the dim-tools list about splitting the > > > dri-devel list to drm core and drivers list

Re: [PATCH v4 0/5] drm/blend: Support generic plane-wide alpha

On Tue, Mar 13, 2018 at 09:54:20PM +0100, Maxime Ripard wrote: > This serie aims at enhancing the support for plane-wide alpha in the > drivers that are implementing it at the moment, by turning it into a > generic property and converting the drivers (rcar-du and atmel-hclcdc). It > also introduces

Re: [Linaro-mm-sig] [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

On Thu, Mar 22, 2018 at 10:37:55AM +0100, Christian König wrote: > Am 22.03.2018 um 08:14 schrieb Daniel Vetter: > > On Wed, Mar 21, 2018 at 10:34:05AM +0100, Christian König wrote: > > > Am 21.03.2018 um 09:18 schrieb Daniel Vetter: > > > > [SNIP] > > > For correct operation you always need to imp

Re: [Intel-gfx] [RFC] splitting dri-devel to drm core and drivers lists?

On Mon, 26 Mar 2018, Daniel Vetter wrote: > And as mentioned I think dri-drivers isn't big enough to be > sustainable on its own. It certainly is big enough to be disruptive to my inbox, and I don't seem to be alone. BR, Jani. -- Jani Nikula, Intel Open Source Technology Center ___

Re: [Linaro-mm-sig] [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

On Thu, Mar 22, 2018 at 10:58:55AM +0100, Christian König wrote: > Am 22.03.2018 um 08:18 schrieb Daniel Vetter: > > On Wed, Mar 21, 2018 at 12:54:20PM +0100, Christian König wrote: > > > Am 21.03.2018 um 09:28 schrieb Daniel Vetter: > > > > On Tue, Mar 20, 2018 at 06:47:57PM +0100, Christian König

[Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880

https://bugs.freedesktop.org/show_bug.cgi?id=99801 --- Comment #21 from Jean-Yves Avenard --- Adding some likely unhelpful info. But I've had similar (though not the same) problem since I got this screen. However, unlike most comments, I do not get two steady, mis-aligned image on each half of th

[Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880

https://bugs.freedesktop.org/show_bug.cgi?id=99801 --- Comment #22 from Jean-Yves Avenard --- Welcome to Ubuntu 17.10 (GNU/Linux 4.15.12-041512-generic x86_64) * Documentation: https://help.ubuntu.com jyavenard@jya7980ex:~$ xrandr Screen 0: minimum 320 x 200, current 7680 x 2880, maximum 163

[Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880

https://bugs.freedesktop.org/show_bug.cgi?id=99801 --- Comment #23 from Jean-Yves Avenard --- Created attachment 138353 --> https://bugs.freedesktop.org/attachment.cgi?id=138353&action=edit Screen capture, right side is continuously scrolling from right to left Using kernel 4.15.12 -- You ar

[Bug 99801] Rx480 doesn't output properly onto z27q at 5120x2880

https://bugs.freedesktop.org/show_bug.cgi?id=99801 --- Comment #24 from Jean-Yves Avenard --- $ dmesg | grep Display [ 34.895577] usb 1-1.4: Product: Display Audio [ 34.911627] input: Apple Inc. Display Audio as /devices/pci:20/:20:00.0/:21:00.0/:22:04.0/:44:00.0/:45:0

Re: [PATCH v3] drm/xen-front: Add support for Xen PV display frontend

On Fri, Mar 23, 2018 at 05:54:49PM +0200, Oleksandr Andrushchenko wrote: > > > My apologies, but I found a few more things that look strange and should > > be cleaned up. Sorry for this iterative review approach, but I think we're > > slowly getting there. > Thank you for reviewing! > > Cheers, Da

Re: [PATCH] drm: udl: Properly check framebuffer mmap offsets

On Thu, Mar 22, 2018 at 05:14:40PM -0700, Kees Cook wrote: > On Thu, Mar 22, 2018 at 2:54 AM, Daniel Vetter wrote: > > On Thu, Mar 22, 2018 at 9:03 AM, Greg Kroah-Hartman > > wrote: > >> On Thu, Mar 22, 2018 at 07:59:59AM +0100, Daniel Vetter wrote: > >>> Does anyone working on overflow-proof int

Re: [PATCH v2 4/4] drm/vc4: Restrict active CTM to one CRTC

On Sun, Mar 25, 2018 at 08:14:35PM +0200, Stefan Schake wrote: > Hey Daniel, > > On Sun, Mar 25, 2018 at 10:01 AM, Daniel Stone wrote: > > Hi Stefan, > > > > On 25 March 2018 at 02:52, Stefan Schake wrote: > >> +static int vc4_crtc_get_ctm_fifo(struct vc4_dev *vc4) > >> +{ > >> + return VC

Re: [PATCH] dma-buf: use parameter structure for dma_buf_attach

On Sun, Mar 25, 2018 at 01:34:51PM +0200, Christian König wrote: > Move the parameters into a structure to make it simpler to extend it in > follow up patches. > > This also adds the importer private as parameter so that we can directly > work with a completely filled in attachment structure. > >

Re: [Nouveau] [PATCH v2 1/2] gpu: drm/lease:: Use list_{next/prev}_entry instead of list_entry

On Sun, Mar 25, 2018 at 11:31:32PM +0530, Arushi Singhal wrote: > It's better to use list_entry instead of list_{next/prev}_entry > as it makes the code more clear to read. > This patch replace list_entry with list_{next/prev}_entry. > > Signed-off-by: Arushi Singhal Applied to drm-misc-next, th

Re: [Intel-gfx] [RFC] splitting dri-devel to drm core and drivers lists?

On Mon, Mar 26, 2018 at 10:00 AM, Jani Nikula wrote: > On Mon, 26 Mar 2018, Daniel Vetter wrote: >> And as mentioned I think dri-drivers isn't big enough to be >> sustainable on its own. > > It certainly is big enough to be disruptive to my inbox, and I don't > seem to be alone. If you want to m

[Bug 199101] AMDGPU Fury X random screen flicker on Linux kernel 4.16rc5

https://bugzilla.kernel.org/show_bug.cgi?id=199101 Thorsten Leemhuis (regressi...@leemhuis.info) changed: What|Removed |Added CC||regressi..

Re: [PATCH v6] ARM: dts: wheat: Fix ADV7513 address usage

Hi Simon, On 26/03/18 09:31, Simon Horman wrote: > On Fri, Mar 23, 2018 at 09:16:13PM +, Kieran Bingham wrote: >> Hi Simon, >> >> On 23/03/18 08:51, Simon Horman wrote: >>> On Thu, Mar 22, 2018 at 09:30:40PM +, Kieran Bingham wrote: The r8a7792 Wheat board has two ADV7513 devices shar

Re: [PATCH 4/7] ARM: dts: sun7i: Add pinmux settings for LCD0 RGB888 output.

Hi, On Sun, Mar 25, 2018 at 04:09:13PM +0200, Paul Kocialkowski wrote: > Le mercredi 21 mars 2018 à 21:03 +0100, Giulio Benetti a écrit : > > The A20 supports RGB888 with H/V sync from LCD0. Add a pinmux setting > > for the needed pins. > > > > Signed-off-by: Giulio Benetti > > --- > > arch/arm

[PATCH libdrm 3/3] xf86drm: replace stat() with access() to verify file existence

Signed-off-by: Eric Engestrom --- xf86drm.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index 5701952ae83634b47628..47a82407df82d37a59b2 100644 --- a/xf86drm.c +++ b/xf86drm.c @@ -3767,10 +3767,8 @@ int drmGetDevice2(int fd, uint32_t flags, drmDevi

[PATCH libdrm 1/3] xf86drm: replace sprintf()+strdup() with asprintf()

Signed-off-by: Eric Engestrom --- xf86drm.c | 28 ++-- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index 3a9d0ed2cc9b196ae7d1..b6e5d8cc1bb50ffe75a2 100644 --- a/xf86drm.c +++ b/xf86drm.c @@ -2823,7 +2823,7 @@ static char *drmGetMin

[PATCH libdrm 2/3] xf86drm: add buffer size safety to sprintf()

Signed-off-by: Eric Engestrom --- xf86drm.c | 6 +++--- xf86drmMode.c | 6 -- 2 files changed, 7 insertions(+), 5 deletions(-) diff --git a/xf86drm.c b/xf86drm.c index b6e5d8cc1bb50ffe75a2..5701952ae83634b47628 100644 --- a/xf86drm.c +++ b/xf86drm.c @@ -349,7 +349,7 @@ static int drmOpen

Re: [PATCH] dma-buf: use parameter structure for dma_buf_attach

Am 26.03.2018 um 10:36 schrieb Daniel Vetter: On Sun, Mar 25, 2018 at 01:34:51PM +0200, Christian König wrote: [SNIP] - attach->dev = dev; + attach->dev = info->dev; attach->dmabuf = dmabuf; + attach->priv = info->priv; The ->priv field is for the exporter, not the im

Re: [PATCH] dma-buf: use parameter structure for dma_buf_attach

Am 26.03.2018 um 10:36 schrieb Daniel Vetter: On Sun, Mar 25, 2018 at 01:34:51PM +0200, Christian König wrote: [SNIP] - attach->dev = dev; + attach->dev = info->dev; attach->dmabuf = dmabuf; + attach->priv = info->priv; The ->priv field is for the exporter, not the im

Re: [PATCH v2 4/4] drm/vc4: Restrict active CTM to one CRTC

On 26 March 2018 at 09:29, Daniel Vetter wrote: > On Sun, Mar 25, 2018 at 08:14:35PM +0200, Stefan Schake wrote: >> On Sun, Mar 25, 2018 at 10:01 AM, Daniel Stone wrote: >> > On 25 March 2018 at 02:52, Stefan Schake wrote: >> >> +static int vc4_crtc_get_ctm_fifo(struct vc4_dev *vc4) >> >> +{ >>

Re: [PATCH v3 0/7] drm/sun4i: Allwinner MIPI-DSI support

Hi, On Fri, Mar 23, 2018 at 10:36:35PM +0530, Jagan Teki wrote: > Hi Maxime, > > On Tue, Mar 6, 2018 at 7:25 PM, Maxime Ripard > wrote: > > Hi, > > > > Here is an preliminary version of the MIPI-DSI support for the Allwinner > > SoCs. > > > > This controller can be found on a number of recent S

Re: [PATCH 4/7] ARM: dts: sun7i: Add pinmux settings for LCD0 RGB888 output.

Hi, Il 26/03/2018 12:01, Maxime Ripard ha scritto: Hi, On Sun, Mar 25, 2018 at 04:09:13PM +0200, Paul Kocialkowski wrote: Le mercredi 21 mars 2018 à 21:03 +0100, Giulio Benetti a écrit : The A20 supports RGB888 with H/V sync from LCD0. Add a pinmux setting for the needed pins. Signed-off-by:

[Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch

https://bugs.freedesktop.org/show_bug.cgi?id=105747 Bug ID: 105747 Summary: TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch Product: DRI Version: DRI git Hardware: x86-64 (AMD64)

[Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch

https://bugs.freedesktop.org/show_bug.cgi?id=105747 --- Comment #1 from Nayan Deshmukh --- Created attachment 138356 --> https://bugs.freedesktop.org/attachment.cgi?id=138356&action=edit dmesg for amd-staging-drm-next -- You are receiving this mail because: You are the assignee for the bug.__

Re: [PATCH 4/7] ARM: dts: sun7i: Add pinmux settings for LCD0 RGB888 output.

On Mon, Mar 26, 2018 at 01:27:05PM +0200, Giulio Benetti wrote: > Hi, > > Il 26/03/2018 12:01, Maxime Ripard ha scritto: > > Hi, > > > > On Sun, Mar 25, 2018 at 04:09:13PM +0200, Paul Kocialkowski wrote: > > > Le mercredi 21 mars 2018 à 21:03 +0100, Giulio Benetti a écrit : > > > > The A20 suppor

Re: [PATCH v6 1/3] dt-bindings: display: bridge: Document THC63LVD1024 LVDS decoder

Hi Laurent, On Tue, Mar 20, 2018 at 02:43:33PM +0200, Laurent Pinchart wrote: > Hi Jacopo, > > (CC'ing Rob) > > Thank you for the patch. > > On Friday, 16 March 2018 17:16:37 EET Jacopo Mondi wrote: > > Document Thine THC63LVD1024 LVDS decoder device tree bindings. > > > > Signed-off-by: Jacopo Mo

[PATCH v3 13/23] drm/zte: Stop consulting plane->crtc

From: Ville Syrjälä We want to get rid of plane->crtc on atomic drivers. Stop looking at it. v2: Use old_state->crtc (Maarten) v3: s/fb/crtc/ in commit message to actually match the patch (Shawn) Cc: Shawn Guo Cc: Maarten Lankhorst Signed-off-by: Ville Syrjälä Acked-by: Shawn Guo --- drive

Re: [PATCH v2 2/2] gpu: drm: nouveau: Use list_{next/prev}_entry instead of list_entry

On Mon, Mar 26, 2018 at 4:01 AM, Arushi Singhal wrote: > It's better to use list_entry instead of list_{next/prev}_entry > as it makes the code more clear to read. > This patch replace list_entry with list_{next/prev}_entry. > > Signed-off-by: Arushi Singhal Acked-by: Ben Skeggs > --- > driver

Re: [PATCH v2 2/2] gpu: drm: nouveau: Use list_{next/prev}_entry instead of list_entry

Quoting Ben Skeggs (2018-03-26 13:34:54) > On Mon, Mar 26, 2018 at 4:01 AM, Arushi Singhal > wrote: > > It's better to use list_entry instead of list_{next/prev}_entry > > as it makes the code more clear to read. > > This patch replace list_entry with list_{next/prev}_entry. > > > > Signed-off-by:

Re: [PATCH v3] drm/xen-front: Add support for Xen PV display frontend

On 03/26/2018 11:18 AM, Daniel Vetter wrote: On Fri, Mar 23, 2018 at 05:54:49PM +0200, Oleksandr Andrushchenko wrote: My apologies, but I found a few more things that look strange and should be cleaned up. Sorry for this iterative review approach, but I think we're slowly getting there. Thank y

[Bug 104090] Reduced colors on RX580 through eDP on Asus GL702ZC laptop

https://bugs.freedesktop.org/show_bug.cgi?id=104090 --- Comment #16 from Hein-Pieter van Braam --- It appears that 4.16.0-rc7 fixed the issue on this laptop. I'll do a bit more testing but it seems on par with a system without dc now. Great stuff. -- You are receiving this mail because: You are

Re: [PATCH v2 00/11] drm/tinydrm: Support device unplug

Hi, Noralf! On 03/17/2018 04:40 PM, Noralf Trønnes wrote: Den 16.03.2018 09.03, skrev Daniel Vetter: On Fri, Sep 8, 2017 at 6:33 PM, Daniel Vetter  wrote: Hi Noralf, On Fri, Sep 08, 2017 at 05:07:19PM +0200, Noralf Trønnes wrote: This adds device unplug support to drm_fb_helper, drm_fb_cma_

[Bug 99349] Failed to build shader (translation from TGSI)

https://bugs.freedesktop.org/show_bug.cgi?id=99349 mirh changed: What|Removed |Added CC||m...@protonmail.ch --- Comment #20 from mirh ---

[Bug 105617] [CI] [CNL only] igt@* - incomplete - Build timed out (after 18 minutes). Marking the build as aborted.

https://bugs.freedesktop.org/show_bug.cgi?id=105617 --- Comment #6 from Marta Löfstedt --- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_7/fi-cnl-y3/igt@kms_frontbuffer_track...@fbcpsr-1p-primscrn-pri-indfb-draw-blt.html running: igt/kms_frontbuffer_tracking/fbcpsr-1p-primscrn-pri-indfb-draw-b

[Bug 105617] [CI] [CNL only] igt@* - incomplete - Build timed out (after 18 minutes). Marking the build as aborted.

https://bugs.freedesktop.org/show_bug.cgi?id=105617 --- Comment #7 from Marta Löfstedt --- This should help: https://patchwork.freedesktop.org/series/40646/ -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing

Re: [PATCH libdrm 1/3] xf86drm: replace sprintf()+strdup() with asprintf()

On Mon, 26 Mar 2018, Eric Engestrom wrote: > Signed-off-by: Eric Engestrom > --- > xf86drm.c | 28 ++-- > 1 file changed, 14 insertions(+), 14 deletions(-) > > diff --git a/xf86drm.c b/xf86drm.c > index 3a9d0ed2cc9b196ae7d1..b6e5d8cc1bb50ffe75a2 100644 > --- a/xf86drm.c >

Re: [PATCH libdrm 1/3] xf86drm: replace sprintf()+strdup() with asprintf()

On 26 March 2018 at 14:57, Jani Nikula wrote: > On Mon, 26 Mar 2018, Eric Engestrom wrote: >> Signed-off-by: Eric Engestrom >> --- >> xf86drm.c | 28 ++-- >> 1 file changed, 14 insertions(+), 14 deletions(-) >> >> diff --git a/xf86drm.c b/xf86drm.c >> index 3a9d0ed2cc9b1

Re: [PATCH libdrm 2/3] xf86drm: add buffer size safety to sprintf()

On 26 March 2018 at 11:26, Eric Engestrom wrote: > Signed-off-by: Eric Engestrom > --- > xf86drm.c | 6 +++--- > xf86drmMode.c | 6 -- > 2 files changed, 7 insertions(+), 5 deletions(-) > > diff --git a/xf86drm.c b/xf86drm.c > index b6e5d8cc1bb50ffe75a2..5701952ae83634b47628 100644 > ---

Re: [PATCH libdrm 3/3] xf86drm: replace stat() with access() to verify file existence

On 26 March 2018 at 11:26, Eric Engestrom wrote: > Signed-off-by: Eric Engestrom > --- > xf86drm.c | 4 +--- > 1 file changed, 1 insertion(+), 3 deletions(-) > > diff --git a/xf86drm.c b/xf86drm.c > index 5701952ae83634b47628..47a82407df82d37a59b2 100644 > --- a/xf86drm.c > +++ b/xf86drm.c > @@

Re: [PATCH v2 2/2] gpu: drm: nouveau: Use list_{next/prev}_entry instead of list_entry

On Mon, Mar 26, 2018 at 01:43:30PM +0100, Chris Wilson wrote: > Quoting Ben Skeggs (2018-03-26 13:34:54) > > On Mon, Mar 26, 2018 at 4:01 AM, Arushi Singhal > > wrote: > > > It's better to use list_entry instead of list_{next/prev}_entry > > > as it makes the code more clear to read. > > > This pa

[PATCH][next] drm/amd/pp: fix logical or'ing of garbage in result by initializing result to zero

From: Colin Ian King Currently result is not initialized, so it contains a garbage value and this is or'd with data from vega10_program_didt_config_registers() which can end up with a non-zero value when the result should be zero. Fix this by ensuring result is initialized to zero. Detected by

[Bug 105725] WARNING: CPU: 0 PID: 487 at drivers/gpu/drm/amd/amdgpu/../display /dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu]

https://bugs.freedesktop.org/show_bug.cgi?id=105725 --- Comment #1 from Harry Wentland --- I'm not sure, but I think they could be related to a hang. A couple questions: * Do you see a hang a boot, or in a different scenario? * What display are you using? * What's your distribution? * Are yo

Re: [linux-sunxi] Preferring cursor plane over overlay plane

On Mon, Mar 26, 2018 at 10:14 PM, Joonas Kylmälä wrote: > Hi DRM subsystem developers, > > I ran into this patch where overlay plane was switched to cursor plane > because there was no proper cursor plane available on the display > hardware: . Can we discuss wh

Re: [RFC] Per file OOM badness

Hi all, Am Dienstag, den 30.01.2018, 11:28 +0100 schrieb Michal Hocko: > On Tue 30-01-18 10:29:10, Michel Dänzer wrote: > > On 2018-01-24 12:50 PM, Michal Hocko wrote: > > > On Wed 24-01-18 12:23:10, Michel Dänzer wrote: > > > > On 2018-01-24 12:01 PM, Michal Hocko wrote: > > > > > On Wed 24-01-18

[Bug 105725] WARNING: CPU: 0 PID: 487 at drivers/gpu/drm/amd/amdgpu/../display /dc/gpio/gpio_base.c:64 dal_gpio_open_ex+0xc/0x30 [amdgpu]

https://bugs.freedesktop.org/show_bug.cgi?id=105725 --- Comment #2 from hjpries...@gmail.com --- Is there a guide a build the 4.15.x kernel using the drm-4.17-wip? I can try to compile/test it next weekend. The problem I have is that when I display a certain png with "imagemagick display" X11 han

Re: [linux-sunxi] Preferring cursor plane over overlay plane

On Mon, Mar 26, 2018 at 10:22:45PM +0800, Chen-Yu Tsai wrote: > On Mon, Mar 26, 2018 at 10:14 PM, Joonas Kylmälä > wrote: > > Hi DRM subsystem developers, > > > > I ran into this patch where overlay plane was switched to cursor plane > > because there was no proper cursor plane available on the d

[Bug 104037] [skl] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, action: reset using kicad

https://bugs.freedesktop.org/show_bug.cgi?id=104037 Elizabeth changed: What|Removed |Added Status|NEW |NEEDINFO Summary|[drm] GPU HANG:

Re: [PATCH] gpu: host1x: Fix compiler errors

On Mon, Mar 26, 2018 at 04:44:14PM +0200, Emil Goode wrote: > The compiler is complaining with the following errors: > > drivers/gpu/host1x/cdma.c:94:48: error: > passing argument 3 of ‘dma_alloc_wc’ from incompatible pointer type > [-Werror=incompatible-pointer-types] > > drivers/gpu

[Bug 104037] [skl] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, action: reset using kicad

https://bugs.freedesktop.org/show_bug.cgi?id=104037 Elizabeth changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop |intel-3d-bugs@lists.freedes

Re: [linux-sunxi] Preferring cursor plane over overlay plane

On Mon, Mar 26, 2018 at 10:45 PM, Maxime Ripard wrote: > On Mon, Mar 26, 2018 at 10:22:45PM +0800, Chen-Yu Tsai wrote: >> On Mon, Mar 26, 2018 at 10:14 PM, Joonas Kylmälä >> wrote: >> > Hi DRM subsystem developers, >> > >> > I ran into this patch where overlay plane was switched to cursor plane

Re: [PATCH] dma-buf: use parameter structure for dma_buf_attach

On Mon, Mar 26, 2018 at 12:47:01PM +0200, Christian König wrote: > Am 26.03.2018 um 10:36 schrieb Daniel Vetter: > > On Sun, Mar 25, 2018 at 01:34:51PM +0200, Christian König wrote: > [SNIP] > > > - attach->dev = dev; > > > + attach->dev = info->dev; > > > attach->dmabuf = dmabuf; > > > +

[PATCH] drm/scheduler: fix param documentation

Signed-off-by: Nayan Deshmukh --- drivers/gpu/drm/scheduler/gpu_scheduler.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/scheduler/gpu_scheduler.c b/drivers/gpu/drm/scheduler/gpu_scheduler.c index 0d95888ccc3e..1d368bc66ac2 100644 --- a/drivers/gpu/drm/sc

Re: [PATCH] drm/scheduler: remove incorrect param documentation

I am not removing jobs parameters as of now as it will lead to changes in all the calls to this function and will affect the etnaviv patches. Regards, Nayan. On Sun, Mar 25, 2018 at 4:59 PM, Christian König wrote: > Am 25.03.2018 um 13:21 schrieb Nayan Deshmukh: >> >> On Sun, Mar 25, 2018 at 4:4

Re: [Linaro-mm-sig] [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

On Mon, Mar 26, 2018 at 10:01:21AM +0200, Daniel Vetter wrote: > On Thu, Mar 22, 2018 at 10:58:55AM +0100, Christian König wrote: > > Am 22.03.2018 um 08:18 schrieb Daniel Vetter: > > > On Wed, Mar 21, 2018 at 12:54:20PM +0100, Christian König wrote: > > > > Am 21.03.2018 um 09:28 schrieb Daniel Ve

Re: [PATCH] drm/gem: Document that handle_create must be the last step

On Thu, Mar 22, 2018 at 10:12:03AM +0200, Oleksandr Andrushchenko wrote: > On 03/22/2018 10:02 AM, Daniel Vetter wrote: > > It published > s/It/If Doesn't make much sense to me, It = drm_gem_handle_create. > > the gem object to userspace, by that point other threads > > can guess the id and sta

[PATCH 0/6] move more drivers to gem_free_object_unlocked

Hi all, Random drive-by crusade against dev->struct_mutex usage. The only two leftover drivers still relying on gem_free_object and the magic lifetime rule that hodling dev->struct_mutex will prevent gem object destruction are msm and gma500. Both actually need this, and don't look like they can b

[PATCH 1/6] drm/tinydrm: Use gem_free_object_unlocked

tinydrm doesn't use dev->struct_mutex and therefore has no need to use gem_free_object. Signed-off-by: Daniel Vetter Cc: "Noralf Trønnes" --- drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 2 +- include/drm/tinydrm/tinydrm.h | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)

[Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch

https://bugs.freedesktop.org/show_bug.cgi?id=105747 --- Comment #2 from Alex Deucher --- Is there an actual bug you are seeing? We no longer print the ring and IB test info in the log unless you enable verbose logging to make the driver less chatty. -- You are receiving this mail because: You

Re: [PATCH DRM] drm: Remove drm_property_{un/reference}_blob aliases

On Tue, 20 Mar 2018, Haneen Mohammed wrote: > This patch remove the compatibility aliases > drm_property_{reference/unreference}_blob of > drm_property_blob_{get/put} since all callers have been converted to the > prefered _{get/put}. > > Remove the helpers from the semantic patch drm-get-put-co

[Patch v2 0/6] drm/omap: Add virtual-planes support

This patch series adds virtual-plane support to omapdrm driver to allow the use of display wider than 2048 pixels. The DT bindings are also cleaned up to remove duplication when properties are common to all implementations. This patch series depends on Peter Ujfalusi's normalized zpos patch set w

[Patch v2 3/6] dt-bindings: display/ti: Add plane binding to dispc node

Currently all available display pipelines (i.e. plane) and output port resources are exposed to user-space. In some cases it is needed to be able to restrict which resources are actually visible from user-space. Also in cases where a display wider than 2048 pixels is to be supported more than one v

[Patch v2 4/6] drm/omap: Add virtual plane DT parsing support

Virtual planes are used to extend display size capability for display larger than 2048 pixels by splitting the frame buffer equally between two physical video-pipelines. Here we are adding DT support to parse 'plane' child nodes which describe how logical planes are mapped to physical video-pipeli

[Patch v2 2/6] dt-bindings: display/ti: Move common dispc bindings to omap-dss.txt

Add common DISPC bindings into the top level bindings file. Move common bindings here instead of having multiple copies of the same information in all of the variant specific files. Signed-off-by: Benoit Parrot Reviewed-by: Rob Herring --- Documentation/devicetree/bindings/display/ti/ti,dra7-ds

[Patch v2 5/6] drm/omap: Add virtual plane support to omap_plane

Add virtual wide plane support by adding an secondary plane_id so that an "omap_plane" can be composed of up to two physical planes. When at least one 'plane' child node is present in DT then omap_plane_init will only use the plane described in DT. Some of these nodes may be a virtual wide plane i

[Patch v2 6/6] drm/omap: Allow wider display when a virtual plane is available

Add an exception case when filtering out display mode so that if a virtual wide plane is available then display wider than 2048 can be supported as long as the required timing parameters can also be met. Signed-off-by: Benoit Parrot --- drivers/gpu/drm/omapdrm/omap_connector.c | 3 ++- drivers/

[Patch v2 1/6] drm/omap: Add ability to filter out modes which can't be supported

Currently available display mode from a connector are filtered out based only on pixel clock capability. However we also need to filter out wider mode if we cannot handle them based on available pipeline capabilities. Signed-off-by: Benoit Parrot --- drivers/gpu/drm/omapdrm/dss/dispc.c | 27

Re: [PATCH v2 00/11] drm/tinydrm: Support device unplug

Den 26.03.2018 15.02, skrev Oleksandr Andrushchenko: Hi, Noralf! On 03/17/2018 04:40 PM, Noralf Trønnes wrote: Den 16.03.2018 09.03, skrev Daniel Vetter: On Fri, Sep 8, 2017 at 6:33 PM, Daniel Vetter  wrote: Hi Noralf, On Fri, Sep 08, 2017 at 05:07:19PM +0200, Noralf Trønnes wrote: This a

[Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch

https://bugs.freedesktop.org/show_bug.cgi?id=105747 --- Comment #3 from Nayan Deshmukh --- Oh..I am seeing any bug as such, I thought the ring buffers are getting initialized. How can I get the verbose output to confirm that everything is working fine? -- You are receiving this mail because: Yo

Re: [PATCH] drm/scheduler: fix param documentation

A bit more commit message would be nice to have, like "There is no more @kernel parameter and document the new @guilty parameter". Am 26.03.2018 um 17:21 schrieb Nayan Deshmukh: Signed-off-by: Nayan Deshmukh With the commit message fixed the patch is Reviewed-by: Christian König . Christi

Re: [PATCH] drm/scheduler: remove incorrect param documentation

Yeah, probably good idea to have that separate. But would still be a nice cleanup and it is merged upstream after the etnaviv patches anyway. Regards, Christian. Am 26.03.2018 um 17:29 schrieb Nayan Deshmukh: I am not removing jobs parameters as of now as it will lead to changes in all the c

[Bug 105747] TOPAZ: ring buffers not getting initialized with the amd-staging-drm-next branch

https://bugs.freedesktop.org/show_bug.cgi?id=105747 Alex Deucher changed: What|Removed |Added Resolution|--- |NOTABUG Status|NEW

[Bug 91808] trine1 misrender r600g

https://bugs.freedesktop.org/show_bug.cgi?id=91808 --- Comment #8 from i...@yahoo.com --- This bug is still present with current Mesa-18.0.0.rc5. Since the old trace is not available anymore I've made a new one(70MB): https://drive.google.com/open?id=16N0m--IKupnWvnuvu27uebBjbDHUP3C4 I used "ll

[PATCH 1/8] drm/arm/malidp: Modified the prototype of malidp_de_irq_fini

'struct drm_device' is being replaced with 'struct malidp_hw_device' as the function argument. The reason being the dependency of malidp_de_irq_fini on 'struct drm_device' needs to be removed so as to enable it to call from functions which receives 'struct malidp_hw_device' as argument. Furthermore

[PATCH 0/8] drm/arm/malidp: Enhance support for system and runtime power management on malidp.

This patch series enhances and fixes certain issues relevant to system and runtime power management on malidp. Ayan Kumar Halder (8): drm/arm/malidp: Modified the prototype of malidp_de_irq_fini drm/arm/malidp: Modified the prototype of malidp_se_irq_fini drm/arm/malidp: Split malidp_de_irq_

[PATCH 2/8] drm/arm/malidp: Modified the prototype of malidp_se_irq_fini

'struct drm_device' is being replaced with 'struct malidp_hw_device' as the function argument.The reason being the dependency of malidp_se_irq_fini on 'struct drm_device' needs to be removed so as to enable it to call from functions which receives 'struct malidp_hw_device' as argument. Furthermore,

[PATCH 7/8] drm/arm/malidp: Set the output_depth register in modeset

One needs to store the value of the OUTPUT_DEPTH that one has parsed from device tree, so that it can be restored on system resume. This value is set in the modeset function as this gets reset when the system suspends. Signed-off-by: Ayan Kumar Halder Change-Id: I361b1214cd4e5005d21eef3ca6bf39ca9

[PATCH 4/8] drm/arm/malidp: Split malidp_se_irq_init

Extract the hardware initialisation part from malidp_se_irq_init() into the malidp_se_irq_hw_init() which will be later invoked from malidpxxx_enable_memwrite() when it needs to re-enable the interrupts. Signed-off-by: Ayan Kumar Halder Change-Id: Ibb26e86b38141993539307705695e3f6a9e32caa --- dr

[PATCH 8/8] drm/arm/malidp: Added the late system pm functions

malidp_pm_suspend_late checks if the runtime status is not suspended and if so, invokes malidp_runtime_pm_suspend which disables the display engine/core interrupts and the clocks. It sets the runtime status as suspended. Subsequently, malidp_pm_resume_early will invoke malidp_runtime_pm_resume whic

[PATCH 5/8] drm/arm/malidp: Enable/disable interrupts in runtime pm

Display engine and core interrupts need to be disabled when the system invokes malidp_runtime_pm_suspend. Consequently, they need to be enabled in malidp_runtime_pm_resume. Signed-off-by: Ayan Kumar Halder Change-Id: Ib8e5e8319fdd768f8a97d9b5960fcfa8ba90eba3 --- drivers/gpu/drm/arm/malidp_drv.c

[PATCH 3/8] drm/arm/malidp: Split malidp_de_irq_init

Extract the hardware initialisation part from malidp_de_irq_init() into the malidp_de_irq_hw_init() which will be later invoked from runtime_pm_resume function when it needs to re-enable the interrupts. Change-Id: If8bdb0e246653cb7d7b7d6d63919c45b01350c10 Signed-off-by: Ayan Kumar Halder --- dri

Re: [PATCH] drm/scheduler: remove incorrect param documentation

I will send in the patches. On Mon, Mar 26, 2018 at 10:29 PM, Christian König wrote: > Yeah, probably good idea to have that separate. > > But would still be a nice cleanup and it is merged upstream after the > etnaviv patches anyway. > > Regards, > Christian. > > > Am 26.03.2018 um 17:29 schrieb

[PATCH 6/8] drm/arm/malidp: Enable/disable the scaling engine interrupts with memory writeback

Scaling engine interrupts need to be enabled/disabled as and when memwrite is enabled and disabled. The reason being scaling engine interrupts are used only by the memory writeout layer. This patch depends on: "[Patch v5,1/3] drm: mali-dp: Add support for writeback on DP550/DP650" Change-Id: Ic7

Re: [PATCH v2 2/3] drm/msm/dsi: add implementation for helper functions

Hi Jordan, Thanks for the review. On 03/20/2018 01:53 AM, Jordan Crouse wrote: On Tue, Mar 20, 2018 at 01:11:02AM +0530, Sibi S wrote: Add dsi host helper function implementation for DSI v2 DSI 6G 1.x and DSI 6G v2.0+ controllers Signed-off-by: Sibi S --- drivers/gpu/drm/msm/dsi/dsi.h

[PATCH] drm/scheduler: fix param documentation

There is no @kernel parameter anymore and document the @guilty parameter Signed-off-by: Nayan Deshmukh --- drivers/gpu/drm/scheduler/gpu_scheduler.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/scheduler/gpu_scheduler.c b/drivers/gpu/drm/scheduler/gpu_sc

[Bug 199101] AMDGPU Fury X random screen flicker on Linux kernel 4.16rc5

https://bugzilla.kernel.org/show_bug.cgi?id=199101 --- Comment #7 from Kevin McCormack (wittyma...@yahoo.com) --- It's not a problem on 4.15. It was still a problem on the last rc I tried. On March 26, 2018 4:58:42 AM EDT, bugzilla-dae...@bugzilla.kernel.org wrote: >https://bugzilla.kernel.org/sh

[Bug 99349] Failed to build shader (translation from TGSI)

https://bugs.freedesktop.org/show_bug.cgi?id=99349 --- Comment #21 from mirh --- Specific issue was reported in bug 105371. Follows there. Sorry for the bother. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel ma

Re: [PATCH] drm/scdc-helper: Convert errors into debug messages

On Sat, Mar 24, 2018 at 08:35:43AM +0530, Sharma, Shashank wrote: > Reviewed-by: Shashank Sharma Thanks. Pushed to drm-misc-next. > > Regards > Shashank > On 3/23/2018 11:55 PM, Ville Syrjala wrote: > > From: Ville Syrjälä > > > > Since we may attempt to reconfigure SCDC when the sink has alre

[PATCH] drm/syncobj: Stop reusing the same struct file for all syncobj -> fd

From: Chris Wilson The vk cts test: dEQP-VK.api.external.semaphore.opaque_fd.export_multiple_times_temporary triggers a lot of VFS: Close: file count is 0 Dave pointed out that clearing the syncobj->file from drm_syncobj_file_release() was sufficient to silence the test, but that opens a can of

Re: [RFC PATCH 2/3] drm: bridge: panel: allow override of the bus format

Hi Peter, (CC'ing Jacopo Mondi) On Sunday, 25 March 2018 15:01:11 EEST Peter Rosin wrote: > On 2018-03-20 14:56, Laurent Pinchart wrote: > > Hi Peter, > > > > Thank you for the patch. > > > > On Sunday, 18 March 2018 00:15:24 EET Peter Rosin wrote: > >> Useful if the bridge does some kind of co

[PATCH 1/1] drm: add parameter explanation for some gem dmabuf_ops

To reduce some warnings. Signed-off-by: Samuel Li --- drivers/gpu/drm/drm_prime.c | 13 + 1 file changed, 13 insertions(+) diff --git a/drivers/gpu/drm/drm_prime.c b/drivers/gpu/drm/drm_prime.c index 7856a9b..caf675e 100644 --- a/drivers/gpu/drm/drm_prime.c +++ b/drivers/gpu/drm/drm

Re: [PATCH 02/23] drm/atomic-helper: Make drm_atomic_helper_disable_all() update the plane->fb pointers

On Thu, Mar 22, 2018 at 05:22:52PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > drm_atomic_helper_shutdown() needs to release the reference held by > plane->fb, so we want to use drm_atomic_clean_old_fb() in > drm_atomic_helper_disable_all(). However during suspend/resume, gpu > reset an

Re: [Intel-gfx] [PATCH 03/23] drm: Clear crtc->primary->crtc when disabling the crtc via setcrtc()

On Thu, Mar 22, 2018 at 05:22:53PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > Keep the primary->crtc in sync with the state->crtc (also with > primary->fb and state->fb) when disabling the crtc (and thus also > the primary) via setcrtc(). > > Signed-off-by: Ville Syrjälä Yeah seems

Re: [Intel-gfx] [PATCH 04/23] drm/atomic-helper: WARN if legacy plane fb pointers are bogus when committing duplicated state

On Thu, Mar 22, 2018 at 05:22:54PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > drm_atomic_helper_commit_duplicated_state() should only be called > resume/reset/load_detect paths where plane->old_fb should always be > NULL and plane->fb should be equal to the new_plane_state->fb. > Asser

Re: [PATCH 02/23] drm/atomic-helper: Make drm_atomic_helper_disable_all() update the plane->fb pointers

On Thu, Mar 22, 2018 at 05:22:52PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > drm_atomic_helper_shutdown() needs to release the reference held by > plane->fb, so we want to use drm_atomic_clean_old_fb() in > drm_atomic_helper_disable_all(). However during suspend/resume, gpu > reset an

  1   2   >