Re: [PATCH] lib/prime_numbers: Suppress warn on kmalloc failure

On pe, 2017-01-13 at 23:51 +, Chris Wilson wrote: > The allocation for the bitmap may become very large, larger than > MAX_ORDER, for large requests. We fail gracefully by falling back to > trail-division, so disable the warning from kmalloc: > >   521.961092] WARNING: CPU: 0 PID: 30637 at

[Bug 95306] Random Blank(black) screens on "Carrizo"

https://bugs.freedesktop.org/show_bug.cgi?id=95306 --- Comment #51 from Kelly Anderson --- 4.10.0-rc4 is looking good. whereas I had some screen glitches with 4.10.0-rc3 and lost pointer cursor, all of that seems to have been fixed with rc4. As far as BLACK screen

RE: [PATCH 3/6] drm/amdgpu: user BO priority instead of self coding it

Reviewed-by: Roger.He -Original Message- From: Christian König [mailto:deathsim...@vodafone.de] Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo Cc: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org Subject: [PATCH 3/6]

RE: [PATCH 6/6] drm/ttm: revert "add optional LRU removal callback v2"

Good way to keep original idea and remove CPU overhead. Reviewed-by: Roger.He and Test-by Roger.He -Original Message- From: Christian König [mailto:deathsim...@vodafone.de] Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo

RE: [PATCH 5/6] drm/ttm: revert "implement LRU add callbacks v2"

Series patches: Reviewed-by: Roger.He and Test-by Roger.He -Original Message- From: Christian König [mailto:deathsim...@vodafone.de] Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo Cc: amd-...@lists.freedesktop.org;

RE: [PATCH 4/6] drm/amdgpu: double the priority of kernel allocations

Reviewed-by: Roger.He -Original Message- From: Christian König [mailto:deathsim...@vodafone.de] Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo Cc: amd-...@lists.freedesktop.org; dri-devel@lists.freedesktop.org Subject: [PATCH 4/6]

RE: [PATCH 2/6] drm/ttm: add BO priorities for the LRUs

Reviewed-by: Roger.He -Original Message- From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Christian K?nig Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo Cc: dri-devel@lists.freedesktop.org;

RE: [PATCH 1/6] drm/ttm: remove allow_errors parameter from ttm_bo_force_list_clean

Looks good to me, patch is Reviewed-by: Roger.He -Original Message- From: amd-gfx [mailto:amd-gfx-boun...@lists.freedesktop.org] On Behalf Of Christian K?nig Sent: Friday, January 13, 2017 5:51 PM To: He, Hongbo Cc:

[Bug 192271] kernel 4.9 hangs during shutdown or reboot

https://bugzilla.kernel.org/show_bug.cgi?id=192271 Zhang Rui changed: What|Removed |Added CC||rui.zh...@intel.com

Re: [PATCH v11 02/12] drm/mediatek: add helpers for coverting from the generic components

On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_ovl' > define helpers for converting from 'mtk_ddp_comp' to 'mtk_disp_rdma' > > Signed-off-by: YT Shen Acked-by CK Hu > --- >

[PATCH] README: Fix grammar

Fix two grammar issues: - "standard autotools packages ---> "standard autotools package" - "If you are install" ---> "If you are installing" Signed-off-by: Fabio Estevam --- README | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README b/README

[Bug 93652] Random crashes/freezing with amdgpu Fury X mesa 11.1

https://bugs.freedesktop.org/show_bug.cgi?id=93652 --- Comment #18 from Adam Bolte --- My Fury X doesn't crash like it used to - no call traces in the kernels now. But quite often the monitor will switch off and simply stay off. This happens when I try to resume from

Re: [PATCH] intel: update global_name before HASH_ADD

On Fri, Jan 13, 2017 at 04:07:00PM -0800, Dongwon Kim wrote: > bo->global_name should be updated first before a hash value > for the entry is calculated with it by HASH_ADD macro. > > Signed-off-by: Dongwon Kim Thanks for the fix! Pushed, -Chris -- Chris Wilson, Intel

Re: [PATCH v2.1 1/7] drm/atomic: Add new iterators over all state, v3.

Hi Maarten, Thank you for the patch. On Tuesday 10 Jan 2017 14:46:58 Maarten Lankhorst wrote: > Add for_each_(old)(new)_(plane,connector,crtc)_in_state iterators to > replace the old for_each_xxx_in_state ones. This is useful for >1 flip > depth and getting rid of all xxx->state dereferences. >

[pull] drm/msm: msm-fixes for 4.10-rc4

Basically fix a couple things I broke in 4.10 ;-) The following changes since commit 9afe69d5a9495f8b023017e4c328fa717e00f092: Merge tag 'drm-misc-fixes-2017-01-09' of git://anongit.freedesktop.org/git/drm-misc into drm-fixes (2017-01-10 08:18:53 +1000) are available in the git repository at:

Re: [Freedreno] [PATCH 10/12] firmware: qcom_scm: Add qcom_scm_gpu_zap_resume()

On Fri, Jan 13, 2017 at 04:24:38PM -0700, Jordan Crouse wrote: > On Fri, Jan 13, 2017 at 11:12:41AM -0600, Andy Gross wrote: > > On Mon, Nov 28, 2016 at 12:28:35PM -0700, Jordan Crouse wrote: > > > Add an interface to trigger the remote processor to reinitialize the GPU > > > zap shader on

[PATCH 4/4] drm: exynos: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

Re: [Freedreno] [PATCH 10/12] firmware: qcom_scm: Add qcom_scm_gpu_zap_resume()

