[Bug 92248] [KBL/SKL/BYT/BXT] igt/kms_plane_scaling fail

[VGA controller]) -- 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/20161013/6b9ea255/attachment.html>

[Bug 98239] saints row 3: performance is limited by flushes

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/a5b9a8df/attachment.html>

[Bug 98238] witcher 2: objects are black when changing lod

window content. HW: R9 270x -- 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/20161013/fc9e5750/attachment.html>

[Bug 94354] R9285 Unigine Valley perf regression since radeonsi: use re-Z

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/ef8a51ba/attachment.html>

[RFC] drm: add atomic state printing

On Thu, Oct 13, 2016 at 01:38:30PM -0400, Sean Paul wrote: > On Thu, Oct 13, 2016 at 1:16 PM, Rob Clark wrote: > > Sometimes we just want to see the atomic state, without getting so many > > other debug traces. So add a new drm.debug bit for that. > > > > Note: it would be nice to put the

[RFC] drm: add atomic state printing

On Thu, Oct 13, 2016 at 01:16:29PM -0400, Rob Clark wrote: > Sometimes we just want to see the atomic state, without getting so many > other debug traces. So add a new drm.debug bit for that. > > Note: it would be nice to put the helpers for printing plane/crtc state > next to plane/crtc state

[PATCH] dma-buf/sw_sync: fix lockdep anger

On Thu, Oct 13, 2016 at 04:04:05PM -0400, Rob Clark wrote: > We were holding the wrong lock to be using fence_is_signaled_locked(). > And holding the child_list_lock over something that could end up calling > fence cb's angers lockdep: > > == >

[PATCH] drm/edid: Only print the bad edid when aborting

Currently, if drm.debug is enabled, we get a DRM_ERROR message on the intermediate edid reads. This causes transient failures in CI which flags up the sporadic EDID read failures, which are recovered by rereading the EDID automatically. This patch combines the reporting done by drm_do_get_edid()

[Intel-gfx] drm/i915: WARN_ON_ONCE(!crtc_clock || cdclk < crtc_clock)

[Adding Matt] On Wed, 2016-10-12 at 14:08 +0300, Joonas Lahtinen wrote: > Bisecting the offending commit between v4.8 and v4.8.1 would be a good > start. 0) Why use a personal notebook when one can just post any half baked idea to lkml? 1) I stumbled on 

[PATCH] drm: Print device information again in debugfs

On 13 October 2016 at 15:13, Daniel Vetter wrote: > I was a bit over-eager in my cleanup in > > commit 95c081c17f284de50eaca60d4d55643a64d39019 > Author: Daniel Vetter > Date: Tue Jun 21 10:54:12 2016 +0200 > > drm: Move master pointer from drm_minor to drm_device > > Noticed by Chris

[Intel-gfx] [PATCH 09/10] drm/i915/gen9: Actually verify WM levels in verify_wm_state()

Em Qui, 2016-10-13 às 18:15 -0300, Paulo Zanoni escreveu: > Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > > > > Thanks to Paulo Zanoni for indirectly pointing this out. > > > > Looks like we never actually added any code for checking whether or > > not > > we actually wrote watermark

[PATCH 10/10] drm/i915/gen9: Don't wrap strings in verify_wm_state()

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: Bikesheding: it would be nice to write a commit message explaining why, even if the message just tells the user to read Documentation/CodingStyle. Reviewed-by: Paulo Zanoni > Signed-off-by: Lyude > Cc: Maarten Lankhorst > Cc: Ville

[PATCH 09/10] drm/i915/gen9: Actually verify WM levels in verify_wm_state()

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > Thanks to Paulo Zanoni for indirectly pointing this out. > > Looks like we never actually added any code for checking whether or > not > we actually wrote watermark levels properly. Let's fix that. Thanks for doing this! Reviewed-by: Paulo

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

ng 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/20161013/19ee09ef/attachment.html>

[PATCH 08/10] drm/i915/gen9: Add skl_wm_level_equals()

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > Helper we're going to be using for implementing verification of the > wm > levels in skl_verify_wm_level(). > > Signed-off-by: Lyude Reviewed-by: Paulo Zanoni > Cc: Maarten Lankhorst > Cc: Ville Syrjälä > Cc: Paulo Zanoni > --- >  

