Re: [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v4)

On 2017年05月12日 12:17, Dave Airlie wrote: On 12 May 2017 at 13:34, zhoucm1 wrote: 1. generally, functions in amdgpu_cs.c should be with amdgpu_cs_ as prefix. Okay I've fixed this and previous patch up locally. 2. If I'm not wrong to your proposal, SYNCOBJ_IN is to

Re: [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v4)

On 12 May 2017 at 13:34, zhoucm1 wrote: > 1. generally, functions in amdgpu_cs.c should be with amdgpu_cs_ as prefix. Okay I've fixed this and previous patch up locally. > 2. If I'm not wrong to your proposal, SYNCOBJ_IN is to semaphore wait while > SYNCOBJ_OUT is to

Re: [PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v4)

1. generally, functions in amdgpu_cs.c should be with amdgpu_cs_ as prefix. 2. If I'm not wrong to your proposal, SYNCOBJ_IN is to semaphore wait while SYNCOBJ_OUT is to semaphore signal. SYNCOBJ_IN/OUT both are based on command submission ioctl, that means user space must generate CS when

[radeon-alex:raven-acp 137/337] drivers/gpu/drm/amd/amdgpu/../powerplay/hwmgr/pp_overdriver.h:48:6: sparse: no newline at end of file

tree: git://people.freedesktop.org/~agd5f/linux.git raven-acp head: 465122e3ee134fb29075d92712676aa92c2b20c2 commit: 0a1b27b47671d195a903037880496ec893a82add [137/337] drm/amd/powerplay: add avfs fuse overdriver func. reproduce: # apt-get install sparse git checkout

[radeon-alex:amd-staging-4.11 500/1085] drivers/gpu/drm/amd/amdgpu/../display/dc/basics/logger.c:74:2-34: duplicated argument to & or | (fwd)

Hello, It seems that (1 << LOG_DETECTION_EDID_PARSER) appears more than once in the bit or (only one instance shown, on line 74). julia -- Forwarded message -- Date: Fri, 12 May 2017 09:54:09 +0800 From: kbuild test robot To: kbu...@01.org Cc: Julia

[Bug 101003] segfault with ideas test of glmark2

https://bugs.freedesktop.org/show_bug.cgi?id=101003 --- Comment #3 from Michel Dänzer --- Please attach a backtrace of the crash. -- You are receiving this mail because: You are the assignee for the bug.___ dri-devel mailing list

[PATCH v7 3/9] drm/i915: Drop AUX backlight enable check for backlight control

There are some panel that (1) does not support display backlight enable via AUX (2) support display backlight adjustment via AUX (3) support display backlight enable via eDP BL_ENABLE pin The current driver required that (1) must be support to enable (2). This patch drops that requirement.

Re: [PATCH v2 00/29] Remove the omapdrm and omapdss devices from platform code

* Tomi Valkeinen [170511 01:37]: > On 10/05/17 21:29, Tony Lindgren wrote: > > * Tomi Valkeinen [170510 10:44]: > >> > >> > >> On 10/05/17 19:46, Tony Lindgren wrote: > >>> * Tomi Valkeinen [170510 00:26]: > On 09/05/17

Re: [drm:qxl] BUG: sleeping function called from invalid context - qxl_bo_kmap_atomic_page()...splat

On Tue, 2017-05-09 at 04:37 +0200, Mike Galbraith wrote: > On Mon, 2017-05-08 at 16:48 -0300, Gabriel Krisman Bertazi wrote: > > > Thanks for reporting this. Can you confirm the following patch prevents > > the issue? > > Nope, it still gripes. The reason for this gripe is that we find that we

Re: [Intel-gfx] [PATCH v6 6/9] drm/i915: Support dynamic backlight via DPCD register

On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > This patch enables dynamic backlight by default for eDP > panel that supports this feature via DPCD register and > set minimum / maximum brightness to 0% and 100% of the > normal brightness. I realized I replied to the previous

[PATCH v3 2/6] drm: Add drm_{crtc/encoder/connector}_mode_valid()

Add a new helper to call crtc->mode_valid, connector->mode_valid and encoder->mode_valid callbacks. Suggested-by: Ville Syrjälä Signed-off-by: Jose Abreu Cc: Carlos Palminha Cc: Alexey Brodkin

[PATCH] drm/hisilicon: Ensure LDI regs are properly configured.

