Re: [RFC][PATCH] libdrm: gralloc_handle.h: Fix build issue with Android

Hey John, On 03/16/2018 10:48 PM, John Stultz wrote: In trying to integrate the new gralloc_handle.h with the drm_hwcomposer, I started seeing the following compilation errors: In file included from external/drm_hwcomposer/platformdrmgeneric.cpp:28:

[Bug 198123] Console is the wrong color at boot with radeon 6670

https://bugzilla.kernel.org/show_bug.cgi?id=198123 --- Comment #47 from sh...@tuta.io --- I analysed individual bits in register dumps. Some bits are set in all 8 dumps with black background and unset in most of dumps with grey background. The value at 0x69F0 is 0x00401004 in all black dumps,

[RESEND PATCH libdrm] tests: fix memory leak issue

Fixed memory leak issue to drmModeRes and drmModePlaneRes objects. These objects were allocated by drmModeGetResources and drmModeGetPlaneResources functions but not freed properly. So this patch frees them by calling drmModeFreeResources drmModeFreePlaneResources functions at failure case.

Re: [PATCH] libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64

On Tue, Mar 20, 2018 at 2:49 AM, John Stultz wrote: > On Tue, Mar 20, 2018 at 6:55 AM, Stefan Schake wrote: >> Hey John, >> >> On Wed, Mar 14, 2018 at 5:47 PM, John Stultz wrote: >>> When building AOSP after updating libdrm

[PATCH libdrm] tests: fix memory leak issue

Fixed memory leak issue to drmModeRes object. This object was allocated by drmModeGetResources function but not freed when device->screens failed. So this patch frees the drmModeRes object when device->screens failed by calling drmModeFreeResources function. Signed-off-by: Inki Dae

[RFC][PATCH] libdrm: intel/Android.mk: Limit x86/x86_64 filtering to just libpciaccess

In ed07718ae7ba ("libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64"), I avoided including the logic from intel/Android.mk on non-x86 based builds. This was done to avoid the inclusion of the libpciaccess library as a build requirement. As a side effect, it removed

Re: [PATCH] libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64

On Tue, Mar 20, 2018 at 6:55 AM, Stefan Schake wrote: > Hey John, > > On Wed, Mar 14, 2018 at 5:47 PM, John Stultz wrote: >> When building AOSP after updating libdrm project to the >> freedesktop/master branch, I've seen the following build errors: >>

linux-next: manual merge of the drm-misc tree with Linus' tree

Hi all, Today's linux-next merge of the drm-misc tree got a conflict in: drivers/gpu/drm/sun4i/sun4i_tcon.h between commit: e742a17cd360 ("drm/sun4i: tcon: Reduce the scope of the LVDS error a bit") from Linus' tree and commit: 6664e9dc5383 ("drm/sun4i: Add support for A80 TCONs")

Re: [PATCH] libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64

On Tue, Mar 20, 2018 at 6:55 AM, Stefan Schake wrote: > Hey John, > > On Wed, Mar 14, 2018 at 5:47 PM, John Stultz wrote: >> When building AOSP after updating libdrm project to the >> freedesktop/master branch, I've seen the following build errors: >>

[Bug 105018] Kernel panic when waking up after screen goes blank.

https://bugs.freedesktop.org/show_bug.cgi?id=105018 --- Comment #23 from L.S.S. --- EDIT: It seems I'm experiencing some intermittent screen flicker with current 4.16 kernel (on the same system, with only Patch 3 applied as it's the only patch needed for 4.16), although