[PATCH 07/10] drm/i915/gen9: Make skl_pipe_wm_get_hw_state() reusable

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > There's not much of a reason this should have the locations to read > out > the hardware state hardcoded, so allow the caller to specify the > location and add this function to intel_drv.h. As well, we're going > to > need this function to be

[Intel-gfx] [PATCH v2 05/10] drm/i915/gen9: Get rid of redundant watermark values

Your is SAGV related, and when we don't make the SAGV happy people's machines usually hang. So I'm definitely for your patches getting merged first On Thu, 2016-10-13 at 17:07 -0300, Paulo Zanoni wrote: > Em Qui, 2016-10-13 às 17:04 -0300, Paulo Zanoni escreveu: > > > > Em Qui, 2016-10-13 às

[PATCH v2 06/10] drm/i915/gen9: Add ddb changes to atomic debug output

Em Sex, 2016-10-07 às 20:11 -0400, Lyude escreveu: > Finally, add some debugging output for ddb changes in the atomic > debug > output. This makes it a lot easier to spot bugs from incorrect ddb > allocations. > > Signed-off-by: Lyude > Reviewed-by: Maarten Lankhorst > Cc: Ville Syrjälä >

[PATCH libdrm] Add support for DRM_MODE_PAGE_FLIP_TARGET_* flags

On 13/10/16 12:54 AM, Emil Velikov wrote: > Hi Michel, > > On 12 October 2016 at 10:41, Michel Dänzer wrote: >> From: Michel Dänzer >> >> Signed-off-by: Michel Dänzer >> --- >> >> The corresponding kernel changes have landed in Linus' tree. >> >> include/drm/drm.h | 1 + >>

[Intel-gfx] [PATCH v2 05/10] drm/i915/gen9: Get rid of redundant watermark values

Em Qui, 2016-10-13 às 17:04 -0300, Paulo Zanoni escreveu: > Em Qui, 2016-10-13 às 15:39 +0200, Maarten Lankhorst escreveu: > > > > Op 08-10-16 om 02:11 schreef Lyude: > > > > > > > > > Now that we've make skl_wm_levels make a little more sense, we > > > can > > > remove all of the redundant

[PATCH libdrm v2 2/2] Add drmModePageFlipTarget

From: Michel Dänzer It supports the DRM_MODE_PAGE_FLIP_TARGET_* flags. Signed-off-by: Michel Dänzer --- See https://cgit.freedesktop.org/~daenzer/xf86-video-amdgpu/commit/?id=b8631a9ba49c0d0ebe5dcd1dbfb68fcfe907296f

[PATCH libdrm v2 1/2] headers: Sync drm{,_mode}.h with the kernel

From: Michel Dänzer Generated using make headers_install, based on linus master commit b67be92feb486f800d80d72c67fd87b47b79b18e. Signed-off-by: Michel Dänzer --- include/drm/drm.h | 17 + include/drm/drm_mode.h | 49

[Intel-gfx] [PATCH v2 05/10] drm/i915/gen9: Get rid of redundant watermark values

Em Qui, 2016-10-13 às 15:39 +0200, Maarten Lankhorst escreveu: > Op 08-10-16 om 02:11 schreef Lyude: > > > > Now that we've make skl_wm_levels make a little more sense, we can > > remove all of the redundant wm information. Up until now we'd been > > storing two copies of all of the skl

[PATCH] dma-buf/sw_sync: fix lockdep anger

On Thu, Oct 13, 2016 at 4:17 PM, Chris Wilson wrote: > On Thu, Oct 13, 2016 at 04:04:05PM -0400, Rob Clark wrote: >> We were holding the wrong lock to be using fence_is_signaled_locked(). >> And holding the child_list_lock over something that could end up calling >> fence cb's angers lockdep: >>

[PATCH v3 9/9] MAINTAINERS: Update HISILICON DRM entries

Signed-off-by: Rongrong Zou --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 4347bce..16f4569 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -4117,6 +4117,7 @@ F:drivers/gpu/drm/gma500/ DRM DRIVERS FOR HISILICON M: Xinliang Liu

[PATCH v3 8/9] drm/hisilicon/hibmc: Add vblank interruput

Add vblank interrupt. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 47 - 1 file changed, 46 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c b/drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c