This patch fixes the following soft lockup: BUG: soft lockup - CPU#0 stuck for 23s! [weston:307] On weston idle-timeout the IP is powered down and reset asserted. On weston resume we get a massive vblank IRQ storm due to the LDI registers having lost some state. This state loss is caused by

[PATCH v7 6/9] drm/i915: Add option to support dynamic backlight via DPCD

This patch adds option to enable dynamic backlight for eDP panel that supports this feature via DPCD register and set minimum / maximum brightness to 0% and 100% of the normal brightness. Signed-off-by: Puthikorn Voravootivat --- drivers/gpu/drm/i915/i915_params.c

Re: [Intel-gfx] [PATCH v6 3/9] drm/i915: Drop AUX backlight enable check for backlight control

On Wed, May 10, 2017 at 5:39 PM, Pandiyan, Dhinakaran < dhinakaran.pandi...@intel.com> wrote: > On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > > There are some panel that > > (1) does not support display backlight enable via AUX > > (2) support display backlight adjustment via

[PATCH v7 4/9] drm/i915: Allow choosing how to adjust brightness if both supported

Add option to allow choosing how to adjust brightness if panel supports both PWM pin and AUX channel. Signed-off-by: Puthikorn Voravootivat --- drivers/gpu/drm/i915/i915_params.c| 8 +--- drivers/gpu/drm/i915/i915_params.h| 2 +-

Re: [linux-sunxi] [PATCH v2 20/20] ARM: sun5i: a10s-olinuxino: Enable HDMI

在 2017-05-11 03:23，Maxime Ripard 写道： Hi, On Thu, May 04, 2017 at 04:05:18PM +0800, Chen-Yu Tsai wrote: On Wed, May 3, 2017 at 7:59 PM, Maxime Ripard wrote: > The A10s Olinuxino has an HDMI connector. Make sure we can use it. > > Acked-by: Chen-Yu Tsai

[PATCH v3 4/6] drm: Use new mode_valid() helpers in connector probe helper

This changes the connector probe helper function to use the new encoder->mode_valid(), bridge->mode_valid() and crtc->mode_valid() helper callbacks to validate the modes. The new callbacks are optional so the behaviour remains the same if they are not implemented. If they are, then the code loops

[PATCH v7 0/9] Enhancement to intel_dp_aux_backlight driver

This patch set contain 9 patches. - First five patches fix bug in the driver and allow choosing which way to adjust brightness if both PWM pin and AUX are supported - Next patch adds enable DBC by default - Next patch makes the driver restore last brightness level after turning display off and

[PATCH v7 9/9] drm/i915: Set PWM divider to match desired frequency in vbt

Read desired PWM frequency from panel vbt and calculate the value for divider in DPCD address 0x724 and 0x728 to have as many bits as possible for PWM duty cyle for granularity of brightness adjustment while the frequency is still within 25% of the desired frequency. Signed-off-by: Puthikorn

[PATCH v3 0/6] Introduce new mode validation callbacks

This series is a follow up from the discussion at [1]. We start by introducing crtc->mode_valid(), encoder->mode_valid() and bridge->mode_valid() callbacks which will be used in followup patches and also by cleaning the documentation a little bit. We proceed by introducing new helpers to call

[PATCH v3 6/6] drm: arc: Use crtc->mode_valid() callback

Now that we have a callback to check if crtc supports a given mode we can use it in arcpgu so that we restrict the number of probbed modes to the ones we can actually display. This is specially useful because arcpgu crtc is responsible to set a clock value in the commit() stage but unfortunatelly

[PATCH v3 1/6] drm: Add crtc/encoder/bridge->mode_valid() callbacks

This adds a new callback to crtc, encoder and bridge helper functions called mode_valid(). This callback shall be implemented if the corresponding component has some sort of restriction in the modes that can be displayed. A NULL callback implicates that the component can display all the modes. We

[PATCH v7 8/9] drm: Add definition for eDP backlight frequency

This patch adds the following definition - Bit mask for EDP_PWMGEN_BIT_COUNT and min/max cap register which only use bit 0:4 - Base frequency (27 MHz) for backlight PWM frequency generator. Signed-off-by: Puthikorn Voravootivat Reviewed-by: Dhinakaran Pandiyan

Re: [Intel-gfx] [PATCH v6 1/9] drm/i915: Fix cap check for intel_dp_aux_backlight driver