Re: [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups

From: Bjorn Helgaas Date: Mon, 19 Mar 2018 14:38:54 -0500 > I'd be happy to remove both. But I wonder how X init works on > sparc. It's been many years since I worked on this, but I think it mapped and used the PCI ROM resource for this.

Re: [PATCH] libdrm: intel/Android.mk: Filter libdrm_intel library requirements on x86/x86_64

Hey John, On Wed, Mar 14, 2018 at 5:47 PM, John Stultz wrote: > When building AOSP after updating libdrm project to the > freedesktop/master branch, I've seen the following build errors: > > external/libdrm/intel/Android.mk: error: libdrm_intel > (SHARED_LIBRARIES

[PATCH] drm/msm/dsi: use correct enum in dsi_get_cmd_fmt

The function dsi_get_cmd_fmt returns enum dsi_cmd_dst_format, use the correct enum value also for MIPI_DSI_FMT_RGB666/_PACKED. This has been discovered using clang: drivers/gpu/drm/msm/dsi/dsi_host.c:743:35: warning: implicit conversion from enumeration type 'enum dsi_vid_dst_format' to

[PATCH] drm/tegra: dc: use correct format array for Tegra124.

Use tegra124_(primary|overlay)_formats for Tegra124. Fixes: 511c7023cf23 ("drm/tegra: dc: Support more formats") Signed-off-by: Stefan Agner --- drivers/gpu/drm/tegra/dc.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/tegra/dc.c

Re: [PATCH] drm/i915/gvt/scheduler: fix potential NULL pointer dereference

Quoting Gustavo A. R. Silva (2018-03-19 20:50:12) > Hi Chris, > > On 03/19/2018 03:38 PM, Chris Wilson wrote: > > Quoting Gustavo A. R. Silva (2018-03-19 19:30:53) > >> _workload_ is being dereferenced before it is null checked, hence > >> there is a potential null pointer dereference. > >> > >>

Re: [PATCH 0/8] ARM: sun9i: a80: Add display support

On Thu, Mar 15, 2018 at 07:41:28PM +0800, Chen-Yu Tsai wrote: > Hi everyone, > > This series adds basic support for the display pipelines found on the > Allwinner A80 SoC. Currently only parallel RGB output via TCON0 is > supported. TCON1 drives the HDMI encoder, which I've not been able to > get

Re: [PATCH 0/2] drm/sun4i: backend: Support interleaved YUV planes

On Thu, Mar 01, 2018 at 08:18:44PM +0100, Maxime Ripard wrote: > Hi, > > This is an attempt at supporting the interleaved YUV planes in the sun4i > DRM driver for SoCs that use the DE1. > > There's nothing out of the extraordinary there, we just have one more > constraint in our DRM driver,

Re: [Outreachy kernel] [PATCH DRM] drm: Introduce drm_global_item_{get/put}()

On Tue, Mar 13, 2018 at 1:02 PM, Haneen Mohammed wrote: > For consistency with other reference counting APIs in the kernel, > introduce drm_global_item_{get/put} functions instead of > drm_global_item_{ref/unref}. > > Compatibility aliases are added to keep existing code

Re: [PATCH] drm/i915/gvt/scheduler: fix potential NULL pointer dereference

Quoting Gustavo A. R. Silva (2018-03-19 19:30:53) > _workload_ is being dereferenced before it is null checked, hence > there is a potential null pointer dereference. > > Fix this by moving the pointer dereference after _workload_ has > been null checked. The checks are misleading and not

Re: [PATCH v2 2/3] drm/msm/dsi: add implementation for helper functions

On Tue, Mar 20, 2018 at 01:11:02AM +0530, Sibi S wrote: > Add dsi host helper function implementation for DSI v2 > DSI 6G 1.x and DSI 6G v2.0+ controllers > > Signed-off-by: Sibi S > --- > drivers/gpu/drm/msm/dsi/dsi.h | 15 +++ > drivers/gpu/drm/msm/dsi/dsi_cfg.c |

[DPU PATCH v3] 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. Changes in v2: - Use state->state in disp duplicate_state callback (Jeykumar) Changes in v3: -

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

On 2018-03-19 08:01, Sean Paul wrote: On Mon, Mar 12, 2018 at 04:23:10PM -0400, Sean Paul wrote: On Thu, Mar 08, 2018 at 05:08:03PM -0800, Jeykumar Sankaran wrote: > On 2018-03-02 06:56, Sean Paul wrote: > > On Thu, Mar 01, 2018 at 07:37:10PM -0500, Rob Clark wrote: > > > On Thu, Mar 1, 2018 at

[PATCH v2 3/3] drm/msm/dsi: replace version checks with helper functions

Replace version checks with the helper functions bound to cfg_handler for DSI v2, DSI 6G 1.x and DSI 6G v2.0+ controllers Signed-off-by: Sibi S --- drivers/gpu/drm/msm/dsi/dsi_host.c | 242 + 1 file changed, 29 insertions(+), 213

[PATCH v2 2/3] drm/msm/dsi: add implementation for helper functions

Add dsi host helper function implementation for DSI v2 DSI 6G 1.x and DSI 6G v2.0+ controllers Signed-off-by: Sibi S --- drivers/gpu/drm/msm/dsi/dsi.h | 15 +++ drivers/gpu/drm/msm/dsi/dsi_cfg.c | 56 +++-- drivers/gpu/drm/msm/dsi/dsi_host.c | 236

[PATCH v2 0/3] Cleanup excessive DSI host controller version checks

This patch series aims to create and bind dsi host controller helper functions to functionalities that vary across DSI v2, DSI 6G 1.x and DSI 6G v2.0+ controllers. These functionalities are currently under excessive version checks which is now replaced with the corresponding helper function. V2:

[PATCH v2 1/3] drm/msm/dsi: add dsi host helper functions support

Add dsi host helper functions support for DSI v2 and DSI 6G 1.x controllers that are under version checks Signed-off-by: Sibi S --- drivers/gpu/drm/msm/dsi/dsi.h | 1 + drivers/gpu/drm/msm/dsi/dsi_cfg.h | 12 2 files changed, 13 insertions(+) diff --git

Re: [PATCH v1 0/2] PCI: Sparc 64-bit resource fixups

[+cc Dave, Alex, dri-devel] On Mon, Mar 19, 2018 at 02:28:31PM -0400, David Miller wrote: > From: Bjorn Helgaas > Date: Mon, 19 Mar 2018 12:11:40 -0500 > > > I could have worded the changelog better. This is about reserving PCI > > bus addresses 0xc-0xc7fff, not the VGA

Re: [DPU PATCH v2] drm/msm: Use atomic private_obj instead of subclassing

On 2018-03-19 10:31, Sean Paul wrote: 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. Changes in v2: - Use state->state in disp duplicate_state

[PATCH v2] drm/i915: Disable some extra clang warnings

Commit 39bf4de89ff7 ("drm/i915: Add -Wall -Wextra to our build, set warnings to full") enabled extra warnings for i915 to spot possible bugs in new code, and then disabled a subset of these warnings to keep the current code building without warnings (with gcc). Enabling the extra warnings also

Re: [PATCH hwc v1] [RFC] drm_hwcomposer: Flatten composition using writeback connector

On Tue, Mar 13, 2018 at 04:21:20PM +, Alexandru Gheorghe wrote: > This patchset tries to add support for using writeback connector to > flatten a scene when it doesn't change for a while. This idea had > been floated around on IRC here [1] and here [2]. > > Developed on top of the latest

[DPU PATCH v2] 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. Changes in v2: - Use state->state in disp duplicate_state callback (Jeykumar) Cc: Jeykumar

[PATCH libdrm 1/1] intel: allocate the requested size when reuse is disabled

From: "Xiong, James" 1) fixed a bug: a bucket size instead of the requested was allocated even when reuse is disabled. 2) set bo_reuse explicitly Signed-off-by: Xiong, James --- intel/intel_bufmgr_gem.c | 6 +- 1 file changed, 5 insertions(+),