[PATCH v3 7/9] drm/hisilicon/hibmc: Add connector for VDAC

Add connector funcs and helper funcs for VDAC. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 8 +++ drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 2 + drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c | 82 3 files changed, 92

[PATCH v3 6/9] drm/hisilicon/hibmc: Add encoder for VDAC

Add encoder funcs and helpers for VDAC. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 ++ drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 2 + drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_vdac.c |

[PATCH v3 5/9] drm/hisilicon/hibmc: Add crtc for DE

Add crtc funcs and helper funcs for DE. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 318 drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 6 + drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 2 + 3 files changed, 326

[PATCH v3 4/9] drm/hisilicon/hibmc: Add plane for DE

Add plane funcs and helper funcs for DE. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/Makefile| 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.c | 188 drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_de.h | 29

[PATCH v3 3/9] drm/hisilicon/hibmc: Add support for frame buffer

Add support for fbdev and kms fb management. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/Makefile | 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 18 ++ drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.h | 24 ++

[PATCH v3 2/9] drm/hisilicon/hibmc: Add video memory management

Hibmc have 32m video memory which can be accessed through PCIe by host, we use ttm to manage these memory. Signed-off-by: Rongrong Zou --- drivers/gpu/drm/hisilicon/hibmc/Makefile| 2 +- drivers/gpu/drm/hisilicon/hibmc/hibmc_drm_drv.c | 12 +-

[PATCH v3 1/9] drm/hisilicon/hibmc: Add hisilicon hibmc drm master driver

Add DRM master driver for Hisilicon Hibmc SoC which used for Out-of-band management. Blow is the general hardware connection, both the Hibmc and the host CPU are on the same mother board. +--+ +--+ | | PCIe | Hibmc | |host CPU( |<->| display | |arm64,x86)|

[PATCH v3 0/9] Add DRM driver for Hisilicon Hibmc

This patch set adds a new drm driver for Hisilicon Hibmc. Hibmc is a BMC SoC with a display controller intergrated, usually it is used on server for Out-of-band management purpose. In this patch set, we just support basic function for Hibmc display subsystem. Hibmc display subsystem is connected

[bug report] drm/amd/powerplay: add vce state tables initialize for ppt v1.

Hello Rex Zhu, The patch 48d7b759a8bc: "drm/amd/powerplay: add vce state tables initialize for ppt v1." from Aug 31, 2016, leads to the following static checker warning: drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/process_pptables_v1_0.c:1211

[RFC] drm: add atomic state printing

On Thu, Oct 13, 2016 at 2:24 PM, Ville Syrjälä wrote: > On Thu, Oct 13, 2016 at 01:16:29PM -0400, Rob Clark wrote: >> Sometimes we just want to see the atomic state, without getting so many >> other debug traces. So add a new drm.debug bit for that. >> >> Note: it would be nice to put the

[PATCH] drm: Print device information again in debugfs

