drm/exynos: fimd: vrefresh is zero

On Mon, May 2, 2016 at 10:30 PM, Tobias Jakobi wrote: >> drm_mode_set_crtcinfo() is meant to be used to fill in all the derived >> values. We might or might not want to have a default call for that in >> atomic helpers actually (before we call down into any of the driver's >> check functions for

[PATCH 01/12] staging/android: remove redundant comments on sync_merge_data

On Wed 2016-04-27 13:27:08, Gustavo Padovan wrote: > From: Gustavo Padovan > > struct sync_merge_data already have documentation on top of the > struct definition. No need to duplicate it. > > Signed-off-by: Gustavo Padovan > Reviewed-by: Maarten Lankhorst > @@ -33,8 +33,8 @@ struct

[PATCH 06/12] staging/android: prepare sync_file for de-staging

Hi! > -} > -EXPORT_SYMBOL(sync_file_merge); > - > static const char *android_fence_get_driver_name(struct fence *fence) > { > struct sync_timeline *parent = fence_parent(fence); if this is meant to be used outside android, should it select some better prefix than android_fence_?

[PATCH] drm: Add gpu.tmpl docbook to MAINTAINERS entry

Patches get misrouted and lost otherwise. And use * to future-proof for sphinx (or whatever the documentation nirvana toolchain will be). Cc: Jonathan Corbet Cc: David Airlie Signed-off-by: Daniel Vetter --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS

[Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards

https://bugs.freedesktop.org/show_bug.cgi?id=87682 --- Comment #5 from Thom --- I can confirm this bug: Laptop HP 6735s 2xTurion + RS780M videochip I happen to have the exact same artefacts with any kernelversion higher than 3.13 It affects the buildin LVDS but NOT the VGA-output. I tested

[PATCH v2 11/14] MAINTAINERS: Add maintainer entry for the MSM DRM driver

Rob and Archit are the main developers behind the driver. v2: Removing Archit for now, correcting the status and adding linux-arm-msm@ mailing list. Cc: Rob Clark Cc: Archit Taneja Signed-off-by: Emil Velikov --- MAINTAINERS | 11 +++ 1 file changed, 11 insertions(+) diff --git

[PATCH v2 12/14] MAINTAINERS: Add maintainer entry for the VMWGFX DRM driver

Thomas is one of the original authors of the driver, with recent contributions from Sinclair and Brian. v2: Add Sinclair as maintainer. Add Sinclair+Thomas's tree, use Supported as status. Cc: Sinclair Yeh Cc: Thomas Hellstrom Cc: Brian Paul Cc: "VMware Graphics" Signed-off-by: Emil Velikov

[PATCH 10/14] MAINTAINERS: Add maintainer entry for the Nouveau DRM driver

rm.h > + > DRM DRIVERS FOR NVIDIA TEGRA > M: Thierry Reding > M: Terje Bergström > -- 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/20160503/486714db/attachment-0001.sig>

ubsan report on gfx_v8_0_get_cu_info

While trying to track down some crashes on my Fiji I enabled UBSAN and got this, this led me to look at the function mentioned, and wow totally undefined code land. The code loops over num_shader_engines with i, then uses i * 16 in a calc for a left-shift. On Fiji at least num_shader_engines is

[Bug 71789] [r300g] Visuals not found in (default) depth = 24

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

[PATCH v3 0/7] drm/i2c: adv7511: ADV7533 support

On 9 March 2016 at 18:57, Archit Taneja wrote: > ADV7533 is a DSI to HDMI encoder chip. It's like ADV7511, but with an > additional DSI RX block that takes in DSI video mode output. > > Trying to get this driver merged has had some challenges: > > - ADV7533 has an I2C control bus, but acts as a

[PATCH] drm/amdgpu: set metadata pointer to NULL after freeing.

From: Dave Airlie Without this there was a double free of the metadata, which ended up freeing the fd table for me here, and taking out the machine more often than not. I reproduced with X.org + modesetting DDX + latest llvm/mesa, also required using dri3. Cc: stable at

[Bug 73785] [HyperZ] Team Fortress 2 causes random GPU stalls on radeonsi

: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160503/e05154fe/attachment-0001.html>

[Bug 75112] Meta Bug for HyperZ issues on r600g and radeonsi

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

linux-next: manual merge of the drm-misc tree with the drm-intel tree

Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/i915/intel_display.c between commits: f7e5838bb37d ("drm/i915: Simplify reset_counter handling during atomic modesetting") from the drm-intel tree and commit: 81072bfd13f2 ("drm/i915: Rename async

linux-next: manual merge of the drm-msm tree with the drm-misc tree

Hi Rob, Today's linux-next merge of the drm-msm tree got a conflict in: drivers/gpu/drm/msm/msm_atomic.c between commit: a3ccfb9feb46 ("drm/msm: Rename async to nonblock.") from the drm-misc tree and commit: afadc4bb9380 ("drm/msm: remove fence_cbs") from the drm-msm tree. I fixed it

[PATCH 1/6] drm/fb: fix missing /** in kerneldoc comment.

From: Dave Airlie Signed-off-by: Dave Airlie --- include/drm/drm_crtc.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h index 297e527..6279989 100644 --- a/include/drm/drm_crtc.h +++

[PATCH 2/6] drm/modes: add connector reference counting. (v2)

From: Dave Airlie This uses the previous changes to add reference counts to drm connector objects. v2: move fbdev changes to their own patch. add some kerneldoc Reviewed-by: Daniel Vetter Signed-off-by: Dave Airlie --- drivers/gpu/drm/drm_atomic.c | 19

[PATCH 3/6] drm/fb_helper: add connector reference counting. (v2)

From: Dave Airlie This takes a reference count when fbdev adds the connector, and drops it when it removes the connector. It also drops the now unneeded code to find connectors and remove the from the modeset as they are reference counted. v2: drop references when removing

[PATCH 4/6] drm/crtc: take references to connectors used in a modeset. (v2)

From: Dave Airlie This just takes a reference on the connector when we set a mode in the non-atomic paths. v2: Follow Daniel Stone's suggestions on when to take/drop references. Signed-off-by: Dave Airlie --- drivers/gpu/drm/drm_crtc_helper.c | 19 +++ 1

[PATCH 5/6] drm/atomic: use connector references (v2)

From: Dave Airlie Take a reference when setting a crtc on a connecter, also take one when duplicating if a crtc is set, and drop one on destroy if a crtc is set. v2: take Daniel Stone's advice and simplify the ref/unref dances, also take care of NULL as connector to state

[PATCH 6/6] drm/i915/mst: use reference counted connectors. (v3)

From: Dave Airlie Don't just free the connector when we get the destroy callback. Drop a reference to it, and set it's mst_port to NULL so no more mst work is done on it. v2: core mst accepts NULLs fine. Cleanup EDID code properly. v3: drop the extra reference we were

[PATCH 02/23] drm: omapdrm: fb: Don't store format BPP for each plane

-- 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/20160503/56e7eef5/attachment.sig>

[GIT PULL] drm/rockchip: some fixes

Hi Dave Here are some little fixes for rockchip drm, looks good for me, and seems there is no doubt on them, So I'd like you can land them. The following changes since commit b89359bdf0f1e95a4c5f92300594ba9dde323fc4: Merge branch 'for-next' of http://git.agner.ch/git/linux-drm-fsl-dcu

[Bug 95247] System hangs after ~10 minutes when using Radeon R9 390

perfectly fine with the integrated Intel GPU. -- 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/20160503/30664fd9/attachment.html>

[Bug 71789] [r300g] Visuals not found in (default) depth = 24

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

[Bug 95247] System hangs after ~10 minutes when using Radeon R9 390

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/20160503/9abd5435/attachment.html>

[Bug 95247] System hangs after ~10 minutes when using Radeon R9 390

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

[PATCH v3 0/7] drm/i2c: adv7511: ADV7533 support

On 05/03/2016 07:22 AM, Xinliang Liu wrote: > On 9 March 2016 at 18:57, Archit Taneja wrote: >> ADV7533 is a DSI to HDMI encoder chip. It's like ADV7511, but with an >> additional DSI RX block that takes in DSI video mode output. >> >> Trying to get this driver merged has had some challenges:

[PATCH v3 4/7] drm/i2c: adv7511: Create a MIPI DSI device

Hi Laurent, On 04/22/2016 10:40 AM, Archit Taneja wrote: > Hi Laurent, > > > On 04/22/2016 03:59 AM, Laurent Pinchart wrote: >> Hi Archit, >> >> Thank you for the patch. >> >> On Wednesday 09 Mar 2016 16:27:15 Archit Taneja wrote: >>> In order to pass DSI specific parameters to the DSI host, we

[PATCH] drm/amdgpu: set metadata pointer to NULL after freeing.

Am 03.05.2016 um 04:44 schrieb Dave Airlie: > From: Dave Airlie > > Without this there was a double free of the metadata, > which ended up freeing the fd table for me here, and taking > out the machine more often than not. > > I reproduced with X.org + modesetting DDX + latest llvm/mesa, > also

[PATCH] drm/vc4: Return -EBUSY if there's already a pending flip event.

Op 02-05-16 om 21:25 schreef robert.foss at collabora.com: > From: Robert Foss > > As per the docs, atomic_commit should return -EBUSY "if an asycnhronous > update is requested and there is an earlier update pending". > > Signed-off-by: Robert Foss > --- > drivers/gpu/drm/vc4/vc4_crtc.c | 6

[Intel-gfx] [PATCH v2 1/4] drm: Add helper for DP++ adaptors

On Mon, 02 May 2016, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > Add a helper which aids in the identification of DP dual mode > (aka. DP++) adaptors. There are several types of adaptors > specified: type 1 DVI, type 1 HDMI, type 2 DVI, type 2 HDMI > > Type 1 adaptors have

linux-next: manual merge of the drm-misc tree with the drm-intel tree

On Tue, May 03, 2016 at 01:24:12PM +1000, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drm-misc tree got a conflict in: > > drivers/gpu/drm/i915/intel_display.c > > between commits: > > f7e5838bb37d ("drm/i915: Simplify reset_counter handling during atomic >

[Bug 95017] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).

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

[PATCH 1/6] drm/fb: fix missing /** in kerneldoc comment.

On Tue, May 03, 2016 at 02:28:21PM +1000, Dave Airlie wrote: > From: Dave Airlie > > Signed-off-by: Dave Airlie Reviewed-by: Daniel Vetter > --- > include/drm/drm_crtc.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/drm/drm_crtc.h b/include/drm/drm_crtc.h

[Intel-gfx] [PATCH 3/6] drm/fb_helper: add connector reference counting. (v2)

On Tue, May 03, 2016 at 02:28:23PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This takes a reference count when fbdev adds the connector, > and drops it when it removes the connector. > > It also drops the now unneeded code to find connectors > and remove the from the modeset as they are

[PATCH 4/6] drm/crtc: take references to connectors used in a modeset. (v2)

On Tue, May 03, 2016 at 02:28:24PM +1000, Dave Airlie wrote: > From: Dave Airlie > > This just takes a reference on the connector when we set a mode > in the non-atomic paths. > > v2: Follow Daniel Stone's suggestions on when to take/drop > references. > > Signed-off-by: Dave Airlie I've

[Bug 87682] Horizontal lines in radeon driver on kernel 3.15 and upwards

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

[Bug 95017] [drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on GFX ring (-35).

both the 5,6 and the 5,8 use a Mobility Radeon 9700. -- 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/20160503/75d1c

[PATCH 5/6] drm/atomic: use connector references (v2)

On Tue, May 03, 2016 at 02:28:25PM +1000, Dave Airlie wrote: > From: Dave Airlie > > Take a reference when setting a crtc on a connecter, > also take one when duplicating if a crtc is set, > and drop one on destroy if a crtc is set. > > v2: take Daniel Stone's advice and simplify the >

[PATCH] drm/fsl-dcu: add COMMON_CLK dependency

On Mon, May 02, 2016 at 02:22:04PM -0700, Stefan Agner wrote: > On 2016-05-02 04:00, Arnd Bergmann wrote: > > The fsl dcu now uses the clk-provider interfaces, which are not available > > when CONFIG_COMMON_CLK is disabled: > > > > drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c: In function

[GIT PULL] imx-drm module autoloading fix

Hi Dave, here is the imx-ipuv3-crtc autoloading fix so you don't have to revert commit 304e6be652e2 ("gpu: ipu-v3: Assign of_node of child platform devices to corresponding ports"). regards Philipp The following changes since commit 02da2d72174c61988eb4456b53f405e3ebdebce4: Linux 4.6-rc5

[PATCH] drm/atomic: Add WARN_ON when state->acquire_ctx is not set.

When I was writing an atomic wrapper for rmfb, I ran into the following backtrace from lockdep: = [ INFO: possible recursive locking detected ] 4.5.0-patser+ #4696 Tainted: G U - kworker/2:2/2608 is trying

[PATCH v3 1/2] drm: bridge: Add sii902x driver

Hi Maxime, On Mon, 2 May 2016 13:05:57 +0200 Maxime Ripard wrote: > > +static void sii902x_reset(struct sii902x *sii902x) > > +{ > > + gpiod_set_value(sii902x->reset_gpio, 1); > > + > > + msleep(100); > > Sleeping for 100ms seems like a lot. Is it required, or is it just a > leftover

[PATCH v3 1/2] drm: bridge: Add sii902x driver

On Tue, May 3, 2016 at 11:39 AM, Boris Brezillon wrote: >> > + .detect = sii902x_connector_detect, >> > + .fill_modes = drm_helper_probe_single_connector_modes, >> > + .destroy = sii902x_connector_destroy, >> > +}; >> >> I'm guessing this is to support both atomic and !atomic drivers. I >>

[PATCH v3 1/2] drm: bridge: Add sii902x driver

On Tue, 3 May 2016 11:53:18 +0200 Daniel Vetter wrote: > On Tue, May 3, 2016 at 11:39 AM, Boris Brezillon > wrote: > >> > + .detect = sii902x_connector_detect, > >> > + .fill_modes = drm_helper_probe_single_connector_modes, > >> > + .destroy = sii902x_connector_destroy, > >> > +}; > >>

[PATCH 5/6] drm/atomic: use connector references (v2)

>>*/ >> + if (connector && state->crtc) { >> + drm_connector_unreference(state->connector); >> + } > > Bikeshed: no need for {} and you don't need to check that connector is > NULL either. Tbh all the destroy_state helpers don't really need their > object argument, only

[PATCH 0/9] drm/msm: Fix issues with DT bindings

Currently, none of the upstream Qualcomm DT files have the display device nodes populated, even when the DT binding documents are upstream. I am not aware of all the issues with the bindings which has prevented it from getting merged, but 2 properties "connectors" (maintains a list of all the

[PATCH 1/9] drm/msm: Get mdss components via parsing ports

The driver currently identifies all the mdss components it needs by parsing a phandle list from the 'connectors' DT property. Instead of this, describe a list of ports that the MDP hardware provides to the external world. These ports are linked to external encoder interfaces such as DSI, HDMI in

[PATCH 2/9] drm/msm: Drop the gpu binding

The driver currently identifies the GPU components it needs by parsing a phandle list from the 'gpus' DT property. This isn't the right binding to go with. So, for now, just search all device nodes and find the gpu node we need by parsing a list of compatible strings. Once we know how to link

[PATCH 3/9] drm/msm/mdp: mdp4: Update LCDC/LVDS port parsing

The LCDC port is the first in the list of the output ports in MDP4. Mention this explicitly in the driver. Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 8 ++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c

[PATCH 4/9] dt-bindings: msm/mdp: Remove connector and gpu bindings

The MDP DT node now contains a list of ports that describe how it connects to external encoder interfaces like DSI and HDMI. These follow the standard of_graph bindings, and allow us to get rid of the 'connectors' phandle that contained a list of all the external encoders connected to MDP. The

[PATCH 5/9] dt-bindings: msm/dsi: Some binding doc cleanups

Some cleanups: - Use simpler names for DT nodes in the example - Fix phandle for specifying data lane mapping in the example. - Use references instead of dumping Document links everywhere Signed-off-by: Archit Taneja --- .../devicetree/bindings/display/msm/dsi.txt| 23

[PATCH 6/9] drm/msm/dsi: Modify port parsing

The DSI interface is going to have two ports defined in its device node. The first port is always going to be the link between the MDP output and the input to DSI, the second port is going to be the link between the DSI output and the connected panel/bridge: - -

[PATCH 7/9] drm/msm/dsi: Use generic PHY bindings

The DSI host links to the DSI PHY device using a custom binding. Switch to the generic PHY bindings. The DSI PHY driver itself doesn't use the common PHY framework for now. Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/dsi/dsi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff

[PATCH 8/9] dt-bindings: msm/dsi: Modify port and PHY bindings

The DSI node now has two ports that describe the connection between the MDP interface output and the DSI input, and the connection between the DSI output and the connected panel/bridge. Update the properties and the example. Also, use generic PHY bindings instead of the custom one.

[PATCH 9/9] dt-bindings: msm/dsi: Add assigned clocks bindings

The PLL in the DSI PHY block generates 2 clock outputs (Byte and Pixel clocks) that are fed into the Multimedia Clock Controller (MMCC). The MMCC uses these as source clocks for some of its RCGs to generate clocks that finally feed to the DSI host controller. Use the assigned clocks DT bindings

[Bug 94900] HD6950 GPU lockup with various steam games (octodad, saints row 4)

tps://lists.freedesktop.org/archives/dri-devel/attachments/20160503/5f4915fd/attachment.html>

[Bug 94900] HD6950 GPU lockup with various steam games (octodad, saints row 4)

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

[PATCH 02/23] drm: omapdrm: fb: Don't store format BPP for each plane

On Tue, May 03, 2016 at 09:08:06AM +0300, Tomi Valkeinen wrote: > > On 03/05/16 00:01, Rob Clark wrote: > > On Mon, May 2, 2016 at 11:43 AM, Tomi Valkeinen > > wrote: > >> Hi Laurent, > >> > >> On 26/04/16 23:35, Laurent Pinchart wrote: > >>> The number of bits per pixel is identical for all

[PATCH] drm/core: Do not preserve framebuffer on rmfb, v3.

Hi, Sorry for the late response, been very busy with other stuff lately. I've tested this version against drm-fixes and it indeed fixes the problem, as far as I can tell. Tested-by: Thomas Hellstrom On 03/31/2016 01:26 PM, Maarten Lankhorst wrote: > It turns out that preserving framebuffers

[PATCH 5/6] drm/atomic: use connector references (v2)

On Tue, May 3, 2016 at 12:09 PM, Dave Airlie wrote: >>>*/ >>> + if (connector && state->crtc) { >>> + drm_connector_unreference(state->connector); >>> + } >> >> Bikeshed: no need for {} and you don't need to check that connector is >> NULL either. Tbh all the

[Intel-gfx] [PATCH] drm/atomic: Add WARN_ON when state->acquire_ctx is not set.

On Tue, May 03, 2016 at 11:12:31AM +0200, Maarten Lankhorst wrote: > When I was writing an atomic wrapper for rmfb, I ran into the > following backtrace from lockdep: > > = > [ INFO: possible recursive locking detected ] > 4.5.0-patser+ #4696 Tainted: G

[PATCH 2/9] drm/msm: Drop the gpu binding

On Tue, May 3, 2016 at 5:57 AM, Archit Taneja wrote: > The driver currently identifies the GPU components it needs by parsing > a phandle list from the 'gpus' DT property. > > This isn't the right binding to go with. So, for now, just search all > device nodes and find the gpu node we need by

[PATCH v3 1/2] drm: bridge: Add sii902x driver

On Tue, May 03, 2016 at 12:03:08PM +0200, Boris Brezillon wrote: > On Tue, 3 May 2016 11:53:18 +0200 > Daniel Vetter wrote: > > > On Tue, May 3, 2016 at 11:39 AM, Boris Brezillon > > wrote: > > >> > + .detect = sii902x_connector_detect, > > >> > + .fill_modes =

[Intel-gfx] [PATCH 1/3] drm/i915: Check pixel rate for DP to VGA dongle

On Tue, May 03, 2016 at 02:46:36PM +0300, Mika Kahola wrote: > Prep work to improve DP branch device handling. > > 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 >

[Intel-gfx] [PATCH 3/3] drm/i915: Check HDMI TMDS clock rate from DPCD

On Tue, May 03, 2016 at 02:46:38PM +0300, Mika Kahola wrote: > Read TMDS clock rate from DPCD for HDMI to filter out > modes that might require higher TMDS clock rate than > supported. > > Signed-off-by: Mika Kahola > --- > drivers/gpu/drm/i915/intel_dp.c | 3 +++ >

[Intel-gfx] [PATCH v2 1/4] drm: Add helper for DP++ adaptors

On Tue, May 03, 2016 at 10:46:26AM +0300, Jani Nikula wrote: > On Mon, 02 May 2016, ville.syrjala at linux.intel.com wrote: > > From: Ville Syrjälä > > > > Add a helper which aids in the identification of DP dual mode > > (aka. DP++) adaptors. There are several types of adaptors > > specified:

[PATCH 1/2] drm/exynos/dpi: use of_graph_get_endpoint_by_regs helper

This allows to remove the local of_graph_get_port_by_reg(), of_graph_get_endpoint_by_reg(), of_get_child_by_name_reg(), and of_graph_get_remote_port_parent() functions. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/exynos/exynos_drm_dpi.c | 69 + 1 file

[PATCH 2/2] drm/exynos/dsi: use of_graph_get_endpoint_by_regs helper

This allows to remove the local of_graph_get_port_by_reg(), of_graph_get_endpoint_by_reg(), and of_get_child_by_name_reg() functions. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/exynos/exynos_drm_dsi.c | 57 ++--- 1 file changed, 3 insertions(+), 54 deletions(-)

[PATCH 1/2] drm/imx: imx-ldb: use of_graph_get_endpoint_by_regs helper

Instead of using of_graph_get_port_by_id() to get the port and then of_get_child_by_name() to get the first endpoint, get to the endpoint in a single step. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/imx-ldb.c | 35 ++- 1 file changed, 18 insertions(+),

[PATCH 2/2] drm/imx: parallel-display: use of_graph_get_endpoint_by_regs helper

Instead of using of_graph_get_port_by_id() to get the port and then of_get_child_by_name() to get the first endpoint, get to the endpoint in a single step. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/parallel-display.c | 24 1 file changed, 12 insertions(+), 12

[PATCH 2/3] drm: Add DP port types from DP 1.3 specification

DP specification 1.3 defines DP downstream ports for DP++ and wireless devices. Let's add these to port definitions. Signed-off-by: Mika Kahola --- include/drm/drm_dp_helper.h | 2 ++ 1 file changed, 2 insertions(+) diff --git a/include/drm/drm_dp_helper.h b/include/drm/drm_dp_helper.h index

fsl-dcu not works on latest "drm-next"

l) from [<80800a61>] (kernel_init_freeable+0xd1/0x168) [<80800a61>] (kernel_init_freeable) from [<80558d13>] (kernel_init+0x7/0xb4) [<80558d13>] (kernel_init) from [<80205261>] (ret_from_fork+0x11/0x30) ---[ end trace b7946726c4e290c4 ]--- Console: switching to colour frame

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

Prep work to improve DP branch device handling. 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 register defines the pixel

[nexus7-flo] backlight brightness

On Mon, May 2, 2016 at 12:56 PM, Thierry Reding wrote: > On Fri, Apr 29, 2016 at 08:04:09AM -0400, Rob Clark wrote: >> On Fri, Apr 29, 2016 at 1:32 AM, Vinay Simha wrote: >> > hi, >> > >> > In nx7, backlight brightness control is controlled by dcs commands of >> >

[PATCH 0/3] drm/i915: DP branch devices

This series of patches reads either pixel rate or TMDS clock rate from DPCD. Pixel rate is defined for DP to VGA dongles and TMDS clock rate for others except wireless dongle. The mode that requires either higher pixel rate or TMDS clock rate are filtered out during the mode validity check. Mika

[PATCH 3/3] drm/i915: Check HDMI TMDS clock rate from DPCD

Read TMDS clock rate from DPCD for HDMI to filter out modes that might require higher TMDS clock rate than supported. Signed-off-by: Mika Kahola --- drivers/gpu/drm/i915/intel_dp.c | 3 +++ drivers/gpu/drm/i915/intel_drv.h | 1 + drivers/gpu/drm/i915/intel_hdmi.c | 7 --- 3 files

[PATCH 3/9] drm/msm/mdp: mdp4: Update LCDC/LVDS port parsing

Am Dienstag, den 03.05.2016, 16:27 +0530 schrieb Archit Taneja: > The LCDC port is the first in the list of the output ports in MDP4. > Mention this explicitly in the driver. > > Signed-off-by: Archit Taneja > --- > drivers/gpu/drm/msm/mdp/mdp4/mdp4_kms.c | 8 ++-- > 1 file changed, 6

[PATCH v2] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver.

From: Eric Anholt Signed-off-by: Eric Anholt [Emil Velikov: drop wildcard, add UAPI and Documentation files] Signed-off-by: Emil Velikov --- This patch is rebased/applied on top of the maintainer series from earlier. --- MAINTAINERS | 8 1 file changed, 8

[PATCH 8/9] dt-bindings: msm/dsi: Modify port and PHY bindings

Am Dienstag, den 03.05.2016, 16:28 +0530 schrieb Archit Taneja: > The DSI node now has two ports that describe the connection between the > MDP interface output and the DSI input, and the connection between the DSI > output and the connected panel/bridge. Update the properties and the > example. >

[Intel-gfx] [PATCH 5/6] drm/atomic: use connector references (v2)

Hi, On 3 May 2016 at 05:28, Dave Airlie wrote: > From: Dave Airlie > > Take a reference when setting a crtc on a connecter, > also take one when duplicating if a crtc is set, > and drop one on destroy if a crtc is set. > > v2: take Daniel Stone's advice and simplify the > ref/unref dances, also

[PATCH] drm/i915: Discard previous atomic state on resume if connectors change

If an MST device is disconnected while the machine is suspended, the number of connectors will change as well after we call intel_dp_mst_resume(). This means that any previous atomic state we had before suspending is no longer valid, since it'll still be pointing to missing connectors. We need to

[PATCH 5/9] dt-bindings: msm/dsi: Some binding doc cleanups

Am Dienstag, den 03.05.2016, 16:27 +0530 schrieb Archit Taneja: > Some cleanups: > > - Use simpler names for DT nodes in the example > - Fix phandle for specifying data lane mapping in the example. > - Use references instead of dumping Document links everywhere > > Signed-off-by: Archit Taneja

[PATCH] drm/vc4: Return -EBUSY if there's already a pending flip event.

On 05/02/2016 08:57 PM, Eric Anholt wrote: > robert.foss at collabora.com writes: > >> From: Robert Foss >> >> As per the docs, atomic_commit should return -EBUSY "if an asycnhronous >> update is requested and there is an earlier update pending". > > Note: docs cited here are drm_crtc.h, and

[PATCH] drm/imx: ipuv3-plane: enable UYVY and VYUY formats

Advertise the DRM_FORMAT_UYVY and DRM_FORMAT_VYUY formats to userspace. Signed-off-by: Philipp Zabel --- drivers/gpu/drm/imx/ipuv3-plane.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/imx/ipuv3-plane.c b/drivers/gpu/drm/imx/ipuv3-plane.c index 681ec6e..8c24df7 100644

[Intel-gfx] [PATCH 1/3] drm/i915: Check pixel rate for DP to VGA dongle

On Tue, May 03, 2016 at 04:23:34PM +0300, Ville Syrjälä wrote: > On Tue, May 03, 2016 at 02:46:36PM +0300, Mika Kahola wrote: > > Prep work to improve DP branch device handling. > > > > Filter out a mode that exceeds the max pixel rate setting > > for DP to VGA dongle. This is defined in DPCD

[Intel-gfx] [PATCH] drm/i915: Discard previous atomic state on resume if connectors change

On Tue, May 03, 2016 at 10:03:40AM -0400, Lyude wrote: > If an MST device is disconnected while the machine is suspended, the > number of connectors will change as well after we call > intel_dp_mst_resume(). This means that any previous atomic state we had > before suspending is no longer valid,

[Intel-gfx] [PATCH 1/3] drm/i915: Check pixel rate for DP to VGA dongle

On Tue, May 03, 2016 at 04:28:00PM +0200, Daniel Vetter wrote: > On Tue, May 03, 2016 at 04:23:34PM +0300, Ville Syrjälä wrote: > > On Tue, May 03, 2016 at 02:46:36PM +0300, Mika Kahola wrote: > > > Prep work to improve DP branch device handling. > > > > > > Filter out a mode that exceeds the

[PATCH 2/3] drm: Add DP port types from DP 1.3 specification

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

[PATCH] st/omx/enc: fix incorrect reference picture order for B frames

Stacking frames is for driver that's capable to do dual instances encoding. Such feature is not enabled for B frames currently. Signed-off-by: Leo Liu Cc: "11.1 11.2" --- src/gallium/state_trackers/omx/vid_enc.c | 19 --- 1 file changed, 12 insertions(+), 7 deletions(-) diff

[PATCH v3 1/4] drm: Add helper for DP++ adaptors

From: Ville Syrjälä Add a helper which aids in the identification of DP dual mode (aka. DP++) adaptors. There are several types of adaptors specified: type 1 DVI, type 1 HDMI, type 2 DVI, type 2 HDMI Type 1 adaptors have a max TMDS clock limit of 165MHz, type 2

[PATCH] Revert "drm/i915: start adding dp mst audio"

Right now MST audio is causing too many kernel panics to really keep around in the kernel. On top of that, even after fixing said panics it's still basically non-functional (at least on all the setups I've tested it on). Revert until we have a proper solution for this. This reverts commit

[Intel-gfx] [PATCH] drm/i915: Discard previous atomic state on resume if connectors change

Yeah airlied said the same thing. This patch is more intended for just 4.6 since the refcounting patch isn't very likely to get into 4.6. On Tue, 2016-05-03 at 16:29 +0200, Daniel Vetter wrote: > On Tue, May 03, 2016 at 10:03:40AM -0400, Lyude wrote: > > > > If an MST device is disconnected

[PATCH] st/omx/enc: fix incorrect reference picture order for B frames

Never mind. Sorry about it. On 05/03/2016 10:49 AM, Leo Liu wrote: > Stacking frames is for driver that's capable to do dual instances > encoding. Such feature is not enabled for B frames currently. > > Signed-off-by: Leo Liu > Cc: "11.1 11.2" > --- > src/gallium/state_trackers/omx/vid_enc.c

[PATCH v2 12/14] MAINTAINERS: Add maintainer entry for the VMWGFX DRM driver

Reviewed-by: Sinclair Yeh On Tue, May 03, 2016 at 12:15:39AM +0100, Emil Velikov wrote: > Thomas is one of the original authors of the driver, with recent > contributions from Sinclair and Brian. > > v2: Add Sinclair as maintainer. Add Sinclair+Thomas's tree, use > Supported as status. > > Cc:

[PATCH] drm: sun4i: print DMA address correctly

The newly added sun4i drm driver prints a dma address using the %x format string, which cannot work when dma_addr_t is 64 bit, and gcc warns about this configuration: drm/sun4i/sun4i_backend.c: In function 'sun4i_backend_update_layer_buffer': drm/sun4i/sun4i_backend.c:193:84: error: format '%x'

[PATCH] drm/amdgpu: set metadata pointer to NULL after freeing.

On Tue, May 3, 2016 at 3:06 AM, Christian König wrote: > Am 03.05.2016 um 04:44 schrieb Dave Airlie: >> >> From: Dave Airlie >> >> Without this there was a double free of the metadata, >> which ended up freeing the fd table for me here, and taking >> out the machine more often than not. >> >>

[PATCH] drm/gem: support BO freeing without dev->struct_mutex

On Mon, May 2, 2016 at 4:40 AM, Daniel Vetter wrote: > Finally all the core gem and a lot of drivers are entirely free of > dev->struct_mutex depencies, and we can start to have an entirely > lockless unref path. > > To make sure that no one who touches the core code accidentally breaks >

  1   2   >