[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 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

[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 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 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] 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

答复: 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

[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>

[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

[PATCH v6 07/10] drm/mediatek: add dsi transfer function

Hi, YT: On Wed, 2016-08-10 at 15:24 +0800, YT Shen wrote: > Hi CK, > > On Fri, 2016-08-05 at 18:08 +0800, CK Hu wrote: > > Hi, YT: > > > > On Thu, 2016-08-04 at 19:07 +0800, YT Shen wrote: > > > From: shaoming chen > > > > > > add dsi read/write commands for transfer function > > > > > >

[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 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

[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 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 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 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.

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 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

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

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 = DRM_FORCE_OFF; hdmi->rxsense maybe false on bridge enable path, then hdmi->disabled

[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

[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, 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 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 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 >> +++

[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 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

[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 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

[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>

[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] drm/bridge: dw-hdmi: fix hdmi display lost

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

[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 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 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 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 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] drm/bridge: dw-hdmi: fix hdmi display lost

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

[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 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

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

pplication/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/992cd2b8/attachment.sig>

[PATCH] drm/imx: imx-ldb: remove unnecessary double disable check

Since the atomic modeset conversion, this should not be an issue anymore. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/imx-ldb.c | 12 1 file changed, 12 deletions(-) diff --git a/drivers/gpu/drm/imx/imx-ldb.c b/drivers/gpu/drm/imx/imx-ldb.c index 27a471c..33a7613 100644

[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 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 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. >

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

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 > lockless_dereference() will suffice. No, no, no... This is 'broken'.

[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] drm/omap: remove unneeded conversions to bool

4.9. Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/a8c988c0/attachment.sig>

[PATCH 2/2] locking/barriers: suppress sparse warnings in lockless_dereference()

From: Johannes Berg After Peter's commit (see below) we get a lot of sparse warnings (one for every rcu_dereference, and more) since the expression here is assigning to the wrong address space. Instead of validating that 'p' is a pointer this way, instead make it fail

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

From: Johannes Berg This reverts commit fa7d81bb3c269a2ee38b6e4d569d9eb8be1a78ad. As Peter explained: [...] lockless_dereference() is _stronger_ than READ_ONCE(), not weaker. [...] Also, clue is in the name: 'dereference', you don't actually dereference the

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

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 _stronger_ than READ_ONCE(), not weaker. > > [...] > > Also, clue is in the

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

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. There is no content change yet; only format conversion and creation of some hyperlinks. Sumit Semwal (4):

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

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. There is no content change yet; only format conversion and creation of some hyperlinks. Sumit Semwal (4):

[RFC 1/4] dma-buf/fence: kerneldoc: remove unused struct members

Commit 0431b9065f28ecf6c320fefebe0241620049984f ("staging/android: bring struct sync_pt back") removed child_list and active_list from struct fence, but left it in kernel doc. Delete them. Fixes: 0431b9065f28 ("staging/android: bring struct sync_pt back") Signed-off-by: Sumit Semwal ---

[RFC 2/4] dma-buf/fence: kerneldoc: remove spurious section header

Commit e941759c74a44d6ac2eed21bb0a38b21fe4559e2 ("fence: dma-buf cross-device synchronization (v18)") had a spurious kerneldoc section header that caused Sphinx to complain. Fix it. Fixes: e941759c74a4 ("fence: dma-buf cross-device synchronization (v18)") Signed-off-by: Sumit Semwal ---

[RFC 3/4] Documentation: move dma-buf documentation to rst

Branch out dma-buf related documentation into its own rst file to allow adding it to the sphinx documentation generated. While at it, move dma-buf-sharing.txt into rst as the dma-buf guide too. Signed-off-by: Sumit Semwal --- Documentation/DocBook/device-drivers.tmpl | 37 ---

[RFC 4/4] Documentation/sphinx: link dma-buf rsts

Include dma-buf sphinx documentation into top level index. Signed-off-by: Sumit Semwal --- Documentation/index.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/index.rst b/Documentation/index.rst index 43c722f15292..2fe8e82d7d8c 100644 --- a/Documentation/index.rst +++

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

On Thu, Aug 11, 2016 at 09:44:55AM +, Peter Chen wrote: > > > >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 > >> --- >

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

On Thu, Aug 11, 2016 at 12:43:39PM +0300, Mika Kahola wrote: > On Thu, 2016-08-11 at 10:18 +0300, Ville Syrjälä wrote: > > 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

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

On Thu, Aug 11, 2016 at 01:51:42PM +0300, Ville Syrjälä wrote: > On Thu, Aug 11, 2016 at 12:43:39PM +0300, Mika Kahola wrote: > > On Thu, 2016-08-11 at 10:18 +0300, Ville Syrjälä wrote: > > > On Mon, Aug 08, 2016 at 04:00:28PM +0300, Mika Kahola wrote: > > > > Filter out a mode that exceeds

[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

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

gt; } >> >> struct device_node * >> -- >> 1.9.1 >> -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/d5ebe0e8/attachment-0001.sig>

[PATCH v4 1/4] drm: extra printk() wrapper macros

We had only DRM_INFO() and DRM_ERROR(), whereas the underlying printk() provides several other useful intermediate levels such as NOTICE and WARNING. So this patch fills out the set by providing both regular and once-only macros for each of the levels INFO, NOTICE, and WARNING, using a common

[PATCH 07/15] drm/omap: Use per-plane rotation property

p-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/57d1035b/attachment.sig>

[RFC 3/4] Documentation: move dma-buf documentation to rst

On Thu, 11 Aug 2016, Sumit Semwal wrote: > diff --git a/Documentation/dma-buf/guide.rst b/Documentation/dma-buf/guide.rst > new file mode 100644 > index ..fd3534fdccb3 > --- /dev/null > +++ b/Documentation/dma-buf/guide.rst > @@ -0,0 +1,503 @@ > + > +.. _dma-buf-guide: > + >

[RFC 3/4] Documentation: move dma-buf documentation to rst

Hello Jani, On 11 August 2016 at 17:17, Jani Nikula wrote: > On Thu, 11 Aug 2016, Sumit Semwal wrote: >> diff --git a/Documentation/dma-buf/guide.rst >> b/Documentation/dma-buf/guide.rst >> new file mode 100644 >> index ..fd3534fdccb3 >> --- /dev/null >> +++

[RFC 3/4] Documentation: move dma-buf documentation to rst

Hi Markus, On 11 August 2016 at 17:28, Markus Heiser wrote: > Hi Sumit, > > I haven't compiled your patch yet, just my 2cent about the > reStructuredText (reST) ASCII markup ... > Thanks very much for your detailed review comments - highly appreciated! > Here are some handy links about reST and

[Bug 96444] GRID Autosport crash on loading race

es/dri-devel/attachments/20160811/4636465a/attachment-0001.html>

[Bug 96626] New account request

this. Re-assigning to Mesa core. -- 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/292ac42a/attachment.html>

[PATCH 07/15] drm/omap: Use per-plane rotation property

On Thu, Aug 11, 2016 at 02:32:44PM +0300, Tomi Valkeinen wrote: > Hi, > > On 22/07/16 16:43, ville.syrjala at linux.intel.com wrote: > > From: Ville Syrjälä > > > > The global mode_config.rotation_property is going away, switch over to > > per-plane rotation_property. > > > > Not sure I got

[PATCH REBASED v10 6/6] drm/i915/skl: Update DDB values atomically with wms/plane attrs

Hey, Op 10-08-16 om 16:28 schreef Lyude: > Now that we can hook into update_crtcs and control the order in which we > update CRTCs at each modeset, we can finish the final step of fixing > Skylake's watermark handling by performing DDB updates at the same time > as plane updates and watermark

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

On Thu, Aug 11, 2016 at 03:26:42PM +0300, Mika Kahola wrote: > On Thu, 2016-08-11 at 12:56 +0200, Daniel Vetter wrote: > > On Thu, Aug 11, 2016 at 01:51:42PM +0300, Ville Syrjälä wrote: > > > On Thu, Aug 11, 2016 at 12:43:39PM +0300, Mika Kahola wrote: > > > > On Thu, 2016-08-11 at 10:18 +0300,

[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 1/5] drm/amdgpu: Remove call to reservation_object_test_signaled_rcu before wait

Since fence_wait_timeout_reservation_object_wait_timeout_rcu() with a timeout of 0 becomes reservation_object_test_signaled_rcu(), we do not need to handle such conversion in the caller. The only challenge are those callers that wish to differentiate the error code between the nonblocking busy

[PATCH 2/5] drm: Remove manual call to reservation_object_test_signaled_rcu before wait

Since fence_wait_timeout_reservation_object_wait_timeout_rcu() with a timeout of 0 becomes reservation_object_test_signaled_rcu(), we do not need to handle such conversion in the caller. The only challenge are those callers that wish to differentiate the error code between the nonblocking busy

[PATCH 4/5] drm/nouveau: Remove call to reservation_object_test_signaled_rcu before wait

Since fence_wait_timeout_reservation_object_wait_timeout_rcu() with a timeout of 0 becomes reservation_object_test_signaled_rcu(), we do not need to handle such conversion in the caller. The only challenge are those callers that wish to differentiate the error code between the nonblocking busy

[PATCH 3/5] drm/msm: Remove call to reservation_object_test_signaled_rcu before wait

Since fence_wait_timeout_reservation_object_wait_timeout_rcu() with a timeout of 0 becomes reservation_object_test_signaled_rcu(), we do not need to handle such conversion in the caller. The only challenge are those callers that wish to differentiate the error code between the nonblocking busy

[PATCH 5/5] drm/vmwgfx: Remove call to reservation_object_test_signaled_rcu before wait

Since fence_wait_timeout_reservation_object_wait_timeout_rcu() with a timeout of 0 becomes reservation_object_test_signaled_rcu(), we do not need to handle such conversion in the caller. The only challenge are those callers that wish to differentiate the error code between the nonblocking busy

[PATCH v2 1/6] staging/android: remove doc from sw_sync

Hi Pavel, 2016-08-09 Pavel Machek : > On Mon 2016-08-08 18:24:17, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > SW_SYNC should never be used by other pieces of the kernel apart from > > sync_debug as it is only a Sync File Validation Framework, so hide any > > info to avoid confuse

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

Hi Eric, 2016-08-11 Eric Engestrom : > 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

[PATCH] dma-buf: Restart reservation_object_get_fences_rcu() after writes

In order to be completely generic, we have to double check the read seqlock after acquiring a reference to the fence. If the driver is allocating fences from a SLAB_DESTROY_BY_RCU, or similar freelist, then within an RCU grace period a fence may be freed and reallocated. The RCU read side critical

[PATCH v3 0/5] de-stage SW_SYNC validation frawework

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 improvements and the rest is preparation to de-stage

[PATCH v3 1/5] staging/android: do not let userspace trigger WARN_ON

From: Gustavo Padovan Closing the timeline without waiting all fences to signal is not a critical failure, it is just bad usage from userspace so avoid calling WARN_ON in this case. Signed-off-by: Gustavo Padovan --- drivers/staging/android/sw_sync.c | 2 +- 1

[PATCH v3 2/5] staging/android: move trace/sync.h to sync_trace.h

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 Engestrom --- drivers/staging/android/sw_sync.c

[PATCH v3 3/5] staging/android: prepare sw_sync files for de-staging

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. v3: improve header description as sugggested by Eric Signed-off-by: Gustavo Padovan Reviewed-by: Eric

[PATCH v3 4/5] staging/android: add Doc for SW_SYNC ioctl interface

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. v2: take in Eric suggestions for the

[PATCH v3 5/5] dma-buf/sw_sync: de-stage SW_SYNC

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 timeline the SW_SYNC_IOC_CREATE_FENCE ioctl should

[PATCH v3 4/5] staging/android: add Doc for SW_SYNC ioctl interface

On Thu, Aug 11, 2016 at 12:26:43PM -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. >

[Bug 97099] Regression in 9ef8537e6 "drm/radeon: don't use fractional dividers on RS[78]80 if SS is enabled" (RV620)

was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/274e73d6/attachment.html>

[Bug 97055] Black screens on A10-8780P (Carrizo) + R7 M260/M265 (Topaz) Combo

... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160811/1adb23ec/attachment.html>

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

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. v2: take in Eric suggestions for the

[PATCH v4 1/4] drm: extra printk() wrapper macros

We had only DRM_INFO() and DRM_ERROR(), whereas the underlying printk() provides several other useful intermediate levels such as NOTICE and WARNING. So this patch fills out the set by providing both regular and once-only macros for each of the levels INFO, NOTICE, and WARNING, using a common

[Bug 97260] R9 290 low performance in Linux 4.7

nce. Note: I've only tested "The Talos Principle" so far, if you need me to test XCOM 2 or other titles as well, let me know. Do you still need the bisect? -- 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/09c0fd61/attachment-0001.html>

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

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

[PATCH 2/3] drm/i915: Track pinned VMA

Treat the VMA as the primary struct responsible for tracking bindings into the GPU's VM. That is we want to treat the VMA returned after we pin an object into the VM as the cookie we hold and eventually release when unpinning. Doing so eliminates the ambiguity in pinning the object and then

[PATCH 3/3] drm/i915: Introduce i915_ggtt_offset()

This little helper only exists to safely discard the upper unused 32bits of the general 64-bit VMA address - as we know that all Global GTT currently are less than 4GiB in size and so that the upper bits must be zero. In many places, we use a u32 for the global GTT offset and we want to document

[PATCH 2/3] dma-buf: Restart reservation_object_wait_timeout_rcu() after writes

In order to be completely generic, we have to double check the read seqlock after acquiring a reference to the fence. If the driver is allocating fences from a SLAB_DESTROY_BY_RCU, or similar freelist, then within an RCU grace period a fence may be freed and reallocated. The RCU read side critical

[PATCH 3/3] dma-buf: Restart reservation_object_test_signaled_rcu() after writes

In order to be completely generic, we have to double check the read seqlock after acquiring a reference to the fence. If the driver is allocating fences from a SLAB_DESTROY_BY_RCU, or similar freelist, then within an RCU grace period a fence may be freed and reallocated. The RCU read side critical

[PATCH 2/3] drm/i915: Track pinned VMA

Apologies, please ignore these 2. Didn't pass the right start point to git-send-email. -Chris -- Chris Wilson, Intel Open Source Technology Centre

[Bug 97303] battery mode for dpm state froze

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

  1   2   >