[Bug 103791] Tearing after screen wakeup/on

https://bugs.freedesktop.org/show_bug.cgi?id=103791 --- Comment #12 from denisgolo...@yandex.ru --- Created attachment 135917 --> https://bugs.freedesktop.org/attachment.cgi?id=135917&action=edit dmesg with debug -- You are receiving this mail because: You are the assignee for the bug.

[Bug 103791] Tearing after screen wakeup/on

https://bugs.freedesktop.org/show_bug.cgi?id=103791 --- Comment #11 from denisgolo...@yandex.ru --- Yes, I fixed some small issues with the patch. Now I have following appear in dmesg: [ 2108.319205] [drm] drm_crtc_vblank_get returned -EINVAL [ 2108.319235] [drm] crtc 0 failed to acquire vblank co

Re: [PATCH 0/4] Move DP phy switch to PHY driver

Hi Chris, Am Montag, 4. Dezember 2017, 10:47:08 CET schrieb Chris Zhong: > On 2017年12月02日 05:58, Heiko Stuebner wrote: > > Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson: > >> Hi, > >> > >> On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote: > >>> Hi Doug > >>> > >>> Thank you

Re: [PATCH v1 2/2] drm/tinydrm: add driver for ILI9225 panels

On Fri, Dec 01, 2017 at 03:03:30PM +0100, Linus Walleij wrote: > On Wed, Nov 8, 2017 at 4:52 AM, David Lechner wrote: > > > This adds a new driver for display panels based on the Ilitek ILI9225 > > controller. > > > > This was developed for a no-name panel with a red PCB that is commonly > > mark

[Bug 104043] TV out garbled with linux > 3.2 (RV516)

https://bugs.freedesktop.org/show_bug.cgi?id=104043 Alex Deucher changed: What|Removed |Added Assignee|xorg-driver-...@lists.x.org |dri-devel@lists.freedesktop

Re: [PATCH 0/4] Move DP phy switch to PHY driver

Hi Heiko On 2017年12月02日 05:58, Heiko Stuebner wrote: Am Freitag, 1. Dezember 2017, 13:42:46 CET schrieb Doug Anderson: Hi, On Wed, Nov 29, 2017 at 6:27 PM, Chris Zhong wrote: Hi Doug Thank you for mentioning this patch. I think the focus of the discussion is: can we put the grf control bi

Re: linux-next: Signed-off-by missing for commits in the drm tree

On 2017.12.04 10:57:35 +1100, Stephen Rothwell wrote: > Hi all, > > There is a series of commits > > 54cff6479fd8 - c1802534e5a6 > (not all in that range) > > that are missing a Signed-off-by from their committer. > They were originally committed by Zhi himself, but I had to rebase onto inte

Re: linux-next: build warning after merge of the drm tree

On 4 December 2017 at 10:30, Stephen Rothwell wrote: > Hi all, > > After merging the drm tree, today's linux-next build (x86_64 allmodconfig) > produced this warning: Oops, not sure how I missed it, force pushed drm-next with the merge fixed. Dave. ___

linux-next: build warning after merge of the drm tree

Hi all, After merging the drm tree, today's linux-next build (x86_64 allmodconfig) produced this warning: drivers/gpu/drm/i915/gvt/cmd_parser.c: In function 'perform_bb_shadow': drivers/gpu/drm/i915/gvt/cmd_parser.c:1647:8: warning: unused variable 'dst' [-Wunused-variable] void *dst = NULL;

linux-next: Signed-off-by missing for commits in the drm tree

Hi all, There is a series of commits 54cff6479fd8 - c1802534e5a6 (not all in that range) that are missing a Signed-off-by from their committer. -- Cheers, Stephen Rothwell ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.fre

[Bug 197925] [amdgpu_dc][carrizo] multiple monitor handling errors

https://bugzilla.kernel.org/show_bug.cgi?id=197925 --- Comment #7 from kwka...@gmx.com --- I have confirmed that the bug (with modified behavior as described above) is still present on my hardware (Carrizo, specifically Toshiba L55D-C with AMD A10-8700P), as of 4.15.0-rc2. -- You are receiving t

Re: omapfb/dss: Delete an error message for a failed memory allocation in three functions

