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

On Tue, May 03, 2016 at 11:01:32AM -0400, Lyude wrote: > 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

[PATCH] drm/edid : calculate vsync and hsync from range limits block according to the EDID 1.4

On Tue, May 03, 2016 at 11:05:25AM -0400, Vitaly Prosyak wrote: > Do calculation of vsync and hsync from range limits > EDID block according to the spec. EDID 1.4. > > Signed-off-by: Vitaly Prosyak Forgot one: For anything related to edid please cc Adam Jackson. Applies to both patches. -Daniel

[PATCH] drm/edid : calculate vsync and hsync from range limits block according to the EDID 1.4

On Tue, May 03, 2016 at 11:05:25AM -0400, Vitaly Prosyak wrote: > Do calculation of vsync and hsync from range limits > EDID block according to the spec. EDID 1.4. > > Signed-off-by: Vitaly Prosyak Seems unrelated to the previous patch, please submit in a separate series. > --- >

[PATCH] drm/edid : cache edid range limits in drm connector

On Tue, May 03, 2016 at 11:05:24AM -0400, Vitaly Prosyak wrote: > Cache in drm connector the edid range limits properties: > min/max vertical refresh rates and max pixel clock. > It would be used when enter to drr mode. > > Signed-off-by: Vitaly Prosyak Where's the patches that will use this?

[Bug 95198] Shadow of Mordor beta has missing geometry with gl 4.3

the issue right away. -- 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/72f7ad5a/attachment.html>

[PATCH] drm/atomic: use connector references (v3)

On Wed, May 04, 2016 at 06:03:05AM +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 v2 1/4] drm: Add helper for DP++ adaptors

On 5/3/2016 12:38 AM, 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

drm/radeon/kms: add dpm support for KB/KV

Hello Alex Deucher, The patch 41a524abff26: "drm/radeon/kms: add dpm support for KB/KV" from Aug 14, 2013, leads to the following static checker warning: drivers/gpu/drm/radeon/kv_dpm.c:1376 kv_init_fps_limits() error: wrong number of bits for 'cpu_to_be16' (8 vs 16) left=

[Intel-gfx] [PATCH] drm/atomic: use connector references (v3)

Hi, On 3 May 2016 at 21:09, Daniel Vetter wrote: > This patch series seems cursed with lots of embarrassement for reviewers. > I totally missed/forgot the FIXME in drm_atomic_state_default_clear(), > which this patch fixes. Anyway, I'm happy to burn my hands again ;-) Let's share the

[Bug 95015] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

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/4033de2a/attachment.html>

[PATCH 5/9] drm/i915: Enable i915 perf stream for Haswell OA unit

lisecond increments and found that although I still see a lot of spurious reports only waiting 1 or 5 milliseconds, at 10 milliseconds its reduced quite a bit and at 15 milliseconds I don't seem to have any errors. 15 milliseconds is still a long time, but at least not as long as 100. Regards, - Robert -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160503/0071cad5/attachment.html>

[PATCH] drm/edid : cache edid range limits in drm connector

Added Adam. -Original Message- From: Prosyak, Vitaly Sent: Tuesday, May 03, 2016 4:45 PM To: 'Daniel Vetter' Cc: dri-devel at lists.freedesktop.org; Deucher, Alexander Subject: RE: [PATCH] drm/edid : cache edid range limits in drm connector We are going to use min/max vertical refresh

[Bug 95015] [drm:.r600_ring_test [radeon]] *ERROR* radeon: ring 0 test failed (scratch(0x8504)=0xCAFEDEAD)

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/9482dc5b/attachment-0001.html>

[PATCH] drm/edid : cache edid range limits in drm connector

We are going to use min/max vertical refresh rate when enter/exit to the dynamic refresh rate mode ,it is known as 'freesync', enter/exit to full screen games. Right , we may have a helper function which extracts these properties and store wherever need it. But this an alternative solution

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

On Tue, May 03, 2016 at 10:03:30PM +0530, Sharma, Shashank wrote: > > > On 5/3/2016 12:38 AM, 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 > >

[PATCH 5/9] drm/i915: Enable i915 perf stream for Haswell OA unit

o, do not hesitate to contact me if non of the proposed > explanation pans out, I will take the time to read through the OA material > and try my > REing skills on it. As I said, I really want to see this upstream! > > Sorry... > > Martin > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160503/3032f5df/attachment-0001.html>