On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > intel_dp_aux_backlight driver should check for the > DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP before enable the driver. > > Signed-off-by: Puthikorn Voravootivat Reviewed-by: Dhinakaran Pandiyan

Re: [Linux-graphics-maintainer] No mouse cursor since 36cc79bc9077319c04bd3b132edcacaa9a0d9f2b

> Sinclair Yeh hat am 10. Mai 2017 um 18:46 geschrieben: > > > Hi, Hi, > On Wed, May 10, 2017 at 12:31:39PM +0200, m.t wrote: > > > > > Thomas Hellstrom hat am 10. Mai 2017 um 10:35 geschrieben: > > > > > > Hi, > > > > > > Thanks for reporting. > > > > I would have reported earlier if it

[PATCH v7 5/9] drm/i915: Set backlight mode before enable backlight

We should set backlight mode register before set register to enable the backlight. Signed-off-by: Puthikorn Voravootivat Reviewed-by: Dhinakaran Pandiyan --- drivers/gpu/drm/i915/intel_dp_aux_backlight.c | 4 ++-- 1 file changed, 2

Re: [Intel-gfx] [PATCH v5 6/9] drm/i915: Support dynamic backlight via DPCD register

Fair enough. Will add kernel switch in next version. On Wed, May 10, 2017 at 6:26 PM, Pandiyan, Dhinakaran < dhinakaran.pandi...@intel.com> wrote: > On Wed, 2017-05-03 at 17:28 -0700, Puthikorn Voravootivat wrote: > > This patch enables dynamic backlight by default for eDP > > panel that

[PATCH v3 3/6] drm: Introduce drm_bridge_mode_valid()

Introduce a new helper function which calls mode_valid() callback for all bridges in an encoder chain. Signed-off-by: Jose Abreu Cc: Carlos Palminha Cc: Alexey Brodkin Cc: Ville Syrjälä Cc:

Re: [Intel-gfx] [PATCH v6 3/9] drm/i915: Drop AUX backlight enable check for backlight control

On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > There are some panel that > (1) does not support display backlight enable via AUX > (2) support display backlight adjustment via AUX > (3) support display backlight enable via eDP BL_ENABLE pin > > The current driver required that

Testing dc-drm-next-atomic-wip

Hi, this is more feedback about how the code works and runs rather than what you're really looking for, so I thought I'd start a new thread. :-) I get the following error when compiling and (obviously) forgetting to enable the new DC option. I see the option will be removed, so maybe that

[PATCH v3 5/6] drm: Use mode_valid() in atomic modeset

This patches makes use of the new mode_valid() callbacks introduced previously to validate the full video pipeline when modesetting. This calls the encoder->mode_valid(), bridge->mode_valid() and crtc->mode_valid() so that we can make sure that the mode will be accepted in every components.

[PATCH v7 1/9] drm/i915: Fix cap check for intel_dp_aux_backlight driver

intel_dp_aux_backlight driver should check for the DP_EDP_BACKLIGHT_BRIGHTNESS_AUX_SET_CAP before enable the driver. Signed-off-by: Puthikorn Voravootivat Reviewed-by: Dhinakaran Pandiyan --- drivers/gpu/drm/i915/intel_dp_aux_backlight.c | 1

Re: [PATCHv2 0/3] Intel FPGA VIP Frame Buffer II DRM Driver

On Tue, 2017-05-09 at 09:40 -0700, Eric Anholt wrote: > "Ong, Hean Loong" writes: > > > > > On Mon, 2017-05-08 at 09:03 -0700, Eric Anholt wrote: > > > > > > "Ong, Hean Loong" writes: > > > > > > > > > > > > > > > On Thu, 2017-05-04 at

[PATCH v7 7/9] drm/i915: Restore brightness level in aux backlight driver

Some panel will default to zero brightness when turning the panel off and on again. This patch restores last brightness level back when panel is turning back on. Signed-off-by: Puthikorn Voravootivat Reviewed-by: Dhinakaran Pandiyan ---

Re: [Intel-gfx] [PATCH v5 3/9] drm/i915: Drop AUX backlight enable check for backlight control

On Wed, 2017-05-10 at 13:05 +0300, Jani Nikula wrote: > On Wed, 10 May 2017, "Pandiyan, Dhinakaran" > wrote: > > On Tue, 2017-05-09 at 16:39 -0700, Puthikorn Voravootivat wrote: > >> > How is backlight enabled in this case? > >> Using eDP BL_ENABLE pin > > > > > >

