[PATCH 01/20] drm/doc: Fix more kerneldoc/sphinx warnings

Am 11.08.2016 um 10:23 schrieb Jani Nikula : > On Thu, 11 Aug 2016, Jani Nikula wrote: >> On Tue, 09 Aug 2016, Daniel Vetter wrote: >>> diff --git a/drivers/gpu/drm/i915/intel_audio.c >>> b/drivers/gpu/drm/i915/intel_audio.c >>> index d32f586f9c05..85389cdd0bec 100644 >>> ---

[PATCH 1/2] Revert "drm/fb-helper: Reduce READ_ONCE(master) to lockless_dereference"

On Thu, Aug 11, 2016 at 12:38:59PM +0200, Daniel Vetter wrote: > On Thu, Aug 11, 2016 at 11:50:21AM +0200, Johannes Berg wrote: > > From: Johannes Berg > > > > This reverts commit fa7d81bb3c269a2ee38b6e4d569d9eb8be1a78ad. > > > > As Peter explained: > > [...] lockless_dereference() is

[PATCH 01/20] drm/doc: Fix more kerneldoc/sphinx warnings

On Thu, 11 Aug 2016, Jani Nikula wrote: > On Tue, 09 Aug 2016, Daniel Vetter wrote: >> diff --git a/drivers/gpu/drm/i915/intel_audio.c >> b/drivers/gpu/drm/i915/intel_audio.c >> index d32f586f9c05..85389cdd0bec 100644 >> --- a/drivers/gpu/drm/i915/intel_audio.c >> +++

[PATCH 01/20] drm/doc: Fix more kerneldoc/sphinx warnings

On Thu, Aug 11, 2016 at 11:15:13AM +0300, Jani Nikula wrote: > On Tue, 09 Aug 2016, Daniel Vetter wrote: > > These are the leftovers I could only track down using keep_warnings = > > True. For some of them we might want to update our style guide on how > > to reference structures and constants,

[PATCH v7 1/5] drm: Read DP branch device HW revision

On Thu, Aug 11, 2016 at 11:14:43AM +0300, Mika Kahola wrote: > On Thu, 2016-08-11 at 10:10 +0300, Ville Syrjälä wrote: > > On Mon, Aug 08, 2016 at 04:00:26PM +0300, Mika Kahola wrote: > > > HW revision is mandatory field for DisplayPort branch > > > devices. This is defined in DPCD register

[PATCH REBASED v10 1/6] drm/i915/skl: Add support for the SAGV, fix underrun hangs

Op 10-08-16 om 16:27 schreef Lyude: > Since the watermark calculations for Skylake are still broken, we're apt > to hitting underruns very easily under multi-monitor configurations. > While it would be lovely if this was fixed, it's not. Another problem > that's been coming from this however, is

[PATCH 5/5] drm/imx: add exclusive fence to plane state

This allows the atomic helper to wait on them, instead of open-coding the same in the imx-drm driver. Signed-off-by: Lucas Stach --- drivers/gpu/drm/imx/imx-drm-core.c | 63 +- 1 file changed, 28 insertions(+), 35 deletions(-) diff --git

[PATCH 4/5] drm/imx: fold ipu_plane_disable into ipu_disable_plane

ipu_disable_plane is the only left caller of ipu_plane_disable. Having those 2 similar named functions is confusing and superfluous, so fold them into 1. Signed-off-by: Lucas Stach --- drivers/gpu/drm/imx/ipuv3-plane.c | 15 +-- 1 file changed, 5 insertions(+), 10 deletions(-) diff

[PATCH 3/5] drm/imx: don't destroy mode objects manually on driver unbind

Instead let drm_mode_config_cleanup() do the work when taking down the master device. This requires all cleanup functions to be properly hooked up to the mode object .destroy callback. Signed-off-by: Lucas Stach --- drivers/gpu/drm/bridge/dw-hdmi.c | 3 ---

[PATCH 2/5] drm/imx: drop deprecated load/unload drm_driver ops

Drop the load/unload driver ops, as they are deprecated because of their inherent races, with devices being visible to userspace before they are fully initialized. Move this code into the driver bind/unbind routines bracketed by the proper drm_dev_alloc/register and drm_dev_unregister/unref

[PATCH 1/5] drm/imx: don't call disable_plane in plane destroy path

When the destroy path is called the plane should already be disabled. If not, this is a core bug and should not be worked around in the driver. Signed-off-by: Lucas Stach --- drivers/gpu/drm/imx/ipuv3-plane.c | 1 - 1 file changed, 1 deletion(-) diff --git a/drivers/gpu/drm/imx/ipuv3-plane.c

[PATCH 01/20] drm/doc: Fix more kerneldoc/sphinx warnings