[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

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 Alex Deucher changed: What|Removed |Added CC||alexdeucher at gmail.com --- Comment #7

[PATCH 00/14] Add/update DRM entries in the MAINTAINERS file

On Fri, Apr 22, 2016 at 12:03:48AM +0100, Emil Velikov wrote: > Hi all, > > A bunch of trivial updates for the MAINTAINERS file - corrected files > lists, git repos. The last few patches 'nominate' developers who have > already been the effective maintainers of the specific drivers. > > With

[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

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #6 from Jani Väinölä --- Also, this machine worked flawlessly with the old fglrx 15.12 drivers. The troubles started when I did the upgrade to Ubuntu 16.04, but I did do fresh install of several distros to try it out. -- You are

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #5 from Jani Väinölä --- Created attachment 215221 --> https://bugzilla.kernel.org/attachment.cgi?id=215221=edit Output of lspci -vv -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #4 from Jani Väinölä --- Created attachment 215211 --> https://bugzilla.kernel.org/attachment.cgi?id=215211=edit Kernel log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #3 from Jani Väinölä --- Created attachment 215201 --> https://bugzilla.kernel.org/attachment.cgi?id=215201=edit xorg.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #2 from Jani Väinölä --- Created attachment 215191 --> https://bugzilla.kernel.org/attachment.cgi?id=215191=edit xrandr outputs after the black screen This is what I get after the black screen (taken with ssh -X) -- You are

[Bug 117591] amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 --- Comment #1 from Jani Väinölä --- Created attachment 215181 --> https://bugzilla.kernel.org/attachment.cgi?id=215181=edit xrandr outputs before the black screen This is what I get with xrandr commands before I get the black screen --

[Bug 117591] New: amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo

https://bugzilla.kernel.org/show_bug.cgi?id=117591 Bug ID: 117591 Summary: amdgpu: Black screens on A10-8700P (Carrizo) + R7 M260/M265 (Topaz) Combo Product: Drivers Version: 2.5 Kernel Version: 4.4.0-21-generic

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

[Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M

e. Cheers, Arthur -- 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/43d20c2a/attachment.html>

[Bug 76490] Hang during boot when DPM is on (R9 270X)

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

[Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M

ves/dri-devel/attachments/20160503/0b828c97/attachment.html>

[Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M

up getting copied several times before getting to the IGP. -- 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/2bd12409/attachment-0001.html>

[Bug 94708] Open source radeon drivers not working properly with Radeon HD 8550M

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

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

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

[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

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

[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

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

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

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

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

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

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

[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 2/2] drm/amdgpu: make sure vertical front porch is at least 1

hw doesn't like a 0 value. Signed-off-by: Alex Deucher Cc: stable at vger.kernel.org --- drivers/gpu/drm/amd/amdgpu/atombios_encoders.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/atombios_encoders.c b/drivers/gpu/drm/amd/amdgpu/atombios_encoders.c index

[PATCH 1/2] drm/radeon: make sure vertical front porch is at least 1

hw doesn't like a 0 value. Signed-off-by: Alex Deucher Cc: stable at vger.kernel.org --- drivers/gpu/drm/radeon/atombios_encoders.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/radeon/atombios_encoders.c b/drivers/gpu/drm/radeon/atombios_encoders.c index

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

[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

[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

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

[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

[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

[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 v2] drm/vc4: Return -EBUSY if there's already a pending flip event.

From: Robert Foss As per the documentation in drm_crtc.h, 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 the whole quote is: * - -EBUSY, if an

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

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

[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

[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 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 v2] drm/vc4: Return -EBUSY if there's already a pending flip event.

- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 818 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160503/c0d82795/attachment.sig>

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

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

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

[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 v3 2/2] dt-bindings: imx: ldb: Add ddc-i2c-bus property

On Fri, Apr 29, 2016 at 09:44:12AM +0200, Philipp Zabel wrote: > Am Donnerstag, den 28.04.2016, 16:48 -0500 schrieb Rob Herring: > > On Wed, Apr 27, 2016 at 04:23:34PM -0400, Akshay Bhat wrote: > > > Document the ddc-i2c-bus property used by imx-ldb driver to read EDID > > > information via I2C

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

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

[PATCH] drm/edid : calculate vsync and hsync from range limits block according to the EDID 1.4

Do calculation of vsync and hsync from range limits EDID block according to the spec. EDID 1.4. Signed-off-by: Vitaly Prosyak --- drivers/gpu/drm/drm_edid.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/drivers/gpu/drm/drm_edid.c

[PATCH] drm/edid : cache edid range limits in drm connector

Cache in drm connector the edid range limits properties: min/max vertical refresh rates and max pixel clock. It would be used when enter to drr mode. Signed-off-by: Vitaly Prosyak --- drivers/gpu/drm/drm_edid.c | 11 +++ include/drm/drm_crtc.h | 5 + 2 files changed, 16

[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

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

[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

  1   2   >