Re: [Intel-gfx] [PATCH v6 4/9] drm/i915: Allow choosing how to adjust brightness if both supported

On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > Add option to allow choosing how to adjust brightness if > panel supports both PWM pin and AUX channel. > > Signed-off-by: Puthikorn Voravootivat > --- > drivers/gpu/drm/i915/i915_params.c| 8

Re: [Intel-gfx] [PATCH v5 6/9] drm/i915: Support dynamic backlight via DPCD register

On Wed, 2017-05-03 at 17:28 -0700, Puthikorn Voravootivat wrote: > This patch enables dynamic backlight by default for eDP > panel that supports this feature via DPCD register and > set minimum / maximum brightness to 0% and 100% of the > normal brightness. I read the link that you shared last

[PATCH v7 2/9] drm/i915: Correctly enable backlight brightness adjustment via DPCD

intel_dp_aux_enable_backlight() assumed that the register BACKLIGHT_BRIGHTNESS_CONTROL_MODE can only has value 01 (DP_EDP_BACKLIGHT_CONTROL_MODE_PRESET) when initialize. This patch fixed that by handling all cases of that register. Signed-off-by: Puthikorn Voravootivat

Re: [Intel-gfx] [PATCH v6 8/9] drm: Add definition for eDP backlight frequency

On Tue, 2017-05-09 at 16:40 -0700, Puthikorn Voravootivat wrote: > This patch adds the following definition > - Bit mask for EDP_PWMGEN_BIT_COUNT and min/max cap > register which only use bit 0:4 > - Base frequency (27 MHz) for backlight PWM frequency > generator. > > Signed-off-by: Puthikorn

[PATCH 4/5] amdgpu/cs: split out fence dependency checking

From: Dave Airlie This just splits out the fence depenency checking into it's own function to make it easier to add semaphore dependencies. Reviewed-by: Christian König Signed-off-by: Dave Airlie ---

[PATCH 3/5] drm/syncobj: add sync_file interaction.

From: Dave Airlie This interface allows importing the fence from a sync_file into an existing drm sync object, or exporting the fence attached to an existing drm sync object into a new sync file object. This should only be used to interact with sync files where necessary.

[PATCH 5/5] amdgpu: use drm sync objects for shared semaphores (v4)

From: Dave Airlie This creates a new command submission chunk for amdgpu to add in and out sync objects around the submission. Sync objects are managed via the drm syncobj ioctls. The command submission interface is enhanced with two new chunks, one for syncobj pre

[PATCH 2/5] drm/syncobj: add sync obj wait interface. (v2)

From: Dave Airlie This interface will allow sync object to be used to back Vulkan fences. This API is pretty much the vulkan fence waiting API, and I've ported the code from amdgpu. v2: accept relative timeout, pass remaining time back to userspace. Signed-off-by: Dave

drm syncobj - can we get some r-b/a-bs?

Okay I'm not convinced this is going to get any better out of tree, I've polished what I can, and fixed up the last few comments from people, I'd like to rebase on drm-misc probably at some point and send a pull request for it. This mostly just addresses things around naming that Chris pointed

[PATCH 1/5] drm: introduce sync objects (v2)

From: Dave Airlie Sync objects are new toplevel drm object, that contain a pointer to a fence. This fence can be updated via command submission ioctls via drivers. There is also a generic wait obj API modelled on the vulkan wait API (with code modelled on some amdgpu code).

[Bug 188911] Function qxl_release_alloc() returns an improper value when the call to kmalloc() fails, resulting in bad memory access

https://bugzilla.kernel.org/show_bug.cgi?id=188911 bianpan (bianpan2...@ruc.edu.cn) changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 188911] Function qxl_release_alloc() returns an improper value when the call to kmalloc() fails, resulting in bad memory access

https://bugzilla.kernel.org/show_bug.cgi?id=188911 --- Comment #1 from bianpan (bianpan2...@ruc.edu.cn) --- Created attachment 256435 --> https://bugzilla.kernel.org/attachment.cgi?id=256435=edit The patch fixes the bug The patch has been merged into the latest version of the Linux kernel. So

[PATCH 1/4] drm/vc4: Adjust modes in DSI to work around the integer PLL divider.

BCM2835's PLLD_DSI1 divider doesn't give us many choices for our pixel clocks, so to support panels on the Raspberry Pi we need to set a higher pixel clock rate than requested and adjust the mode we program to extend out the HFP so that the refresh rate matches. Signed-off-by: Eric Anholt