[Bug 105611] Alt-Tabbing in kwin results in SIGSEV in radeonsi

https://bugs.freedesktop.org/show_bug.cgi?id=105611 Clemens Eisserer changed: What|Removed |Added Status|NEW |RESOLVED

[Bug 103234] KWin crashed when Alt+Tab-ing through open windows

https://bugs.freedesktop.org/show_bug.cgi?id=103234 Clemens Eisserer changed: What|Removed |Added CC|

Re: [GIT PULL] drm/tegra: Changes for v4.17-rc1

On Mon, Mar 19, 2018 at 02:32:08PM +, Marcel Ziswiler wrote: > Hi Thierry > > On Mon, 2018-03-19 at 10:59 +0100, Thierry Reding wrote: > > Hi Dave, > > > > The following changes since commit > > 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: > > > > Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) >

[PATCH] drm/i915: Promote .format_mod_supported() to the lead role

From: Ville Syrjälä Up to now we've used the plane's modifier list as the primary source of information for which modifiers are supported by a given plane. In order to allow auxiliary metadata to be embedded within the bits of the modifier we need to stop doing

[Bug 105611] Alt-Tabbing in kwin results in SIGSEV in radeonsi

https://bugs.freedesktop.org/show_bug.cgi?id=105611 Bug ID: 105611 Summary: Alt-Tabbing in kwin results in SIGSEV in radeonsi Product: Mesa Version: 17.3 Hardware: Other OS: All Status: NEW Severity:

Re: [PATCH 1/3] drm: Trust format_mod_supported() when it OKs a plane modifier.