I was a bit over-eager in my cleanup in commit 95c081c17f284de50eaca60d4d55643a64d39019 Author: Daniel Vetter Date: Tue Jun 21 10:54:12 2016 +0200 drm: Move master pointer from drm_minor to drm_device Noticed by Chris Wilson. Fixes: 95c081c17f28 ("drm: Move master pointer from drm_minor

[PATCH] dma-buf/sw_sync: fix lockdep anger

We were holding the wrong lock to be using fence_is_signaled_locked(). And holding the child_list_lock over something that could end up calling fence cb's angers lockdep: == [ INFO: possible circular locking dependency detected ] 4.7.0-rc7+ #489

[PATCH] drm: Print device information again in debugfs

On Thu, Oct 13, 2016 at 04:13:44PM +0200, Daniel Vetter wrote: > I was a bit over-eager in my cleanup in > > commit 95c081c17f284de50eaca60d4d55643a64d39019 > Author: Daniel Vetter > Date: Tue Jun 21 10:54:12 2016 +0200 > > drm: Move master pointer from drm_minor to drm_device > >

[Intel-gfx] [PATCH v2 05/10] drm/i915/gen9: Get rid of redundant watermark values

Op 08-10-16 om 02:11 schreef Lyude: > Now that we've make skl_wm_levels make a little more sense, we can > remove all of the redundant wm information. Up until now we'd been > storing two copies of all of the skl watermarks: one being the > skl_pipe_wm structs, the other being the global wm struct

[PATCH] drm/crtc: constify drm_crtc_mask parameter

On Thu, 13 Oct 2016, Maarten Lankhorst wrote: > Now that drm_crtc_index takes a const, the same can be done for drm_crtc_mask. > > Signed-off-by: Maarten Lankhorst Reviewed-by: Jani Nikula > --- > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h > index

[PATCH v2] drm/bridge: analogix: protect power when get_modes or detect

On Wed, Oct 12, 2016 at 9:50 PM, Mark Yao wrote: > The drm callback ->detect and ->get_modes seems is not power safe, > they may be called when device is power off, do register access on > detect or get_modes will cause system die. > > Here is the path call ->detect before analogix_dp power on >

[patch] drm/i915: fix a read size argument

On Thu, 13 Oct 2016, walter harms wrote: > Am 13.10.2016 10:55, schrieb Dan Carpenter: >> We want to read 3 bytes here, but because the parenthesis are in the >> wrong place we instead read: >> >> sizeof(intel_dp->edp_dpcd) == sizeof(intel_dp->edp_dpcd) >> >> which is one byte. >> >>

[patch] drm/imx: drm_dev_alloc() returns error pointers

Am Donnerstag, den 13.10.2016, 11:53 +0300 schrieb Dan Carpenter: > We are checking for NULL here, when we should be checking for error > pointers. > > Fixes: 54db5decce17 ("drm/imx: drop deprecated load/unload drm_driver > ops") > Signed-off-by: Dan Carpenter Reviewed-by: Lucas Stach > >

[PATCH] virtio-gpu: fix vblank events

virtio-gpu sends vblank events in virtio_gpu_crtc_atomic_flush, and because of that it must be called for disabled planes too. Ask drm_atomic_helper_commit_planes to do that. Signed-off-by: Gerd Hoffmann --- drivers/gpu/drm/virtio/virtgpu_display.c | 2 +- 1 file changed, 1 insertion(+), 1

[RFC] drm: add atomic state printing

On Thu, Oct 13, 2016 at 1:38 PM, Sean Paul wrote: > On Thu, Oct 13, 2016 at 1:16 PM, Rob Clark wrote: >> Sometimes we just want to see the atomic state, without getting so many >> other debug traces. So add a new drm.debug bit for that. >> >> Note: it would be nice to put the helpers for

[RFC] drm: add atomic state printing

On Thu, Oct 13, 2016 at 1:16 PM, Rob Clark wrote: > Sometimes we just want to see the atomic state, without getting so many > other debug traces. So add a new drm.debug bit for that. > > Note: it would be nice to put the helpers for printing plane/crtc state > next to plane/crtc state structs..

[patch] drm/exynos: fix a timeout loop

We were trying to print an error message if we timed out here, but the loop actually ends with "tries" set to UINT_MAX and not zero. Fix this by changing from tries-- to --tries. A for loop would actually be the most natural way to do this. My fix means we only loop 99 times instead of 100 but

[RFC] drm: add atomic state printing

Sometimes we just want to see the atomic state, without getting so many other debug traces. So add a new drm.debug bit for that. Note: it would be nice to put the helpers for printing plane/crtc state next to plane/crtc state structs.. so someone adding new stuff to the state structs is more

[Bug 94354] R9285 Unigine Valley perf regression since radeonsi: use re-Z

-- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/b112d3c0/attachment.html>

[patch] drm/exynos: fix a timeout loop

Hello Dan, sorry for the blunder! Patch looks good to me. Reviewed-by: Tobias Jakobi With best wishes, Tobias Dan Carpenter wrote: > We were trying to print an error message if we timed out here, but the > loop actually ends with "tries" set to UINT_MAX and not zero. Fix this > by changing

[Intel-gfx] [patch] drm/i915: fix a read size argument

On Thu, Oct 13, 2016 at 10:01:03AM +0100, Chris Wilson wrote: > On Thu, Oct 13, 2016 at 11:55:08AM +0300, Dan Carpenter wrote: > > We want to read 3 bytes here, but because the parenthesis are in the > > wrong place we instead read: > > > > sizeof(intel_dp->edp_dpcd) ==

[PATCH] drm/msm/mdp5: handle non-fullscreen base plane case

If the bottom-most layer is not fullscreen, we need to use the BASE mixer stage for solid fill (ie. MDP5_CTL_BLEND_OP_FLAG_BORDER_OUT). The blend_setup() code pretty much handled this already, we just had to figure this out in _atomic_check() and assign the stages appropriately. Signed-off-by:

[patch] drm/i915: fix a read size argument

We want to read 3 bytes here, but because the parenthesis are in the wrong place we instead read: sizeof(intel_dp->edp_dpcd) == sizeof(intel_dp->edp_dpcd) which is one byte. Fixes: fe5a66f91c88 ("drm/i915: Read PSR caps/intermediate freqs/etc. only once on eDP") Signed-off-by: Dan

[patch] drm/vc4: Fix a couple error codes in vc4_cl_lookup_bos()

If the allocation fails the current code returns success. If copy_from_user() fails it returns the number of bytes remaining instead of -EFAULT. Fixes: d5b1a78a772f ("drm/vc4: Add support for drawing 3D frames.") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/vc4/vc4_gem.c

[patch] drm/imx: drm_dev_alloc() returns error pointers

We are checking for NULL here, when we should be checking for error pointers. Fixes: 54db5decce17 ("drm/imx: drop deprecated load/unload drm_driver ops") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/imx/imx-drm-core.c b/drivers/gpu/drm/imx/imx-drm-core.c index 98df09c..3acc976

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

wmgr)) { >> tmp_result = smu7_enable_voltage_control(hwmgr); >> -- >> 2.7.4 >> >> ___ >> amd-gfx mailing list >> amd-gfx at lists.freedesktop.org >> https://lists.freedesktop.org/mailman/listinfo/amd-gfx > ___ > amd-gfx mailing list > amd-gfx at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/amd-gfx -- next part -- A non-text attachment was scrubbed... Name: 0001-drm-amdgpu-disable-smu-hw-first-on-tear-down.patch Type: text/x-patch Size: 1655 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/899cc18a/attachment.bin>

[patch] drm/i915: fix a read size argument

Am 13.10.2016 10:55, schrieb Dan Carpenter: > We want to read 3 bytes here, but because the parenthesis are in the > wrong place we instead read: > > sizeof(intel_dp->edp_dpcd) == sizeof(intel_dp->edp_dpcd) > > which is one byte. > > Fixes: fe5a66f91c88 ("drm/i915: Read PSR

[PATCH] drm: atomic: Clarify documentation around drm_atomic_crtc_needs_modeset

On Thu, Oct 13, 2016 at 5:47 AM, Brian Starkey wrote: > Add some additional comments to more explicitly describe the meaning and > usage of the three CRTC modeset detection booleans: mode_changed, > connectors_changed and active_changed. > > Suggested-by: Daniel Vetter > Signed-off-by: Brian

[PATCH] drm: atomic: Clarify documentation around drm_atomic_crtc_needs_modeset

Add some additional comments to more explicitly describe the meaning and usage of the three CRTC modeset detection booleans: mode_changed, connectors_changed and active_changed. Suggested-by: Daniel Vetter Signed-off-by: Brian Starkey --- Hi Daniel, I guess I asked for this one :-), please

[PATCH] drm/crtc: constify drm_crtc_mask parameter

Now that drm_crtc_index takes a const, the same can be done for drm_crtc_mask. Signed-off-by: Maarten Lankhorst --- diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h index 0aa292526567..98ec40713921 100644 --- a/include/drm/drm_crtc.h +++ b/include/drm/drm_crtc.h @@ -1354,7 +1354,7 @@

[patch] drm/vc4: Fix a couple error codes in vc4_cl_lookup_bos()

: Dan Carpenter Looks good. Waiting for rc1 to show up to put together a -next. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 800 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-deve

[RFC PATCH 00/11] Introduce writeback connectors

e approach. > > Hopefully we can agree that a new atomic commit can't be completed > whilst there's a writeback ongoing, otherwise managing the fence and > framebuffer lifetime sounds really tricky - they'd need to be decoupled > from the atomic_state and outlive the commit that spawned them. Oh, good point. I'm fine with that, but then my anticipated usecases for writeback are testing (don't care about performance) and fallback plane-squashing when a complicated modeset exceeds limits (in which case you have no simpler plane config to modeset to until the writeback is completed, anyway). -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 800 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/f8b26281/attachment.sig>

[PATCH] drm: Print device information again in debugfs

On Thu, Oct 13, 2016 at 10:13 AM, Daniel Vetter wrote: > I was a bit over-eager in my cleanup in > > commit 95c081c17f284de50eaca60d4d55643a64d39019 > Author: Daniel Vetter > Date: Tue Jun 21 10:54:12 2016 +0200 > > drm: Move master pointer from drm_minor to drm_device > > Noticed by

[PULL] topic/drm-misc

Hi Dave, Sumits undug himself from conference traveling, so here's one more pull request for 4.9, essentially just containing the reservation rcu fixes and polish from Chris. Btw plan is that between -rc1 and -rc2 we do a tree-wide s/fence/dma_fence/ since the current name is a bit too generic

[Intel-gfx] [PATCH v2 4/4] drm: Add and handle new aspect ratios in DRM layer

On Tue, Aug 09, 2016 at 08:25:50PM +0530, Shashank Sharma wrote: > 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

[Intel-gfx] [PATCH v2 2/4] drm: Add aspect ratio parsing in DRM layer

On Tue, Aug 09, 2016 at 08:25:48PM +0530, Shashank Sharma wrote: > 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

[Intel-gfx] [PATCH v2 1/4] drm: add picture aspect ratio flags

On Tue, Aug 09, 2016 at 08:25:47PM +0530, Shashank Sharma wrote: > This patch adds drm flag bits for aspect ratio information > > Currently drm flag bits don't have field for mode's picture > aspect ratio. This field will help the driver to pick mode with > right aspect ratio, and help in setting

[patch] drm/i915: fix a read size argument

On Thu, Oct 13, 2016 at 11:55:08AM +0300, Dan Carpenter wrote: > We want to read 3 bytes here, but because the parenthesis are in the > wrong place we instead read: > > sizeof(intel_dp->edp_dpcd) == sizeof(intel_dp->edp_dpcd) > > which is one byte. > > Fixes: fe5a66f91c88 ("drm/i915: Read

[Intel-gfx] [patch] drm/i915: fix a read size argument

On Thu, Oct 13, 2016 at 11:55:08AM +0300, Dan Carpenter wrote: > We want to read 3 bytes here, but because the parenthesis are in the > wrong place we instead read: > > sizeof(intel_dp->edp_dpcd) == sizeof(intel_dp->edp_dpcd) > > which is one byte. > > Fixes: fe5a66f91c88 ("drm/i915: Read

Question: Re: [PATCH] drm/bridge: analogix: protect power when get_modes or detect

On 2016年10月12日 22:51, Sean Paul wrote: > On Wed, Oct 12, 2016 at 6:22 AM, Mark yao wrote: >> I'm not familiar with the analogix driver, maybe use a power reference count >> would better then direct power on/off analogix_dp. >> >> Does anyone has the idea to protect detect and get_modes

[bug report] drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7.

> PHM_PlatformCaps_ClockStretcher)) { > > regards, > dan carpenter > > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/01752e1e/attachment.html>

[PATCH v2] drm/bridge: analogix: protect power when get_modes or detect

The drm callback ->detect and ->get_modes seems is not power safe, they may be called when device is power off, do register access on detect or get_modes will cause system die. Here is the path call ->detect before analogix_dp power on [] analogix_dp_detect+0x44/0xdc []

[PATCH 00/10] mm: adjust get_user_pages* functions to explicitly pass FOLL_* flags

Am 13.10.2016 um 02:20 schrieb Lorenzo Stoakes: > This patch series adjusts functions in the get_user_pages* family such that > desired FOLL_* flags are passed as an argument rather than implied by flags. > > The purpose of this change is to make the use of FOLL_FORCE explicit so it is > easier to

[PATCH 02/10] mm: remove write/force parameters from __get_user_pages_unlocked()

On 13/10/2016 02:20, Lorenzo Stoakes wrote: > This patch removes the write and force parameters from > __get_user_pages_unlocked() to make the use of FOLL_FORCE explicit in callers > as > use of this flag can result in surprising behaviour (and hence bugs) within > the > mm subsystem. > >

[PATCH] drm/amd/powerplay: don't give up if DPM is already running

___ amd-gfx mailing list amd-gfx at lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/amd-gfx -- next part -- A non-text attachment was scrubbed... Name: 0001-drm-amdgpu-need-to-disable-dpm-first-when-rmmod-amdg.patch Type: applicati

[bug report] drm/amd/powerplay: implement smu7 hwmgr to manager asics with smu ip version 7.

t attachment was scrubbed... Name: 0001-drm-amd-powerplay-fix-static-checker-warnings-in-smu.patch Type: application/octet-stream Size: 1105 bytes Desc: 0001-drm-amd-powerplay-fix-static-checker-warnings-in-smu.patch URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161013/7bf264a5/attachment-0001.obj>

[PATCH 10/10] mm: replace access_process_vm() write parameter with gup_flags

This patch removes the write parameter from access_process_vm() and replaces it with a gup_flags parameter as use of this function previously _implied_ FOLL_FORCE, whereas after this patch callers explicitly pass this flag. We make this explicit as use of FOLL_FORCE can result in surprising

[PATCH 09/10] mm: replace access_remote_vm() write parameter with gup_flags

This patch removes the write parameter from access_remote_vm() and replaces it with a gup_flags parameter as use of this function previously _implied_ FOLL_FORCE, whereas after this patch callers explicitly pass this flag. We make this explicit as use of FOLL_FORCE can result in surprising

[PATCH 08/10] mm: replace __access_remote_vm() write parameter with gup_flags

This patch removes the write parameter from __access_remote_vm() and replaces it with a gup_flags parameter as use of this function previously _implied_ FOLL_FORCE, whereas after this patch callers explicitly pass this flag. We make this explicit as use of FOLL_FORCE can result in surprising

[PATCH 07/10] mm: replace get_user_pages_remote() write/force parameters with gup_flags

This patch removes the write and force parameters from get_user_pages_remote() and replaces them with a gup_flags parameter to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo

[PATCH 06/10] mm: replace get_user_pages() write/force parameters with gup_flags

This patch removes the write and force parameters from get_user_pages() and replaces them with a gup_flags parameter to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo Stoakes

[PATCH 05/10] mm: replace get_vaddr_frames() write/force parameters with gup_flags

This patch removes the write and force parameters from get_vaddr_frames() and replaces them with a gup_flags parameter to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo Stoakes

[PATCH 04/10] mm: replace get_user_pages_locked() write/force parameters with gup_flags

This patch removes the write and force parameters from get_user_pages_locked() and replaces them with a gup_flags parameter to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo

[PATCH 03/10] mm: replace get_user_pages_unlocked() write/force parameters with gup_flags

This patch removes the write and force parameters from get_user_pages_unlocked() and replaces them with a gup_flags parameter to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo

[PATCH 02/10] mm: remove write/force parameters from __get_user_pages_unlocked()

This patch removes the write and force parameters from __get_user_pages_unlocked() to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo Stoakes --- include/linux/mm.h | 3

[PATCH 01/10] mm: remove write/force parameters from __get_user_pages_locked()

This patch removes the write and force parameters from __get_user_pages_locked() to make the use of FOLL_FORCE explicit in callers as use of this flag can result in surprising behaviour (and hence bugs) within the mm subsystem. Signed-off-by: Lorenzo Stoakes --- mm/gup.c | 47

[PATCH 00/10] mm: adjust get_user_pages* functions to explicitly pass FOLL_* flags

This patch series adjusts functions in the get_user_pages* family such that desired FOLL_* flags are passed as an argument rather than implied by flags. The purpose of this change is to make the use of FOLL_FORCE explicit so it is easier to grep for and clearer to callers that this flag is being

[PATCH] drm/sun4i: Check that the plane coordinates are not negative

On Mon, Oct 03, 2016 at 06:18:40PM +0200, Boris Brezillon wrote: > On Mon, 3 Oct 2016 14:58:11 +0200 > Maxime Ripard wrote: > > > Hi Boris, > > > > On Fri, Sep 30, 2016 at 06:08:26PM +0200, Boris Brezillon wrote: > > > On Fri, 30 Sep 2016 16:33:20 +0200 > > > Maxime Ripard wrote: > > > > >