[PATCH 3/4] drm/bridge: Add support for the Raspberry Pi 7" Touchscreen.

This driver communicates with the Atmel microcontroller for sequencing the poweron of the TC358762 DSI-DPI bridge and controlling the backlight PWM. The following lines are required in config.txt, to keep the firmware from trying to bash our I2C lines and steal the DSI interrupts:

[PATCH 4/4] drm/panel: Add the Raspberry Pi 7" touchscreen's panel.

The timings are those that the firmware defines as the baseline, which will be modified by the bridge/host as necessary to get the clocking to work. Signed-off-by: Eric Anholt --- drivers/gpu/drm/panel/panel-simple.c | 30 ++ 1 file changed, 30

[PATCH 2/4] dt-bindings: Document the Raspberry Pi Touchscreen nodes.

The Raspberry Pi 7" Touchscreen is a DPI touchscreen panel with DSI->DPI bridge and touchscreen controller integrated, that connects to the Raspberry Pi through its 15-pin "DSI" connector (some lines are DSI, some lines are I2C). This device is represented in the DT as three nodes (DSI device,

[PATCH 0/4] Raspberry Pi Touchscreen bridge/panel drivers

Here's the rewrite of the Raspberry Pi display support to split out a bridge driver representing the toshiba+atmel pair. It depends on the panel-bridge layer I've submitted. The RPi DSI stack isn't completely working yet -- I've got some flickery pixels on the display where it seems some color

Re: Requests for Proposal for hosting XDC 2018

Hi Daniel, Is Call for Papers opened yet for XDC? When do they usually start accepting proposals? Regards Manasi On Fri, May 12, 2017 at 12:08:45AM +0200, Daniel Vetter wrote: > Hi all, > > The X.org board is soliciting proposals to host XDC in 2017. By the usual > rotation a location in

[PATCH] drm/radeon: Unbreak HPD handling for r600+

We end up reading the interrupt register for HPD5, and then writing it to HPD6 which on systems without anything using HPD5 results in permanently disabling hotplug on one of the display outputs after the first time we acknowledge a hotplug interrupt from the GPU. This code is really bad. But for

Requests for Proposal for hosting XDC 2018

Hi all, The X.org board is soliciting proposals to host XDC in 2017. By the usual rotation a location in Europe is preferred, but the board will also consider other locations, especially if there's an interesting co-location with another conference. If you consider hosting XDC, we have assembled

[Bug 100984] QupZilla crashes at startup after mesa upgrade

https://bugs.freedesktop.org/show_bug.cgi?id=100984 --- Comment #6 from Francesco Turco --- $ glxinfo | grep "renderer string" couldn't open libtxc_dxtn.so, software DXTn compression/decompression unavailable i915_get_shader_param: Unknown cap 28. i915_get_shader_param:

Re: [PATCH] drm: fourcc byteorder: brings header file comments in line with reality.

On Fri 2017-04-21 14:08:04, Ville Syrjälä wrote: > On Fri, Apr 21, 2017 at 11:50:18AM +0200, Gerd Hoffmann wrote: > > On Fr, 2017-04-21 at 12:25 +0300, Ville Syrjälä wrote: > > > On Fri, Apr 21, 2017 at 09:58:24AM +0200, Gerd Hoffmann wrote: > > > > While working on graphics support for virtual

Re: [PATCH RFC v2 1/2] drm: Add optinal YCBCR_ENCODING property to drm_plane

Hi Jyri, On Thursday 11 May 2017 17:30:01 Jyri Sarha wrote: > On 05/05/17 16:03, Laurent Pinchart wrote: > > On Friday 05 May 2017 15:11:06 Jyri Sarha wrote: > >> On 05/05/17 12:07, Laurent Pinchart wrote: > >>> On Thursday 04 May 2017 10:14:25 Jyri Sarha wrote: > Add a standard optinal

Re: Re: [Intel-gfx] GPU hang with kernel 4.10rc3

On Mon 2017-01-23 10:39:27, Juergen Gross wrote: > On 13/01/17 15:41, Juergen Gross wrote: > > On 12/01/17 10:21, Chris Wilson wrote: > >> On Thu, Jan 12, 2017 at 07:03:25AM +0100, Juergen Gross wrote: > >>> On 11/01/17 18:08, Chris Wilson wrote: > On Wed, Jan 11, 2017 at 05:33:34PM +0100,

