[PATCH] drm/atomic: Add new reverse iterator over all plane state (V2)

From: Shirish S Add reverse iterator for_each_oldnew_plane_in_state_reverse to compliment the for_each_oldnew_plane_in_state way or reading plane states. The plane states are required to be read in reverse order for amd drivers, cause the z order convention followed in

Re: [PATCH v4 6/6] drm/omap: Use normalized zpos for plane placement

On 06/02/18 14:05, Peter Ujfalusi wrote: > Planes with identical zpos value will result undefined behavior: > disappearing planes, screen flickering and it is not supported by the > hardware. > > Use normalized zpos to make sure that we don't encounter invalid > configuration. > > Signed-off-by:

Re: [PATCHv2 17/17] drm/omap: cleanup color space conversion

On 28/02/18 23:23, Laurent Pinchart wrote: >> +REG_FLD_MOD(dispc, DISPC_OVL_ATTRIBUTES(plane), !!ct->full_range, 11, >> 11); > > I think I mentioned in my review of v1 that you can drop the !!. Apart from > that, > > Reviewed-by: Laurent Pinchart Sorry

[Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes

https://bugs.freedesktop.org/show_bug.cgi?id=105302 Bug ID: 105302 Summary: [DC] - Maximum pixel clock of dual-link DVI too low for some modes Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS:

[Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel)

https://bugs.freedesktop.org/show_bug.cgi?id=104001 --- Comment #24 from mikhail.v.gavri...@gmail.com --- Created attachment 137710 --> https://bugs.freedesktop.org/attachment.cgi?id=137710=edit photo of test when computer is hang -- You are receiving this mail because: You are the assignee

[Bug 104001] GPU driver hung when start steam client while playback video on Youtube (it occurs on latest staging kernel)

https://bugs.freedesktop.org/show_bug.cgi?id=104001 --- Comment #23 from mikhail.v.gavri...@gmail.com --- Found you another crash case: The @GraphicsFuzz demo found 1 issue (14/15 tests passed) on my desktop device, affecting my @AMD GPU driver Give it a try: www.graphicsfuzz.com/#demo

Re: [DPU PATCH 06/11] drm/msm: Remove msm_commit/kthread, use atomic helper commit

On 2018-02-28 11:19, Sean Paul wrote: Moving further towards switching fully to the the atomic helpers, this patch removes the hand-rolled kthread nonblock commit code and uses the atomic helpers commit_work model. There's still a lot of copypasta here, but it's still needed to facilitate the

[Bug 105262] ttf fonts are invisible

https://bugs.freedesktop.org/show_bug.cgi?id=105262 --- Comment #8 from Pavel Vinogradov --- Sorry, no qt stuff here, but I have rxvt-unicode with the same problem. So, it's not gtk specific. (In reply to LoneVVolf from comment #5) > Installed gvim to verify, and that has

[Bug 105244] NULL dereference during startup of Cape Verde with AMDGPU and GPU passthrough

https://bugs.freedesktop.org/show_bug.cgi?id=105244 --- Comment #4 from Alex Deucher --- SI still uses the legacy dpm code rather than powerplay so it doesn't expose all the same options as newer chips. SI also has an older smu implementation so it has a more limited

Re: [Xen-devel] [PATCH 0/9] drm/xen-front: Add support for Xen PV display frontend

On Wed, 28 Feb 2018, Julien Grall wrote: > (+ Stefano and Wei) > > Hi, > > On 02/27/2018 12:40 PM, Oleksandr Andrushchenko wrote: > > Please find some more clarifications on VirtIO use with Xen > > (I would like to thank Xen community for helping with this) > > > > 1. Possible security issues -

Re: [PATCH 0/9] drm/xen-front: Add support for Xen PV display frontend

Hi all, just as a clarification, this patch series implements the frontend driver for the "vdispl" protocol, which was reviewed, approved and committed in xen.git back in April: https://xenbits.xen.org/gitweb/?p=xen.git;a=blob;f=xen/include/public/io/displif.h As Xen maintainer, if a competing

[PULL] drm-intel-fixes

Hi Dave, I have these same patches stashed since last week, but last week I wasn't confident that CI was happy with these ones so I decided to hold on. Now after running multiple times with and without the patches applied I see that it was only a fix on test case, which is now catching old bugs

[radeon-alex:amd-staging-drm-next 699/734] sound/soc//amd/raven/pci-acp3x.c:122:2: error: implicit declaration of function 'pci_disable_msi'; did you mean 'pci_disable_sriov'?

Hi Maruthi, FYI, the error/warning still remains. tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: 2846f4ca3abe46839b82f424cc2ef935a3cb038a commit: 944b5289c92d9c1aad3760c012daf4cf2478381f [699/734] ASoC: AMD: enable ACP3x drivers build config: sh-allyesconfig

[Bug 105244] NULL dereference during startup of Cape Verde with AMDGPU and GPU passthrough

https://bugs.freedesktop.org/show_bug.cgi?id=105244 --- Comment #3 from Bas Nieuwenhuizen --- Sorry for the delay, I can confirm this fixes the NULL issue. pp_dpm_mclk / pp_dpm_sclk look empty to me, not sure though if that is just because they are not hooked up yet

[PATCH] drm/radeon/mkregtable: Delete unused list functions and macros

The util mkregtable includes a copy of the kernel API for linked lists, only a small subset of it is used. Delete the unused functions and macros. Signed-off-by: Matthias Kaehlcke --- drivers/gpu/drm/radeon/mkregtable.c | 433 1 file changed, 433

Re: [PATCH v2 1/2] drm/panel: Remove drm_panel_detach() calls from all panel drives

On 28/02/18 20:53, Thierry Reding wrote: > On Wed, Feb 28, 2018 at 01:09:29PM +0200, Jyri Sarha wrote: >> Setting the connector and drm to NULL when the drm panel device is >> going away hardly serves any purpose. Usually the the whole memory >> stucture is freed right after the remove call. >> >>

Re: [PATCHv2 17/17] drm/omap: cleanup color space conversion

Hi Tomi, Thank you for the patch. On Wednesday, 28 February 2018 13:26:14 EET Tomi Valkeinen wrote: > The setup code for color space conversion is a bit messy. This patch > cleans it up. > > For some reason the TRM uses values in YCrCb order, which is also used > in the current driver, whereas

Re: [PATCHv2 04/17] drm/omap: add HPD support to connector-dvi

Hi Tomi, Thank you for the patch. On Wednesday, 28 February 2018 13:26:01 EET Tomi Valkeinen wrote: > Add HPD support to the DVI connector driver. The code is almost > identical to the HPD code in the HDMI connector driver. > > Signed-off-by: Tomi Valkeinen Reviewed-by:

Re: [PATCHv2 02/17] drm/omap: cleanup fbdev init/free

Hi Tomi, Thank you for the patch. On Wednesday, 28 February 2018 13:25:59 EET Tomi Valkeinen wrote: > omap_fbdev_init() and omap_fbdev_free() use priv->fbdev directly. > However, omap_fbdev_init() returns the fbdev, and omap_drv.c also > assigns the return value to priv->fbdev. This is slightly

[Bug 36072] celestia causes kernel oops when allocation a lot of memory (for textures)

https://bugzilla.kernel.org/show_bug.cgi?id=36072 aceman (aceli...@atlas.sk) changed: What|Removed |Added Status|REOPENED|RESOLVED

Re: [RFC][PATCH 04/11] drm: Split the display info into static and dynamic parts

On Tue, Feb 27, 2018 at 7:56 AM, Ville Syrjala wrote: > From: Ville Syrjälä > > Currently we have a mix of static and dynamic information stored in > the display info structure. That makes it rather difficult to repopulate > the

RE: [PATCH 1/1] drm: Add dirty_rects atomic blob property for drm_plane

> -Original Message- > From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf > Of Daniel Vetter > Sent: Thursday, December 21, 2017 5:11 AM > To: Ville Syrjälä > Cc: airl...@linux.ie; daniel.vet...@intel.com; dri- >

Re: [Intel-gfx] [PATCH 5/8] drm/i915: Fix plane YCbCr->RGB conversion for GLK

On Wed, Feb 14, 2018 at 09:23:24PM +0200, Ville Syrjala wrote: > From: Ville Syrjälä > > On GLK the plane CSC controls moved into the COLOR_CTL register. > Update the code to progam the YCbCr->RGB CSC mode correctly when > faced with an YCbCr framebuffer. > > The

[pull] amdgpu drm-fixes-4.16

Hi Dave, A few misc fixes for 4.16. The following changes since commit 219b3b22df9d828367a4eeceed7600890e2ff4ef: Merge branch 'drm-fixes-4.16' of git://people.freedesktop.org/~agd5f/linux into drm-fixes (2018-02-28 11:39:52 +1000) are available in the git repository at:

[PULL] drm-misc-next

Hi Dave, Here's this weeks pull, relatively small when you pull out the trivial fixes. drm-misc-next-2018-02-28: drm-misc-next for 4.17: UAPI Changes: Fix drm_color_ctm matrix docs to match usage and change the type to __u64 make it obvious (Ville) Core Changes: Check modifier with format

[Bug 105300] amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock

https://bugs.freedesktop.org/show_bug.cgi?id=105300 Bug ID: 105300 Summary: amd-staging-drm-next-git 4.16 & RX 560 DL-DVI: corruption with refreshrates >73Hz when DPM changing VRAM clock Product: DRI Version:

[Bug 104555] RX 560 DPM auto - driver doesn't reliably set high clocks, causing stutter in mpv

https://bugs.freedesktop.org/show_bug.cgi?id=104555 tempel.jul...@gmail.com changed: What|Removed |Added Severity|major |normal -- You are receiving

Re: [PATCH] tinydrm: add backlight dependency

On Wed, Feb 28, 2018 at 02:40:48PM +0100, Arnd Bergmann wrote: > Calling devm_of_find_backlight directly means we get a link failure > without CONFIG_BACKLIGHT_CLASS_DEVICE: > > drivers/gpu/drm/tinydrm/mi0283qt.o: In function `mi0283qt_probe': > mi0283qt.c:(.text+0x684): undefined reference to

Re: [PATCH v3 05/10] pwm: add PWM mode to pwm_config()

On Wed, 28 Feb 2018, Thierry Reding wrote: > Anyone that needs something other than normal mode should use the new > atomic PWM API. At the risk of revealing my true ignorance, what is the new atomic PWM API? Where? Examples of how one would convert old code over to the

Re: [PATCH 8/9] drm/xen-front: Implement GEM operations

On 02/28/2018 09:46 PM, Boris Ostrovsky wrote: On 02/27/2018 01:52 AM, Oleksandr Andrushchenko wrote: On 02/27/2018 01:47 AM, Boris Ostrovsky wrote: On 02/23/2018 10:35 AM, Oleksandr Andrushchenko wrote: On 02/23/2018 05:26 PM, Boris Ostrovsky wrote: On 02/21/2018 03:03 AM, Oleksandr

Re: [PATCH v2 0/2] drm/panel: Add device link in drm_panel_attach()

On Wed, Feb 28, 2018 at 01:09:28PM +0200, Jyri Sarha wrote: > The device_link_del() is still there in drm_panel_detach(), despite > Lukas Wunner's comment[1]. In the usual (currently all) cases things > would work perfectly without the call too, because > device_links_driver_cleanup() will

Re: [PATCH v3 05/10] pwm: add PWM mode to pwm_config()

On Thu, Feb 22, 2018 at 02:01:16PM +0200, Claudiu Beznea wrote: > Add PWM mode to pwm_config() function. The drivers which uses pwm_config() > were adapted to this change. > > Signed-off-by: Claudiu Beznea > --- > arch/arm/mach-s3c24xx/mach-rx1950.c | 11

Re: [PATCH v2 2/2] drm/panel: Add device_link from panel device to drm device

On Wed, Feb 28, 2018 at 01:09:30PM +0200, Jyri Sarha wrote: > Add device_link from panel device (supplier) to drm device (consumer) > with DL_FLAG_AUTOREMOVE when drm_panel_attach() is called. Currently > the master drm driver is not protected against the attached. The > device_link with

[DPU PATCH 07/11] drm/msm: Use atomic private_obj instead of subclassing

Instead of subclassing atomic state, store driver private data in private_obj/state. This allows us to remove the swap_state driver hook for mdp5 and get closer to using the atomic helpers entirely. Change-Id: I65a4a2887593ae257d584e00b352b5daf00e4e61 Signed-off-by: Sean Paul

[DPU PATCH 11/11] drm/msm: Remove dpu input fences

These are already provided by drm atomic core. In conjunction with the output fences removed earlier, this obsoletes dpu_fence, and it can be entirely removed as well. Change-Id: Ida4924a09c455d7a84bfee569bd0d2fb436418de Signed-off-by: Sean Paul ---

[DPU PATCH 06/11] drm/msm: Remove msm_commit/kthread, use atomic helper commit

Moving further towards switching fully to the the atomic helpers, this patch removes the hand-rolled kthread nonblock commit code and uses the atomic helpers commit_work model. There's still a lot of copypasta here, but it's still needed to facilitate the swap_state and prepare_fence private

[DPU PATCH 09/11] drm/msm: Remove prepare_fence kms_function

This is the last piece that is keeping us from matching the atomic helper commit function. By removing this (now unused) hook, we can switch to drm_atomic_helper_commit() Change-Id: I081056a6e1689807871f5deedc76499bb91b6969 Signed-off-by: Sean Paul ---

[DPU PATCH 05/11] drm/msm: Mark the crtc->state->event consumed

Don't leave the event != NULL once it's consumed, this is used a signal to the atomic helpers that the event will be handled by the driver. Change-Id: Ib934fb2e97bacbb4a1f9c780cc7369c2bb98ed50 Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 ++

[DPU PATCH 10/11] drm/msm: Switch to atomic_helper_commit()

Now that all of the msm-specific goo is tucked safely away we can switch over to using the atomic helper commit directly. \o/ Change-Id: Ieab0bd0c526b2a9d3b3345eeba402ac4857fe418 Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/msm_atomic.c | 120

[DPU PATCH 03/11] drm/msm: Refactor complete_commit() to look more the helpers

Factor out the commit_tail() portions of complete_commit() into a separate function to facilitate moving to the atomic helpers in future patches. Change-Id: I4b858ad9fe356b31ed0ed9eecdb394a61048e39c Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/msm_atomic.c | 25

[DPU PATCH 08/11] drm/msm: Remove hand-rolled out fences

Remove release/output/retire fences from the dpu driver. These are already available via drm core's OUT_FENCE property. Change-Id: Id4238d0b5457f2c8ee2e87bb7814e1850a573623 Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/disp/dpu1/dpu_connector.c | 66 +--

[DPU PATCH 02/11] drm/msm: Don't duplicate modeset_enables atomic helper

Instead, shuffle things around so we kickoff crtc after enabling encoder during modesets. Also moves the vblank wait to after the frame. Change-Id: I16c7b7f9390d04f6050aa20e17a5335fbf49eba3 Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c| 9 ++

[DPU PATCH 00/11] drm/msm: Use atomic helper functions for msm

Hey! This set converts msm to using the atomic helper functions for commit. In order to do this, I needed to do the following: Relocate/remove the copied atomic helper code from msm_atomic: Most of this was to deal with seamless modesets introduced in the dpu. I'll need to revisit the

[DPU PATCH 01/11] drm/msm: Skip seamless disables in crtc/encoder

Instead of duplicating whole swaths of atomic helper functions (which are already out-of-date), just skip the encoder/crtc disables in the .disable hooks. Change-Id: I7bd9183ae60624204fb1de9550656b776efc7202 Signed-off-by: Sean Paul ---

[DPU PATCH 04/11] drm/msm: Move implicit sync fence handling to prepare_fb

This is another piece that can be moved out of atomic to facilitate using the atomic helpers. Change-Id: I6dc3c4e5df508942bbc378c73a44e46e511b8469 Signed-off-by: Sean Paul --- drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 8 drivers/gpu/drm/msm/msm_atomic.c

Re: [PATCH v1 2/2] drm/panel: Add support for Raydium rm68200 panel driver

On Thu, Feb 08, 2018 at 03:30:26PM +0100, Philippe Cornu wrote: > This patch adds Raydium Semiconductor Corporation rm68200 > 5.5" 720x1280 TFT LCD panel driver (MIPI-DSI video mode). > > Signed-off-by: Philippe Cornu > --- > drivers/gpu/drm/panel/Kconfig

[Bug 102323] [DC] System crashes when woken up from S3 sleep while HDMI display is switched off

https://bugs.freedesktop.org/show_bug.cgi?id=102323 --- Comment #7 from Arvind --- (In reply to dwagner from comment #6) > @Arvind: From the description of the symptoms you experience it might be > rather the scenario of

Re: [PATCH v2 1/2] drm/panel: Remove drm_panel_detach() calls from all panel drives

On Wed, Feb 28, 2018 at 01:09:29PM +0200, Jyri Sarha wrote: > Setting the connector and drm to NULL when the drm panel device is > going away hardly serves any purpose. Usually the the whole memory > stucture is freed right after the remove call. > > Signed-off-by: Jyri Sarha >

[PATCH libdrm] omap: add Android build support

From: Gowtham Tammana Add Android.mk file to build libdrm_omap library. Signed-off-by: Gowtham Tammana Signed-off-by: Andrew F. Davis --- omap/Android.mk | 13 + 1 file changed, 13 insertions(+) create mode 100644 omap/Android.mk

Re: [PATCH v2] drm/panel: simple: Add TVC S9700RTWV43TR-01B 800x480 panel support

On Wed, Feb 28, 2018 at 12:40:43PM +0200, Jyri Sarha wrote: > Add support for TVC S9700RTWV43TR-01B 800x480 panel found on TI's > AM335X-EVM. > > Signed-off-by: Jyri Sarha > Reviewed-by: Tomi Valkeinen > --- > The only change is added "Reviewed-by: Tomi

Re: [PATCH] drm/sun4i: init dclk_min_div & dclk_max_div inside encoder init functions

Hi, Il 28/02/2018 17:34, Giulio Benetti ha scritto: Hi, Il 28/02/2018 16:55, Maxime Ripard ha scritto: Hi, On Wed, Feb 28, 2018 at 01:51:58PM +0100, Giulio Benetti wrote: sun4i_dclk_round_rate is called before sun4i_tcon_mode_set, so it finds dclk_min_div and dclk_max_div set to 0 and fails

Re: [PATCH v2 2/2] drm/panel: Add device_link from panel device to drm device

Jyri Sarha writes: > Add device_link from panel device (supplier) to drm device (consumer) > with DL_FLAG_AUTOREMOVE when drm_panel_attach() is called. Currently > the master drm driver is not protected against the attached. The > device_link with DL_FLAG_AUTOREMOVE should make

Aspirant for GSOC 2018 for Nouveau Vulkan driver

Hi, I would like to participate in GSOC 2018 with Xorg to contribute to project "Initial Nouveau Vulkan driver' I would need some help in how to get started with the same. Regards, Anusha Srivastava ___ dri-devel mailing list

[PATCH 2/2] drm/sun4i: add lvds mode_valid function

mode_valid function is missing for lvds. Add it based on rgb model, also setting up dclk_min_div and dclk_max_div Signed-off-by: Giulio Benetti --- drivers/gpu/drm/sun4i/sun4i_lvds.c | 55 ++ 1 file changed, 55 insertions(+)

[PATCH 1/2] drm/sun4i: increase lvds dclk max divisor

At the moment both min and max dclk div are set to 7. This doesn't allow to have lower frequencies. Increase dclk_max_div to 18 to achieve 30Mhz. Signed-off-by: Giulio Benetti --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 2 +- 1 file changed, 1 insertion(+), 1

Re: [PATCH libdrm] meson: add configuration summary

Quoting Eric Engestrom (2018-02-28 07:11:20) > On Tuesday, 2018-02-27 12:30:48 -0800, Eric Anholt wrote: > > Dylan Baker writes: > > > > > [ Unknown signature status ] > > > Quoting Eric Engestrom (2018-02-27 03:11:07) > > >> The message block printed is the same as the one

Re: [PATCH v2] drm/panel: simple: Add TVC S9700RTWV43TR-01B 800x480 panel support

Jyri Sarha writes: > Add support for TVC S9700RTWV43TR-01B 800x480 panel found on TI's > AM335X-EVM. > > Signed-off-by: Jyri Sarha > Reviewed-by: Tomi Valkeinen > --- > The only change is added "Reviewed-by: Tomi Valkeinen >

[Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock)

https://bugs.freedesktop.org/show_bug.cgi?id=104274 --- Comment #12 from Jordan L --- Thanks. Just to clarify, you aren't able to enable DC with your current Kconfig configuration, which prevents you from retrying on this ticket? If so, please just open a new bug rather

[Bug 105284] Every boot I get an error in dmesg "WARNING: CPU: 2 PID: 1380 at drivers/gpu/drm/amd/amdgpu/../display/dc/dm_services.h:132 generic_reg_update_ex+0x108/0x150 [amdgpu]"

https://bugs.freedesktop.org/show_bug.cgi?id=105284 --- Comment #2 from mikhail.v.gavri...@gmail.com --- (In reply to Harry Wentland from comment #1) > Is this on a Vega or Raven ASIC? > > If so it's known and a fix should land shortly. This is Sapphire Radeon RX VEGA 56 -- You are receiving

Re: [2/3] drm/sun4i: rgb: Fix potential division by zero

Il 21/02/2018 13:57, Maxime Ripard ha scritto: In the case where mode_valid callback of our RGB connector was called before mode_set was being called, the range of dividers would not be set, resulting in a division by zero later on in the clk_round_rate logic. Set the range of dividers before

[PATCH v6 3/3] drm: writeback: Add client capability for exposing writeback connectors

Due to the fact that writeback connectors behave in a special way in DRM (they always report being disconnected) we might confuse some userspace. Add a client capability for writeback connectors that will filter them out for clients that don't understand the capability. Re-requested-by: Sean Paul

[PATCH v6 1/3] drm: Add writeback connector type

From: Brian Starkey Writeback connectors represent writeback engines which can write the CRTC output to a memory framebuffer. Add a writeback connector type and related support functions. Drivers should initialize a writeback connector with drm_writeback_connector_init()

[PATCH v6 2/3] drm: writeback: Add out-fences for writeback connectors

From: Brian Starkey Add the WRITEBACK_OUT_FENCE_PTR property to writeback connectors, to enable userspace to get a fence which will signal once the writeback is complete. It is not allowed to request an out-fence without a framebuffer attached to the connector. A timeline

[PATCH v6 0/3] drm: Introduce writeback connectors

Hi, This is v6 of the writeback connector series. Based on renewed interest in the feature and recent efforts from Rob Clark I'm refreshing the series to address some comments and feedback. Main changes are to incorporate Rob Clark's atomic_commit() vfunc for the connector helper funcs, change

[PATCH] drm/sun4i: Fix dclk_set_phase

Phase value is not shifted before writing. Shift left of 28 bits to fit right bits Signed-off-by: Giulio Benetti --- drivers/gpu/drm/sun4i/sun4i_dotclock.c | 5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #21 from Kyle De'Vir (kyle.de...@mykolab.com) --- > I don't see any DC or other DRM change in the stable kernel between 4.15.5 > and 4.15.6. What about any of the other point releases? I tried without your patch, and amdgpu.dc=1

[Bug 105262] ttf fonts are invisible

https://bugs.freedesktop.org/show_bug.cgi?id=105262 --- Comment #7 from LoneVVolf --- I started bisecting this. Had to move head several times due to build failures and runtime problems, but managed to find some more good commits. $ git bisect log git bisect start # good:

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #20 from Kyle De'Vir (kyle.de...@mykolab.com) --- I'm going to test without your patch to see if the problem pops up again. -- You are receiving this mail because: You are watching the assignee of the bug.

Re: [PATCH] drm/sun4i: init dclk_min_div & dclk_max_div inside encoder init functions

Hi, Il 28/02/2018 16:55, Maxime Ripard ha scritto: Hi, On Wed, Feb 28, 2018 at 01:51:58PM +0100, Giulio Benetti wrote: sun4i_dclk_round_rate is called before sun4i_tcon_mode_set, so it finds dclk_min_div and dclk_max_div set to 0 and fails adding crtc. Move dclk_min_div and dclk_max_div to

Re: [PATCH] drm/drm_ioctl.c: Test client capability value early when setting.

On Wed, Feb 28, 2018 at 05:57:15PM +0200, Ville Syrjälä wrote: > On Wed, Feb 28, 2018 at 03:44:44PM +, Liviu Dudau wrote: > > On Wed, Feb 28, 2018 at 05:40:41PM +0200, Ville Syrjälä wrote: > > > On Wed, Feb 28, 2018 at 03:27:41PM +, Liviu Dudau wrote: > > > > The drm_setclientcap()

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #9 from Michael Zapf --- Unfortunately, that does not work, I just tried it. I suppose that otherwise, turning the monitor off and on should have already helped. The only way to restore leads me via killing the

Re: [Xen-devel] [PATCH 0/9] drm/xen-front: Add support for Xen PV display frontend

(+ Stefano and Wei) Hi, On 02/27/2018 12:40 PM, Oleksandr Andrushchenko wrote: Please find some more clarifications on VirtIO use with Xen (I would like to thank Xen community for helping with this) 1. Possible security issues - VirtIO devices are PCI bus masters, thus allowing real device

Re: [PATCH v3 05/43] drm/bridge: analogix_dp: Don't power bridge in analogix_dp_bind

On 28/02/18 14:37, Heiko Stübner wrote: > Am Dienstag, 30. Januar 2018, 21:28:35 CET schrieb Thierry Escande: >> From: zain wang >> >> The bridge does not need to be powered in analogix_dp_bind(), so >> remove the calls to pm_runtime_get()/phy_power_on()/analogix_dp_init_dp()

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #19 from Harry Wentland (harry.wentl...@amd.com) --- I don't see any DC or other DRM change in the stable kernel between 4.15.5 and 4.15.6. -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH] drm/sun4i: Handle DRM_BUS_FLAG_PIXDATA_*EDGE

Handle both positive and negative dclk polarity, according to bus_flags. Signed-off-by: Giulio Benetti --- drivers/gpu/drm/sun4i/sun4i_tcon.c | 13 - 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/sun4i/sun4i_tcon.c

[Bug 105284] Every boot I get an error in dmesg "WARNING: CPU: 2 PID: 1380 at drivers/gpu/drm/amd/amdgpu/../display/dc/dm_services.h:132 generic_reg_update_ex+0x108/0x150 [amdgpu]"

https://bugs.freedesktop.org/show_bug.cgi?id=105284 --- Comment #1 from Harry Wentland --- Is this on a Vega or Raven ASIC? If so it's known and a fix should land shortly. -- You are receiving this mail because: You are the assignee for the

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #18 from Kyle De'Vir (kyle.de...@mykolab.com) --- Actually, there was a change! Didn't have to boot headless at all, happily. Your patch didn't seem to change anything, but the update to 4.15.6 might have done something...? Did

Re: [PATCH] drm/drm_ioctl.c: Test client capability value early when setting.

On Wed, Feb 28, 2018 at 03:44:44PM +, Liviu Dudau wrote: > On Wed, Feb 28, 2018 at 05:40:41PM +0200, Ville Syrjälä wrote: > > On Wed, Feb 28, 2018 at 03:27:41PM +, Liviu Dudau wrote: > > > The drm_setclientcap() function implementing the DRM_IOCTL_SET_CLIENT_CAP > > > ioctl expects that

Re: [PATCH 2/2] drm/sun4i: Handle DRM_MODE_FLAG_**SYNC_POSITIVE correctly

Hi, Il 16/02/2018 16:50, Maxime Ripard ha scritto: On Thu, Feb 15, 2018 at 07:05:56PM +0100, Giulio Benetti wrote: If so, and if remember the captures properly, the sampling would occur right before the rise, and not really around the fall. Would 2/3 be better here? Yes, you're right, 2/3

Re: [PATCH] drm/sun4i: init dclk_min_div & dclk_max_div inside encoder init functions

Hi, On Wed, Feb 28, 2018 at 01:51:58PM +0100, Giulio Benetti wrote: > sun4i_dclk_round_rate is called before sun4i_tcon_mode_set, > so it finds dclk_min_div and dclk_max_div set to 0 and fails > adding crtc. > > Move dclk_min_div and dclk_max_div to encoders init functions. > > Signed-off-by:

[PATCH 02/23] drm/mali-dp: Align pitch size to be multiple of bus burst read size.

Mali DP hardware needs pitch line sizes aligned to the bus burst size for reads, so take that into consideration when allocating dumb buffers. If the layer is rotated then the stride size requirement is even larger for some hardware versions, so allocate for the worst case scenario. Update the

[PATCH 04/23] drm/mali-dp: Don't enable scaling engine for planes that only rotate.

Currently the scaling engine gets enabled for a plane where the input size differs from the composition size. As rotation is done natively by the plane's hardware layer, we don't need the scaling engine to be enabled. Signed-off-by: Liviu Dudau ---

[PATCH 01/23] drm/mali-dp: Rotated planes need a larger pitch size.

Rotated planes need a pitch size that is aligned to 8 bytes for older DP500 and DP550 and at least 64 bytes for DP650. Replace the malidp_hw_pitch_valid() function with one that calculates the correct pitch alignment to take into account rotation. Signed-off-by: Liviu Dudau

Re: [PATCH] drm/drm_ioctl.c: Test client capability value early when setting.

On Wed, Feb 28, 2018 at 05:40:41PM +0200, Ville Syrjälä wrote: > On Wed, Feb 28, 2018 at 03:27:41PM +, Liviu Dudau wrote: > > The drm_setclientcap() function implementing the DRM_IOCTL_SET_CLIENT_CAP > > ioctl expects that any capability set by the client will have a value of 1. > > Make the

Re: [PATCH] drm/drm_ioctl.c: Test client capability value early when setting.

On Wed, Feb 28, 2018 at 03:27:41PM +, Liviu Dudau wrote: > The drm_setclientcap() function implementing the DRM_IOCTL_SET_CLIENT_CAP > ioctl expects that any capability set by the client will have a value of 1. > Make the check early so that we don't have to test the value for each >

[PULL] drm-misc-fixes

Hi Dave, A few more fixes for 4.16, including 2 regression fixes. Please pull. Thanks, Gustavo drm-misc-fixes-2018-02-28: Two regression fixes here: a fb format regression on nouveau and a 4.16-rc1 regression with on LVDS with one sun4i device. Plus a sun4i and a virtio-gpu fixes. The

[Bug 105046] Screen resolution reset to 1368x768 when turning monitor off

https://bugs.freedesktop.org/show_bug.cgi?id=105046 --- Comment #8 from Harry Wentland --- Unplugging and replugging the display should get you back to normal. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH 0/3] console: Expand dummy functions for CFI

On Wed, Feb 28, 2018 at 04:14:38PM +0100, Bartlomiej Zolnierkiewicz wrote: > On Wednesday, February 28, 2018 04:09:47 PM Bartlomiej Zolnierkiewicz wrote: > > On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote: > > > This is a small series that cleans up struct consw a bit and > > > prepares

[PATCH] drm/drm_ioctl.c: Test client capability value early when setting.

The drm_setclientcap() function implementing the DRM_IOCTL_SET_CLIENT_CAP ioctl expects that any capability set by the client will have a value of 1. Make the check early so that we don't have to test the value for each capability. Signed-off-by: Liviu Dudau ---

[Bug 198745] Blank screen on RX 580 with AMDGPU Display Core enabled

https://bugzilla.kernel.org/show_bug.cgi?id=198745 --- Comment #17 from Harry Wentland (harry.wentl...@amd.com) --- Thanks for checking. Non-DC display driver and DC do detection somewhat differently. It's somewhat difficult to say what's going wrong there. Do you see different behavior when

Re: [PATCH v3 05/43] drm/bridge: analogix_dp: Don't power bridge in analogix_dp_bind

Am Dienstag, 30. Januar 2018, 21:28:35 CET schrieb Thierry Escande: > From: zain wang > > The bridge does not need to be powered in analogix_dp_bind(), so > remove the calls to pm_runtime_get()/phy_power_on()/analogix_dp_init_dp() > as well as their power-off counterparts. >

Re: [PATCH 0/3] console: Expand dummy functions for CFI

On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote: > This is a small series that cleans up struct consw a bit and > prepares it for Control Flow Integrity checking (i.e. Clang's > -fsanitize=cfi). for drivers/video/ parts: Acked-by: Bartlomiej Zolnierkiewicz

[PATCH] drm: mali-dp: Turn off CRTC vblank when removing module.

When unbinding the mali-dp driver the drm_vblank_cleanup() function warns us that the vblanks are still enabled. Fix that by calling drm_crtc_vblank_off() in the malidp_unbind() function. Signed-off-by: Liviu Dudau --- drivers/gpu/drm/arm/malidp_drv.c | 2 ++ 1 file

Re: [PATCH 0/3] console: Expand dummy functions for CFI

On Wednesday, February 28, 2018 04:09:47 PM Bartlomiej Zolnierkiewicz wrote: > On Monday, February 26, 2018 04:04:17 PM Kees Cook wrote: > > This is a small series that cleans up struct consw a bit and > > prepares it for Control Flow Integrity checking (i.e. Clang's > > -fsanitize=cfi). > > for

[PATCH] drm/arm: mali-dp: Reorder atomic_commit_hw_done to avoid waiting on wrong vblank event

mali-dp driver sets the 'go' bit (config_valid) and then waits for confirmation from the hardware that the config has been updated before arming the vblank event. The issue is that config_valid is actually asserted by the hardware after vblank event, during the prefetch phase, so when arming the

Re: [PATCH libdrm] meson: add configuration summary

On Tuesday, 2018-02-27 12:30:48 -0800, Eric Anholt wrote: > Dylan Baker writes: > > > [ Unknown signature status ] > > Quoting Eric Engestrom (2018-02-27 03:11:07) > >> The message block printed is the same as the one in configure.ac > >> > >> Signed-off-by: Eric Engestrom

RE: [PATCH 05/10] drm: Define helper function for plane color enabling

>-Original Message- >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of >Sean Paul >Sent: Tuesday, February 27, 2018 8:59 PM >To: Daniele Castagna >Cc: dri-devel@lists.freedesktop.org >Subject: Re: [PATCH 05/10] drm: Define helper

Re: [PATCH v3 05/43] drm/bridge: analogix_dp: Don't power bridge in analogix_dp_bind

Am Mittwoch, 28. Februar 2018, 15:54:30 CET schrieb Marc Zyngier: > On 28/02/18 14:37, Heiko Stübner wrote: > > Am Dienstag, 30. Januar 2018, 21:28:35 CET schrieb Thierry Escande: > >> From: zain wang > >> > >> The bridge does not need to be powered in analogix_dp_bind(), so

RE: [PATCH 03/10] drm: Add Plane CTM property

>-Original Message- >From: dri-devel [mailto:dri-devel-boun...@lists.freedesktop.org] On Behalf Of >Sean Paul >Sent: Tuesday, February 27, 2018 8:53 PM >To: Daniele Castagna >Cc: dri-devel@lists.freedesktop.org >Subject: Re: [PATCH 03/10] drm: Add Plane CTM

RE: [PATCH 02/10] drm: Add Plane Degamma properties

>-Original Message- >From: Sean Paul [mailto:seanp...@chromium.org] >Sent: Tuesday, February 27, 2018 8:44 PM >To: Daniele Castagna >Cc: dri-devel@lists.freedesktop.org; brian.star...@arm.com; Shankar, Uma > >Subject: Re: [PATCH 02/10] drm:

  1   2   >