[PULL] drm-amdkfd-next

Hi Dave, Here are a few amdkfd patches for 4.6. These patches defer radeon/amdgpu loading in case amdkfd is not yet loaded, by returning -EPROBE_DEFER during their probing stage. Thanks, Oded The following changes since commit 44ab4042178bd596275927ea050980aa4257581b: Merge branch 'for-next'

[Bug 60879] [radeonsi] X11 can't start with acceleration enabled

https://www.bountysource.com/issues/5643054-radeonsi-x11-can-t-start-with-acceleration-enabled -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/

[Bug 113341] New: GPU Lockup on AMD Kaveri

https://bugzilla.kernel.org/show_bug.cgi?id=113341 Bug ID: 113341 Summary: GPU Lockup on AMD Kaveri Product: Drivers Version: 2.5 Kernel Version: 4.4.2 Hardware: x86-64 OS: Linux Tree: Mainline Sta

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #14 from Dionisus Torimens --- Created attachment 206311 --> https://bugzilla.kernel.org/attachment.cgi?id=206311&action=edit Temperature Graph with nomodeset radeon.modeset=1 without redshift -- You are receiving this mail becaus

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #13 from Dionisus Torimens --- Created attachment 206301 --> https://bugzilla.kernel.org/attachment.cgi?id=206301&action=edit Temperature Graph with nomodeset radeon.modeset=1 and redshift -- You are receiving this mail because: Y

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 Dionisus Torimens changed: What|Removed |Added Attachment #203781|0 |1 is obsolete|

[Bug 112491] Radeon: HD 7400G / A4-4355M System overheats with 3D graphics active.

https://bugzilla.kernel.org/show_bug.cgi?id=112491 --- Comment #12 from Dionisus Torimens --- [Wonderful, fglrx doesn't work at all with kernel 4.2... ...] The fastest way to get the system to overheat is to - enable redshift (or probably xgamma) - disable vsync - set dpm to preformance* echo pe

[Bug 93826] 144Hz graphic glitches and bad refresh rate

ed to radeon_compute_pll_avivo() in atombios_adjust_pll(). -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160227/65a1eb54/attachment.html>

[Bug 94315] AMDGPU 290X Refresh rate issue at 144Hz

tps://lists.freedesktop.org/archives/dri-devel/attachments/20160227/0a73dbf5/attachment.html>

[Bug 93826] 144Hz graphic glitches and bad refresh rate

scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160227/1620b00b/attachment.html>

[patch] drm/amd: cleanup get_mfd_cell_dev()

On Sat, Feb 27, 2016 at 10:50:40AM +0100, walter harms wrote: > > > Am 25.02.2016 08:47, schrieb Dan Carpenter: > > It's simpler to just use snprintf() to print this to one buffer instead > > of using strcpy() and strcat(). Also using snprintf() is slightly safer > > than using sprintf(). > > >

[PATCH v4 5/5] staging/android: add flags member to sync ioctl structs

Hi Emil, 2016-02-27 Emil Velikov : > Hi Gustavo, > > On 26 February 2016 at 18:31, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Play safe and add flags member to all structs. So we don't need to > > break API or create new IOCTL in the future if new features that requires > > flags

[PATCH] staging/android: refactor SYNC_IOC_FILE_INFO

Hi Emil, 2016-02-27 Emil Velikov : > Hi Gustavo, > > On 26 February 2016 at 21:00, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and > > optimize buffer allocation. In the new approach the ioctl needs to be called > > tw

[patch] drm/amd: cleanup get_mfd_cell_dev()

Am 27.02.2016 11:40, schrieb Dan Carpenter: > On Sat, Feb 27, 2016 at 10:50:40AM +0100, walter harms wrote: >> >> >> Am 25.02.2016 08:47, schrieb Dan Carpenter: >>> It's simpler to just use snprintf() to print this to one buffer instead >>> of using strcpy() and strcat(). Also using snprintf() i

[Bug 112921] Lock-up after screensaver on radeon

https://bugzilla.kernel.org/show_bug.cgi?id=112921 Jean Delvare changed: What|Removed |Added Status|NEEDINFO|ASSIGNED --- Comment #6 from Jean Delvare

[patch] drm/amd: cleanup get_mfd_cell_dev()

Am 25.02.2016 08:47, schrieb Dan Carpenter: > It's simpler to just use snprintf() to print this to one buffer instead > of using strcpy() and strcat(). Also using snprintf() is slightly safer > than using sprintf(). > > Signed-off-by: Dan Carpenter > > diff --git a/drivers/gpu/drm/amd/amdgpu/

[PATCH v4 5/5] staging/android: add flags member to sync ioctl structs

Hi Gustavo, On 26 February 2016 at 18:31, Gustavo Padovan wrote: > From: Gustavo Padovan > > Play safe and add flags member to all structs. So we don't need to > break API or create new IOCTL in the future if new features that requires > flags arises. > > v2: check if flags are valid (zero, in t

[PATCH] staging/android: refactor SYNC_IOC_FILE_INFO

Hi Gustavo, On 26 February 2016 at 21:00, Gustavo Padovan wrote: > From: Gustavo Padovan > > Change SYNC_IOC_FILE_INFO behaviour to avoid future API breaks and > optimize buffer allocation. In the new approach the ioctl needs to be called > twice to retrieve the array of fence_infos pointed by i

[PATCH 3/5] drm: introduce pipe color correction properties

On 26 February 2016 at 15:43, Lionel Landwerlin wrote: > On 26/02/16 00:36, Emil Velikov wrote: >> >> Hi Lionel, >> >> A bunch of suggestions - feel free to take or ignore them :-) >> >> On 25 February 2016 at 10:58, Lionel Landwerlin >> wrote: > I'm not sure it matters as the drm_crtc_state you