[Bug 100984] QupZilla crashes at startup after mesa upgrade

https://bugs.freedesktop.org/show_bug.cgi?id=100984 --- Comment #5 from Emil Velikov --- Francesco there can be two driver for your device. The following command will show which one. $ glxinfo| grep "renderer string" In either case - these drivers have hardly anyone

[Bug 101011] Shadow of Mordor crashes with mesa from 08.05.2017.

https://bugs.freedesktop.org/show_bug.cgi?id=101011 Bug ID: 101011 Summary: Shadow of Mordor crashes with mesa from 08.05.2017. Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity:

Re: [RFC v2 0/7] drm: asynchronous atomic plane update

2017-05-09 Ville Syrjälä : > On Thu, Apr 27, 2017 at 12:15:12PM -0300, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Hi, > > > > Second take of Asynchronous Plane Updates over Atomic. Here I looked > > to msm, vc4 and

[radeon-alex:vega10-drop0509 1707/1987] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd_gfx_v9.c:518:10: note: in expansion of macro 'lower_32_bits'

tree: git://people.freedesktop.org/~agd5f/linux.git vega10-drop0509 head: b97044091f42cad26368a402c31af13e1319c7ab commit: 3488464228578f9ab9065246e1ec049a78ae0e53 [1707/1987] drm/amdgpu: Add Vega10 support for KFD config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian

