[radeon-alex:amd-mainline-hybrid-4.12 1596/2092] drivers/gpu/drm/amd/amdkfd/kfd_pm4_headers_ai.h:517:80: sparse: dubious one-bit signed bitfield

tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-hybrid-4.12 head: 0439a4b45dfef1c775f45f29831bfbcee37a582f commit: 86a60e76532a64856c762cd98ee612a6cadf3fd2 [1596/2092] Change fence references to dma_fence reproduce: # apt-get install sparse git checkout

Re: [PATCH v4 3/3] ARM: dts: exynos: Remove the display-timing and delay from rinato dts

Hi Krzysztof, The driver has been merged into exynos-drm-misc. Could you please check this patch(3/3). Best regards, Hoegeun On 07/13/2017 11:20 AM, Hoegeun Kwon wrote: The display-timing and delay are included in the panel driver. So it should be removed in dts. Signed-off-by: Hoegeun Kwon

[GIT PULL] drm-hisilicon-next

Hi Dave, One fix for next. Sorry for late pull request. If it can't catch this round, will resend on next round. Best, Xinliang The following changes since commit 7846b12fe0b5feab5446d892f41b5140c1419109: Merge branch 'drm-vmwgfx-next' of git://people.freedesktop.org/~syeh/repos_linux into

[Bug 99195] Random GPU lockup on Fedora 25 Wayland & X sessions with Mobility Radeon HD 5650/5750 Opensource drivers

https://bugs.freedesktop.org/show_bug.cgi?id=99195 --- Comment #13 from Michel Dänzer --- (In reply to johnrory.odwyer from comment #12) > Often when I turn back on the system it just goes straight away to a black > screen. It doesn't even go the the Dell boot menu that gives

[radeon-alex:amd-mainline-hybrid-4.12 1229/2092] drivers/gpu/drm/radeon/radeon_kfd.c:1431:2: note: in expansion of macro 'pr_debug'

tree: git://people.freedesktop.org/~agd5f/linux.git amd-mainline-hybrid-4.12 head: 0439a4b45dfef1c775f45f29831bfbcee37a582f commit: d35e5029162c64ba73eb0ae70366f1df9a6eb5eb [1229/2092] radeon_kfd.c copied config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0

RE: [PATCH v3 04/22] drm/arc: Use drm_gem_fb_create()

Hi Noralf, > -Original Message- > From: Noralf Trønnes [mailto:nor...@tronnes.org] > Sent: Sunday, August 13, 2017 4:32 PM > To: dri-devel@lists.freedesktop.org > Cc: daniel.vet...@ffwll.ch; alexey.brod...@synopsys.com; > alison.w...@freescale.com; benjamin.gaign...@linaro.org; >

Re: DRM Format Modifiers in v4l2

Le jeudi 24 août 2017 à 13:26 +0100, Brian Starkey a écrit : > > What I mean was: an application can use the modifier to give buffers from > > one device to another without needing to understand it. > > > > But a generic video capture application that processes the video itself > > cannot be

Re: [PATCH 0/6] drm/tinydrm: Support device unplug

Hi Noralf, On Mon, Aug 28, 2017 at 07:17:42PM +0200, Noralf Trønnes wrote: > This adds device unplug support to drm_fb_helper, drm_fb_cma_helper > (fbdev) and tinydrm. > > My motivation for doing this is to make tinydrm useable with USB > devices. This discussion gave insight into the problem: >

Re: [PATCH 6/6] drm/tinydrm: Support device unplug

On Mon, Aug 28, 2017 at 07:17:48PM +0200, Noralf Trønnes wrote: > Support device unplugging to make tinydrm suitable for USB devices. > > Cc: David Lechner > Signed-off-by: Noralf Trønnes > --- > drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 69 >

Re: [PATCH 4/6] drm/tinydrm: Embed drm_device in tinydrm_device

On Mon, Aug 28, 2017 at 07:17:46PM +0200, Noralf Trønnes wrote: > Might as well embed drm_device since tinydrm_device (embeds pipe struct > and fbdev pointer) needs to stick around after driver-device unbind to > handle open fd's after device removal. > > Cc: David Lechner

