[PATCH 1/1] drm/mediatek: do not dereference NULL

After having verified that dpi is NULL we should not dereference it. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/mediatek/mtk_dpi.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/mediatek/mtk_dpi.c b/drivers/gpu/drm/mediatek/mtk_dpi.c index

[PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

On Wed, May 18, 2016 at 10:31 PM, Heinrich Schuchardt wrote: > Only dereference sender after checking if sender is NULL. Hi Heinrich I think we had a patch that did something similar a while ago. Don't remember what happened to it. We do check for !sender right before calling this function (at

[PATCH 1/1] drm/gma500: mdfld: avoid possible null pointer dereference

Only dereference sender after checking if sender is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/gma500/mdfld_dsi_pkg_sender.c

[PATCH] drm: Nuke ->vblank_disable_allowed

This was added in commit 0a3e67a4caac273a3bfc4ced3da364830b1ab241 Author: Jesse Barnes Date: Tue Sep 30 12:14:26 2008 -0700 drm: Rework vblank-wait handling to allow interrupt reduction. to stay backwards-compatible with old UMS code that didn't even tell the kernel when it did a

[PATCH] drm/mm: avoid possible null pointer dereference

Do not dereference node before the check if node is NULL. Signed-off-by: Heinrich Schuchardt --- drivers/gpu/drm/drm_mm.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/drm_mm.c b/drivers/gpu/drm/drm_mm.c index 04de6fd..cb39f45 100644 ---

[PULL] topic/drm-misc

Hi Dave, Update drm-misc pull with a few more fixes included, plus the two from Arnd for the fallout from the drm_gem_object_lookup() refactor that I failed to spot :( Cheers, Daniel The following changes since commit 99ee87295017e36abb6925e6139ca303cb55aee7: Merge tag

[PATCH] drm: Nuke ->vblank_disable_allowed

This was added in commit 0a3e67a4caac273a3bfc4ced3da364830b1ab241 Author: Jesse Barnes Date: Tue Sep 30 12:14:26 2008 -0700 drm: Rework vblank-wait handling to allow interrupt reduction. to stay backwards-compatible with old UMS code that didn't even tell the kernel when it did a

[PATCH] gpu/nouveau/nouveau_acpi.c: Fix Type Mismatch ACPI warning

nouveau_optimus_dsm is using ACPI_TYPE_BUFFER, and this triggers warnings on ACPI: [7.730564] ACPI: \_SB_.PCI0.RP05.PEGP: failed to evaluate _DSM [7.730570] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (201509

[PATCH 5/5] drm/i915: Move psr.link_standby setup to intel_psr_match_conditions()

From: Ville Syrjälä Determine the value of psr.link_standby at runtime rather than at init time. This helps in testing since you can change between link-off and link-standby at runtime. Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/i915/intel_psr.c | 41

[PATCH 4/5] drm/i915: Ask the sink whether training is required when exiting PSR main-link off mode

From: Ville Syrjälä The sink can tell us if link training needs to be performed when exiting PSR main-link off mode. Currently we get that information from the VBT, but at least on my HSW the VBT says one thing, the sink another. And in practice the sink doesn't

[PATCH 3/5] drm/dp: Add drm_dp_psr_need_train_on_exit()

From: Ville Syrjälä Add a small helper to parse from the DPCD whether link training is required when exiting PSR main-link off mode. Cc: Daniel Vetter Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_dp_helper.c | 14 ++

[PATCH 2/5] drm/i915: Check PSR setup time vs. vblank length

From: Ville Syrjälä Bspec says: "Restriction : SRD must not be enabled when the PSR Setup time from DPCD 00071h is greater than the time for vertical blank minus one line." Let's check for that and disallow PSR if we exceed the limit. Cc: Daniel Vetter

[PATCH 1/5] drm/dp: Add drm_dp_psr_setup_time()

From: Ville Syrjälä Add a small helper to parse the PSR setup time from the DPCD PSR capabilities and return the value in microseconds. Cc: Daniel Vetter Reviewed-by: Daniel Vetter Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_dp_helper.c | 28

[PATCH 0/5] drm/i915: Additional PSR stuff

From: Ville Syrjälä Some more PSR stuff. Some of this depends on Daniel's PSR fixes [1]. The most important thing here for my HSW HSB machine is the drm_dp_psr_need_train_on_exit() check, since apparently the VBT on that thing is no good. [1]

[RFC 2/3] drm/mediatek: add support for Mediatek SoC MT2701

On 18 May 2016 at 09:33, YT Shen wrote: >> > @@ -108,6 +108,10 @@ int mtk_drm_gem_dumb_create(struct drm_file >> > *file_priv, struct drm_device *dev, >> > int ret; >> > >> > args->pitch = DIV_ROUND_UP(args->width * args->bpp, 8); >> > + /* >> > + * align to 8 bytes

[PATCH 1/5] headers_check: don't warn about c++ guards

On 18 May 2016 at 17:07, Arnd Bergmann wrote: > A recent addition to the DRM tree for 4.7 added 'extern "C"' guards > for c++ to all the DRM headers, and that now causes warnings > in 'make headers_check': > > usr/include/drm/amdgpu_drm.h:38: userspace cannot reference function or > variable

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/1960094d/attachment.html>

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

s 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/20160518/13202386/attachment.html>

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/7242b0f6/attachment.html>

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

d on this, it seems that the user-space component (mesa + llvm) is the bottleneck. -- 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

[Intel-gfx] [PATCH 5/5] drm/i915: Move psr.link_standby setup to intel_psr_match_conditions()

On Wed, May 18, 2016 at 09:34:22PM +0300, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > Determine the value of psr.link_standby at runtime rather than at init > time. This helps in testing since you can change between link-off and > link-standby at runtime. > >

[PATCH 4/5] drm/i915: Ask the sink whether training is required when exiting PSR main-link off mode

On Wed, May 18, 2016 at 09:34:21PM +0300, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > The sink can tell us if link training needs to be performed when > exiting PSR main-link off mode. Currently we get that information > from the VBT, but at least on my HSW the VBT says

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/df5ba3ca/attachment-0001.html>

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

t part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/b5452191/attachment.html>

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poorly on any GPU with GCN >=1.1

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

[Bug 95474] Bioshock Infinite and DiRT Showdown perform very poor on any GPU with GCN >=1.1

org See http://www.phoronix.com/scan.php?page=article=nv-amd-23ppw -- 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/20160518/b8

[PATCH 5/5] drm: remove unused dev variables

On Wed, May 18, 2016 at 06:07:33PM +0200, Arnd Bergmann wrote: > After drm_gem_object_lookup() was changed along with all its callers, > we have several drivers that have unused variables: > > drm/armada/armada_crtc.c: In function 'armada_drm_crtc_cursor_set': > drm/armada/armada_crtc.c:900:21:

drm/dp/mst: change MST detection scheme (v2)

From: Mykola Lysenko 1. Get edid for all connected MST displays, not only on logical ports, in the same thread as MST topology detection is done: There are displays that have branches inside w/o logical ports. So in case another SST display

[PATCH 5/5] drm: remove unused dev variables

After drm_gem_object_lookup() was changed along with all its callers, we have several drivers that have unused variables: drm/armada/armada_crtc.c: In function 'armada_drm_crtc_cursor_set': drm/armada/armada_crtc.c:900:21: error: unused variable 'dev' [-Werror=unused-variable]

[PATCH 4/5] drm: exynos: mark pm functions as __maybe_unused

The rework of the exynos DRM clock handling introduced warnings for configurations that have CONFIG_PM disabled: drivers/gpu/drm/exynos/exynos_hdmi.c:736:13: error: 'hdmi_clk_disable_gates' defined but not used [-Werror=unused-function] static void hdmi_clk_disable_gates(struct hdmi_context

[PATCH 3/5] drm: mediatek: fixup drm_gem_object_lookup API change

The drm_gem_object_lookup() function prototype changed while this driver was added, so it fails to build now: drivers/gpu/drm/mediatek/mtk_drm_gem.c: In function 'mtk_drm_gem_dumb_map_offset': drivers/gpu/drm/mediatek/mtk_drm_gem.c:142:30: error: passing argument 1 of 'drm_gem_object_lookup'

[PATCH 2/5] 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 1/5] headers_check: don't warn about c++ guards

A recent addition to the DRM tree for 4.7 added 'extern "C"' guards for c++ to all the DRM headers, and that now causes warnings in 'make headers_check': usr/include/drm/amdgpu_drm.h:38: userspace cannot reference function or variable defined in the kernel usr/include/drm/drm.h:63: userspace

[PATCH 0/5] drm: fixes for merge-window regressions

A couple of new warnings and build errors appeared through the DRM tree in linux-next after the merge window opened. The first patch here is for scripts/headers_check.pl, but as the bug is only present in drm-next at the moment, it would be good to add all five patches to that tree before they

[PATCH 0/5] drm: fixes for merge-window regressions

On Wed, May 18, 2016 at 03:45:01PM +0200, Arnd Bergmann wrote: > A couple of new warnings and build errors appeared through the DRM > tree in linux-next after the merge window opened. The first patch > here is for scripts/headers_check.pl, but as the bug is only > present in drm-next at the

[PATCH V3] drm/tegra: Fix crash caused by reference count imbalance

es: d2307dea14a4 ("drm/atomic: use connector references (v3)") > > Signed-off-by: Jon Hunter > Reviewed-by: Daniel Vetter > Acked-by: Thierry Reding Applied to drm-misc, thanks. -Daniel > --- > > V3 changes: > - Dropped WARN_ON > > V2 change

[PATCH 24/24] drm/omap: DPI: rename "DSI" related names

Originally DSS only had DSI PLLs, and thus the DPI driver has functions and variables that refer to DSI or DSI PLL. Now we support DSI, VIDEO and HDMI PLLs, so it's time to remove the DSI references from the code. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dpi.c | 44

[PATCH 23/24] drm/omap: support type B PLL for DPI

Type A and B PLLs require a bit different calculations for the clock rates. DPI driver supports only type A PLLs. This patch adds support for the type B PLL. Type B PLLs are simpler than type A, as type B can produce a good clock for almost any rate. Thus we can just ask it to produce the pixel

[PATCH 22/24] drm/omap: add comments for PLL calculations

Add comments showing how the PLL clock rates are calculated. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/pll.c | 7 +++ 1 file changed, 7 insertions(+) diff --git a/drivers/gpu/drm/omapdrm/dss/pll.c b/drivers/gpu/drm/omapdrm/dss/pll.c index 6daf7bc3a67a..4768a85e6c73

[PATCH 21/24] drm/omap: generalize dss_pll_calc_b()

dss_pll_calc_b() takes HDMI TMDS clock rate as a parameter. To make dss_pll_calc_b() usable for non-HDMI users, change the function to take clkout rate as parameter, and also change the current users of dss_pll_calc_b() to accommodate that. Signed-off-by: Tomi Valkeinen ---

[PATCH 20/24] drm/omap: move HDMI PLL calc function to pll.c

Move hdmi_pll_compute(), used to calculate the config for HDMI PLL, from hdmi_pll.c to pll.c, with the name of dss_pll_calc_b(), to make it available to non-HDMI users. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dss.h | 4 +++ drivers/gpu/drm/omapdrm/dss/hdmi.h | 2

[PATCH 19/24] drm/omap: rename PLL calc functions

Add a "_a" postfix to the type A PLL calc functions, to differentiate them from the type B PLL calculations which we will add shortly. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dpi.c | 4 ++-- drivers/gpu/drm/omapdrm/dss/dsi.c | 8 drivers/gpu/drm/omapdrm/dss/dss.h

[PATCH 18/24] drm/omap: HDMI PLL: use runtime pm

To make it possible to use HDMI PLL for other video outputs than HDMI, the HDMI PLL code needs to do runtime_get/put for the HDMI IP, so that the IP (include the PLL) is enabled. To do that we also need to store the HDMI pdev in the hdmi_pll_data. Signed-off-by: Tomi Valkeinen ---

[PATCH 17/24] drm/omap: fix DPI clkout index handling

DPI driver uses a fixed clkout index, 0. This has worked fine as the first clkout is usually used. To generalize the code and to support additional clock sources, change the code to use dss_pll_get_clkout_idx_for_src() to get the clkout index. Signed-off-by: Tomi Valkeinen ---

[PATCH 16/24] drm/omap: cleanup DPI clock source handling

We can clean up the DPI driver's clock source handling by using the dss_clk_source instead of only a dss_pll pointer. This will also make it possible to use additional clock sources, like PLL1_3 or HDMI_PLL, which the code did not support earlier. Signed-off-by: Tomi Valkeinen ---

[PATCH 15/24] drm/omap: cleanup dispc_fclk_rate()

With the new PLL helpers, we can clean up the dispc_fclk_rate(). This will also make dispc_fclk_rate() support clock sources it didn't support earlier. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 31 +++ 1 file changed, 11 insertions(+),

[PATCH 14/24] drm/omap: cleanup dispc_mgr_lclk_rate()

With the new PLL helpers, we can clean up the dispc_mgr_lclk_rate(). This will also make dispc_mgr_lclk_rate() support clock sources it didn't support earlier. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 46 ++--- 1 file changed, 17

[PATCH 13/24] drm/omap: add PLL helper funcs

Add two PLL helper functions: dss_pll_find_by_src() which returns the dss_pll for the given dss_clk_source. dss_pll_get_clkout_idx_for_src() which returns the clkout index for the given dss_clk_source. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dss.h | 2 ++

[PATCH 12/24] drm/omap: clean up the LCD clk mux code

The code to set the clock muxes for DISPC's LCD clock inputs is very confusing. Especially on DRA7, there's an additional clock muxing that needs to be done, which at the moment is done in dpi.c using dss_ctrl_pll_set_control_mux(). Clean this all up by: - Using dss_clk_source instead of

[PATCH 11/24] drm/omap: add field for PLL type

DSS uses two types of PLLs, type A (DSI & Video) and type B (HDMI). The two types behave slightly differently, but we don't have the type of the PLL available anywhere for the driver. This patch adds an enum for the PLL type and a field in the PLL's HW data to store it. Signed-off-by: Tomi

[PATCH 10/24] drm/omap: Add missing clock sources

enum dss_clk_source does not have values for all clock sources available on OMAP4+ DSS versions. Add the missing clock sources. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dss.c | 3 +++ drivers/gpu/drm/omapdrm/dss/dss.h | 4 2 files changed, 7 insertions(+) diff --git

[PATCH 09/24] drm/omap: rename dss_clk_source enums

The names of the enum dss_clk_source's values are legacy names, only correct for OMAP3 DSS. Rename the names to more generic ones. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 12 +-- drivers/gpu/drm/omapdrm/dss/dpi.c | 10 -

[PATCH 08/24] drm/omap: rename dss_get_generic_clk_source_name()

Now that there is no "non-generic" version of the function to get the clock source name, lets rename dss_get_generic_clk_source_name() to dss_get_clk_source_name(). Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c | 4 ++-- drivers/gpu/drm/omapdrm/dss/dsi.c | 6 +++---

[PATCH 07/24] drm/omap: remove dss_feat_get_clk_source_name()

We have two functions to return a name for clock sources for debugging purposes: dss_feat_get_clk_source_name() and dss_get_generic_clk_source_name(). The former is supposed to return a DSS IP version specific name for the clock source, and the latter is supposed to return a more generic name.

[PATCH 06/24] drm/omap: rename omap_dss_clk_source

'enum omap_dss_clk_source' is internal to dss. Let's rename it to 'dss_clk_source' match our naming convention. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dispc.c| 4 ++-- drivers/gpu/drm/omapdrm/dss/dpi.c | 2 +- drivers/gpu/drm/omapdrm/dss/dsi.c

[PATCH 05/24] drm/omap: copy enum omap_dss_clk_source

At the moment 'enum omap_dss_clk_source' is in omapdss.h, shared by omapdrm and omapfb. We're about to improve the omapdrm clock code, so we need to make a separate copy of the enum for each driver. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/dss.h | 11 +++

[PATCH 04/24] drm/omap: video-pll: add missing data for clkout2 & 3

Video pll hw data is missing bitfield definitions for clkout2 and clkout3. We don't use those clkouts at the moment, so this has not caused any issues. Add the bitfields. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/video-pll.c | 4 1 file changed, 4 insertions(+) diff

[PATCH 03/24] drm/omap: fix wrong variable type

'r' is supposed to be int, not u16, so fix it. Signed-off-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/dss/hdmi_pll.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/omapdrm/dss/hdmi_pll.c b/drivers/gpu/drm/omapdrm/dss/hdmi_pll.c index

[PATCH 02/24] drm/omap: remove unused enum omap_overlay_manager_caps

'enum omap_overlay_manager_caps' is not used anywhere, remove it. Signed-off-by: Tomi Valkeinen --- include/video/omapdss.h | 5 - 1 file changed, 5 deletions(-) diff --git a/include/video/omapdss.h b/include/video/omapdss.h index 5b51789259c8..e4942d046f96 100644 ---

[PATCH 01/24] drm/omap: remove unused enum omap_hdmi_flags

'enum omap_hdmi_flags' is not used anywhere, remove it. Signed-off-by: Tomi Valkeinen --- include/video/omapdss.h | 4 1 file changed, 4 deletions(-) diff --git a/include/video/omapdss.h b/include/video/omapdss.h index 8e14ad7327c9..5b51789259c8 100644 --- a/include/video/omapdss.h +++

[PATCH 00/24] drm/omap: DSS PLL work

Hi, The main goal of this work was to get AM5/DRA7 HDMI PLL usable for LCD outputs (currently it's only usable for HDMI) and to get LCD2 output of AM5/DRA7 working (PLL config for LCD2 is not implemented). The end result is, in my opinion, quite nice cleanup of the PLL related code, which had

[PATCH 2/2] Documentation: add fence-collection to kernel DocBook

From: Gustavo Padovan Include fence-collection files in the DocBook. Signed-off-by: Gustavo Padovan --- Documentation/DocBook/device-drivers.tmpl | 2 ++ 1 file changed, 2 insertions(+) diff --git a/Documentation/DocBook/device-drivers.tmpl

[PATCH 1/2] dma-buf/fence: add fence_collection fences

From: Gustavo Padovan struct fence_collection inherits from struct fence and carries a collection of fences that needs to be waited together. It is useful to translate a sync_file to a fence to remove the complexity of dealing with sync_files on DRM drivers. So

[PATCH] drm: Nuke ->vblank_disable_allowed

On Wed, May 18, 2016 at 4:29 PM, Daniel Vetter wrote: > This was added in > > commit 0a3e67a4caac273a3bfc4ced3da364830b1ab241 > Author: Jesse Barnes > Date: Tue Sep 30 12:14:26 2008 -0700 > > drm: Rework vblank-wait handling to allow interrupt reduction. > > to stay backwards-compatible

[PATCH] drm/i915/dp: Try to find proper bpc for DP->legacy converters. (v2)

On Wed, 18 May 2016, Mario Kleiner wrote: > On 05/17/2016 08:51 AM, Daniel Vetter wrote: >> On Thu, May 12, 2016 at 06:43:58PM +0200, Mario Kleiner wrote: >>> This fixes a regression in output precision for DVI and VGA >>> video sinks connected to Intel hw via active DisplayPort->DVI/VGA >>>

[PATCH V3] drm/tegra: Fix crash caused by reference count imbalance

ector_destroy_state() in order to put the reference for the connector. Fixes: d2307dea14a4 ("drm/atomic: use connector references (v3)") Signed-off-by: Jon Hunter Reviewed-by: Daniel Vetter Acked-by: Thierry Reding --- V3 changes: - Dropped WARN_ON V2 changes: - Updated to next

[RFC 2/3] drm/mediatek: add support for Mediatek SoC MT2701

Hi Emil, On Tue, 2016-05-17 at 10:55 +0100, Emil Velikov wrote: > Hi YT Shen, > > On 12 May 2016 at 12:49, wrote: > > From: YT Shen > > > > This patch add support for the Mediatek MT2701 DISP subsystem. > > There is only one OVL engine in MT2701, and we have shadow > > register support here.

[PATCH V2] drm/tegra: Fix crash caused by reference count imbalance

t; } > With the WARN_ON() dropped this looks good to me: Acked-by: Thierry Reding -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/288228e4/attachment.sig>

[Intel-gfx] [PATCH] drm: use seqlocks for vblank time/count

There's an updated version of this patch already on the ml [1], which I Cc'd you in on. I take it that your @tuebingen.mpg.de is in fact an old email address? [1] https://patchwork.freedesktop.org/patch/86354/

[PATCH] drm: Nuke ->vblank_disable_allowed

On Wed, May 18, 2016 at 3:47 PM, Daniel Vetter wrote: > This was added in > > commit 0a3e67a4caac273a3bfc4ced3da364830b1ab241 > Author: Jesse Barnes > Date: Tue Sep 30 12:14:26 2008 -0700 > > drm: Rework vblank-wait handling to allow interrupt reduction. > > to stay backwards-compatible

[PATCH v2] drm/imx: Match imx-ipuv3-crtc components using device node in platform data

Hi, On Wed, 18 May 2016 14:56:40 +0200 Philipp Zabel wrote: > The component master driver imx-drm-core matches component devices using > their of_node. Since commit 950b410dd1ab ("gpu: ipu-v3: Fix imx-ipuv3-crtc > module autoloading"), the imx-ipuv3-crtc dev->of_node is not set during > probing.

[Intel-gfx] [PATCH] drm: use seqlocks for vblank time/count

On 05/09/2016 08:11 PM, Daniel Vetter wrote: > On Mon, May 09, 2016 at 08:16:07PM +0300, Ville Syrjälä wrote: >> On Mon, May 09, 2016 at 05:08:43PM +0100, Matthew Auld wrote: >>> This patch aims to replace the roll-your-own seqlock implementation with >>> full-blown seqlock'. We also remove the

[PATCH] drm/i915/dp: Try to find proper bpc for DP->legacy converters. (v2)

On 05/17/2016 08:51 AM, Daniel Vetter wrote: > On Thu, May 12, 2016 at 06:43:58PM +0200, Mario Kleiner wrote: >> This fixes a regression in output precision for DVI and VGA >> video sinks connected to Intel hw via active DisplayPort->DVI/VGA >> converters. >> >> The regression was indirectly

[PATCH 0/5] drm: fixes for merge-window regressions

A couple of new warnings and build errors appeared through the DRM tree in linux-next after the merge window opened. The first patch here is for scripts/headers_check.pl, but as the bug is only present in drm-next at the moment, it would be good to add all five patches to that tree before they

[Bug 118431] New: kernel NULL pointer dereference with a Radeon HD 7970/8970 OEM / R9 280X

https://bugzilla.kernel.org/show_bug.cgi?id=118431 Bug ID: 118431 Summary: kernel NULL pointer dereference with a Radeon HD 7970/8970 OEM / R9 280X Product: Drivers Version: 2.5 Kernel Version: 4.4.9-300.fc23.x86_64

[PATCH v2] drm/imx: Match imx-ipuv3-crtc components using device node in platform data

The component master driver imx-drm-core matches component devices using their of_node. Since commit 950b410dd1ab ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading"), the imx-ipuv3-crtc dev->of_node is not set during probing. Before that, of_node was set and caused an of: modalias to be used

imx-drm: regression due to commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")

Am Mittwoch, den 18.05.2016, 11:12 +0200 schrieb Lothar Waßmann: > Hi, > > On Fri, 13 May 2016 13:04:12 +0200 Philipp Zabel wrote: > > Hi Lothar, > > > > Am Freitag, den 13.05.2016, 12:33 +0200 schrieb Lothar Waßmann: > > > Hi, > > > > > > the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix

[PATCH] Revert "drm/imx: Remove of_node assignment from ipuv3-crtc driver probe"

Hi Fabio, Am Mittwoch, den 18.05.2016, 07:51 -0300 schrieb Fabio Estevam: > Hi Philipp, > > On Wed, May 18, 2016 at 5:38 AM, Philipp Zabel > wrote: > > > Could you also test https://patchwork.kernel.org/patch/9081661/ ? > > With this patch applied I still do not get HDMI working on a mx6q

[PATCH V2] drm/tegra: Fix crash caused by reference count imbalance

nally, add a warning if allocating memory for the state information > fails in tegra_dsi_connector_reset(). > > Fixes: d2307dea14a4 ("drm/atomic: use connector references (v3)") > > Signed-off-by: Jon Hunter Reviewed-by: Daniel Vetter Thierry, since Dave hasn't pulle

[PATCH] drm/vc4: Make pageflip completion handling more robust.

Protect both the setup of the pageflip event and the latching of the new requested displaylist head pointer by the event lock, so we can't get into a situation where vc4_atomic_flush latches the new display list via HVS_WRITE, then immediately gets preempted before queueing the pageflip event,

[pull] amdgpu drm-next-4.7

Hi Dave, Some amdgpu fixes for 4.7: - Various powerplay bug fixes - Add some new polaris pci ids - misc bug fixes and code cleanups The following changes since commit b4eeed590deeff13a53db641129f0301d70248f3: drm/amd/powerplay: rewrite pp_sw_init to make code readable (2016-05-11 13:30:33

[Bug 95308] [radeonsi] Hangs after some minutes on Team Fortress 2

-40 minutes here: https://youtu.be/1iBkh6SYSZU -- 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/20160518/c95650dd/attachment.html>

[Bug 95308] [radeonsi] Hangs after some minutes on Team Fortress 2

bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/585220d5/attachment.html>

[Bug 95308] [radeonsi] Hangs after some minutes on Team Fortress 2

bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160518/6f1ebc40/attachment-0001.html>

[PATCH] drm/tegra: Fix crash caused by reference count imbalance

On Wed, May 18, 2016 at 10:18:52AM +0100, Jon Hunter wrote: > > On 17/05/16 18:36, Daniel Vetter wrote: > > On Tue, May 17, 2016 at 7:29 PM, Jon Hunter wrote: > @@ -764,6 +769,9 @@ tegra_dsi_connector_duplicate_state(struct > drm_connector *connector) > if (!copy) >

[PATCH] drm: Avoid connector reference imbalance on error path

On Fri, May 06, 2016 at 12:47:45PM +0100, Chris Wilson wrote: > Whilst looking at the fallout from using connector references for > atomic, I noticed that there is an early return buried in > drm_atomic_set_crtc_for_connector() that if hit could cause us to leak a > reference on the connector. >

[PATCH V2] drm/tegra: Fix crash caused by reference count imbalance

ector_destroy_state() in order to put the reference for the connector. Finally, add a warning if allocating memory for the state information fails in tegra_dsi_connector_reset(). Fixes: d2307dea14a4 ("drm/atomic: use connector references (v3)") Signed-off-by: Jon Hunter --- V2 changes: -

[RFC 1/8] dma-buf/fence: add fence_collection fences

Hi Christian, 2016-05-18 Christian König : > Am 15.04.2016 um 21:25 schrieb Daniel Vetter: > > On Fri, Apr 15, 2016 at 11:27:50AM -0700, Gustavo Padovan wrote: > > > 2016-04-15 Christian König : > > > > Amdgpu also has an implementation for a fence collection which uses a a > > > > hashtable

next-20160518 build: 2 failures 20 warnings (next-20160518)

On Wed, May 18, 2016 at 11:15:59AM +0100, Mark Brown wrote: > On Wed, May 18, 2016 at 08:05:26AM +0100, Build bot for Mark Brown wrote: > > Today's -next fails to build arm and arm64 allmodconfigs fail to build > due to: > > > arm64-allmodconfig > > arm-allmodconfig > >

next-20160518 build: 2 failures 20 warnings (next-20160518)

rm_device from drm_gem_object_lookup()) which didn't update the Mediatek drivers. -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/

imx-drm: regression due to commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module autoloading")

Hi, On Fri, 13 May 2016 13:04:12 +0200 Philipp Zabel wrote: > Hi Lothar, > > Am Freitag, den 13.05.2016, 12:33 +0200 schrieb Lothar Waßmann: > > Hi, > > > > the commit 503fe87bd0a8 ("gpu: ipu-v3: Fix imx-ipuv3-crtc module > > autoloading") > > indeed fixes the autoloading issue, but

[PATCH v2] drm/imx: Match imx-ipuv3-crtc components using device node in platform data

On Wed, May 18, 2016 at 9:56 AM, Philipp Zabel wrote: > The component master driver imx-drm-core matches component devices using > their of_node. Since commit 950b410dd1ab ("gpu: ipu-v3: Fix imx-ipuv3-crtc > module autoloading"), the imx-ipuv3-crtc dev->of_node is not set during > probing.

[PATCH] drm/etnaviv: enable GPU module level clock gating support

From: Russell King Enable GPU module level hardware clock gating, using the conditions found in the galcore v5 driver. v2 lst: Split out clock gating enable into separate function, as there might be more conditions needed for new hardware. Signed-off-by: Russell

[PATCH] Revert "drm/imx: Remove of_node assignment from ipuv3-crtc driver probe"

Hi Fabio, Chris, Am Mittwoch, den 18.05.2016, 09:02 +0800 schrieb Chris Ruehl: > Hi > On Wednesday, May 18, 2016 01:11 AM, Fabio Estevam wrote: > > Commit 407c9eba789767 ("drm/imx: Remove of_node assignment from ipuv3-crtc > > driver probe") causes the IPU to be non-functional, so better to > >

[PATCH] drm/tegra: Fix crash caused by reference count imbalance

On 17/05/16 18:36, Daniel Vetter wrote: > On Tue, May 17, 2016 at 7:29 PM, Jon Hunter wrote: @@ -764,6 +769,9 @@ tegra_dsi_connector_duplicate_state(struct drm_connector *connector) if (!copy) return NULL; +if (copy->base.crtc) +

[PATCH 0/6] ARM: dts: sun5i: q8-common: Enable various peripherals

Hi Chen-Yu, On 17-05-16 17:56, Chen-Yu Tsai wrote: > Hi everyone, > > This series enables more peripherals for Allwinner A13-based Q8 devices. > The peripherals include the WiFi, the PMIC's micro-usb power supply > (driver), audio codec (headphone and speaker), and full display support > with the

[PATCH] drm: Fix error handling in drm_connector_register

On Fri, May 06, 2016 at 02:55:02PM +0200, Daniel Vetter wrote: > When debugfs or sysfs registration failed, we failed to clean up the > idr registration. Reorder to fix this. > > Cc: Dave Airlie > Signed-off-by: Daniel Vetter Had to check that we could do the idr_replace after exposing

[RFC 1/8] dma-buf/fence: add fence_collection fences

Am 15.04.2016 um 21:25 schrieb Daniel Vetter: > On Fri, Apr 15, 2016 at 11:27:50AM -0700, Gustavo Padovan wrote: >> 2016-04-15 Christian König : >>> Amdgpu also has an implementation for a fence collection which uses a a >>> hashtable to keep the fences grouped by context (e.g. only the latest

[PATCH] Revert "drm/imx: Remove of_node assignment from ipuv3-crtc driver probe"

Hi On Wednesday, May 18, 2016 01:11 AM, Fabio Estevam wrote: > Commit 407c9eba789767 ("drm/imx: Remove of_node assignment from ipuv3-crtc > driver probe") causes the IPU to be non-functional, so better to > revert it to avoid such regression. > > This reverts commit

[PATCH] tty: vt: Fix soft lockup in fbcon cursor blink timer.

On Wed, May 18, 2016 at 4:49 AM, Pavel Machek wrote: > On Tue 2016-05-17 11:41:04, David Daney wrote: >> From: David Daney >> >> We are getting somewhat random soft lockups with this signature: >> >> [ 86.992215] [] el1_irq+0xa0/0x10c >> [ 86.997082] [] cursor_timer_handler+0x30/0x54 >> [

  1   2   >