[PATCH 13/13] drm/amdgpu: free vm lru when vm fini

That means bo isn't per vm bo when vm fini, back to normal bo instead. Change-Id: Ida56abd0351422dd0b4a4393545c9cdb0e1a6818 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 50 +- 1 file changed, 43 insertions(+), 7 deletions(-) diff --gi

[PATCH 12/13] drm/amdgpu: transferred bo doesn't use vm lru

Change-Id: I1179a21aa3712b095fd50bed6956654e0f72e611 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 12 +++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index 537f

[PATCH 11/13] ttm: export ttm_transfered_destroy

driver will use it to check if the bo is transferred bo. Change-Id: I6a4f3bc00621f9cb3fc24b3bc9d7d7a8ac6cd629 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/ttm/ttm_bo_util.c | 3 ++- include/drm/ttm/ttm_bo_driver.h | 1 + 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers

[PATCH 10/13] drm/amdgpu: bulk move per vm bo

Change-Id: I0d5fa7e5e88568f79e836ff47f9c9132cb7d349e Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c index 5bef4ffa1c87..537f04d25535 1

[PATCH 09/13] drm/amdgpu: add bo index counter

Change-Id: Iaec4e12164124c155753fc7aea85f76fde8d1ed6 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 1 + 3 files changed, 3 insertions(+) diff --git a/drivers/gpu/dr

[PATCH 08/13] drm/amdgpu: use RB tree instead of link list

Change-Id: Iaca5cdaccbc5beeb7a37c0f703cdfc97df4ece4f Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 2 + drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c| 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 85 +++--- drivers/gpu/drm/amd/amdgpu/am

[PATCH 06/13] drm/amdgpu: add amdgpu lru implementation

Change-Id: I023d3dd314e49bc9b1649468a82ecca6043e4317 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 59 ++ 1 file changed, 59 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c b/drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c ind

[PATCH 07/13] drm/ttm: export ttm_bo_ref_bug

Change-Id: I5b5f36b4c8af422b5c9d0eaf0c2d3b4db4d9cd0b Signed-off-by: Chunming Zhou --- drivers/gpu/drm/ttm/ttm_bo.c| 3 ++- include/drm/ttm/ttm_bo_driver.h | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c index 98

[PATCH 05/13] drm/amdgpu: pass vm lru to buffer object

Change-Id: I28351ad8e69c13038ccff40fd9f0369ddae91371 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu.h| 3 ++- drivers/gpu/drm/amd/amdgpu/amdgpu_fb.c | 2 +- drivers/gpu/drm/amd/amdgpu/amdgpu_gem.c| 14 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_object.c

[PATCH 04/13] drm/amdgpu: init/fini vm lru

Change-Id: Icba45a329e2e2094581ad6c4b8b9028a2e5c5faa Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu.h| 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_device.c | 1 + drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c| 2 ++ drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 37

[PATCH 00/13] *** per vm lru ***

move implemenation from ttm to amdgpu driver. (suggested by Christian) per-vm-lru is because of per-vm-bo, which has no chance to refresh lru, the nagtive effect is game performance isn't stable. so all per-vm-bo should have a default order, every per-vm-bo has its priority, relying on its creati

[PATCH 01/13] ttm: abstruct evictable bo

Change-Id: Ie81985282fab1e564fc2948109fae2173613b465 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/ttm/ttm_bo.c | 35 --- 1 file changed, 24 insertions(+), 11 deletions(-) diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c index 98e06f8bf2

[PATCH 03/13] drm/amdgpu: add lru backend for amdgpu driver