Re: [PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func.

On Thu, 11 May 2017 11:31:27 -0700 Eric Anholt wrote: > drm_encoder_cleanup() finishes with memsetting it to 0, already. > > Signed-off-by: Eric Anholt Acked-by: Boris Brezillon > --- >

Re: [PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge.

Hi Eric, On Thu, 11 May 2017 11:31:28 -0700 Eric Anholt wrote: > This cuts 135 lines of boilerplate, at the cost of losing the > filtering of get_modes() using atmel_hlcdc_dc_mode_valid(). The > atomic check will still check that we don't set an invalid mode, > though. Nice.

[PATCH 7/8] drm: remove unsafe drm_for_each_connector()

From: Gustavo Padovan After converting all users to drm_for_each_connector_iter() we no longer need drm_for_each_connector() so we can go ahead and remove it. Signed-off-by: Gustavo Padovan --- include/drm/drm_connector.h | 15

[PATCH 4/8] drm/mediatek: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter(). Cc: Philipp Zabel Signed-off-by: Gustavo Padovan --- only built-tested! ---

[PATCH 6/8] drm/vc4: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter(). Cc: Eric Anholt Signed-off-by: Gustavo Padovan --- only built-tested! ---

[PATCH 8/8] drm: todo: remove task about switch to drm_connector_list_iter

From: Gustavo Padovan This is now completed. Signed-off-by: Gustavo Padovan --- Documentation/gpu/todo.rst | 13 - 1 file changed, 13 deletions(-) diff --git a/Documentation/gpu/todo.rst b/Documentation/gpu/todo.rst

[PATCH 5/8] drm/nouveau: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter(). Cc: Ben Skeggs Signed-off-by: Gustavo Padovan --- only built-tested! ---

[PATCH 1/8] drm/exynos: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter() Cc: Inki Dae Cc: Joonyoung Shim Signed-off-by: Gustavo Padovan ---

[PATCH 3/8] drm/i915: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter(). Cc: Daniel Vetter Cc: Jani Nikula Signed-off-by: Gustavo Padovan

[PATCH 2/8] drm/rockchip: use drm_for_each_connector_iter()

From: Gustavo Padovan Drop legacy drm_for_each_connector() in favor of the race-free drm_for_each_connector_iter() Cc: Mark Yao Signed-off-by: Gustavo Padovan --- only built-tested! ---

[PATCH 0/8] remove unsafe drm_for_each_connector()

From: Gustavo Padovan Hi all, Something ligth in the middle of all my other tasks. I removed drm_for_each_connector() in favor of drm_for_each_connector_iter(). The i915 patch was tested, but I only *built-tested* the others! Gustavo --- Gustavo Padovan (8):

[radeon-alex:vega10-drop0509 1381/1987] drivers/gpu/drm/radeon/radeon_kfd.c:1426:32: warning: cast to pointer from integer of different size

tree: git://people.freedesktop.org/~agd5f/linux.git vega10-drop0509 head: b97044091f42cad26368a402c31af13e1319c7ab commit: 8e8443a9512d6794e1715bad20dad1fd2e6cd045 [1381/1987] radeon_kfd.c copied config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901

[PATCH v2 7/7] drm/atmel-hlcdc: Replace the panel usage with drm_panel_bridge.

This cuts 135 lines of boilerplate, at the cost of losing the filtering of get_modes() using atmel_hlcdc_dc_mode_valid(). The atomic check will still check that we don't set an invalid mode, though. Signed-off-by: Eric Anholt --- This patch is just a proposal for atmel-hlcdc

[PATCH v2 6/7] drm/atmel-hlcdc: Drop custom encoder cleanup func.

drm_encoder_cleanup() finishes with memsetting it to 0, already. Signed-off-by: Eric Anholt --- drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 8 +--- 1 file changed, 1 insertion(+), 7 deletions(-) diff --git a/drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c

[PATCH v2 5/7] drm/ltdc: Use the panel-bridge helper.

Another 100 lines of boilerplate gone. Bridges aren't supported yet, but will be trivial to add later. Signed-off-by: Eric Anholt --- Also untested. drivers/gpu/drm/stm/ltdc.c | 128 + drivers/gpu/drm/stm/ltdc.h | 2 +- 2 files

[PATCH v2 2/7] drm/vc4: Switch DSI to the panel-bridge layer, and support bridges.

The newer version of the RPi panel driver is going to be a combination of a bridge and a panel, but we should also support panels without a bridge, so the panel-bridge layer lets us do that cleanly. v2: Drop "dev" argument. Signed-off-by: Eric Anholt Acked-by: Daniel Vetter

[PATCH v2 3/7] drm/vc4: Switch DPI to using the panel-bridge helper.

Another 100 lines of boilerplate gone, while allowing for bridges to be connected in the display chain. Signed-off-by: Eric Anholt --- drivers/gpu/drm/vc4/vc4_dpi.c | 164 -- 1 file changed, 30 insertions(+), 134 deletions(-) diff --git

[PATCH v2 1/7] drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge.

Many DRM drivers have common code to make a stub connector implementation that wraps a drm_panel. By wrapping the panel in a DRM bridge, all of the connector code (including calls during encoder enable/disable) goes away. v2: Fix build with CONFIG_DRM=m, drop "dev" argument that should just

[PATCH v2 4/7] drm/mediatek: Use the panel-bridge helper.

Avoids a bunch of connector boilerplate. Note that this causes panel prepare() to be moved before mtk_dsi_poweron() and unprepare() to be after poweroff(). I think this is the expected usage of the panel API (enable should be when you do things that require the link to be brought up), but there

Re: [Intel-gfx] [PATCH 1/2] drm/dp: start a DPCD based DP sink/branch device quirk database

On Thu, May 11, 2017 at 12:57:20PM +0300, Jani Nikula wrote: > Face the fact, there are Display Port sink and branch devices out there > in the wild that don't follow the Display Port specifications, or they > have bugs, or just otherwise require special treatment. Start a common > quirk database

[radeon-alex:vega10-drop0509 1379/1987] drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:356:11: warning: format '%llx' expects argument of type 'long long unsigned int', but argument 3 has type 'resource_s

tree: git://people.freedesktop.org/~agd5f/linux.git vega10-drop0509 head: b97044091f42cad26368a402c31af13e1319c7ab commit: f0829a4c8f2abc5b12bfd7a4338b97864cfd2e47 [1379/1987] port in all files config: i386-allmodconfig (attached as .config) compiler: gcc-6 (Debian 6.2.0-3) 6.2.0 20160901

[Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.

https://bugs.freedesktop.org/show_bug.cgi?id=96868 --- Comment #21 from Alex Deucher --- Created attachment 131322 --> https://bugs.freedesktop.org/attachment.cgi?id=131322=edit possible fix 4/4 -- You are receiving this mail because: You are the assignee for the

[Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.

https://bugs.freedesktop.org/show_bug.cgi?id=96868 --- Comment #20 from Alex Deucher --- Created attachment 131321 --> https://bugs.freedesktop.org/attachment.cgi?id=131321=edit possible fix 3/4 -- You are receiving this mail because: You are the assignee for the

[Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.

https://bugs.freedesktop.org/show_bug.cgi?id=96868 --- Comment #19 from Alex Deucher --- Created attachment 131320 --> https://bugs.freedesktop.org/attachment.cgi?id=131320=edit possible fix 2/4 -- You are receiving this mail because: You are the assignee for the

[Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.

https://bugs.freedesktop.org/show_bug.cgi?id=96868 --- Comment #18 from Alex Deucher --- Created attachment 131319 --> https://bugs.freedesktop.org/attachment.cgi?id=131319=edit possible fix 1/4 Does this patch set help? -- You are receiving this mail because: You are

Re: [PATCH 2/3] drm: Create a format/modifier blob

On 17-05-03 14:15:15, Liviu Dudau wrote: On Tue, May 02, 2017 at 10:14:27PM -0700, Ben Widawsky wrote: Updated blob layout (Rob, Daniel, Kristian, xerpi) Cc: Rob Clark Cc: Daniel Stone Cc: Kristian H. Kristensen Signed-off-by:

[Bug 101007] AMDgpu kernel BUG with 5 cards

https://bugs.freedesktop.org/show_bug.cgi?id=101007 Christian König changed: What|Removed |Added Status|RESOLVED|CLOSED ---

[Bug 101007] AMDgpu kernel BUG with 5 cards

https://bugs.freedesktop.org/show_bug.cgi?id=101007 --- Comment #3 from GSaraber --- Created attachment 131318 --> https://bugs.freedesktop.org/attachment.cgi?id=131318=edit lspci output Here's the lspci -vvv output -- You are receiving this mail because: You are the

[Bug 101007] AMDgpu kernel BUG with 5 cards

https://bugs.freedesktop.org/show_bug.cgi?id=101007 GSaraber changed: What|Removed |Added Resolution|--- |NOTABUG

[Bug 96868] AMDGPU Tonga only does 2560x1440 at 120hz, switching to 144hz causes display errors, same thing used to happen with fglrx.

https://bugs.freedesktop.org/show_bug.cgi?id=96868 --- Comment #17 from Andy Furniss --- Oh, OK, I don't know whether that's expected or not on an R9 390 -- You are receiving this mail because: You are the assignee for the

[Bug 99029] VCE VAAPI segfault using ffmpeg

https://bugs.freedesktop.org/show_bug.cgi?id=99029 --- Comment #6 from Andy Furniss --- (In reply to Martin Bednar from comment #4) > The file is the OSS Elephant's dream movie : https://orange.blender.org/ > Purposely tested with this for easy sharing. > Contained streams

Re: [PATCH 2/2] drm/i915: Detect USB-C specific dongles before reducing M and N

On 05/11/2017 02:57 AM, Jani Nikula wrote: From: Clint Taylor The Analogix 7737 DP to HDMI converter requires reduced M and N values when to operate correctly at HBR2. Detect this IC by its OUI value of 0x0022B9 via the DPCD quirk list. v2 by Jani: Rebased on the

Re: [PATCH 1/2] drm/dp: start a DPCD based DP sink/branch device quirk database

On 05/11/2017 02:57 AM, Jani Nikula wrote: Face the fact, there are Display Port sink and branch devices out there in the wild that don't follow the Display Port specifications, or they have bugs, or just otherwise require special treatment. Start a common quirk database the drivers can query

[Bug 100984] QupZilla crashes at startup after mesa upgrade

https://bugs.freedesktop.org/show_bug.cgi?id=100984 --- Comment #4 from Francesco Turco --- See also https://bugs.gentoo.org/show_bug.cgi?id=618206 -- You are receiving this mail because: You are the assignee for the bug.___

Re: [PATCH v2 0/3] drm/amd/display: add HDMI Stereo 3D support

Note, the higher level pieces are not yet in place, for this to work on X for instance. I started to look at that a while back, only to realize the kernel driver needed help first. On Thu, May 11, 2017 at 10:33 AM, Jeffrey Smith wrote: > I took the work from

[Bug 101007] AMDgpu kernel BUG with 5 cards

https://bugs.freedesktop.org/show_bug.cgi?id=101007 --- Comment #1 from Christian König --- Please attach the output of "sudo lspci -". -- You are receiving this mail because: You are the assignee for the bug.___

[Bug 101007] AMDgpu kernel BUG with 5 cards

https://bugs.freedesktop.org/show_bug.cgi?id=101007 Bug ID: 101007 Summary: AMDgpu kernel BUG with 5 cards Product: DRI Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity:

  1   2   >