> How many times have I told you to include the reason for your patches > in your proposed commit message? Will it be useful to look again at the involved circumstances? > Too often. Did I answer any concerns partly? > Many people do not know that a generic kmalloc does a dump_stack() on OOM.

[Bug 104053] DDX opcode causes black screen on radeon R730

https://bugs.freedesktop.org/show_bug.cgi?id=104053 Bug ID: 104053 Summary: DDX opcode causes black screen on radeon R730 Product: DRI Version: XOrg git Hardware: All OS: Linux (All) Status: NEW Severity:

Re: [RFC] Rebasing the IDR

On Thu, Nov 30, 2017 at 10:09 PM, Matthew Wilcox wrote: > On Thu, Nov 30, 2017 at 08:56:43PM +0100, Daniel Vetter wrote: >> Adding dri-devel, I think a pile of those are in drm. > > Yeah, quite a lot! This is a good thing; means you didn't invent your > own custom ID allocator. > >> On Thu, Nov 3

[PATCH 8/9] v4l: vsp1: Integrate DISCOM in display pipeline

The DISCOM is used to compute CRCs on display frames. Integrate it in the display pipeline at the output of the blending unit to process output frames. Computing CRCs on input frames is possible by positioning the DISCOM at a different point in the pipeline. This use case isn't supported at the mo

[PATCH 3/9] v4l: vsp1: Share the CLU, LIF and LUT set_fmt pad operation code

The implementation of the set_fmt pad operation is identical in the three modules. Move it to a generic helper function. Signed-off-by: Laurent Pinchart --- drivers/media/platform/vsp1/vsp1_clu.c| 65 +-- drivers/media/platform/vsp1/vsp1_entity.c | 75

[PATCH 4/9] v4l: vsp1: Reset the crop and compose rectangles in the set_fmt helper

To make vsp1_subdev_set_pad_format() usable by entities that support selection rectangles, we need to reset the crop and compose rectangles when setting the format on the sink pad. Do so and replace the custom set_fmt implementation of the histogram code by a call to vsp1_subdev_set_pad_format().

[PATCH 9/9] drm: rcar-du: Add support for CRC computation

Implement CRC computation configuration and reporting through the DRM debugfs-based CRC API. The CRC source can be configured to any input plane or the pipeline output. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_crtc.c | 148 +++-- drivers/gpu

[PATCH 7/9] v4l: vsp1: Add support for the DISCOM entity

The DISCOM calculates a CRC on a configurable window of the frame. It interfaces to the VSP through the UIF glue, hence the name used in the code. The module supports configuration of the CRC window through the crop rectangle on the ink pad of the corresponding entity. However, unlike the traditio

[PATCH 0/9] R-Car DU: Support CRC calculation

control can be added later without affecting how CRC is exposed through the DRM/KMS API. The patches are based on top of a merge of the Linux media master branch and the pending DU patches. For convenience they are available at git://linuxtv.org/pinchartl/media.git vsp1-discom-v1-20171203 Th

[PATCH 6/9] v4l: vsp1: Extend the DU API to support CRC computation

Add a parameter (in the form of a structure to ease future API extensions) to the VSP atomic flush handler to pass CRC source configuration, and pass the CRC value to the completion callback. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/rcar-du/rcar_du_vsp.c | 6 -- drivers/media/pl

[PATCH 5/9] v4l: vsp1: Document the vsp1_du_atomic_config structure

The structure is used in the API that the VSP1 driver exposes to the DU driver. Documenting it is thus important. Signed-off-by: Laurent Pinchart --- include/media/vsp1.h | 10 ++ 1 file changed, 10 insertions(+) diff --git a/include/media/vsp1.h b/include/media/vsp1.h index 68a8abe4fac

[PATCH 1/9] v4l: vsp1: Fix display stalls when requesting too many inputs

Make sure we don't accept more inputs than the hardware can handle. This is a temporary fix to avoid display stall, we need to instead allocate the BRU or BRS to display pipelines dynamically based on the number of planes they each use. Signed-off-by: Laurent Pinchart --- drivers/media/platform/

[PATCH 2/9] v4l: vsp1: Print the correct blending unit name in debug messages

The DRM pipelines can use either the BRU or the BRS for blending. Make sure the right name is used in debugging messages to avoid confusion. Signed-off-by: Laurent Pinchart --- drivers/media/platform/vsp1/vsp1_drm.c | 12 +++- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a