+ Stanimir On Sat, Jan 14, 2017 at 09:49:01PM -0600, Andy Gross wrote: > On Fri, Jan 13, 2017 at 04:24:38PM -0700, Jordan Crouse wrote: > > On Fri, Jan 13, 2017 at 11:12:41AM -0600, Andy Gross wrote: > > > On Mon, Nov 28, 2016 at 12:28:35PM -0700, Jordan Crouse wrote: > > > > Add an interface to

Re: [PATCH 10/12] firmware: qcom_scm: Add qcom_scm_gpu_zap_resume()

On Mon, Nov 28, 2016 at 12:28:35PM -0700, Jordan Crouse wrote: > Add an interface to trigger the remote processor to reinitialize the GPU > zap shader on power-up. > > Signed-off-by: Jordan Crouse > --- > +int __qcom_scm_gpu_zap_resume(struct device *dev) > +{ > +

Re: [PATCH 10/12] firmware: qcom_scm: Add qcom_scm_gpu_zap_resume()

On Fri, Jan 13, 2017 at 10:22:45AM -0700, Jordan Crouse wrote: > On Fri, Jan 13, 2017 at 11:12:41AM -0600, Andy Gross wrote: > > On Mon, Nov 28, 2016 at 12:28:35PM -0700, Jordan Crouse wrote: > > > Add an interface to trigger the remote processor to reinitialize the GPU > > > zap shader on

[PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

[PATCH] drm: etnaviv: constify etnaviv_iommu_ops structures

Declare etnaviv_iommu_ops structure as const as it is only used when the reference of one of its field is stored in the ops field of a iommu_domain structure. This ops field is of type const, so etnaviv_iommu_ops structures having similar properties can be declared const too. Done using

[PATCH 0/4] Drop drivers for Exynos4415

Hi, Support for Exynos4415 is being removed because: 1. There are no upstream users, 2. There are no known downstream users, 3. Except compile testing, you cannot build working kernel for Exynos4415 anymore. Patches are rebased on current next and are independent. Please pick up as you wish.

Re: [PATCH 0/4] Drop drivers for Exynos4415

Hi Krzk, 2017. 1. 14. PM 8:36 Krzysztof Kozlowski wrote: > Hi, > > Support for Exynos4415 is being removed because: > 1. There are no upstream users, > 2. There are no known downstream users, > 3. Except compile testing, you cannot build working kernel > for Exynos4415

[PATCH 1/4] ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the mach code. Signed-off-by: Krzysztof Kozlowski ---

[PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

Support for Exynos4415 is going away because there are no internal nor external users. Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), the platform cannot be instantiated so remove also the drivers. Signed-off-by: Krzysztof Kozlowski ---

[PATCH] intel: update global_name before HASH_ADD

bo->global_name should be updated first before a hash value for the entry is calculated with it by HASH_ADD macro. Signed-off-by: Dongwon Kim --- intel/intel_bufmgr_gem.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/intel/intel_bufmgr_gem.c

Re: [Intel-gfx] GPU hang with kernel 4.10rc3

On 12/01/17 10:21, Chris Wilson wrote: > On Thu, Jan 12, 2017 at 07:03:25AM +0100, Juergen Gross wrote: >> On 11/01/17 18:08, Chris Wilson wrote: >>> On Wed, Jan 11, 2017 at 05:33:34PM +0100, Juergen Gross wrote: With kernel 4.10rc3 running as Xen dm0 I get at each boot: [

[Bug 99419] Crash(Segmentation fault) si_shader_select in Master Of Orion

https://bugs.freedesktop.org/show_bug.cgi?id=99419 Andreas Schultes changed: What|Removed |Added Summary|Crash si_shader_select in

Re: [PATCH 3/7] i2c: designware-baytrail: Take punit lock on bus acquire

> Once I've a patch-set everyone likes I will start talking to people > to coordinate the merging, I believe it is probably best for all this > to be merged through the drm-intel tree. But we'll see about that > when the patch-set is ready. Agreed. signature.asc Description: PGP signature

[Bug 99419] Crash si_shader_select in Master Of Orion

https://bugs.freedesktop.org/show_bug.cgi?id=99419 Bug ID: 99419 Summary: Crash si_shader_select in Master Of Orion Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal

Re: [PATCH 3/7] i2c: designware-baytrail: Take punit lock on bus acquire

Hi, On 15-01-17 12:45, Wolfram Sang wrote: Hi Hans, So Wolfram, what is the plan with these ? As said they are necessary for the 2 i2c patches in this patch-set, so do you want the entire set of 8 i2c patches to go through an other tree to avoid inter tree dependencies ? Thanks for the

[Bug 99418] DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off

https://bugs.freedesktop.org/show_bug.cgi?id=99418 Bug ID: 99418 Summary: DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off Product: DRI Version: XOrg git Hardware: x86-64 (AMD64) OS: Linux

Re: [PATCH 3/7] i2c: designware-baytrail: Take punit lock on bus acquire

Hi Hans, > So Wolfram, what is the plan with these ? As said they are necessary > for the 2 i2c patches in this patch-set, so do you want the > entire set of 8 i2c patches to go through an other tree to avoid > inter tree dependencies ? Thanks for the heads up. So, my plan was that I send a pull

Re: [PATCH 3/7] i2c: designware-baytrail: Take punit lock on bus acquire

Hi, On 12-01-17 19:45, Wolfram Sang wrote: On Sun, Jan 08, 2017 at 02:44:23PM +0100, Hans de Goede wrote: Take the punit lock to stop others from accessing the punit while the pmic i2c bus is in use. This is necessary because accessing the punit from the kernel may result in the punit trying