Change-Id: I4ee2abf1ddf5c0fe59c5803da51e99bb57388d05 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 4 drivers/gpu/drm/amd/amdgpu/amdgpu_vm.c | 25 + drivers/gpu/drm/amd/amdgpu/amdgpu_vm.h | 9 + 3 files changed, 38 insertions(+

[PATCH 02/13] ttm: allow driver has own lru policy

general ttm lru cannot statisfy amdgpu per-vm-bo requirement, we have to adapt it in amdgpu driver at least. Change-Id: I92b2286ef507c2e055ad9101cf31279d5f8db475 Signed-off-by: Chunming Zhou --- drivers/gpu/drm/ttm/ttm_bo.c| 54 ++--- include/drm/ttm/ttm_b

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

On Tue, May 08, 2018 at 10:30:19PM +0300, Jani Nikula wrote: > On Wed, 09 May 2018, Feng Tang wrote: > > >> > > > On Mon, May 07, 2018 at 11:40:45AM +0100, Chris Wilson wrote: > >> >> > > > > Quoting Feng Tang (2018-05-07 11:36:09) > >> >> > > > > > To fulfil the Dell 4K monitor, the dpcd max ret

[Bug 106434] Graphical hangs, no keyboard, rest of system still active

https://bugs.freedesktop.org/show_bug.cgi?id=106434 --- Comment #5 from Koz Ross --- Yes, I do - I tried using a stock kernel, as well as a CK one which wasn't 4.17-rc3, and they all had this behaviour. -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 106447] System freeze after resuming from suspend (amdgpu)

https://bugs.freedesktop.org/show_bug.cgi?id=106447 Bug ID: 106447 Summary: System freeze after resuming from suspend (amdgpu) Product: DRI Version: XOrg git Hardware: Other OS: All Status: NEW Severity: n

[Bug 91808] trine1 misrender r600g

https://bugs.freedesktop.org/show_bug.cgi?id=91808 Dave Airlie changed: What|Removed |Added Attachment #139029|0 |1 is obsolete|

[Bug 199621] iMac 2009, Mobility Radeon HD 4670: black screen on boot

https://bugzilla.kernel.org/show_bug.cgi?id=199621 --- Comment #5 from Florian Echtler (f...@butterbrot.org) --- I know how it's supposed to work in theory, I'll give it a try. Do you know if there's a kernel repository that also carries the Ubuntu patches? -- You are receiving this mail because

Re: [PATCH] Add SPDX idenitifier and clarify license

On 05/08/2018 11:52 PM, Alex Deucher wrote: On Thu, May 3, 2018 at 11:41 AM, Dirk Hohndel wrote: On Thu, May 03, 2018 at 08:46:20AM -0400, Sean Paul wrote: Thank you for the awesome summary, it is very helpful! So since the boilerplate has to stay, is there a benefit to adding the SPDX header?

Re: linux-next: build failure after merge of the drm-intel tree

Hi Christoph, On Wed, 9 May 2018 07:08:55 +0200 Christoph Hellwig wrote: > > FYI, because the dma_configure change touch so much code and the author > wants to base more work on it it actually is in a guranteed stable > branch with just those patches: > > git://git.infradead.org/users/hch/dm

Re: linux-next: build failure after merge of the drm-intel tree

On Wed, May 09, 2018 at 03:02:55PM +1000, Stephen Rothwell wrote: > > - ret = of_dma_configure(dev, NULL); > > + ret = of_dma_configure(dev, NULL, true); > > if (ret < 0) { > > DRM_ERROR("Cannot setup DMA ops, ret %d", ret); > > return ret; > > -- > > 2.17.0 > > Th

Re: linux-next: build failure after merge of the drm-intel tree

Hi all, On Tue, 8 May 2018 11:07:16 +1000 Stephen Rothwell wrote: > > After merging the drm-intel tree, today's linux-next build (x86_64 > allmodconfig) failed like this: > > drivers/gpu/drm/xen/xen_drm_front.c: In function 'xen_drv_probe': > drivers/gpu/drm/xen/xen_drm_front.c:740:10: error: '

[Bug 199633] Stable kernel regression after 4.16.3: startxfce4 no longer works: X startup seems to hang

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

[Bug 199621] iMac 2009, Mobility Radeon HD 4670: black screen on boot

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

[Bug 106446] Stutter at higher refresh rates ( 75 Hz) and artifacts on desktop

https://bugs.freedesktop.org/show_bug.cgi?id=106446 --- Comment #1 from Mike Bendel --- Something else that may be of note: Setting amdgpu.dc to 0 sort of fixes the stutter and general performance issues I'm seeing. Also there is no flickering/artifacts after a fresh boot, without touching the p

[Bug 106374] feature request: allow increasing maxium GPU power consumption like implemented in Wattman on Windows

https://bugs.freedesktop.org/show_bug.cgi?id=106374 --- Comment #1 from Alex Deucher --- It is implemented. power1_cap_min/max are RO. They define the range of values that are valid for power. The OEM defines the range and the information is stored in tables in the vbios. The driver uses that

[Bug 100390] [steam] Grand Ages: Medieval crashes instantly

https://bugs.freedesktop.org/show_bug.cgi?id=100390 Timothy Arceri changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #33 from Paul van Maaren (ker...@vanmaaren.org) --- OK, tried that. Same result... -- You are receiving this mail because: You are watching the assignee of the bug. ___ dri-devel mailing li

[Bug 106446] Stutter at higher refresh rates ( 75 Hz) and artifacts on desktop

https://bugs.freedesktop.org/show_bug.cgi?id=106446 Bug ID: 106446 Summary: Stutter at higher refresh rates ( 75 Hz) and artifacts on desktop Product: DRI Version: unspecified Hardware: Other OS: Linux (All)

[Bug 106434] Graphical hangs, no keyboard, rest of system still active

https://bugs.freedesktop.org/show_bug.cgi?id=106434 --- Comment #4 from Alex Deucher --- Do you still have the issue without the CK patches? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@

[GIT PULL] exynos-drm-fixes

Hi Dave, Just fixup to pagefault issue of mixer driver I missed and a trivial cleanup to avoid duplicated drm_bridge_attach. Please kindly let me know if there is any problem Thanks, Inki Dae The following changes since commit a02cbe2e34c576cdc5e7846a3cd55245ab81db47: Merge branch '

[PATCH] drm: Fix render node numbering regression from control node removal.

drm_minor_alloc() does multiplication on this enum, so the removal ended up moving render nodes down from 128 base to 64. This caused Mesa's surfaceless backend to be unable to open the render nodes, since it was still looking up at 128. Signed-off-by: Eric Anholt Fixes: 0d49f303e8a7 ("drm: remo

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #32 from todd (todd...@gmail.com) --- @Paul p.s. Almost forgot to mention. Again, please use the systemctl method. So to test your systems suspend use. systemctl suspend -- You are receiving this mail because: You are watching the

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #31 from todd (todd...@gmail.com) --- @Paul Use the correct method to set your run levels. The original post tells you how and comment #6 even tells you where to get the information. read the file /etc/inittab The correct

[PATCH] video: fbdev: nvidia: fix spelling mistake: "scaleing" -> "scaling"

From: Colin Ian King Trivial fix to spelling mistake in module parameter description text Signed-off-by: Colin Ian King --- drivers/video/fbdev/nvidia/nvidia.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/video/fbdev/nvidia/nvidia.c b/drivers/video/fbdev/nvidia/

Re: [Freedreno] [PATCH] drm/msm/gpu: Increase the pm runtime autosuspend for 5xx

On Mon, May 7, 2018 at 6:47 PM, Jordan Crouse wrote: > Experimentation shows that resuming power quickly after suspending > ends up forcing a system hang for unknown reasons on 5xx targets. > To avoid cycling the power too much (especially during init) > turn up the autosuspend time for a5xx to 25

[Bug 106188] Can't successfully set pstates in pp_od_clk_voltage

https://bugs.freedesktop.org/show_bug.cgi?id=106188 --- Comment #6 from Alex Deucher --- (In reply to tempel.julian from comment #4) > However, I am still not able to raise the maximum allowed power consumption > of the GPU. > It's clear that "/sys/class/drm/card0/device/hwmon/hwmon0/power1_cap"

[Bug 106309] MST Multi-Stream Transport Kills All Displays Using Radeon Driver On Radeon HD 7570

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

[PATCH] drm/i915/gvt: fix spelling mistake: "resseting" -> "resetting"

From: Colin Ian King Trivial fix to spelling mistake in gvt_dbg_core debug message Signed-off-by: Colin Ian King --- drivers/gpu/drm/i915/gvt/vgpu.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/gvt/vgpu.c b/drivers/gpu/drm/i915/gvt/vgpu.c index 2e0a0

[Bug 106306] amdgpu CIK power management issues (overdrive and wattman)

https://bugs.freedesktop.org/show_bug.cgi?id=106306 --- Comment #2 from Alex Deucher --- CI parts default to the legacy dpm support, you need to enable powerplay to use the new APIs. Boot with amdgpu.dpm=1 on the kernel command line in grub to force the driver to use powerplay rather than the ol

[Bug 106303] amdgpu on RX 560: memory and core clocks not lowered on idle

https://bugs.freedesktop.org/show_bug.cgi?id=106303 --- Comment #4 from Alex Deucher --- Can you bisect? Are you using multiple monitors? -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list dri-devel@li

Re: [PATCH] Add SPDX idenitifier and clarify license

On Thu, May 3, 2018 at 11:41 AM, Dirk Hohndel wrote: > On Thu, May 03, 2018 at 08:46:20AM -0400, Sean Paul wrote: >> >> Thank you for the awesome summary, it is very helpful! So since the >> boilerplate >> has to stay, is there a benefit to adding the SPDX header? Is it just to make >> scripting/

[Bug 106404] Hang in draw function caused by interaction of glutInitWindowPosition, glutFullScreen , glDrawBuffer(GL_FRONT)

https://bugs.freedesktop.org/show_bug.cgi?id=106404 Alex Deucher changed: What|Removed |Added Product|DRI |Mesa QA Contact|

[Bug 106177] overclocking doesn't work with 4.17-rc1

https://bugs.freedesktop.org/show_bug.cgi?id=106177 --- Comment #5 from Alex Deucher --- Please use debugfs (e.g., /sys/kernel/debug/dri/0/amdgpu_pm_info) to check the current clocks. -- You are receiving this mail because: You are the assignee for the bug.__

[Bug 106402] amdgpu causes kernel Oops: 0002 [#1] SMP PTI

https://bugs.freedesktop.org/show_bug.cgi?id=106402 --- Comment #1 from Alex Deucher --- Please attach your full dmesg output and xorg log if you are using X. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel maili

[Bug 106228] amdgpu reads back brightness 0 (which is not true) if checked before a brightness has been explicitly set

https://bugs.freedesktop.org/show_bug.cgi?id=106228 --- Comment #2 from Harry Wentland --- That patch only affects Carrizo and should only be needed for S3. We don't see this issue with Ubuntu 18.04 on a Raven laptop we have available. The OS (Gnome) shows brightness as expected on boot. I wond

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #30 from Patrice (p.pol...@free.fr) --- I can't access the faulty machine until next Saturday - but it runs Fedora28's latest Xfce . -- You are receiving this mail because: You are watching the assignee of the bug. __

[Bug 106228] amdgpu reads back brightness 0 (which is not true) if checked before a brightness has been explicitly set

https://bugs.freedesktop.org/show_bug.cgi?id=106228 --- Comment #1 from Alex Deucher --- Harry, I thought we fixed something like this recently. Maybe this patch? https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c3d7bad88e3b35b981eecc1645ddbb3f13a8b54f -- You are r

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

On Wed, 09 May 2018, Feng Tang wrote: > >> > > > On Mon, May 07, 2018 at 11:40:45AM +0100, Chris Wilson wrote: >> >> > > > > Quoting Feng Tang (2018-05-07 11:36:09) >> >> > > > > > To fulfil the Dell 4K monitor, the dpcd max retries has been >> >> > > > > > bumped >> >> > > > > > from 7 to 32, w

Re: [PATCH 2/2] drm/dp: Correctly mask DP_TRAINING_AUX_RD_INTERVAL values for DP 1.4

On Fri, May 04, 2018 at 03:18:00PM -0700, matthew.s.atw...@intel.com wrote: > From: Matt Atwood > > DP_TRAINING_AUX_RD_INTERVAL with DP 1.3 spec changed bit scheeme from 8 > bits to 7 in DPCD 0x000e. The 8th bit is used to identify extended > receiver capabilities. For panels that use this new fe

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #29 from Paul van Maaren (ker...@vanmaaren.org) --- I just did the runlevel test and it does not make difference for me. I did: ln -sf /usr/lib/systemd/system/multi-user.target /etc/systemd/system/default.target and a reboot to 4.16

Re: amdgpu hangs on boot or shutdown on AMD Raven Ridge CPU (Engineer Sample)

WHi Alex, On Thu, Apr 19, 2018 at 4:13 PM, Alex Deucher wrote: https://bugs.freedesktop.org/show_bug.cgi?id=105684 >>> >>> No progress made on that bug report so far. >>> What can we do to help this advance? >> >> Ping, any news here? How can we help advance on this bug? > > Can you try one

Re: [PATCH 00/18] Fix some build warnings/errors with Sphinx

On Tue, May 08, 2018 at 10:13:42AM -0600, Jonathan Corbet wrote: > On Mon, 7 May 2018 06:35:36 -0300 > Mauro Carvalho Chehab wrote: > > > I decided to give a try with Sphinx last stable version > > (1.17.4), and noticed several issues. The worse one was > > with the networking book: a non-standa

Re: [PATCH 1/7] drm/mediatek: move dpi private data to device

-ci/linux/commits/Bibby-Hsieh/drm-mediatek-support-hdmi-output-for-mt2701-and-mt7623/20180508-140924 base: git://people.freedesktop.org/~airlied/linux.git drm-next config: arm-allyesconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 7.2.0-11) 7.2.0 reproduce: wget https

[Bug 106441] Totem video playback stuttering and graphical artifacts

https://bugs.freedesktop.org/show_bug.cgi?id=106441 Michel Dänzer changed: What|Removed |Added Attachment #139426|text/x-log |text/plain mime type|

Re: [PATCH 00/18] Fix some build warnings/errors with Sphinx

On Mon, 7 May 2018 06:35:36 -0300 Mauro Carvalho Chehab wrote: > I decided to give a try with Sphinx last stable version > (1.17.4), and noticed several issues. The worse one was > with the networking book: a non-standard footnote there > with [*] instead of a number causes it to break PDF build

[Bug 106441] Totem video playback stuttering and graphical artifacts

https://bugs.freedesktop.org/show_bug.cgi?id=106441 Bug ID: 106441 Summary: Totem video playback stuttering and graphical artifacts Product: Mesa Version: 18.0 Hardware: x86-64 (AMD64) OS: Linux (All)

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

>> > > > On Mon, May 07, 2018 at 11:40:45AM +0100, Chris Wilson wrote: > >> > > > > Quoting Feng Tang (2018-05-07 11:36:09) > >> > > > > > To fulfil the Dell 4K monitor, the dpcd max retries has been > >> > > > > > bumped > >> > > > > > from 7 to 32, which may hurt the boot/init time for some >

[PATCH] drm/etnaviv: replace license text with SPDX tags

This replaces the repetitive GPL-2.0 license text in code and header files with the SPDX tags. Generated hardware headers aren't changed, as any changes there need to be done in the upstream rnndb repository. Signed-off-by: Lucas Stach --- Christian, I've replaced some of your copyright statement

[Bug 199655] amdgpu: XFX Radeon RX 580 runs its fans only in dangerously low speeds and ignores temperature

https://bugzilla.kernel.org/show_bug.cgi?id=199655 --- Comment #1 from Sergey Kondakov (virtuous...@gmail.com) --- Created attachment 275837 --> https://bugzilla.kernel.org/attachment.cgi?id=275837&action=edit lspci_2018-05-08-quircks -- You are receiving this mail because: You are watching th

Re: [PATCH v3 3/3] ARM: dts: sun7i: Add support for the Ainol AW1 tablet

On Mon, May 07, 2018 at 10:15:46PM +0200, Paul Kocialkowski wrote: > > > + backlight: backlight { > > > + compatible = "pwm-backlight"; > > > + pwms = <&pwm 0 5 PWM_POLARITY_INVERTED>; > > > + brightness-levels = <0 10 20 30 40 50 60 70 80 90 100>; > > > > The increase

[Bug 199655] New: amdgpu: XFX Radeon RX 580 runs its fans only in dangerously low speeds and ignores temperature

https://bugzilla.kernel.org/show_bug.cgi?id=199655 Bug ID: 199655 Summary: amdgpu: XFX Radeon RX 580 runs its fans only in dangerously low speeds and ignores temperature Product: Drivers Version: 2.5 Kernel Version: 4.16.7

[PATCH] drm/etnaviv: mmuv2: support 40 bit phys address

MMUv2 supports up to 40 bits of physical address by folding the upper 8 bits into bits [4:11] of the PTE. Signed-off-by: Lucas Stach --- drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/etnaviv/etnaviv_iommu_v2.c

[PATCH v2 1/2] drm/etnaviv: switch MMU page tables to writecombine memory

We are likely to write multiple page entries at once and already ensure proper write buffer flushing before GPU submit, so this improves CPU time usage in the submit path without any downsides. Signed-off-by: Lucas Stach --- v2: use shorter _wc function names. --- drivers/gpu/drm/etnaviv/etnaviv

[PATCH v2 2/2] drm/etnaviv: mmuv2: allocate 2nd level page tables on demand

With etnaviv not being tied into the IOMMU framework anymore, the MMU functions will only be called under sleeping locks. Thus we are able to allocate the memory for the 2nd level page tables on demand without having to deal with memory allocation in atomic context. This speeds up driver intitiali

[Bug 105786] System freeze, amdgpu 4.17-WIP, 4.16.0-rc1-576e538e5fe6

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

Re: [PATCH v2 10/26] drm/bridge: panel: provide an owner .odev device

On 05/08/18 10:58, Peter Rosin wrote: > On 2018-05-08 08:51, Jyri Sarha wrote: >> On 05/04/18 16:51, Peter Rosin wrote: >>> It gets rid of an #ifdef and the .of_node member is going away. >>> >>> Signed-off-by: Peter Rosin >>> --- >>> drivers/gpu/drm/bridge/panel.c | 4 +--- >>> 1 file changed, 1

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

On Tue, May 8, 2018 at 1:33 PM, Chris Wilson wrote: > Quoting Feng Tang (2018-05-08 20:03:15) >> >> On Mon, May 07, 2018 at 05:09:21PM +0200, Daniel Vetter wrote: >> > On Mon, May 07, 2018 at 02:33:25PM +0100, Chris Wilson wrote: >> > > Quoting Feng Tang (2018-05-07 22:26:34) >> > > > Hi Chris, >>

Re: [PATCH 1/3] drm/xen-front: checking for NULL instead of IS_ERR

On 05/08/2018 12:34 PM, Oleksandr Andrushchenko wrote: On 05/08/2018 12:26 PM, Dan Carpenter wrote: drm_dev_alloc() returns error pointers, it never returns NULL. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carpenter Thank you, Reviewed-

Re: [PATCH 2/3] drm/xen-front: fix xen_drm_front_shbuf_alloc() error handling

On 05/08/2018 12:37 PM, Oleksandr Andrushchenko wrote: On 05/08/2018 12:27 PM, Dan Carpenter wrote: The xen_drm_front_shbuf_alloc() function was returning a mix of error pointers and NULL and the the caller wasn't checking correctly. I've changed it to always return error pointer consistently.

Re: [PATCH 3/3] drm/xen-front: Fix loop timeout

On 05/08/2018 12:37 PM, Oleksandr Andrushchenko wrote: On 05/08/2018 12:28 PM, Dan Carpenter wrote: If the loop times out then we want to exit with "to" set to zero, but in the current code it's set to -1. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-o

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

Quoting Feng Tang (2018-05-08 20:03:15) > > On Mon, May 07, 2018 at 05:09:21PM +0200, Daniel Vetter wrote: > > On Mon, May 07, 2018 at 02:33:25PM +0100, Chris Wilson wrote: > > > Quoting Feng Tang (2018-05-07 22:26:34) > > > > Hi Chris, > > > > > > > > Thanks for the prompt review! > > > > > > >

[PATCH v14 08/10] drm: Expose modes with aspect ratio, only if requested

From: Ankit Nautiyal We parse the EDID and add all the modes in the connector's modelist. This adds CEA modes with aspect ratio information too, regardless of whether user space requested this information or not. This patch: -prunes the modes with aspect-ratio information, from the drm_mode_get

[PATCH v14 06/10] drm: Add DRM client cap for aspect-ratio

From: Ankit Nautiyal To enable aspect-ratio support in DRM, blindly exposing the aspect ratio information along with mode, can break things in existing non-atomic user-spaces which have no intention or support to use this aspect ratio information. To avoid this, a new drm client cap is required

[PATCH v14 05/10] video/hdmi: Reject illegal picture aspect ratios

From: Ville Syrjälä AVI infoframe can only carry none, 4:3, or 16:9 picture aspect ratios. Return an error if the user asked for something different. Cc: Shashank Sharma Cc: "Lin, Jia" Cc: Akashdeep Sharma Cc: Jim Bride Cc: Jose Abreu Cc: Daniel Vetter Cc: Emil Velikov Cc: Thierry Reding

[PATCH v14 07/10] drm: Handle aspect ratio info in legacy modeset path

From: Ankit Nautiyal If the user-space does not support aspect-ratio, and requests for a modeset with mode having aspect ratio bits set, then the given user-mode must be rejected. Secondly, while preparing a user-mode from kernel mode, the aspect-ratio info must not be given, if aspect-ratio is n

[PATCH v14 10/10] drm: Add and handle new aspect ratios in DRM layer

From: "Sharma, Shashank" HDMI 2.0/CEA-861-F introduces two new aspect ratios: - 64:27 - 256:135 This patch: - Adds new DRM flags for to represent these new aspect ratios. - Adds new cases to handle these aspect ratios while converting from user->kernel mode or vise versa. This patch was once

[PATCH v14 09/10] drm: Add aspect ratio parsing in DRM layer

From: "Sharma, Shashank" Current DRM layer functions don't parse aspect ratio information while converting a user mode->kernel mode or vice versa. This causes modeset to pick mode with wrong aspect ratio, eventually causing failures in HDMI compliance test cases, due to wrong VIC. This patch add

[PATCH v14 03/10] drm/edid: Fix cea mode aspect ratio handling

From: Ville Syrjälä commit 6dffd431e229 ("drm: Add aspect ratio parsing in DRM layer") cause us to not send out any VICs in the AVI infoframes. That commit was since reverted, but if and when we add aspect ratio handing back we need to be more careful. Let's handle this by considering the aspect

[PATCH v14 04/10] drm/edid: Don't send bogus aspect ratios in AVI infoframes

From: Ville Syrjälä If the user mode would specify an aspect ratio other than 4:3 or 16:9 we now silently ignore it. Maybe a better apporoach is to return an error? Let's try that. Also we must be careful that we don't try to send illegal picture aspect in the infoframe as it's only capable of s

[PATCH v14 02/10] drm/edid: Use drm_mode_match_no_clocks_no_stereo() for consistentcy

From: Ville Syrjälä Use drm_mode_equal_no_clocks_no_stereo() in drm_match_hdmi_mode_clock_tolerance() for consistency as we also use it in drm_match_hdmi_mode() and the cea mode matching functions. This doesn't actually change anything since the input mode comes from detailed timings and we matc

[PATCH v14 00/10] Aspect ratio support in DRM layer

From: Ankit Nautiyal This patch series is a re-attempt to enable aspect ratio support in DRM layer. Currently the aspect ratio information gets lost in translation during a user->kernel mode or vice versa. The old patch series (https://pw-emeril.freedesktop.org/series/10850/) had 4 patches, out

[PATCH v14 01/10] drm/modes: Introduce drm_mode_match()

From: Ville Syrjälä Make mode matching less confusing by allowing the caller to specify which parts of the modes should match via some flags. Signed-off-by: Ville Syrjälä Reviewed-by: Shashank Sharma --- drivers/gpu/drm/drm_modes.c | 134 ++-- include/d

Re: [Intel-gfx] [PATCH] drm/dp: add module parameter for the dpcd access max retries

On Mon, May 07, 2018 at 05:09:21PM +0200, Daniel Vetter wrote: > On Mon, May 07, 2018 at 02:33:25PM +0100, Chris Wilson wrote: > > Quoting Feng Tang (2018-05-07 22:26:34) > > > Hi Chris, > > > > > > Thanks for the prompt review! > > > > > > On Mon, May 07, 2018 at 11:40:45AM +0100, Chris Wilson

Re: [PATCH V2 4/5] backlight: qcom-wled: Add support for OVP interrupt handling

On Thu, May 03, 2018 at 03:42:31PM +0530, Kiran Gunda wrote: > WLED peripheral has over voltage protection(OVP) circuitry and the OVP > fault is notified through an interrupt. Though this fault condition rising > is due to an incorrect hardware configuration is mitigated in the hardware, > it still

Re: [PATCH V2 3/5] backlight: qcom-wled: Add support for short circuit handling

On Thu, May 03, 2018 at 03:42:30PM +0530, Kiran Gunda wrote: > Handle the short circuit interrupt and check if the short circuit > interrupt is valid. Re-enable the module to check if it goes > away. Disable the module altogether if the short circuit event > persists. > > Signed-off-by: Kiran Gund

Re: [PATCH v2 10/26] drm/bridge: panel: provide an owner .odev device

On Tue, May 08, 2018 at 09:58:49AM +0200, Peter Rosin wrote: > On 2018-05-08 08:51, Jyri Sarha wrote: > > On 05/04/18 16:51, Peter Rosin wrote: > >> It gets rid of an #ifdef and the .of_node member is going away. > >> > >> Signed-off-by: Peter Rosin > >> --- > >> drivers/gpu/drm/bridge/panel.c |

Re: [PATCH] dma-buf: Remove unused sync_dump()

Quoting Chris Wilson (2018-02-08 10:09:06) > sync_dump() is an unused, unexported, function that adds 64k to the > kernel image and doesn't even provide locking around the global array it > uses. > > add/remove: 0/2 grow/shrink: 0/0 up/down: 0/-65734 (-65734) > Function

Re: [PATCH v2 7/8] drm/vmwgfx: add SPDX idenitifier and clarify license

Hi Dirk, On 7 May 2018 at 00:16, Dirk Hohndel (VMware) wrote: > These files are licensed under GPL-2.0. > Removing the MIT boilerplate as that really didn't make any sense for > those two header files. > > Signed-off-by: Dirk Hohndel (VMware) > --- > drivers/gpu/drm/vmwgfx/Kconfig

[Bug 199025] Suspend hangs. Never fully suspends and impossible to return to running state.

https://bugzilla.kernel.org/show_bug.cgi?id=199025 --- Comment #28 from Paul van Maaren (ker...@vanmaaren.org) --- I will change the runlevel to text and see if it resolves the problem. I assume I can test by typing: "echo mem > /sys/power/state" ? -- You are receiving this mail because: You are

Re: [PATCH 2/3] drm/xen-front: fix xen_drm_front_shbuf_alloc() error handling

On 05/08/2018 12:27 PM, Dan Carpenter wrote: The xen_drm_front_shbuf_alloc() function was returning a mix of error pointers and NULL and the the caller wasn't checking correctly. I've changed it to always return error pointer consistently. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xe

Re: [PATCH 3/3] drm/xen-front: Fix loop timeout

On 05/08/2018 12:28 PM, Dan Carpenter wrote: If the loop times out then we want to exit with "to" set to zero, but in the current code it's set to -1. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carpenter Thank you, Reviewed-by: Oleksandr A

[PATCH] drm/exynos/dsi: mask frame-done interrupt

DSI driver is not really interested in this interrupt. It causes only unnecessary code execution of interrupt handler and could possibly cause FIFO overflow - as it triggers DSI interrupt handler to process next DSI transfer. With this patch we will get rid of about 30 IRQ handler calls per second.

Re: [PATCH 1/3] drm/xen-front: checking for NULL instead of IS_ERR

On 05/08/2018 12:26 PM, Dan Carpenter wrote: drm_dev_alloc() returns error pointers, it never returns NULL. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carpenter Thank you, Reviewed-by: Oleksandr Andrushchenko diff --git a/drivers/gpu/dr

[PATCH 3/3] drm/xen-front: Fix loop timeout

If the loop times out then we want to exit with "to" set to zero, but in the current code it's set to -1. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/xen/xen_drm_front.c b/drivers/gpu/drm/xen/xen_drm_fr

[PATCH 2/3] drm/xen-front: fix xen_drm_front_shbuf_alloc() error handling

The xen_drm_front_shbuf_alloc() function was returning a mix of error pointers and NULL and the the caller wasn't checking correctly. I've changed it to always return error pointer consistently. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carp

[PATCH 1/3] drm/xen-front: checking for NULL instead of IS_ERR

drm_dev_alloc() returns error pointers, it never returns NULL. Fixes: c575b7eeb89f ("drm/xen-front: Add support for Xen PV display frontend") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/xen/xen_drm_front.c b/drivers/gpu/drm/xen/xen_drm_front.c index 1b0ea9ac330e..8615e8522c7a 1006

[Bug 199653] [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded)

https://bugzilla.kernel.org/show_bug.cgi?id=199653 --- Comment #3 from Marcus Husar (marcus.hu...@gmail.com) --- Created attachment 275833 --> https://bugzilla.kernel.org/attachment.cgi?id=275833&action=edit Call trace of i2c designware warning (taints kernel) -- You are receiving this mail be

[Bug 199653] [AMDGPU][DC] BUG: unable to handle kernel NULL pointer dereference (trace decoded)

https://bugzilla.kernel.org/show_bug.cgi?id=199653 --- Comment #2 from Marcus Husar (marcus.hu...@gmail.com) --- Created attachment 275831 --> https://bugzilla.kernel.org/attachment.cgi?id=275831&action=edit Journal log with amdgpu.dc_log=1 drm.debug=6 -- You are receiving this mail because: Y

  1   2   >