Re: [PATCH 3/6] drm/fb-cma-helper: Support device unplug

On Mon, Aug 28, 2017 at 07:17:45PM +0200, Noralf Trønnes wrote: > Add drm_fbdev_cma_dev_unplug() and use the drm_fb_helper device unplug > support. Pin driver module on fb_open(). > > Cc: Laurent Pinchart > Signed-off-by: Noralf Trønnes >

Re: [PATCH 2/6] drm/fb-helper: Support device unplug

On Mon, Aug 28, 2017 at 07:17:44PM +0200, Noralf Trønnes wrote: > Support device unplug by introducing a new initialization function: > drm_fb_helper_simple_init() which together with > drm_fb_helper_dev_unplug() and drm_fb_helper_fb_destroy() handles open > fbdev fd's after device unplug. There's

[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

https://bugs.freedesktop.org/show_bug.cgi?id=101483 --- Comment #7 from FFAB --- Created attachment 133857 --> https://bugs.freedesktop.org/attachment.cgi?id=133857=edit kernel 4.13-rc7 kernel parameter iommu=soft -- You are receiving this mail because: You are the assignee

Re: [PATCH 1/6] drm/fb-helper: Avoid NULL ptr dereference in fb_set_suspend()

On Mon, Aug 28, 2017 at 07:17:43PM +0200, Noralf Trønnes wrote: > drm_fb_helper_resume_worker() uses fb_helper->fbdev to call > fb_set_suspend() which dereferences the pointer. > Move sync-canceling of the resume worker in drm_fb_helper_fini() before > setting fb_helper->fbdev to NULL. > >

[Bug 101483] A10-8780P (Carrizo) + R7 M260/M265 does not boot without any "workaround" parameter.

https://bugs.freedesktop.org/show_bug.cgi?id=101483 --- Comment #6 from FFAB --- Created attachment 133856 --> https://bugs.freedesktop.org/attachment.cgi?id=133856=edit no workaround parameter Upstream kernel test - kernel 4.13-rc7 Installation, on which upstream kernel was

[PULL] drm-misc-next-fixes

Hi Dave, Only one change in -misc-next-fixes as well. Simply a rename to use consistent types across ioctl structs. drm-misc-next-fixes-2017-08-28: UAPI Changes: - Rename u32 to __u32 in struct drm_format_modifier_blob (Lionel) Cc: Lionel Landwerlin Cheers, Sean

[PULL] drm-misc-fixes

Hi Dave, Apologies for the late pull req. This is a regression fix to a patch committed in Feb which prevents writes to an incorrect register. Andrzej: once this lands in Linus' tree, please send it over to stable@ so they can add it to the stable releases of the affected trees.

[PATCH 1/2] drm/syncobj: Add a reset ioctl (v3)

This just resets the dma_fence to NULL so it looks like it's never been signaled. This will be useful once we add the new wait API for allowing wait on "submit and signal" behavior. v2: - Take an array of sync objects (Dave Airlie) v3: - Throw -EINVAL if pad != 0 Signed-off-by: Jason Ekstrand

[PATCH 2/2] drm/syncobj: Add a signal ioctl (v3)

This IOCTL provides a mechanism for userspace to trigger a sync object directly. There are other ways that userspace can trigger a syncobj such as submitting a dummy batch somewhere or hanging on to a triggered sync_file and doing an import. This just provides an easy way to manually trigger the

[Git PULL] vmwgfx-next

Hi Dave, The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Merge branch 'linux-4.14' of git://github.com/skeggsb/linux into drm-next (2017-08-23 05:32:26 +1000) are available in the git repository at: git://people.freedesktop.org/~syeh/repos_linux

Re: drm_atomic_helper_shutdown() doesn't drop ref on active fb

On Mon, Aug 28, 2017 at 10:54 PM, Daniel Vetter wrote: > I don't see your code, but from the logs it sound like you're > replacing a call for this with the shutdown helper. That will ofcourse > the references the fb helper holds. You need both calls to clean up > everything in

Re: drm_atomic_helper_shutdown() doesn't drop ref on active fb

On Mon, Aug 28, 2017 at 7:25 PM, Noralf Trønnes wrote: > Hi, > > If I use drm_atomic_helper_shutdown() when there's no framebuffer > active, it works fine, but if there is, it fails to drop a reference and > drm_mode_config_cleanup() complains that there are framebuffers left.

Re: DRM Format Modifiers in v4l2

On Mon, Aug 28, 2017 at 8:07 PM, Nicolas Dufresne wrote: > Le jeudi 24 août 2017 à 13:26 +0100, Brian Starkey a écrit : >> > What I mean was: an application can use the modifier to give buffers from >> > one device to another without needing to understand it. >> > >> > But a

Re: drm: Why shmem?

On Mon, Aug 28, 2017 at 8:44 PM, Noralf Trønnes wrote: > Hi, > > Currently I'm using the cma library with tinydrm because it was so > simple to use even though I have to work around the fact that reads are > uncached. A bigger problem that I have become aware of, is that it >

Re: drm: Why shmem?

Noralf Trønnes writes: > Hi, > > Currently I'm using the cma library with tinydrm because it was so > simple to use even though I have to work around the fact that reads are > uncached. A bigger problem that I have become aware of, is that it > restricts the dma buffers it

Re: [Git PULL] vmwgfx-next

On Tue, Aug 29, 2017 at 06:35:38AM +1000, Dave Airlie wrote: > On 29 August 2017 at 06:22, Sinclair Yeh wrote: > > Hi Dave, > > > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: > > Just a reminder, -next branches need to be sent before rc6 if you

Re: [Git PULL] vmwgfx-next

On 29 August 2017 at 06:22, Sinclair Yeh wrote: > Hi Dave, > > The following changes since commit 7c0059dd832cc686bf0febefdcf8295cdd93007f: Just a reminder, -next branches need to be sent before rc6 if you want them in the next kernel. I'll take a look at this branch later

drm: Why shmem?

Hi, Currently I'm using the cma library with tinydrm because it was so simple to use even though I have to work around the fact that reads are uncached. A bigger problem that I have become aware of, is that it restricts the dma buffers it can import since they have to be continous. So I looked

[Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 --- Comment #5 from Takashi Iwai (ti...@suse.de) --- It doesn't matter what zypper says. Simply check initrd content via lsinitrd. If the target firmware file is found there, it's OK. If not, that's the problem. -- You are receiving this mail

[Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 --- Comment #4 from Walther Pelser (w.pel...@web.de) --- Correction: Taken from: var/log/zypper/history -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel

[Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 --- Comment #3 from Walther Pelser (w.pel...@web.de) --- Created attachment 258139 --> https://bugzilla.kernel.org/attachment.cgi?id=258139=edit dracut logs during kernel installation -- You are receiving this mail because: You are watching

[Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 --- Comment #2 from Walther Pelser (w.pel...@web.de) --- (In reply to Takashi Iwai from comment #1) > Did you rebuild initrd after updating kernel-firmware containing > /lib/firmware/radeon/RV710_pfb.bin? kernel-firmware was installed at Di 15

drm_atomic_helper_shutdown() doesn't drop ref on active fb

Hi, If I use drm_atomic_helper_shutdown() when there's no framebuffer active, it works fine, but if there is, it fails to drop a reference and drm_mode_config_cleanup() complains that there are framebuffers left. The difference between using drm_atomic_helper_shutdown() and not using it, is a

[PATCH 5/6] drm/tinydrm/mi0283qt: Let the display pipe handle power

It's better to leave power handling and controller init to the modesetting machinery using the simple pipe .enable and .disable callbacks. Remove the probe done message since drm_dev_register() already puts out one. Signed-off-by: Noralf Trønnes ---

[PATCH 3/6] drm/fb-cma-helper: Support device unplug

Add drm_fbdev_cma_dev_unplug() and use the drm_fb_helper device unplug support. Pin driver module on fb_open(). Cc: Laurent Pinchart Signed-off-by: Noralf Trønnes --- drivers/gpu/drm/drm_fb_cma_helper.c | 139

[PATCH 1/6] drm/fb-helper: Avoid NULL ptr dereference in fb_set_suspend()

drm_fb_helper_resume_worker() uses fb_helper->fbdev to call fb_set_suspend() which dereferences the pointer. Move sync-canceling of the resume worker in drm_fb_helper_fini() before setting fb_helper->fbdev to NULL. Signed-off-by: Noralf Trønnes ---

[PATCH 2/6] drm/fb-helper: Support device unplug

Support device unplug by introducing a new initialization function: drm_fb_helper_simple_init() which together with drm_fb_helper_dev_unplug() and drm_fb_helper_fb_destroy() handles open fbdev fd's after device unplug. There's also a drm_fb_helper_simple_fini() for drivers who's device won't be

[PATCH 6/6] drm/tinydrm: Support device unplug

Support device unplugging to make tinydrm suitable for USB devices. Cc: David Lechner Signed-off-by: Noralf Trønnes --- drivers/gpu/drm/tinydrm/core/tinydrm-core.c | 69 - drivers/gpu/drm/tinydrm/mi0283qt.c | 4 ++

[PATCH 4/6] drm/tinydrm: Embed drm_device in tinydrm_device

Might as well embed drm_device since tinydrm_device (embeds pipe struct and fbdev pointer) needs to stick around after driver-device unbind to handle open fd's after device removal. Cc: David Lechner Signed-off-by: Noralf Trønnes ---

[PATCH 0/6] drm/tinydrm: Support device unplug

This adds device unplug support to drm_fb_helper, drm_fb_cma_helper (fbdev) and tinydrm. My motivation for doing this is to make tinydrm useable with USB devices. This discussion gave insight into the problem: [PATCH v5 2/6] drm/bridge: Add a devm_ allocator for panel bridge.

[Bug 196791] load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 Takashi Iwai (ti...@suse.de) changed: What|Removed |Added CC||ti...@suse.de --- Comment

[Bug 196791] New: load for radeon/RV71O_pfd.bin failed with error -2

https://bugzilla.kernel.org/show_bug.cgi?id=196791 Bug ID: 196791 Summary: load for radeon/RV71O_pfd.bin failed with error -2 Product: Drivers Version: 2.5 Kernel Version: 4.13.rc6 f Hardware: All OS: Linux

[Bug 83023] A problem related to Radeon DPM causes a corrupted console and black X display.

https://bugs.freedesktop.org/show_bug.cgi?id=83023 --- Comment #6 from Alex Deucher --- (In reply to Pablo Estigarribia from comment #5) > I had to disable dpm on amdgpu too due to very similar bug on rx550 > https://bugs.freedesktop.org/show_bug.cgi?id=101976 Different

[Bug 99195] Random GPU lockup on Fedora 25 Wayland & X sessions with Mobility Radeon HD 5650/5750 Opensource drivers

https://bugs.freedesktop.org/show_bug.cgi?id=99195 --- Comment #12 from johnrory.odw...@gmail.com --- I have been meaning to update this bug report for a long time but I have been having difficulty getting back to a stable system with the right combination of kernel, mesa & xorg-x11-drv-ati.

[PATCH 5/10] drm/syncobj: Add a callback mechanism for replace_fence (v3)

It is useful in certain circumstances to know when the fence is replaced in a syncobj. Specifically, it may be useful to know when the fence goes from NULL to something valid. This does make syncobj_replace_fence a little more expensive because it has to take a lock but, in the common case where

Re: [PATCH] drm/syncobj: Fix the cb_list comment

Never mind this one. I'm squashing this into the relavant patch and sending a v2 of that one patch On Mon, Aug 28, 2017 at 7:33 AM, Jason Ekstrand wrote: > Signed-off-by: Jason Ekstrand > --- > include/drm/drm_syncobj.h | 2 +- > 1 file changed, 1

[PATCH] drm/syncobj: Fix the cb_list comment

Signed-off-by: Jason Ekstrand --- include/drm/drm_syncobj.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_syncobj.h b/include/drm/drm_syncobj.h index aef7c10..c00fee5 100644 --- a/include/drm/drm_syncobj.h +++

[Bug 102358] WarThunder freezes at start, with activated vsync (vblank_mode=2)

https://bugs.freedesktop.org/show_bug.cgi?id=102358 --- Comment #17 from har...@gmx.de --- @Michel, i did just now, but WarThunder freeze behavoir didn't really change. xorg.conf: Section "Device" Identifier "AMD" Driver "modesetting" EndSection DRI 3 is used per default too (X.Org X

[Bug 74203] Window corruption on dual-GPU (integrated+discrete) Radeon setup in GNOME 3.8

https://bugs.freedesktop.org/show_bug.cgi?id=74203 --- Comment #7 from Michel Dänzer --- Does this still happen with current versions of the kernel, Mesa and xf86-video-ati? -- You are receiving this mail because: You are the assignee for the

[PATCH libdrm 1/1] i915 perf framework changes for supporting DAPC

Cc: Lionel Landwerlin Signed-off-by: Sourab Gupta Signed-off-by: Sagar Arun Kamble --- include/drm/i915_drm.h | 87 ++ 1 file changed, 80 insertions(+), 7

[Bug 196789] WARNING: generic_reg_update_ex+0x112/0x180 [amdgpu on Vega 10]

https://bugzilla.kernel.org/show_bug.cgi?id=196789 --- Comment #2 from Vedran Miletić (ved...@miletic.net) --- Unfortunately, doesn't seem to be the case here. -- You are receiving this mail because: You are watching the assignee of the bug. ___

Re: [RESEND PATCH] drm/hisilicon: Ensure LDI regs are properly configured.

Hi Daniel, On 28 August 2017 at 16:51, Daniel Vetter wrote: > On Mon, Aug 28, 2017 at 04:44:30PM +0800, Xinliang Liu wrote: >> Hi, >> >> On 15 August 2017 at 22:14, Peter Griffin wrote: >> >> > This patch fixes the following soft lockup: >> > BUG:

[Bug 102423] kwin segfaults when Alt+Tabbing with windows thumbnails on AMDGPU

https://bugs.freedesktop.org/show_bug.cgi?id=102423 --- Comment #2 from leguen.yann...@gmail.com --- How can I provide such debugging symbols? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

Re: [RESEND PATCH] drm/hisilicon: Ensure LDI regs are properly configured.

On Mon, Aug 28, 2017 at 04:44:30PM +0800, Xinliang Liu wrote: > Hi, > > On 15 August 2017 at 22:14, Peter Griffin wrote: > > > This patch fixes the following soft lockup: > > BUG: soft lockup - CPU#0 stuck for 23s! [weston:307] > > > > On weston idle-timeout the IP

Re: [RESEND PATCH] drm/hisilicon: Ensure LDI regs are properly configured.

Hi, On 15 August 2017 at 22:14, Peter Griffin wrote: > This patch fixes the following soft lockup: > BUG: soft lockup - CPU#0 stuck for 23s! [weston:307] > > On weston idle-timeout the IP is powered down and reset > asserted. On weston resume we get a massive vblank

[Bug 101691] gfx corruption on windowed 3d-apps running on dGPU

https://bugs.freedesktop.org/show_bug.cgi?id=101691 --- Comment #37 from Michel Dänzer --- I wonder if it could be related to the caching attributes of the system memory pages being shared between the GPUs. AFAICT the amdgpu driver should end up treating them as

Re: [PATCH] drm/tve200: Pass NULL format_modifier to drm_simple_display_pipe_init

On Fri, Aug 25, 2017 at 01:16:12PM -0700, Rodrigo Vivi wrote: > This Fixes build on branches where we already have format-modifier. > > Reference: > https://lists.freedesktop.org/archives/dri-devel/2017-August/151044.html > Fixes: e6fc3b68558e ("drm: Plumb modifiers through plane init") tve200

Re: [PATCH v5] drm: kirin: Add mode_valid logic to avoid mode clocks we can't generate

On 23 August 2017 at 02:42, John Stultz wrote: > Currently the hikey dsi logic cannot generate accurate byte > clocks values for all pixel clock values. Thus if a mode clock > is selected that cannot match the calculated byte clock, the > device will boot with a blank

[Bug 63011] radeon: horizontal stripes when updating screen

https://bugzilla.kernel.org/show_bug.cgi?id=63011 Mikko Rapeli (mikko.rap...@iki.fi) changed: What|Removed |Added Status|NEW |RESOLVED