On Fri, Mar 16, 2018 at 03:04:33PM -0700, Eric Anholt wrote: > For parameterized modifiers (Broadcom's SAND and UIF), we need to > allow the parameter fields to be filled in, while exposing only the > variant of the modifier with the parameter unfilled in the internal > arrays and the format blob.

[Bug 91880] Radeonsi on Grenada cards (r9 390) exceptionally unstable and poorly performing

https://bugs.freedesktop.org/show_bug.cgi?id=91880 --- Comment #187 from Lauri Gustafsson --- About "I can force a system hard-lock by doing anything which disables a monitor", on my system it used to crash more frequently the less desktop area I had. Small resolution monitor

Re: [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

Am 19.03.2018 um 16:53 schrieb Chris Wilson: Quoting Christian König (2018-03-16 14:22:32) [snip, probably lost too must context] This allows for full grown pipelining, e.g. the exporter can say I need to move the buffer for some operation. Then let the move operation wait for all existing

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #14 from Alex Deucher --- (In reply to philipmorant from comment #13) > No, that's not it either. Apparently it's not going through > amdgpu_connector_dvi_mode_valid(). My trace output (using DRM_ERROR())

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #13 from philipmor...@gmail.com --- No, that's not it either. Apparently it's not going through amdgpu_connector_dvi_mode_valid(). My trace output (using DRM_ERROR()) does not appear in syslog. -- You are receiving this mail

Re: [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

Quoting Christian König (2018-03-16 14:22:32) [snip, probably lost too must context] > This allows for full grown pipelining, e.g. the exporter can say I need > to move the buffer for some operation. Then let the move operation wait > for all existing fences in the reservation object and install

[Bug 105610] [CI] igt@gem_ctx_isolation@vecs0-s3 - fail - igt_core-WARNING: [cmd] rtcwake: /dev/rtc0: unable to find device: Device or resource busy

https://bugs.freedesktop.org/show_bug.cgi?id=105610 Marta Löfstedt changed: What|Removed |Added Whiteboard||ReadyForDev

[Bug 105610] [CI] igt@gem_ctx_isolation@vecs0-s3 - fail - igt_core-WARNING: [cmd] rtcwake: /dev/rtc0: unable to find device: Device or resource busy

https://bugs.freedesktop.org/show_bug.cgi?id=105610 Marta Löfstedt changed: What|Removed |Added Component|DRM/Intel |IGT

Re: [PATCH RESEND v2 1/2] drm/xen-front: Add support for Xen PV display frontend

On Mon, Mar 19, 2018 at 3:19 PM, Oleksandr Andrushchenko wrote: > On 03/19/2018 03:51 PM, Daniel Vetter wrote: >> >> On Fri, Mar 16, 2018 at 12:52:09PM +0200, Oleksandr Andrushchenko wrote: >>> >>> Hi, Daniel! >>> Sorry, if I strip the patch too much below. >>> >>> On

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #12 from philipmor...@gmail.com --- static int amdgpu_connector_dvi_mode_valid(struct drm_connector *connector, struct drm_display_mode *mode) has a hard-coded 165000 and looks likely. I'll

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #11 from philipmor...@gmail.com --- #TDMS_MAX_PIXEL_CLOCK 33 makes no difference. See syslog files attached above. -- You are receiving this mail because: You are the assignee for the

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #10 from philipmor...@gmail.com --- Created attachment 138200 --> https://bugs.freedesktop.org/attachment.cgi?id=138200=edit syslog for xrandr --output with drm.debug-0xe and TDMS_MAX_PIXEL_CLOCK 33 -- You are receiving this

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #9 from philipmor...@gmail.com --- Created attachment 138199 --> https://bugs.freedesktop.org/attachment.cgi?id=138199=edit syslog for xrandr --addmode with drm.debug-0xe and TDMS_MAX_PIXEL_CLOCK 33 -- You are receiving this

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

On Mon, Mar 12, 2018 at 04:23:10PM -0400, Sean Paul wrote: > On Thu, Mar 08, 2018 at 05:08:03PM -0800, Jeykumar Sankaran wrote: > > On 2018-03-02 06:56, Sean Paul wrote: > > > On Thu, Mar 01, 2018 at 07:37:10PM -0500, Rob Clark wrote: > > > > On Thu, Mar 1, 2018 at 3:37 PM,

Re: [PATCH v2 00/11] drm/tinydrm: Support device unplug

On 03/19/2018 03:45 PM, Daniel Vetter wrote: On Sat, Mar 17, 2018 at 03:40:29PM +0100, Noralf Trønnes wrote: Den 16.03.2018 09.03, skrev Daniel Vetter: On Fri, Sep 8, 2017 at 6:33 PM, Daniel Vetter wrote: Hi Noralf, On Fri, Sep 08, 2017 at 05:07:19PM +0200, Noralf Trønnes

[Bug 199139] System freezes (kernel, amdgpu NULL pointer dereference) when video enters powersafe state

https://bugzilla.kernel.org/show_bug.cgi?id=199139 Harry Wentland (harry.wentl...@amd.com) changed: What|Removed |Added CC|

Re: [PATCH] libdrm: Use readdir instead of readdir_r to avoid build warnings

On Monday, 2018-03-19 06:47:32 -0700, John Stultz wrote: > Building libdrm under AOSP, we see the following build warning: > external/libdrm/xf86drm.c:2861:12: warning: 'readdir_r' is deprecated: > readdir_r is deprecated; use readdir instead [-Wdeprecated-declarations] > while

Re: [PATCH RESEND v2 1/2] drm/xen-front: Add support for Xen PV display frontend

On 03/19/2018 03:51 PM, Daniel Vetter wrote: On Fri, Mar 16, 2018 at 12:52:09PM +0200, Oleksandr Andrushchenko wrote: Hi, Daniel! Sorry, if I strip the patch too much below. On 03/16/2018 10:23 AM, Daniel Vetter wrote: S-o-b line went missing here :-) will restore it back ;) I've read

Re: [PATCH] drm: Reduce object size of DRM_DEV_ uses

On Fri, Mar 16, 2018 at 01:56:27PM -0700, Joe Perches wrote: > These macros are similar to the DRM_ with the addition > of a struct device * to the arguments. > > Convert the single drm_dev_printk function into 2 separate functions. > drm_dev_printk with a KERN_ * for generic use and drm_dev_dbg

Re: linux-next: manual merge of the drm-misc tree with the drm tree

On Mon, Mar 19, 2018 at 12:29:29PM +1100, Stephen Rothwell wrote: > Hi all, > > Today's linux-next merge of the drm-misc tree got a conflict in: > > drivers/gpu/drm/i915/intel_color.c > > between commit: > > db61d160b3ed ("drm/i915: Remove the pointless 1:1 matrix copy") > > from the drm

Re: [Outreachy kernel] [PATCH DRM] drm: remove drm_mode_object_{un/reference} aliases

On Mon, Mar 19, 2018 at 01:58:20AM -0400, Haneen Mohammed wrote: > This patch remove the compatibility aliases > drm_mode_object_{reference/unreference} of drm_mode_object_{get/put} > since all callers have been converted to the prefered _{get/put}. > > Remove the helpers from the semantic patch

Re: [Outreachy kernel] [PATCH] gpu: drm: Use list_{next/prev}_entry instead of list_entry

On Mon, Mar 19, 2018 at 10:35:30AM +0530, Arushi Singhal wrote: > This patch replace list_entry with list_{next/prev}_entry as it makes > the code more clear to read. > Done using coccinelle: > > @@ > expression e1; > identifier e3; > type t; > @@ > ( > - list_entry(e1->e3.next,t,e3) > +

Re: [PATCH] libdrm: Use readdir instead of readdir_r to avoid build warnings

On 19 March 2018 at 13:47, John Stultz wrote: > Building libdrm under AOSP, we see the following build warning: > external/libdrm/xf86drm.c:2861:12: warning: 'readdir_r' is deprecated: > readdir_r is deprecated; use readdir instead [-Wdeprecated-declarations] > while

[Bug 105534] amdgpu cannot set 2560x1440@60 mode even though monitor,gpu and motherboard support it

https://bugs.freedesktop.org/show_bug.cgi?id=105534 --- Comment #8 from Harry Wentland --- (In reply to philipmorant from comment #4) > I understand if AMD object to coding for something that hasn't been > validated (I'd do the same myself). Would it be possible

Re: [PATCH 2/3] drm/vc4: Add color transformation matrix (CTM) support

On Fri, Mar 16, 2018 at 10:50:58PM +0100, Stefan Schake wrote: > The hardware supports a CTM with S0.9 values. We therefore only allow > a value of 1.0 or fractional only and reject all others with integer > parts. This restriction is mostly inconsequential in practice since > commonly used

Re: RFC: unpinned DMA-buf exporting v2

On Fri, Mar 16, 2018 at 02:20:44PM +0100, Christian König wrote: > Hi everybody, > > since I've got positive feedback from Daniel I continued working on this > approach. > > A few issues are still open: > 1. Daniel suggested that I make the invalidate_mappings callback a parameter > of

Re: [PATCH 1/5] dma-buf: add optional invalidate_mappings callback v2

On Fri, Mar 16, 2018 at 02:20:45PM +0100, Christian König wrote: > Each importer can now provide an invalidate_mappings callback. > > This allows the exporter to provide the mappings without the need to pin > the backing store. > > v2: don't try to invalidate mappings when the callback is NULL,

Re: [DPU PATCH 2/2] drm/msm: Add hardware catalog file for SDM845

On Wed, Mar 14, 2018 at 11:21:38AM +0530, Sravanthi Kollukuduru wrote: > This change adds the hardware catalog information in driver source > for SDM845. This removes the current logic of dt based parsing > of target catalog information. > > Signed-off-by: Sravanthi Kollukuduru

Re: [Intel-gfx] [PATCH libdrm 0/5] improve reuse implementation

On Fri, Mar 16, 2018 at 05:10:44PM +, Emil Velikov wrote: > On 16 March 2018 at 08:43, Daniel Vetter wrote: > > On Thu, Mar 15, 2018 at 06:20:09PM -0700, James Xiong wrote: > >> From: "Xiong, James" > >> > >> With gem_reuse enabled, when a buffer size

[Bug 198123] Console is the wrong color at boot with radeon 6670

https://bugzilla.kernel.org/show_bug.cgi?id=198123 --- Comment #46 from Harry Wentland (harry.wentl...@amd.com) --- Michel, nobody jumps out to me in dce5_crtc_load_lut but I have only cursory familiary with those registers. -- You are receiving this mail because: You are watching the assignee

Re: [PATCH] drm: Reduce object size of DRM_ERROR and DRM_DEBUG uses

On Fri, Mar 16, 2018 at 05:29:02AM -0700, Joe Perches wrote: > On Fri, 2018-03-16 at 08:41 +0100, Daniel Vetter wrote: > > On Tue, Mar 13, 2018 at 03:02:15PM -0700, Joe Perches wrote: > > > drm_printk is used for both DRM_ERROR and DRM_DEBUG with unnecessary > > > arguments that can be removed by

Re: [PATCH RESEND v2 1/2] drm/xen-front: Add support for Xen PV display frontend

On Fri, Mar 16, 2018 at 12:52:09PM +0200, Oleksandr Andrushchenko wrote: > Hi, Daniel! > Sorry, if I strip the patch too much below. > > On 03/16/2018 10:23 AM, Daniel Vetter wrote: > > > > S-o-b line went missing here :-) > will restore it back ;) > > > > I've read through it, 2 actual review