On Tue, 09 Aug 2016, Daniel Vetter wrote: > These are the leftovers I could only track down using keep_warnings = > True. For some of them we might want to update our style guide on how > to reference structures and constants, not sure ... > > Cc: Markus Heiser > Cc: Jonathan Corbet > Cc:

[PATCH v7 1/5] drm: Read DP branch device HW revision

On Thu, 2016-08-11 at 10:10 +0300, Ville Syrjälä wrote: > On Mon, Aug 08, 2016 at 04:00:26PM +0300, Mika Kahola wrote: > > HW revision is mandatory field for DisplayPort branch > > devices. This is defined in DPCD register field 0x509. > > But what do we want to do with it? Me, I don't see a

[PATCH v4.5 3/4] drm/mediatek: Add gamma correction.

>From 2f3f4dda747c0619594d13996e65598ab675c60c Mon Sep 17 00:00:00 2001 From: Bibby Hsieh Date: Thu, 28 Jul 2016 10:22:54 +0800 Subject: [PATCH] drm/mediatek: Add gamma correction. Add gamma set function to correct brightness values. It applies arbitrary mapping curve

[PATCH v2 0/7] drm/mediatek: cleaning up and refine

Am Donnerstag, den 11.08.2016, 10:51 +0200 schrieb Daniel Vetter: > On Thu, Aug 11, 2016 at 09:33:26AM +0200, Philipp Zabel wrote: > > Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh: > > > These patches based on 4.7-rc1 to clean up unused function > > > & variable and use drm core

[PATCH v4 3/4] drm/mediatek: Add gamma correction.

On Thu, Aug 11, 2016 at 09:51:16AM +0200, Philipp Zabel wrote: > Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä: > > On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote: > > > Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh: > > > > Add gamma set

drm/fb-helper: Reduce READ_ONCE(master) to lockless_dereference

On Thu, Aug 11, 2016 at 11:44:08AM +0200, Peter Zijlstra wrote: > On Wed, Jun 22, 2016 at 08:46:12AM +0100, Chris Wilson wrote: > > We are only documenting that the read is outside of the lock, and do not > > require strict ordering on the operation. In this case the more relaxed > >

[PATCH v2 6/6] dma-buf/sw_sync: de-stage SW_SYNC

On Mon, Aug 08, 2016 at 06:24:22PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > SW_SYNC allows to run tests on the sync_file framework via debugfs on > > /sync/sw_sync > > Opening and closing the file triggers creation and release of a sync > timeline. To create fences on this

[PATCH v7 4/5] drm: Update bits per component for display info

On Thu, Aug 11, 2016 at 10:22:27AM +0300, Ville Syrjälä wrote: > On Mon, Aug 08, 2016 at 04:00:29PM +0300, Mika Kahola wrote: > > DisplayPort branch device may define max supported bits per > > component. Update display info based on this value if bpc > > is defined. > > > > v2: cleanup to

[PATCH v2 0/7] drm/mediatek: cleaning up and refine

On Thu, Aug 11, 2016 at 09:33:26AM +0200, Philipp Zabel wrote: > Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh: > > These patches based on 4.7-rc1 to clean up unused function > > & variable and use drm core function instead. > > > > The following patches are needed to cleanly

[PATCH v4 3/4] drm/mediatek: Add gamma correction.

On Thu, Aug 11, 2016 at 11:02:27AM +0300, Ville Syrjälä wrote: > On Thu, Aug 11, 2016 at 09:51:16AM +0200, Philipp Zabel wrote: > > Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä: > > > On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote: > > > > Am Donnerstag, den

[Intel-gfx] [PATCH v2 05/15] drm/atmel-hlcdc: Use per-plane rotation property

On Wed, Aug 10, 2016 at 06:38:39PM +0200, Boris Brezillon wrote: > On Wed, 10 Aug 2016 16:04:37 +0200 > Daniel Vetter wrote: > > > On Wed, Aug 10, 2016 at 01:52:45PM +0200, Boris Brezillon wrote: > > > On Wed, 10 Aug 2016 14:41:52 +0300 > > > Ville Syrjälä wrote: > > > > > > > On Wed, Aug

[PATCH v4 3/4] drm/mediatek: Add gamma correction.

On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote: > Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh: > > Add gamma set function to correct brightness values. > > It applies arbitrary mapping curve to compensate the > > incorrect transfer function of the panel. > > > >

[PATCH v2 5/6] staging/android: add Doc for SW_SYNC ioctl interface

On Mon, Aug 08, 2016 at 06:24:21PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > This interface is hidden from kernel headers and it is intended for use > only for testing. So testers would have to add the ioctl information > internally. This is to prevent misuse of this feature. >

[PATCH v2 4/6] staging/android: prepare sw_sync files for de-staging

