[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 --- Comment #19 from ArneJ (kernelbug5...@arnej.de) --- (In reply to Dmitri Seletski from comment #16) > (In reply to Shmerl from comment #14) > > Looks like the same issue with Pathfinder: Kingmaker: > > https://bugs.freedesktop.org/show_bug.cgi?

[PATCH v5 21/24] mm/gup_benchmark: use proper FOLL_WRITE flags instead of hard-coding "1"

Fix the gup benchmark flags to use the symbolic FOLL_WRITE, instead of a hard-coded "1" value. Also, clean up the filtering of gup flags a little, by just doing it once before issuing any of the get_user_pages*() calls. This makes it harder to overlook, instead of having little "gup_flags & 1" phr

[PATCH v5 23/24] selftests/vm: run_vmtests: invoke gup_benchmark with basic FOLL_PIN coverage

It's good to have basic unit test coverage of the new FOLL_PIN behavior. Fortunately, the gup_benchmark unit test is extremely fast (a few milliseconds), so adding it the the run_vmtests suite is going to cause no noticeable change in running time. So, add two new invocations to run_vmtests: 1) R

[PATCH v5 05/24] mm: devmap: refactor 1-based refcounting for ZONE_DEVICE pages

An upcoming patch changes and complicates the refcounting and especially the "put page" aspects of it. In order to keep everything clean, refactor the devmap page release routines: * Rename put_devmap_managed_page() to page_is_devmap_managed(), and limit the functionality to "read only": return

[PATCH v5 07/24] IB/umem: use get_user_pages_fast() to pin DMA pages

And get rid of the mmap_sem calls, as part of that. Note that get_user_pages_fast() will, if necessary, fall back to __gup_longterm_unlocked(), which takes the mmap_sem as needed. Reviewed-by: Jason Gunthorpe Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- drivers/infiniband/core/umem.c

[PATCH v5 24/24] mm, tree-wide: rename put_user_page*() to unpin_user_page*()

In order to provide a clearer, more symmetric API for pinning and unpinning DMA pages. This way, pin_user_pages*() calls match up with unpin_user_pages*() calls, and the API is a lot closer to being self-explanatory. Signed-off-by: John Hubbard --- Documentation/core-api/pin_user_pages.rst |

[PATCH v5 02/24] mm/gup: factor out duplicate code from four routines

There are four locations in gup.c that have a fair amount of code duplication. This means that changing one requires making the same changes in four places, not to mention reading the same code four times, and wondering if there are subtle differences. Factor out the common code into static functi

[PATCH v5 18/24] media/v4l2-core: pin_user_pages (FOLL_PIN) and put_user_page() conversion

1. Change v4l2 from get_user_pages() to pin_user_pages(). 2. Because all FOLL_PIN-acquired pages must be released via put_user_page(), also convert the put_page() call over to put_user_pages_dirty_lock(). Acked-by: Hans Verkuil Cc: Ira Weiny Signed-off-by: John Hubbard --- drivers/media/v4l2-

[PATCH v5 14/24] drm/via: set FOLL_PIN via pin_user_pages_fast()

Convert drm/via to use the new pin_user_pages_fast() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages, and therefore for any code that calls put_user_page(). In partial anticipation of this work, the drm/via driver was already calling put_

[PATCH v5 10/24] mm/gup: introduce pin_user_pages*() and FOLL_PIN

Introduce pin_user_pages*() variations of get_user_pages*() calls, and also pin_longterm_pages*() variations. For now, these are placeholder calls, until the various call sites are converted to use the correct get_user_pages*() or pin_user_pages*() API. These variants will eventually all set FOLL

[PATCH v5 20/24] powerpc: book3s64: convert to pin_user_pages() and put_user_page()

1. Convert from get_user_pages() to pin_user_pages(). 2. As required by pin_user_pages(), release these pages via put_user_page(). In this case, do so via put_user_pages_dirty_lock(). That has the side effect of calling set_page_dirty_lock(), instead of set_page_dirty(). This is probably more acc

[PATCH v5 22/24] mm/gup_benchmark: support pin_user_pages() and related calls

Up until now, gup_benchmark supported testing of the following kernel functions: * get_user_pages(): via the '-U' command line option * get_user_pages_longterm(): via the '-L' command line option * get_user_pages_fast(): as the default (no options required) Add test coverage for the new correspon

[PATCH v5 01/24] mm/gup: pass flags arg to __gup_device_* functions

A subsequent patch requires access to gup flags, so pass the flags argument through to the __gup_device_* functions. Also placate checkpatch.pl by shortening a nearby line. Reviewed-by: Jan Kara Reviewed-by: Jérôme Glisse Reviewed-by: Ira Weiny Cc: Kirill A. Shutemov Signed-off-by: John Hubba

[PATCH v5 17/24] mm/gup: track FOLL_PIN pages

Add tracking of pages that were pinned via FOLL_PIN. As mentioned in the FOLL_PIN documentation, callers who effectively set FOLL_PIN are required to ultimately free such pages via put_user_page(). The effect is similar to FOLL_GET, and may be thought of as "FOLL_GET for DIO and/or RDMA use". Pag

[PATCH v5 19/24] vfio, mm: pin_user_pages (FOLL_PIN) and put_user_page() conversion

1. Change vfio from get_user_pages_remote(), to pin_user_pages_remote(). 2. Because all FOLL_PIN-acquired pages must be released via put_user_page(), also convert the put_page() call over to put_user_pages_dirty_lock(). Note that this effectively changes the code's behavior in vfio_iommu_type1.c:

[PATCH v5 08/24] media/v4l2-core: set pages dirty upon releasing DMA buffers

After DMA is complete, and the device and CPU caches are synchronized, it's still required to mark the CPU pages as dirty, if the data was coming from the device. However, this driver was just issuing a bare put_page() call, without any set_page_dirty*() call. Fix the problem, by calling set_page_

[PATCH v5 06/24] goldish_pipe: rename local pin_user_pages() routine

1. Avoid naming conflicts: rename local static function from "pin_user_pages()" to "pin_goldfish_pages()". An upcoming patch will introduce a global pin_user_pages() function. Reviewed-by: Jérôme Glisse Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- drivers/platform/goldfish/goldfish_

[PATCH v5 11/24] goldish_pipe: convert to pin_user_pages() and put_user_page()

1. Call the new global pin_user_pages_fast(), from pin_goldfish_pages(). 2. As required by pin_user_pages(), release these pages via put_user_page(). In this case, do so via put_user_pages_dirty_lock(). That has the side effect of calling set_page_dirty_lock(), instead of set_page_dirty(). This i

[PATCH v5 16/24] net/xdp: set FOLL_PIN via pin_user_pages()

Convert net/xdp to use the new pin_longterm_pages() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages. In partial anticipation of this work, the net/xdp code was already calling put_user_page() instead of put_page(). Therefore, in order to

[PATCH v5 04/24] mm: Cleanup __put_devmap_managed_page() vs ->page_free()

From: Dan Williams After the removal of the device-public infrastructure there are only 2 ->page_free() call backs in the kernel. One of those is a device-private callback in the nouveau driver, the other is a generic wakeup needed in the DAX case. In the hopes that all ->page_free() callbacks ca

[PATCH v5 12/24] IB/{core, hw, umem}: set FOLL_PIN via pin_user_pages*(), fix up ODP

Convert infiniband to use the new pin_user_pages*() calls. Also, revert earlier changes to Infiniband ODP that had it using put_user_page(). ODP is "Case 3" in Documentation/core-api/pin_user_pages.rst, which is to say, normal get_user_pages() and put_page() is the API to use there. The new pin_u

[PATCH v5 00/24] mm/gup: track dma-pinned pages: FOLL_PIN

Hi, Please note that two of these patches are also out for review separately, and may go in earlier than this series. This series requires those, so to ease review and testing, they are also included here: patches 4 and 5, the devmap cleanups. There is a git repo and branch, for convenience:

[PATCH v5 09/24] vfio, mm: fix get_user_pages_remote() and FOLL_LONGTERM

As it says in the updated comment in gup.c: current FOLL_LONGTERM behavior is incompatible with FAULT_FLAG_ALLOW_RETRY because of the FS DAX check requirement on vmas. However, the corresponding restriction in get_user_pages_remote() was slightly stricter than is actually required: it forbade all

[PATCH v5 15/24] fs/io_uring: set FOLL_PIN via pin_user_pages()

Convert fs/io_uring to use the new pin_user_pages() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages, and therefore for any code that calls put_user_page(). In partial anticipation of this work, the io_uring code was already calling put_us

[PATCH v5 13/24] mm/process_vm_access: set FOLL_PIN via pin_user_pages_remote()

Convert process_vm_access to use the new pin_user_pages_remote() call, which sets FOLL_PIN. Setting FOLL_PIN is now required for code that requires tracking of pinned pages. Also, release the pages via put_user_page*(). Also, rename "pages" to "pinned_pages", as this makes for easier reading of p

[PATCH v5 03/24] mm/gup: move try_get_compound_head() to top, fix minor issues

An upcoming patch uses try_get_compound_head() more widely, so move it to the top of gup.c. Also fix a tiny spelling error and a checkpatch.pl warning. Reviewed-by: Jan Kara Reviewed-by: Ira Weiny Signed-off-by: John Hubbard --- mm/gup.c | 29 +++-- 1 file changed, 15

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #10 from Timo Aaltonen --- maybe try drm-tip mainline build to see if it's any better? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #9 from Peter D. --- All three ports work. If my computer boots to a blank screen, plugging in a second monitor "resets" the video and both screens display the desktop as clones. There are two monitors; a slow one with a maximu

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #8 from Peter D. --- Hi, I'm the Peter D. who raised the Ubuntu bug report - writing from a different email address. I can probably bisect the kernel with a little gentle instruction. Initial results are; Raven ridge APU, VGA po

[PATCH 1/1] drm/radeon drm/amdgpu: fix bad DMA from INTERRUPT_CNTL2

The INTERRUPT_CNTL2 register expects a valid DMA address, but is currently set with a GPU MC address. This can cause problems on systems that detect the resulting DMA read from an invalid address (found on a Power8 guest). Instead, use the DMA address of the dummy page because it will always be s

[git pull] drm fixes for 5.4-rc8

Hey Linus, Assuming an rc8 might happen, anyways here is this weeks non-intel hw vuln fixes pull. 3 drivers, all small fixes. Thanks, Dave. drm-fixes-2019-11-15: drm fixes for 5.4-rc8 i915: - MOCS table fixes for EHL and TGL - Update Display's rawclock on resume - GVT's dmabuf reference drop fi

[Bug 112266] [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error

https://bugs.freedesktop.org/show_bug.cgi?id=112266 --- Comment #5 from Shmerl --- Just tested it, and can confirm, that reverting that commit indeed prevents the hang in Pathfinder: Kingmaker! -- You are receiving this mail because: You are the assignee for the bug.

[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 --- Comment #18 from Shmerl (shtetl...@gmail.com) --- I can confirm, that reverting that commit indeed prevents the hang in Pathfinder: Kingmaker! -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 --- Comment #17 from Shmerl (shtetl...@gmail.com) --- (In reply to Dmitri Seletski from comment #16) > (In reply to Shmerl from comment #14) > > Looks like the same issue with Pathfinder: Kingmaker: > > https://bugs.freedesktop.org/show_bug.cgi?id

Re: [PATCH v3 1/6] drm/komeda: Add side by side assembling

Hi James, On Thursday, 14 November 2019 08:37:24 GMT james qian wang (Arm Technology China) wrote: > Komeda HW can support side by side, which splits the internal display > processing to two single halves (LEFT/RIGHT) and handle them by two > pipelines separately. > komeda "side by side" is enabl

Re: [PATCH] drm/komeda: Clean warnings: candidate for 'gnu_printf’ format attribute

On Thursday, 14 November 2019 10:04:37 GMT james qian wang (Arm Technology China) wrote: > komeda/komeda_event.c: In function ‘komeda_sprintf’: > komeda/komeda_event.c:31:2: warning: function ‘komeda_sprintf’ might be a > candidate for ‘gnu_printf’ format attribute [-Wsuggest-attribute=format] >

Re: [PATCH v3 2/6] drm/komeda: Add side by side plane_state split

On Thursday, 14 November 2019 08:37:31 GMT james qian wang (Arm Technology China) wrote: > On side by side mode, The full display frame will be split into two parts > (Left/Right), and each part will be handled by a single pipeline separately > master pipeline for left part, slave for right. > >

Re: [PATCH] drm/msm/dpu: ignore NULL clocks

On Thu, Nov 14, 2019 at 7:54 PM Rob Clark wrote: > From: Rob Clark > > This isn't an error. Also the clk APIs handle the NULL case, so we can > just delete the check. > > Signed-off-by: Rob Clark > Tested-by: Matthias Kaehlcke Reviewed-by: Linus Walleij Yours, Linus Walleij ___

Re: [PATCH RFC 1/1] drm/radeon: fix bad DMA from INTERRUPT_CNTL2

On Thu, Nov 14, 2019 at 6:08 PM Sam Bobroff wrote: > > On Thu, Nov 14, 2019 at 12:05:19AM -0500, Alex Deucher wrote: > > On Wed, Nov 13, 2019 at 9:53 PM Sam Bobroff wrote: > > > > > > Currently, binding the radeon driver to a Radeon FirePro (PCI > > > 1002:68f2) that has been passed through to a

Re: [PATCH RFC 1/1] drm/radeon: fix bad DMA from INTERRUPT_CNTL2

On Thu, Nov 14, 2019 at 12:05:19AM -0500, Alex Deucher wrote: > On Wed, Nov 13, 2019 at 9:53 PM Sam Bobroff wrote: > > > > Currently, binding the radeon driver to a Radeon FirePro (PCI > > 1002:68f2) that has been passed through to a guest on a Power8 machine > > causes a bad DMA read which causes

[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 --- Comment #15 from Dmitri Seletski (drj...@gmail.com) --- (In reply to ArneJ from comment #13) > I had a similar issue with Borderlands 2: > https://gitlab.freedesktop.org/mesa/mesa/issues/2004 > > > After I reverted the patch mentioned in co

[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 --- Comment #16 from Dmitri Seletski (drj...@gmail.com) --- (In reply to Shmerl from comment #14) > Looks like the same issue with Pathfinder: Kingmaker: > https://bugs.freedesktop.org/show_bug.cgi?id=112266 in my case its with ALL games. pls tr

[pull] amdgpu drm-fixes-5.4

Hi Dave, Daniel, Just one fix for 5.4. The following changes since commit 31f4f5b495a62c9a8b15b1c3581acd5efeb9af8c: Linux 5.4-rc7 (2019-11-10 16:17:15 -0800) are available in the Git repository at: git://people.freedesktop.org/~agd5f/linux tags/drm-fixes-5.4-2019-11-14 for you to fetch ch

[Bug 205169] AMDGPU driver with Navi card hangs Xorg in fullscreen only.

https://bugzilla.kernel.org/show_bug.cgi?id=205169 Shmerl (shtetl...@gmail.com) changed: What|Removed |Added CC||shtetl...@gmail.com --- Co

Re: [PATCH] drm/amdgpu/dm: Do not throw an error for a display with no audio

On Thu, Nov 14, 2019 at 4:23 PM Harry Wentland wrote: > > On 2019-11-14 3:44 p.m., Chris Wilson wrote: > > An old display with no audio may not have an EDID with a CEA block, or > > it may simply be too old to support audio. This is not a driver error, > > so don't flag it as such. > > > > Bugzill

Re: [PATCH] drm/amdgpu/dm: Do not throw an error for a display with no audio

On 2019-11-14 3:44 p.m., Chris Wilson wrote: > An old display with no audio may not have an EDID with a CEA block, or > it may simply be too old to support audio. This is not a driver error, > so don't flag it as such. > > Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112140 > References:

[PATCH] drm/amdgpu/dm: Do not throw an error for a display with no audio

An old display with no audio may not have an EDID with a CEA block, or it may simply be too old to support audio. This is not a driver error, so don't flag it as such. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=112140 References: ae2a3495973e ("drm/amd: be quiet when no SAD block is fo

Re: [PATCH v2] drm/tegra: Turn off and reset hardware across suspend-resume

On Sun, Aug 11, 2019 at 09:39:32PM +0300, Dmitry Osipenko wrote: > The drivers core bumps runtime PM refcount during of entering into > suspend to workaround some problem where parent device may become turned > off before its children. In order to disable and reset CRTCs/HDMI/etc > hardware, the ru

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #7 from mortenkjeldga...@gmail.com --- I am using the DVI port for my monitor. I can't test the VGA port on the motherboard because I don't have a VGA cable, and my monitor is old and doesn't have an HDMI port. Sorry. -- You are rec

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #6 from Alex Deucher --- Do any of the display connectors work properly? If so which? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[Bug 205523] AMDGPU display lockup during boot with 5.4 RC on Ryzen 2700u

https://bugzilla.kernel.org/show_bug.cgi?id=205523 --- Comment #3 from briancsch...@gmail.com --- "iommu=off" seems to work, "iommu=pt" does not. -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing li

Re: [PATCH 0/4] drm/amd/display: remove some set but not used variables

On Thu, Nov 14, 2019 at 11:41 AM Harry Wentland wrote: > > On 2019-11-14 7:36 a.m., zhengbin wrote: > > zhengbin (4): > > drm/amd/display: remove set but not used variable 'old_plane_crtc' > > drm/amd/display: remove set but not used variable 'bp' in > > bios_parser2.c > > drm/amd/displa

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #5 from mortenkjeldga...@gmail.com --- Created attachment 145957 --> https://bugs.freedesktop.org/attachment.cgi?id=145957&action=edit dmesg output -- You are receiving this mail because: You are the assignee for the bug._

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #4 from Alex Deucher --- Can you get the dmesg output from when the driver is loaded? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list d

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #3 from Alex Deucher --- from your dmesg output: [1.094054] [drm:amdgpu_init [amdgpu]] *ERROR* VGACON disables amdgpu kernel modesetting. Did you enable vga console? -- You are receiving this mail because: You are the assignee

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #2 from mortenkjeldga...@gmail.com --- (In reply to Alex Deucher from comment #1) > Can you bisect? I am not a developer, just a user. All I can tell you is that the problem arises when upgrading Ubuntu from 19.04 to 19.10. -- You

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 --- Comment #1 from Alex Deucher --- Can you bisect? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.

[Bug 112288] Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs

https://bugs.freedesktop.org/show_bug.cgi?id=112288 Bug ID: 112288 Summary: Blank display on Ubuntu 19.10 on Ryzen 3 2200G and Ryzen 5 2400G APUs Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: L

Re: [PATCH v4] pci: prevent putting nvidia GPUs into lower device states on certain intel bridges

ping on the patch. I wasn't able to verify this issue on any other bridge controller, so it really might be only this one. On Thu, Oct 17, 2019 at 2:19 PM Karol Herbst wrote: > > Fixes state transitions of Nvidia Pascal GPUs from D3cold into higher device > states. > > v2: convert to pci_dev qui

[PATCH] drm/msm/dpu: ignore NULL clocks

From: Rob Clark This isn't an error. Also the clk APIs handle the NULL case, so we can just delete the check. Signed-off-by: Rob Clark Tested-by: Matthias Kaehlcke --- drivers/gpu/drm/msm/disp/dpu1/dpu_io_util.c | 26 ++--- 1 file changed, 7 insertions(+), 19 deletions(-) di

Re: [PATCH v1 1/2] drm/panel: add support for rm69299 visionox panel driver

On Thu, Nov 14, 2019 at 2:17 AM Harigovindan P wrote: > > Add support for Visionox panel driver. > > Signed-off-by: Harigovindan P > --- > drivers/gpu/drm/panel/Kconfig | 9 + > drivers/gpu/drm/panel/Makefile | 1 + > drivers/gpu/drm/panel/panel-visionox-rm69

[Bug 112266] [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error

https://bugs.freedesktop.org/show_bug.cgi?id=112266 --- Comment #4 from Shmerl --- (In reply to Pierre-Eric Pelloux-Prayer from comment #3) > - revert this kernel commit: > https://bugzilla.kernel.org/show_bug.cgi?id=205169#c10 Just for the reference: https://git.kernel.org/pub/scm/linux/kernel

Re: [PATCH v1 2/2] drm/msm: add DSI config changes to support DSI version

On Thu, Nov 14, 2019 at 2:16 AM Harigovindan P wrote: > > Add DSI config changes to support DSI version. > > Signed-off-by: Harigovindan P Reviewed-by: Rob Clark For patch 1/2 with the panel driver, probably best to split that out into a different patch(set), since panel drivers are merged int

[Bug 112266] [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error

https://bugs.freedesktop.org/show_bug.cgi?id=112266 --- Comment #3 from Pierre-Eric Pelloux-Prayer --- This bug looks similar to this one: https://bugzilla.kernel.org/show_bug.cgi?id=205169 2 possible workarounds to test: - do not run the game in fullscreen - revert this kernel commit: https://

Re: [Freedreno] [v1] msm: disp: dpu1: add support to access hw irqs regs depending on revision

On Thu, Nov 14, 2019 at 11:18:56AM +0530, Shubhashree Dhar wrote: > Current code assumes that all the irqs registers offsets can be > accessed in all the hw revisions; this is not the case for some > targets that should not access some of the irq registers. > This change adds the support to selecti

[Bug 112266] [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error

https://bugs.freedesktop.org/show_bug.cgi?id=112266 --- Comment #2 from Shmerl --- I'll give it a test, thanks. Pathfinder: Kingmaker is using in game custom cursor for the reference and it's a Unity game. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 112266] [Navi] Pathfinder: Kingmaker is causing a GPU hang: flip_done timed out error

https://bugs.freedesktop.org/show_bug.cgi?id=112266 --- Comment #1 from rLy --- I experience the same in CS:GO and Shadow of the tomb raider. What I noticed is that the crash only happens when I move the mouse. Also it's somewhat related to the mouse pointer. For example starting a CS:GO game usi

[PATCH][next] video: hyperv: hyperv_fb: fix indentation issue

From: Colin Ian King There is a block of statements that are indented too deeply, remove the extraneous tabs. Signed-off-by: Colin Ian King --- drivers/video/fbdev/hyperv_fb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/video/fbdev/hyperv_fb.c b/drivers/vide

Re: [PATCH v1 0/2] Add suppport for rm69299 Visionox panel driver and add DSI config to support DSI version

Quoting Harigovindan P (2019-11-14 02:16:26) > Current patchset adds support for rm69299 visionox panel driver used in MSM > reference platforms > and also adds DSI config that supports the respective DSI version. > > The visionox panel driver supports a resolution of 1080x2248 with 4 lanes and

[Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U

https://bugs.freedesktop.org/show_bug.cgi?id=109206 --- Comment #68 from Luya Tshimbalanga --- (In reply to Alex Deucher from comment #67) > (In reply to Luya Tshimbalanga from comment #65) > > Change the title reflecting the impact on Raven Ridge > > This is completely unrelated to your issue.

[Bug 205521] 5.3.11 update broke AMDGPU Raven Ridge

https://bugzilla.kernel.org/show_bug.cgi?id=205521 Luya Tshimbalanga (l...@fedoraproject.org) changed: What|Removed |Added URL|https://bugs.freedesktop.or |https://bugzi

Re: [PATCH 0/4] drm/amd/display: remove some set but not used variables

On 2019-11-14 7:36 a.m., zhengbin wrote: > zhengbin (4): > drm/amd/display: remove set but not used variable 'old_plane_crtc' > drm/amd/display: remove set but not used variable 'bp' in > bios_parser2.c > drm/amd/display: remove set but not used variable 'bp' in > bios_parser.c > dr

[Bug 205497] Attempt to read amd gpu id causes a freeze

https://bugzilla.kernel.org/show_bug.cgi?id=205497 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added Attachment #285883|0 |1 is obsole

Re: [PATCH 1/2 v6] drm/panel: Add DT bindings for Sony ACX424AKP

On Thu, Nov 14, 2019 at 7:15 AM Linus Walleij wrote: > > This adds device tree bindings for the Sony ACX424AKP panel. > Let's use YAML. > > Cc: devicet...@vger.kernel.org > Signed-off-by: Linus Walleij > --- > ChangeLog v5->v6: > - Fix the binding by simply not referencing the display controller

[Bug 109628] WARNING at dcn10_hw_sequencer.c:868 dcn10_verify_allow_pstate_change_high()

https://bugs.freedesktop.org/show_bug.cgi?id=109628 --- Comment #35 from peter m --- updated kernel to 5.3.11-200.fc30, problem still exists -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@

[Bug 205523] AMDGPU display lockup during boot with 5.4 RC on Ryzen 2700u

https://bugzilla.kernel.org/show_bug.cgi?id=205523 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

[drm-intel:for-linux-next 5/19] ERROR: "pm_suspend_target_state" [drivers/gpu/drm/i915/i915.ko] undefined!

tree: git://anongit.freedesktop.org/drm-intel for-linux-next head: 789c4aea3f08026360d026c0ea69b33797ac88c2 commit: a70a9e998e8e64417c1213572c1dda617e355653 [5/19] drm/i915: Defer rc6 shutdown to suspend_late config: x86_64-randconfig-d003-20191114 (attached as .config) compiler: gcc-7

[Bug 109206] Kernel 4.20 amdgpu fails to load firmware on Ryzen 2500U

https://bugs.freedesktop.org/show_bug.cgi?id=109206 Alex Deucher changed: What|Removed |Added Summary|Kernel 5.3.11 and onward|Kernel 4.20 amdgpu fails to

[Bug 109206] Kernel 5.3.11 and onward amdgpu fails to load firmware on Raven Ridge

https://bugs.freedesktop.org/show_bug.cgi?id=109206 --- Comment #67 from Alex Deucher --- (In reply to Luya Tshimbalanga from comment #65) > Change the title reflecting the impact on Raven Ridge This is completely unrelated to your issue. Please don't appropriate other bugs for unrelated issues

Re: [PULL] topic/drm-mipi-dsi-dsc-updates

On Mon, 11 Nov 2019, Jani Nikula wrote: > Hi Sean, Maarten and Maxime - > > Here's the topic branch about DSI changes as I wrote in [1]. Once you've > pulled this in drm-misc, I'll follow suit in i915. Ping. FWIW Daniel acked the approach on IRC. BR, Jani. > > > Thanks, > Jani. > > [1] http:/

RE: [Intel-gfx] [PATCH 5/5] drm/i915: Drop redundant aspec ratio prop value initialization

>-Original Message- >From: Intel-gfx On Behalf Of Ville >Syrjala >Sent: Thursday, June 20, 2019 7:57 PM >To: dri-devel@lists.freedesktop.org >Cc: intel-...@lists.freedesktop.org; Ilia Mirkin >Subject: [Intel-gfx] [PATCH 5/5] drm/i915: Drop redundant aspec ratio prop >value >initializa

Re: [PATCH] drm/ast: Fix potential NULL-pointer read during atomic mode setting

On Thu, Nov 14, 2019 at 12:45:32PM +0100, Thomas Zimmermann wrote: > When enabling the CRTC after waking up from a power-saving mode, the > primary plane's framebuffer might be NULL, which leads to a stack trace > as shown below. > > [ 632.624608] BUG: kernel NULL pointer dereference, address:

RE: drm-next + i915 CVE yolo merge

> -Original Message- > From: Daniel Vetter > Sent: Thursday, November 14, 2019 12:13 AM > To: Dave Airlie > Cc: Jani Nikula ; Bloomfield, Jon > ; Joonas Lahtinen > ; Chris Wilson ; > Stephen Rothwell ; dri-devel de...@lists.freedesktop.org>; Intel Graphics Development g...@lists.freedes

RE: [PATCH 4/5] drm/i915: Do not override mode's aspect ratio with the prop value NONE

>-Original Message- >From: dri-devel On Behalf Of Ville >Syrjala >Sent: Thursday, June 20, 2019 7:57 PM >To: dri-devel@lists.freedesktop.org >Cc: intel-...@lists.freedesktop.org >Subject: [PATCH 4/5] drm/i915: Do not override mode's aspect ratio with the >prop >value NONE > >From: Vill

[PATCH 2/5] drm/udl: Remove udl implementation of GEM's free_object()

Udl's custom implementation for struct drm_gem_object_funcs.free_object unmaps perma-mapped memory buffer before freeing the buffer object. After switching to generic fbdev emulation and fixing the damage handler, no perma-mapped buffers have to be released. Switch to SHMEM's implementation of fre

[PATCH 3/5] drm/udl: Store active framebuffer in device structure

The framebuffer's 'active_16' flag signals which framebuffer to flush to device memory. Moving the 'active_16' state from struct udl_framebuffer into struct udl_device prepares for using the generic GEM framebuffer. Signed-off-by: Thomas Zimmermann --- drivers/gpu/drm/udl/udl_drv.h | 5

[PATCH 4/5] drm/udl: Call udl_handle_damage() with DRM framebuffer

Simplifying the udl code before replacing struct udl_framebuffer. Signed-off-by: Thomas Zimmermann --- drivers/gpu/drm/udl/udl_drv.h | 2 +- drivers/gpu/drm/udl/udl_fb.c | 35 --- drivers/gpu/drm/udl/udl_modeset.c | 15 +++-- 3 files changed, 26 inse

[PATCH 1/5] drm/udl: Unmap buffer object after damage update

Udl keeps a BO mapped for its entire lifetime if it has been used in a damage update at least once. The BO's free callback release the mapping before it frees the BO. Change this behaviour to unmap immediately after the damage update, so SHMEM's implementation of free can be used. Signed-off-by:

[PATCH 5/5] drm/udl: Replace struct udl_framebuffer with generic implementation

The udl driver's struct udl_framebuffer stores a DRM framebuffer with an associated GEM object. This functionality is also provided by generic code. Switch udl over. Signed-off-by: Thomas Zimmermann --- drivers/gpu/drm/udl/udl_drv.h | 7 drivers/gpu/drm/udl/udl_fb.c | 62 -

[PATCH 0/5] drm/udl: Convert to GEM framebuffer helpers

Udl uses struct udl_framebuffer for representing its framebuffer. The type can be replaced by the standard DRM framebuffer structure. Patches 1 to 4 prepare the driver for the conversion. Patch 5 replaces the structure. The patchset has been tested by running the fb console, X11 and Weston on a D

[Bug 109206] Kernel 5.3.11 and onward amdgpu fails to load firmware on Raven Ridge

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

[Bug 205521] 5.3.11 update broke AMDGPU Raven Ridge

https://bugzilla.kernel.org/show_bug.cgi?id=205521 Alex Deucher (alexdeuc...@gmail.com) changed: What|Removed |Added CC||alexdeuc...@gmail.c

Re: [PATCH] drm/imx: parallel-display: Adjust bus_flags and bus_format handling

On 2019-11-14 14:17, Marek Vasut wrote: > The bus_flags and bus_format handling logic does not seem to cover > all potential usecases. Specifically, this seems to fail with an > "edt,etm0700g0edh6" display attached to an 24bit display interface, > with interface-pix-fmt = "rgb24" set in DT. > > In

[git pull] vmwgfx-next

Dave, Daniel Two minor cleanups / fixes for -next. The following changes since commit 3ca3a9eab7085b3c938b5d088c3020269cfecdc8: Merge tag 'drm-misc-next-fixes-2019-11-06' of git://anongit.freedesktop.org/drm/drm-misc into drm-next (2019-11-08 16:48:22 +1000) are available in the Git reposit

[PATCH 2/2 v6] drm/panel: Add driver for Sony ACX424AKP panel

The Sony ACX424AKP is a command/videomode DSI panel for mobile devices. It is used on the ST-Ericsson HREF520 reference design. We support video mode by default, but it is possible to switch the panel into command mode by using the bool property "dsi-command-mode". Cc: Stephan Gerhold Signed-off-

[PATCH 1/2 v6] drm/panel: Add DT bindings for Sony ACX424AKP

This adds device tree bindings for the Sony ACX424AKP panel. Let's use YAML. Cc: devicet...@vger.kernel.org Signed-off-by: Linus Walleij --- ChangeLog v5->v6: - Fix the binding by simply not referencing the display controller bindings from a panel binding. ChangeLog v4->v5: - Fix up all warning

[PATCH v5 2/3] drm/fb-helper: Remove drm_fb_helper_unlink_fbi()

There are no callers of drm_fb_helper_unlink_fbi() left. Remove the function. Signed-off-by: Thomas Zimmermann Reviewed-by: Noralf Trønnes --- drivers/gpu/drm/drm_fb_helper.c | 16 +--- include/drm/drm_fb_helper.h | 6 -- 2 files changed, 1 insertion(+), 21 deletions(-) di

[PATCH v5 1/3] drm/udl: Replace fbdev code with generic emulation

The udl driver can use the generic fbdev implementation. Convert it. v5: * initialize console after registering device v4: * hardcode console bpp to 16 v3: * remove module parameter fb_bpp in favor of fbdev's video * call drm_fbdev_generic_setup() directly; remove u

[PATCH v5 0/3] drm/udl: Replace fbdev by generic emulation

The udl driver can use the generic fbdev emulation. After conversion, a number of cleanups can be applied. The fbdev conversion is in patch 1. As udl was the only remaining external user of unlink_framebuffer(), that function now becomes an internal interface of the fbdev code (Patches 2 + 3). Th

[PATCH v5 3/3] fbdev: Unexport unlink_framebuffer()

There are no external callers of unlink_framebuffer() left. Make the function an internal interface. Signed-off-by: Thomas Zimmermann Reviewed-by: Noralf Trønnes --- drivers/video/fbdev/core/fbmem.c | 3 +-- include/linux/fb.h | 1 - 2 files changed, 1 insertion(+), 3 deletions(-)

  1   2   >