Re: [PATCH v1] drm/dp/mst: Fix off-by-one typo when dump payload table

On Thu, Jan 11, 2018 at 05:33:03PM +0200, Andy Shevchenko wrote: > It seems there is a classical off-by-one typo from the beginning > when commit > > ad7f8a1f9ced ("drm/helper: add Displayport multi-stream helper (v0.6)") > > introduced a new helper. > > Fix a typo by introducing a macro

[PATCH] libdrm: Use readdir instead of readdir_r to avoid build warnings

Building libdrm under AOSP, we see the following build warning: external/libdrm/xf86drm.c:2861:12: warning: 'readdir_r' is deprecated: readdir_r is deprecated; use readdir instead [-Wdeprecated-declarations] while (readdir_r(sysdir, pent, ) == 0 && ent != NULL) { ^ Thus, this

Re: [PATCH v2 00/11] drm/tinydrm: Support device unplug

On Sat, Mar 17, 2018 at 03:40:29PM +0100, Noralf Trønnes wrote: > > Den 16.03.2018 09.03, skrev Daniel Vetter: > > On Fri, Sep 8, 2017 at 6:33 PM, Daniel Vetter wrote: > > > Hi Noralf, > > > > > > On Fri, Sep 08, 2017 at 05:07:19PM +0200, Noralf Trønnes wrote: > > > > This adds

Re: [PATCH] drm/doc: Put all driver docs into a separate chapter

On Fri, Mar 16, 2018 at 03:24:14PM -0400, Alex Deucher wrote: > On Fri, Mar 16, 2018 at 3:59 AM, Daniel Vetter wrote: > > We have quite a few driver docs now, which is great, but having them > > all in the top-level gpu documentation chapter makes it harder to spot > > the

[PATCH] drm/i915/gvt: fix spelling mistake: "registeration" -> "registration"

From: Colin Ian King Trivial fix to spelling mistake in gvt_err error message text Signed-off-by: Colin Ian King --- drivers/gpu/drm/i915/gvt/gvt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

Re: [PATCH 1/4] GPU: drm: Fixed Spacing issue

On Mon, Mar 19, 2018 at 12:52:22AM +, Paul McQuade wrote: > "foo * bar" should be "foo *bar" > > Signed-off-by: Paul McQuade Thank you for your patches. I've squashed them all into one, fixed up the commit message and applied them to drm-misc-next. Sean > --- >

Re: [PATCH DRM] drm: remove drm_mode_object_{un/reference} aliases

On Mon, Mar 19, 2018 at 01:58:20AM -0400, Haneen Mohammed wrote: > This patch remove the compatibility aliases > drm_mode_object_{reference/unreference} of drm_mode_object_{get/put} > since all callers have been converted to the prefered _{get/put}. > > Remove the helpers from the semantic patch

Re: [Outreachy kernel] Re: [PATCH] gpu: drm: Use list_first_entry instead of list_entry

Am 19.03.2018 um 12:06 schrieb Julia Lawall: On Mon, 19 Mar 2018, Christian König wrote: Mhm, actually that patch isn't correct. What we grab get here is the next entry, not the first one. We don't have an alias list_next_entry for list_first_entry? As compared to the semantic patch I

Re: [PATCH 3/3] arm64: dts: meson-gxl-s905x-libretech-cc: add cec-disable

On 19/03/2018 12:43, Hans Verkuil wrote: > From: Hans Verkuil > > This board has two CEC controllers: the DesignWare controller and > a meson-specific controller. Disable the DW controller since the > CEC line is hooked up to the meson controller. > > Signed-off-by: Hans

Re: [PATCH 2/3] drm: bridge: dw-hdmi: check the cec-disable property

On 19/03/2018 12:43, Hans Verkuil wrote: > From: Hans Verkuil > > If the cec-disable property was set, then disable the DW CEC > controller. This is needed for boards that have their own > CEC controller. > > Signed-off-by: Hans Verkuil > --- >

Re: [PATCH 1/3] dt-bindings: display: dw_hdmi.txt

On 19/03/2018 12:43, Hans Verkuil wrote: > From: Hans Verkuil > > Some boards have both a DesignWare and their own CEC controller. > The CEC pin is only hooked up to their own CEC controller and not > to the DW controller. > > Add the cec-disable property to disable the

Re: [PATCH 0/3] dw-hdmi: add property to disable CEC

Hi Hans, On 19/03/2018 12:43, Hans Verkuil wrote: > From: Hans Verkuil > > Some boards (amlogic) have two CEC controllers: the DesignWare controller > and their own CEC controller (meson ao-cec). > > Since the CEC line is not hooked up to the DW controller we need a way

Re: [PATCH v4 1/3] drm/panel: refactor INNOLUX P079ZCA panel driver

On 15 March 2018 at 02:35, hl wrote: > Hi Emil, > > > > On Wednesday, March 14, 2018 08:02 PM, Emil Velikov wrote: >> >> Hi Lin, >> >> On 14 March 2018 at 09:12, Lin Huang wrote: >>> >>> From: huang lin >>> >>> Refactor Innolux

Re: [PATCH 1/3] dt-bindings: display: dw_hdmi.txt

On 03/19/2018 12:46 PM, Fabio Estevam wrote: > Hi Hans, > > On Mon, Mar 19, 2018 at 8:43 AM, Hans Verkuil wrote: >> From: Hans Verkuil > > It seems the Subject line is missing some content? Oops. That should have been: dt-bindings: display:

Re: [PATCH 1/3] dt-bindings: display: dw_hdmi.txt

Hi Hans, On Mon, Mar 19, 2018 at 8:43 AM, Hans Verkuil wrote: > From: Hans Verkuil It seems the Subject line is missing some content? ___ dri-devel mailing list dri-devel@lists.freedesktop.org

[PATCH 0/3] dw-hdmi: add property to disable CEC

From: Hans Verkuil Some boards (amlogic) have two CEC controllers: the DesignWare controller and their own CEC controller (meson ao-cec). Since the CEC line is not hooked up to the DW controller we need a way to disable that controller. This patch series adds the

[PATCH 2/3] drm: bridge: dw-hdmi: check the cec-disable property

From: Hans Verkuil If the cec-disable property was set, then disable the DW CEC controller. This is needed for boards that have their own CEC controller. Signed-off-by: Hans Verkuil --- drivers/gpu/drm/bridge/synopsys/dw-hdmi.c | 3 ++- 1 file

[PATCH 1/3] dt-bindings: display: dw_hdmi.txt

From: Hans Verkuil Some boards have both a DesignWare and their own CEC controller. The CEC pin is only hooked up to their own CEC controller and not to the DW controller. Add the cec-disable property to disable the DW CEC controller. This particular situation happens

[PATCH 3/3] arm64: dts: meson-gxl-s905x-libretech-cc: add cec-disable

From: Hans Verkuil This board has two CEC controllers: the DesignWare controller and a meson-specific controller. Disable the DW controller since the CEC line is hooked up to the meson controller. Signed-off-by: Hans Verkuil ---

Re: [Outreachy kernel] Re: [PATCH] gpu: drm: Use list_first_entry instead of list_entry

On Mon, 19 Mar 2018, Christian König wrote: > Mhm, actually that patch isn't correct. What we grab get here is the next > entry, not the first one. > > We don't have an alias list_next_entry for list_first_entry? As compared to the semantic patch I proposed earlier today, it would seem that

[GIT PULL] drm/tegra: Changes for v4.17-rc1

Hi Dave, The following changes since commit 7928b2cbe55b2a410a0f5c1f154610059c57b1b2: Linux 4.16-rc1 (2018-02-11 15:04:29 -0800) are available in the Git repository at: git://anongit.freedesktop.org/tegra/linux tags/drm/tegra/for-4.17-rc1 for you to fetch changes up to

[Bug 105597] [CI] igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transition - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105597 Marta Löfstedt changed: What|Removed |Added See Also|

[Bug 105598] [CI] igt@kms_frontbuffer_tracking@drrs-2p-scndscrn-spr-indfb-move - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105598 Marta Löfstedt changed: What|Removed |Added See Also|

[Bug 105523] [CI] igt@pm_rpm@universal-planes - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105523 Marta Löfstedt changed: What|Removed |Added Summary|[Ci]|[CI]

[Bug 105598] [CI] igt@kms_frontbuffer_tracking@drrs-2p-scndscrn-spr-indfb-move - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105598 Marta Löfstedt changed: What|Removed |Added Whiteboard||ReadyForDev

[Bug 105598] [CI] igt@kms_frontbuffer_tracking@drrs-2p-scndscrn-spr-indfb-move - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105598 Bug ID: 105598 Summary: [CI] igt@kms_frontbuffer_tracking@drrs-2p-scndscrn-spr-indf b-move - Build timed out (after 18 minutes) Product: DRI Version: DRI git

[Bug 105523] [Ci] igt@pm_rpm@universal-planes - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105523 Marta Löfstedt changed: What|Removed |Added See Also|

[Bug 105523] [Ci] igt@pm_rpm@universal-planes - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105523 Marta Löfstedt changed: What|Removed |Added QA Contact|intel-gfx-bugs@lists.freede |

[Bug 105597] [CI] igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transition - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105597 Marta Löfstedt changed: What|Removed |Added See Also|

[Bug 105597] [CI] igt@kms_cursor_legacy@cursora-vs-flipa-atomic-transition - incomplete - Build timed out (after 18 minutes)

https://bugs.freedesktop.org/show_bug.cgi?id=105597 Marta Löfstedt changed: What|Removed |Added Component|DRM/Intel |IGT

[Bug 198123] Console is the wrong color at boot with radeon 6670

https://bugzilla.kernel.org/show_bug.cgi?id=198123 --- Comment #45 from sh...@tuta.io --- Created attachment 274815 --> https://bugzilla.kernel.org/attachment.cgi?id=274815=edit radeonreg grey background Linux 4.15.10-1-ARCH SMP PREEMPT x86_64 I made 11 dumps from different boots and selected

  1   2   >