On Mon, Aug 08, 2016 at 06:24:20PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > remove file paths in the comments and add short description about each > file. > > v2: remove file paths instead of just change them. > > Signed-off-by: Gustavo Padovan > --- >

[PATCH v2 3/6] staging/android: move trace/sync.h to sync_trace.h

On Mon, Aug 08, 2016 at 06:24:19PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > The common behaviour for trace headers is to have them in the same folder > they are used, instead of creating a special trace/ directory. > > Signed-off-by: Gustavo Padovan Reviewed-by: Eric

[PATCH v2 0/6] de-stage SW_SYNC validation frawework

On Mon, Aug 08, 2016 at 06:24:16PM -0300, Gustavo Padovan wrote: > From: Gustavo Padovan > > Hi Greg, > > This is the last step in the Sync Framwork de-stage task. It de-stage > the SW_SYNC validation framework and the sync_debug info debugfs file. > > The first 2 patches are clean up and

[PATCH v7 4/5] drm: Update bits per component for display info

On Mon, Aug 08, 2016 at 04:00:29PM +0300, Mika Kahola wrote: > DisplayPort branch device may define max supported bits per > component. Update display info based on this value if bpc > is defined. > > v2: cleanup to match the drm_dp_helper.c patches introduced > earlier in this series > v3:

[PATCH v7 1/5] drm: Read DP branch device HW revision

On Thu, Aug 11, 2016 at 11:22:15AM +0300, Ville Syrjälä wrote: > On Thu, Aug 11, 2016 at 11:14:43AM +0300, Mika Kahola wrote: > > On Thu, 2016-08-11 at 10:10 +0300, Ville Syrjälä wrote: > > > On Mon, Aug 08, 2016 at 04:00:26PM +0300, Mika Kahola wrote: > > > > HW revision is mandatory field

[PATCH v7 3/5] drm/i915: Check pixel rate for DP to VGA dongle

On Mon, Aug 08, 2016 at 04:00:28PM +0300, Mika Kahola wrote: > Filter out a mode that exceeds the max pixel rate setting > for DP to VGA dongle. This is defined in DPCD register 0x81 > if detailed cap info i.e. info field is 4 bytes long and > it is available for DP downstream port. > > The

[PATCH v7 1/5] drm: Read DP branch device HW revision

On Mon, Aug 08, 2016 at 04:00:26PM +0300, Mika Kahola wrote: > HW revision is mandatory field for DisplayPort branch > devices. This is defined in DPCD register field 0x509. But what do we want to do with it? Me, I don't see a point in parsing a bunch of stuff from the DPCD unless there's a real

[PATCH v4 3/4] drm/mediatek: Add gamma correction.

Am Donnerstag, den 11.08.2016, 10:44 +0300 schrieb Ville Syrjälä: > On Thu, Aug 11, 2016 at 09:32:59AM +0200, Philipp Zabel wrote: > > Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh: > > > Add gamma set function to correct brightness values. > > > It applies arbitrary mapping

[RESEND Patch 2/4] gpu: drm: omapdrm: dss-of: add missing of_node_put after calling of_parse_phandle

>On 15/07/16 06:17, Peter Chen wrote: >> of_node_put needs to be called when the device node which is got from >> of_parse_phandle has finished using. >> >> Cc: Tomi Valkeinen >> Signed-off-by: Peter Chen >> --- >> drivers/gpu/drm/omapdrm/dss/dss-of.c | 7 --- >> 1 file changed, 4

[PATCH v2 0/7] drm/mediatek: cleaning up and refine

Am Donnerstag, den 04.08.2016, 10:59 +0800 schrieb Bibby Hsieh: > These patches based on 4.7-rc1 to clean up unused function > & variable and use drm core function instead. > > The following patches are needed to cleanly apply on top of v4.7-rc1: > - https://patchwork.kernel.org/patch/8044001/ >

[PATCH v4 3/4] drm/mediatek: Add gamma correction.

Am Donnerstag, den 28.07.2016, 10:22 +0800 schrieb Bibby Hsieh: > Add gamma set function to correct brightness values. > It applies arbitrary mapping curve to compensate the > incorrect transfer function of the panel. > > Signed-off-by: Bibby Hsieh > --- >

[PATCH] drm/bridge: dw-hdmi: fix hdmi display lost

On Thu, Aug 11, 2016 at 03:54:03PM +0800, Mark Yao wrote: > hdmi->disabled maybe not match to the real hardware status. > > ->dw_hdmi_bridge_enable() > hdmi->disabled = false; > -->dw_hdmi_update_power() >if (hdmi->rxsense) >force = DRM_FORCE_ON; >else >force =

[PATCH v3 3/3] drm/mediatek: fix the wrong pixel clock when resolution is 4K

Am Donnerstag, den 04.08.2016, 10:38 +0800 schrieb Bibby Hsieh: > From: Junzhi Zhao > > Pixel clock should be 297MHz when resolution is 4K. > > Signed-off-by: Junzhi Zhao > Signed-off-by: Bibby Hsieh > --- > drivers/gpu/drm/mediatek/mtk_dpi.c |8 ++-- > 1 file changed, 6

[Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/dc5f9cf6/attachment.html>

答复: Re: [RESEND PATCH] drm/gma500: Fix comments in gtt.c

Daniel Vetter wrote on 2016/08/10 17:22:14: > Daniel Vetter > From: Daniel Vetter > 2016/08/10 17:22 > > To: jiang.biao2 at zte.com.cn, > > Re: [RESEND PATCH] drm/gma500: Fix comments in gtt.c > > On Wed, Aug 10, 2016 at 04:52:53PM +0800, jiang.biao2 at zte.com.cn wrote: > > > > > > Daniel

[PATCH 0/9] v4.8 build regressions

Am Mittwoch, den 10.08.2016, 23:54 +0200 schrieb Arnd Bergmann: > This is a set of patches to address build warnings and errors that have > come up in linux-4.8 but that worked fine in v4.7. I've added the > tinyconfig warning patch in there as well, which is not a regression > but is something

[RFC 0/4] doc: dma-buf: sphinx conversion and cleanup

On Thu, 11 Aug 2016 16:17:56 +0530 Sumit Semwal wrote: > Convert dma-buf documentation over to sphinx; also cleanup to > address sphinx warnings. > > While at that, convert dma-buf-sharing.txt as well, and make it the > dma-buf API guide. Thanks for working to improve the documentation! I do

[PATCH] exynos-drm: Fix display manager failing to start without IOMMU problem

Hi Shuah, 2016년 08월 11일 02:30에 Shuah Khan 이(가) 쓴 글: > Fix exynos_drm_gem_create_ioctl() attempts to allocate non-contiguous GEM > memory without IOMMU. In this case, there is no point in attempting to DRM gem can be used for Non-DRM drivers such as GPU, V4L2 based Multimedia

[PATCH 1/1] Revert "gpu: drm: omapdrm: dss-of: add missing of_node_put after calling of_parse_phandle"

On Thu, Aug 11, 2016 at 5:44 AM, Peter Chen wrote: > This reverts commit 2ab9f5879162499e1c4e48613287e3f59e593c4f. > > The of_get_next_parent will drop refcount on the passed node, so the reverted > patch is wrong, thanks for Tomi Valkeinen points it. > Indeed it is. Tomi, are you going to pick

[Bug 93649] [radeonsi] Graphics lockup while playing tf2

-- 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/20160811/58a939a8/attachment.html>

[v10 PATCH 0/5] Rockchip Type-C and DisplayPort driver

Hi Chanwoo On 08/10/2016 08:37 AM, Chanwoo Choi wrote: > Hi Chris, > > On 2016년 08월 10일 08:32, Chris Zhong wrote: >> Hi all >> >> This series patch is for rockchip Type-C phy and DisplayPort controller >> driver. >> >> The USB Type-C PHY is designed to support the USB3 and DP applications.

[PATCH 5/9] drm/mediatek: add ARM_SMCCC dependency

ARM SMCCC is only set for ARMv7 and ARMv8 CPUs, but we currently allow the driver to be build for older architecture levels as well, which results in a link failure: drivers/gpu/built-in.o: In function `mtk_hdmi_hw_make_reg_writable': :(.text+0x1e737c): undefined reference to `arm_smccc_smc'

[PATCH 4/9] drm/mediatek: add CONFIG_OF dependency

The mediatek DRM driver can be configured for compile testing with CONFIG_OF disabled, but then fails to link: drivers/gpu/built-in.o: In function `mtk_drm_bind': analogix_dp_reg.c:(.text+0x52888): undefined reference to `of_find_device_by_node' analogix_dp_reg.c:(.text+0x52930): undefined

[PATCH 3/9] drm/mediatek: add COMMON_CLK dependency

On kernel builds without COMMON_CLK, the newly added mediatek drm driver fails to build: drivers/gpu/drm/mediatek/mtk_mipi_tx.c:130:16: error: field 'pll_hw' has incomplete type struct clk_hw pll_hw; ^~ In file included from ../include/linux/clk.h:16:0,

[PATCH 0/9] v4.8 build regressions

This is a set of patches to address build warnings and errors that have come up in linux-4.8 but that worked fine in v4.7. I've added the tinyconfig warning patch in there as well, which is not a regression but is something that shows up in the kernelci.org build bots. The other patches address

<    1   2