Re: [PATCH] drm/atomic: Try to preserve the crtc enabled state in drm_atomic_remove_fb, v2.

Op 07-11-17 om 15:31 schreef Daniel Vetter: > On Wed, Nov 01, 2017 at 04:04:33PM +0100, Maarten Lankhorst wrote: >> This introduces a slight behavioral change to rmfb. Instead of >> disabling a crtc when the primary plane is disabled, we try to >> preserve it. >> >> Apart from old versions of the v

RE: [PATCH] drm/ttm: set bo->resv point to tbo->ttm_resv after individualize_resv

I guess this because you move the resv changing out of lock of bo->resv. Because at the beginning ttm_mem_evict_first may __ttm_bo_reserve(bo->resv) success, and then bo->resv has been changed by another thread. That is not matched and at this point bo->ttm_resv also may been freed already. And

Re: [PATCH v5 06/12] drm/cma-helper: Turn to_drm_gem_cma_obj() into a macro

Hi Noralf, Thank you for the patch. On Tuesday, 7 November 2017 21:13:42 EET Noralf Trønnes wrote: > This allows the argument to be a const. > > The other option was to keep it an inline function and make the argument > a const: > > static inline struct drm_gem_cma_object * > to_drm_gem_cma_obj

[PATCH v1 0/2] DRM driver for ILI9225 display panels

This is a new driver for ILI9225 based display panels. There are a couple of things that stand out: 1. Despite my best efforts, I could not find a name for this display[1], so I have made up a generic name for it. If someone recognizes this and has a name for it, please speak up. The bes

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

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 marketed for Arduino. See . I really did try very hard to find a make and model for this panel, but the

[PATCH v1 1/2] dt-bindings: Add binding for Ilitek ILI9225 display panels

This adds a new binding for display panels that use an Ilitek ILI9225 controller. The "generic,2.2in-176x220-ili9225-tft" device listed has no identification markings whatsoever and an hour of googling turned up nothing, hence the use of "generic". An example of this nameless device can be found

[PATCH v2] drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT

This patch defines the DP DSC receiver capability size that gives total number of DP DSC DPCD registers. This also adds a missing SHIFT define missed in the commit id (ab6a46ea6842ce "Add DPCD definitions for DP 1.4 DSC feature") v2: * Missed th SHIFT define that I mentioned in the message Cc: Ja

[PATCH] drm/dp: Add DP DSC DPCD receiver capability size define and missing SHIFT

This patch defines the DP DSC receiver capability size that gives total number of DP DSC DPCD registers. This also adds a missing SHIFT define missed in the commit id (ab6a46ea6842ce "Add DPCD definitions for DP 1.4 DSC feature") Cc: Jani Nikula Cc: dri-devel@lists.freedesktop.org Signed-off-by:

[Bug 103544] Graphical glitches r600 in game this war of mine linux native

https://bugs.freedesktop.org/show_bug.cgi?id=103544 --- Comment #15 from Roland Scheidegger --- (In reply to Roland Scheidegger from comment #14) > - the driver doesn't use the ieee variants consistently (e.g. muls from > lerps). > There's also some inconsistencies - for r600, the comments say fo

[Bug 66963] Rv6xx dpm problems

https://bugs.freedesktop.org/show_bug.cgi?id=66963 --- Comment #296 from Mihai Coman --- Hello, On a whim I've decided to try radeon.dpm=1 again. I've been running it for the past couple of days and I haven't had gotten any lockups, and I used to get them in the first 30 min. The temp. decrease

[Bug 103544] Graphical glitches r600 in game this war of mine linux native

https://bugs.freedesktop.org/show_bug.cgi?id=103544 --- Comment #14 from Roland Scheidegger --- (In reply to Ilia Mirkin from comment #13) > (In reply to Roland Scheidegger from comment #12) > > Here's a apitrace for this (1GB, of course the corruption is only seen > > towards the end...), should

[radeon-alex:amd-staging-drm-next 2135/2152] sound/soc/amd/acp-pcm-dma.c:857: undefined reference to `__umoddi3'

tree: git://people.freedesktop.org/~agd5f/linux.git amd-staging-drm-next head: 9ef4af0611bafed9fd40c4af92c1daeefba45e95 commit: fb837978e0395a5f936e56bb3ed4c824d50da8e8 [2135/2152] ASoC: amd: Report accurate hw_ptr during dma config: i386-randconfig-x0-11080703 (attached as .config) compiler:

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #3 from EoD --- Created attachment 135291 --> https://bugs.freedesktop.org/attachment.cgi?id=135291&action=edit GDBs Backtrace with -O0 -- You are receiving this mail because: You are the assignee for the bug.

[Bug 99923] HITMAN (2016) having lighting and artefacting, and overly light room.

https://bugs.freedesktop.org/show_bug.cgi?id=99923 --- Comment #18 from Christoph Schwerdtfeger --- Unfortunately still the same... # glxinfo | grep Mesa client glx vendor string: Mesa Project and SGI OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.2.4 OpenGL version string: 3.0 M

Re: AMD, please run Smatch on your driver

Thanks, Dan, for bringing this to our attention. We (the display guys here) weren't aware of smatch and will give it a spin and try to address some of the remaining items (after your, Dave's, and Ernst's patches). Harry On 2017-11-06 06:34 AM, Dan Carpenter wrote: > Linux-next was offline for t

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #2 from EoD --- On request from IRC, I also tried using UXA instead of SNA with the intel driver. It does not crash anymore, but when I try to enable the 2nd monitor, I get a "xrandr: Configure crtc 6 failed" and the following outpu

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

https://bugs.freedesktop.org/show_bug.cgi?id=103613 --- Comment #1 from EoD --- I also tried using modesetting instead of the other drivers and Enabling the monitor... - works, when I set driver=modesetting on the both cards via an xorg.conf - works, when I set driver=modesetting on the intel c

[Bug 103544] Graphical glitches r600 in game this war of mine linux native

https://bugs.freedesktop.org/show_bug.cgi?id=103544 --- Comment #13 from Ilia Mirkin --- (In reply to Roland Scheidegger from comment #12) > Here's a apitrace for this (1GB, of course the corruption is only seen > towards the end...), should be available a week (?): > https://we.tl/EanuxRG7Yf We

[PATCH v5 11/12] drm/tinydrm: Use drm_gem_cma_print_info()

There is a new core debugfs file that prints fb/gem info: /dri//framebuffer Use drm_gem_cma_print_info() to provide info to that output instead of using drm_fb_cma_debugfs_show(). Reviewed-by: Daniel Vetter Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/tinydr

[PATCH v5 10/12] drm/tilcdc: Use drm_gem_cma_print_info()

There is a new core debugfs file that prints fb/gem info: /dri//framebuffer Use drm_gem_cma_print_info() to provide info to that output instead of using drm_fb_cma_debugfs_show(). Cc: Jyri Sarha Cc: Tomi Valkeinen Signed-off-by: Noralf Trønnes Acked-by: Jyri Sarha Reviewed-by: Laurent Pinchar

[PATCH v5 12/12] drm/cma-helper: Remove drm_fb_cma_debugfs_show()

drm_fb_cma_debugfs_show() and drm_gem_cma_describe() are superseded by drm_framebuffer_debugfs_init() and drm_gem_cma_print_info(). Cc: Laurent Pinchart Signed-off-by: Noralf Trønnes Reviewed-by: Daniel Vetter Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/drm_fb_cma_helper.c | 37 ---

[PATCH v5 09/12] drm/arm/hdlcd: Use drm_gem_cma_print_info()

There is a new core debugfs file that prints fb/gem info: /dri//framebuffer Use drm_gem_cma_print_info() to provide info to that output instead of using drm_fb_cma_debugfs_show(). Cc: Liviu Dudau Cc: Brian Starkey Signed-off-by: Noralf Trønnes Acked-by: Liviu Dudau Reviewed-by: Laurent Pincha

[PATCH v5 05/12] drm/atomic: Use drm_framebuffer_print_info()

Use drm_framebuffer_print_info() to print framebuffer info in drm_atomic_plane_print_state(). This will give optional GEM info as well. Reviewed-by: Daniel Vetter Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/drm_atomic.c | 18 +++--- 1 file change

Re: [Intel-gfx] [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On Tue, 2017-11-07 at 13:39 +0100, Daniel Vetter wrote: > On Tue, Nov 07, 2017 at 10:47:00AM +0100, Michel Dänzer wrote: > > On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: > > > Some HW vblank counters reset due to power management events, which messes > > > up the vblank counting logic. This lea

[PATCH v5 02/12] drm/framebuffer: drm_framebuffer_read_refcount() constify argument

Constify argument so functions calling into this take a const argument. Reviewed-by: Ville Syrjälä Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- include/drm/drm_framebuffer.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_framebuffer.h b/i

[PATCH v5 06/12] drm/cma-helper: Turn to_drm_gem_cma_obj() into a macro

This allows the argument to be a const. The other option was to keep it an inline function and make the argument a const: static inline struct drm_gem_cma_object * to_drm_gem_cma_obj(const struct drm_gem_object *gem_obj) { return container_of(gem_obj, struct drm_gem_cma_object, base); }

[PATCH v5 07/12] drm/cma-helper: Add drm_gem_cma_print_info()

Add drm_gem_cma_print_info() for debugfs printing struct drm_gem_cma_object specific info. Reviewed-by: Daniel Vetter Signed-off-by: Noralf Trønnes --- drivers/gpu/drm/drm_gem_cma_helper.c | 19 +++ include/drm/drm_gem_cma_helper.h | 3 +++ 2 files changed, 22 insertions(+)

[PATCH v5 08/12] drm/arc: Use drm_gem_cma_print_info()

There is a new core debugfs file that prints fb/gem info: /dri//framebuffer Use drm_gem_cma_print_info() to provide info to that output instead of using drm_fb_cma_debugfs_show(). Cc: Alexey Brodkin Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/arc/arcpgu_drv

[PATCH v5 04/12] drm/framebuffer: Add framebuffer debugfs file

Add debugfs file that dumps info about the framebuffers and its planes. Also dump info about any connected gem object(s). Reviewed-by: Daniel Vetter Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- drivers/gpu/drm/drm_debugfs.c | 6 drivers/gpu/drm/drm_framebuffer.c |

[PATCH v5 03/12] drm/print: Add drm_printf_indent()

Add drm_printf_indent() that adds tab indentation according to argument. Indentation overflow is marked with an X. Reviewed-by: Daniel Vetter Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- include/drm/drm_print.h | 8 1 file changed, 8 insertions(+) diff --git a/incl

[PATCH v5 01/12] drm/vma-manager: drm_vma_node_start() constify argument

Constify argument so functions calling into this take a const argument. Reviewed-by: Ville Syrjälä Signed-off-by: Noralf Trønnes Reviewed-by: Laurent Pinchart --- include/drm/drm_vma_manager.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/include/drm/drm_vma_manager.h b/i

[PATCH v5 00/12] drm/framebuffer: Add framebuffer debugfs file

This patchset adds a debugfs file that prints info about the framebuffers. Changes since version 4: - Add framebuffer debugfs file: Fix printk formats and add info about indent argument in gem_print_info callback docs (Laurent) - Turn to_drm_gem_cma_obj() into a macro (Laurent) - drm_gem_cma_pri

[Bug 103613] Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor

https://bugs.freedesktop.org/show_bug.cgi?id=103613 Bug ID: 103613 Summary: Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor Product: DRI Version: DRI git Hardware: Other

Re: [Intel-gfx] [RFC 1/7] drm: Add Plane Degamma properties

On Tue, Nov 07, 2017 at 05:49:56PM +, Brian Starkey wrote: In one of the previous discussions[1] related to per-plane color management, Lionel suggested that the 16-bit color lut entries weren't enough when considering HDR. It might be worth creating a new gamma lut format with 32-bit entri

Re: [Intel-gfx] [RFC 1/7] drm: Add Plane Degamma properties

Hi, On Tue, Nov 07, 2017 at 05:36:25PM +0530, Uma Shankar wrote: Add Plane Degamma as a blob property and plane degamma size as a range property. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_atomic.c| 12 drivers/gpu/drm/drm_atomic_helper.c |6 ++

Re: [RFC 2/7] drm: Add Plane CTM property

Hi Uma, On Tue, Nov 07, 2017 at 05:36:26PM +0530, Uma Shankar wrote: Add a blob property for plane CSC usage. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_atomic.c| 10 ++ drivers/gpu/drm/drm_atomic_helper.c |3 +++ drivers/gpu/drm/drm_mode_config.c |

[PATCH v3 7/7] drm/bridge: tc358767: add copyright lines

Add copyright lines for Zodiac who paid for driver development. Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c |2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/bridge/tc358767.c b/drivers/gpu/drm/bridge/tc358767.c index 37e33f2..69d2af3 100644 --- a/

[PATCH v3 6/7] drm/bridge: tc358767: fix 1-lane behavior

Use drm_dp_channel_eq_ok helper Acked-by: Philipp Zabel Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c | 13 +++-- 1 file changed, 3 insertions(+), 10 deletions(-) diff --git a/drivers/gpu/drm/bridge/tc358767.c b/drivers/gpu/drm/bridge/tc358767.c index bb5d277..

[PATCH v3 2/7] drm/bridge: tc358767: filter out too high modes

Pixel clock limitation for DPI is 154 MHz. Do not accept modes with higher pixel clock rate. Reviewed-by: Andrzej Hajda Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c |5 - 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/bridge/tc358767.

[PATCH v3 3/7] drm/bridge: tc358767: fix DP0_MISC register set

Remove shift from TU_SIZE_RECOMMENDED define as it used to calculate max_tu_symbols. Acked-by: Philipp Zabel Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c |5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/bridge/tc358767.c b/drive

[PATCH v3 4/7] drm/bridge: tc358767: fix timing calculations

Fields in HTIM01 and HTIM02 regs should be even. Recomended thresh_dly value is max_tu_symbol. Remove set of VPCTRL0.VSDELAY as it is related to DSI input interface. Currently driver supports only DPI. Acked-by: Philipp Zabel Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c |

[PATCH v3 5/7] drm/bridge: tc358767: fix AUXDATAn registers access

First four bytes should go to DP0_AUXWDATA0. Due to bug if len > 4 first four bytes was writen to DP0_AUXWDATA1 and all data get shifted by 4 bytes. Fix it. Acked-by: Philipp Zabel Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c |2 +- 1 file changed, 1 insertion(+), 1 d

[PATCH v3 1/7] drm/bridge: tc358767: do no fail on hi-res displays

Do not fail data rates higher than 2.7 and more than 2 lanes. Try to fall back to 2.7Gbps and 2 lanes. Acked-by: Philipp Zabel Reviewed-by: Andrzej Hajda Signed-off-by: Andrey Gusakov --- drivers/gpu/drm/bridge/tc358767.c | 14 +- 1 file changed, 9 insertions(+), 5 deletions(-)

[PATCH v3 0/7] drm/bridge: tc358767: fixes and improvements

This set of patches fixes several issues that was found during testing tc358767 with desktop DisplayPort displays. Changes since v3 - added comment about removed VPCTRL0 write - corrected comment in "filter out too high modes" - added sing-off Changes since v2: - f

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

On 11/7/2017 5:07 PM, Mark Brown wrote: On Tue, Nov 07, 2017 at 07:26:03PM +0530, Mukunda,Vijendar wrote: Removing URL links and commit-ready description in v2. This doesn't really answer my question: These two URLs are different, what was being reviewed here? What is Commit-Ready suppose

Re: [PATCH] drm/ttm: set bo->resv point to tbo->ttm_resv after individualize_resv

On 07/11/17 02:44 PM, Christian König wrote: > Set bo->resv to ttm_resv during BO cleanup. This way freed BOs can be > better reaped during eviction. > > Signed-off-by: Roger He > Signed-off-by: Christian König KASAN caught some badness while running piglit with this applied, see the attached d

Re: [Intel-gfx] [PATCH 0/7] Add Plane Color Properties

Hi Uma, On 7 November 2017 at 12:06, Uma Shankar wrote: > This patch series adds properties for plane color features. It adds > properties for degamma used to linearize data, CSC used for gamut > conversion, and gamma used to again non-linearize data as per panel > supported color space. These ca

Re: [PATCH] drm/stm: ltdc: add clut mode support

+ Peter Hi Peter, CLUT support on STM32 has been removed thanks to your clean up patch named "drm: stm: remove dead code and pointless local lut storage" (https://patchwork.freedesktop.org/patch/166898/) This below patch puts back the clut mode support using the new drm gamma api. May I ask

Re: [Intel-gfx] [RFC 1/7] drm: Add Plane Degamma properties

On 7 November 2017 at 12:06, Uma Shankar wrote: > Add Plane Degamma as a blob property and plane > degamma size as a range property. > > v2: Rebase > Hi Uma, seems like something has gone wrong during the rebase. > Signed-off-by: Uma Shankar > --- > drivers/gpu/drm/drm_atomic.c| 12 ++

Re: [PATCH] drm/atomic: Try to preserve the crtc enabled state in drm_atomic_remove_fb, v2.

On Wed, Nov 01, 2017 at 04:04:33PM +0100, Maarten Lankhorst wrote: > This introduces a slight behavioral change to rmfb. Instead of > disabling a crtc when the primary plane is disabled, we try to > preserve it. > > Apart from old versions of the vmwgfx xorg driver, there is > nothing depending on

Re: [Intel-gfx] [PATCH] drm/selftests/mm: Insert cond_resched() between insert modes

On Tue, 2017-11-07 at 14:51 +0200, Joonas Lahtinen wrote: > On Tue, 2017-11-07 at 10:41 +, Chris Wilson wrote: > > kbuilder has begun running the selftests and reported a soft-lockup > > inside __igt_insert(), so break up the test loop over different > > modes > > with another call to cond_resc

[PATCH 1/2] fbdev: pxa3xx: use ktime_get_ts64 for time stamps

do_gettimeofday() is deprecated because it is not y2038 safe, so I'm changing the calculation for the diagnostic output over to using 'timespec64'. We really only print time deltas here, so changing it to monotonic time makes this more robust, the correct accessor for this is ktime_get_ts64(). Si

[PATCH 2/2] fbdev: radeon: stop use ktime_get() for HZ calibration

do_gettimeofday() is deprecated and a bit clumsy. This changes radeon_probe_pll_params() over to using ktime_get() with monotonic times. There is no need to check for negative values any more since the monotonic clocksource cannot go backwards, but I'm adding a check for zero-division in case of a

drivers/gpu/drm/bridge/lvds-encoder.c broken in mainline

Hi, drivers/gpu/drm/bridge/lvds-encoder.c driver is currently dysfunctional due to: |commit 13dfc0540a575b47b2d640b093ac16e9e09474f6 |Author: Eric Anholt |Date: Fri Jun 2 13:25:14 2017 -0700 | |drm/bridge: Refactor out the panel wrapper from the lvds-encoder bridge. Also, there is no in-ke

Re: [PATCH v1 2/2] drm/stm: ltdc: add a 2nd endpoint

2017-10-26 13:48 GMT+02:00 Philippe Cornu : > ltdc can have up to 2 endpoints: > - dpi external gpios: for rgb panels or external bridge ICs. > - dpi internal ios: connected internally to dsi. > > Note: Refer to the reference manual to know if the dsi is > present on your device. Applied on drm-

Re: [PATCH v1 1/2] dt-bindings: display: stm32: add a 2nd endpoint

2017-10-27 16:38 GMT+02:00 Rob Herring : > On Thu, Oct 26, 2017 at 01:48:08PM +0200, Philippe Cornu wrote: >> ltdc can have up to 2 endpoints: >> - dpi external gpios: for rgb panels or external bridge ICs. >> - dpi internal ios: connected internally to dsi. >> >> Note: Refer to the reference man

Re: [PATCH] drm/stm: checkpatch strict minor updates

2017-11-01 12:33 GMT+01:00 Gustavo Padovan : > 2017-10-26 Philippe Cornu : > >> Minor fixes detected with "scripts/checkpatch.pl --strict" >> >> Signed-off-by: Philippe Cornu >> --- >> drivers/gpu/drm/stm/dw_mipi_dsi-stm.c | 4 ++-- >> drivers/gpu/drm/stm/ltdc.c| 2 +- >> 2 files chan

Re: [PATCH] drm/stm: dsi: Rename driver name

2017-11-01 12:31 GMT+01:00 Gustavo Padovan : > Hi Philippe, > > 2017-10-26 Philippe Cornu : > >> Rename the driver name from "dw_mipi_dsi-stm" to >> "stm32-display-dsi" for a better readability >> in /sys/bus/platform/drivers entries. >> >> Signed-off-by: Philippe Cornu >> --- >> drivers/gpu/drm/

[PULL] drm-misc-next-fixes

Hi Dave, drm-misc-next-fixes-2017-11-07: Fixes for 4.15 merge window: Just the cherry-picked vc4 fix plus a GFP_NOFAIL annotation (there's apparently some new options in-flight to change/audit too-small-to-fail kmalloc semantics or something like that). Cheers, Daniel The following changes sinc

[PATCH] drm/ttm: set bo->resv point to tbo->ttm_resv after individualize_resv

Set bo->resv to ttm_resv during BO cleanup. This way freed BOs can be better reaped during eviction. Signed-off-by: Roger He Signed-off-by: Christian König --- drivers/gpu/drm/ttm/ttm_bo.c | 23 --- 1 file changed, 8 insertions(+), 15 deletions(-) diff --git a/drivers/gpu/d

Re: [PATCH] drm/selftests/mm: Insert cond_resched() between insert modes

On Tue, 2017-11-07 at 10:41 +, Chris Wilson wrote: > kbuilder has begun running the selftests and reported a soft-lockup > inside __igt_insert(), so break up the test loop over different modes > with another call to cond_resched(). > > Reported-by: Fengguang Wu > Signed-off-by: Chris Wilson

Re: [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On Tue, Nov 07, 2017 at 10:47:00AM +0100, Michel Dänzer wrote: > On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: > > Some HW vblank counters reset due to power management events, which messes > > up the vblank counting logic. This leads to screen freezes with user space > > waiting on vblank event

Re: [Intel-gfx] [PATCH 3/5] drm/vmwgfx: Try to fix plane clipping

On Mon, Nov 06, 2017 at 08:04:38PM +0200, Ville Syrjälä wrote: > On Thu, Nov 02, 2017 at 03:19:30PM +0200, Ville Syrjälä wrote: > > On Thu, Nov 02, 2017 at 11:12:09AM +0100, Daniel Vetter wrote: > > > On Wed, Nov 01, 2017 at 08:29:18PM +0200, Ville Syrjala wrote: > > > > From: Ville Syrjälä > > >

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

On Tue, Nov 07, 2017 at 07:26:03PM +0530, Mukunda,Vijendar wrote: > Removing URL links and commit-ready description in v2. This doesn't really answer my question: > > These two URLs are different, what was being reviewed here? What is > > Commit-Ready supposed to mean? Please don't top post, re

[RFC 7/7] drm/i915: Load plane color luts from atomic flip

Load plane color luts as part of atomic plane updates. This will be done only if the plane color luts are changed. Signed-off-by: Uma Shankar --- drivers/gpu/drm/i915/intel_atomic_plane.c |4 drivers/gpu/drm/i915/intel_color.c|8 drivers/gpu/drm/i915/intel_drv.h

[RFC 6/7] drm/i915: Implement Plane Gamma for Bdw and Gen9 platforms

Implement Plane Gamma feature for BDW and Gen9 platforms. Signed-off-by: Uma Shankar --- drivers/gpu/drm/i915/i915_pci.c |5 ++- drivers/gpu/drm/i915/i915_reg.h | 24 ++ drivers/gpu/drm/i915/intel_color.c | 58 ++ drivers/gpu/drm/i9

[RFC 5/7] drm/i915: Enable plane color features

Enable and initialize plane color features. v2: Rebase and some cleanup Signed-off-by: Uma Shankar --- drivers/gpu/drm/i915/i915_drv.h| 10 ++ drivers/gpu/drm/i915/intel_color.c | 12 drivers/gpu/drm/i915/intel_drv.h |9 + 3 files changed, 31 insertion

[RFC 3/7] drm: Add Plane Gamma properties

Add plane gamma as blob property and size as a range property. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_atomic.c|8 drivers/gpu/drm/drm_atomic_helper.c |3 +++ drivers/gpu/drm/drm_mode_config.c | 14 ++ include/drm/drm_mode_config.h

[RFC 4/7] drm: Define helper function for plane color enabling

Define helper function to enable Plane color features to attach plane color properties to plane structure. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_plane.c | 45 ++ include/drm/drm_color_mgmt.h |5 + 2 files changed, 50 ins

[RFC 2/7] drm: Add Plane CTM property

Add a blob property for plane CSC usage. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_atomic.c| 10 ++ drivers/gpu/drm/drm_atomic_helper.c |3 +++ drivers/gpu/drm/drm_mode_config.c |7 +++ include/drm/drm_mode_config.h |6 ++ includ

[RFC 1/7] drm: Add Plane Degamma properties

Add Plane Degamma as a blob property and plane degamma size as a range property. v2: Rebase Signed-off-by: Uma Shankar --- drivers/gpu/drm/drm_atomic.c| 12 drivers/gpu/drm/drm_atomic_helper.c |6 ++ drivers/gpu/drm/drm_mode_config.c | 14 ++ inclu

[PATCH 0/7] Add Plane Color Properties

This patch series adds properties for plane color features. It adds properties for degamma used to linearize data, CSC used for gamut conversion, and gamma used to again non-linearize data as per panel supported color space. These can be utilize by user space to convert planes from one format to an

Re: [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On Tue, Nov 07, 2017 at 11:55:44AM +0100, Michel Dänzer wrote: > On 07/11/17 11:50 AM, Ville Syrjälä wrote: > > On Tue, Nov 07, 2017 at 10:47:00AM +0100, Michel Dänzer wrote: > >> On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: > >>> Some HW vblank counters reset due to power management events, wh

Re: [PATCH v4 1/2] drm/bridge: Add Cadence DSI driver

On 20/10/17 10:49, Boris Brezillon wrote: > Add a driver for Cadence DPI -> DSI bridge. > > This driver only support a subset of Cadence DSI bridge capabilities. > > Here is a non-exhaustive list of missing features: > * burst mode > * dynamic configuration of the DPHY based on the > * support

Re: [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On 07/11/17 11:50 AM, Ville Syrjälä wrote: > On Tue, Nov 07, 2017 at 10:47:00AM +0100, Michel Dänzer wrote: >> On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: >>> Some HW vblank counters reset due to power management events, which messes >>> up the vblank counting logic. This leads to screen freez

Re: [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On Tue, Nov 07, 2017 at 10:47:00AM +0100, Michel Dänzer wrote: > On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: > > Some HW vblank counters reset due to power management events, which messes > > up the vblank counting logic. This leads to screen freezes with user space > > waiting on vblank event

[PATCH] drm/selftests/mm: Insert cond_resched() between insert modes

kbuilder has begun running the selftests and reported a soft-lockup inside __igt_insert(), so break up the test loop over different modes with another call to cond_resched(). Reported-by: Fengguang Wu Signed-off-by: Chris Wilson Cc: Joonas Lahtinen --- drivers/gpu/drm/selftests/test-drm_mm.c |

[PATCH] drm/tilcdc: Remove drm_framebuffer_get() and *_put() calls

The drm_framebuffer_get() and drm_framebuffer_put() calls in the tilcdc driver are obsolete. The drm atomic modesetting core should take care of holding the references while the atomic state object is in use. The old state is deleted when a commit of a new one is completed after drm_atomic_helper_w

Re: [RFC PATCH] drm/vblanks: Deal with HW vblank counter resets.

On 07/11/17 07:26 AM, Dhinakaran Pandiyan wrote: > Some HW vblank counters reset due to power management events, which messes > up the vblank counting logic. This leads to screen freezes with user space > waiting on vblank events that may not occur if the counter keeps resetting. > > For e.g., Aft

Re: [PATCH 3/3] ASoC: rt5645: Wait for 400msec before concluding on value of RT5645_VENDOR_ID2

On 11/6/2017 9:54 PM, Mark Brown wrote: On Fri, Nov 03, 2017 at 04:35:45PM -0400, Alex Deucher wrote: Minimum time required between power On of codec and read of RT5645_VENDOR_ID2 is 400msec. We should wait and attempt before erroring out. So the description says we have to wait 400ms befor

Re: [PATCH v4 5/9] drm/exynos: Add generic support for devices shared with V4L2 subsystem

Hi Inki, On 2017-11-06 02:20, Inki Dae wrote: 2017년 11월 03일 21:28에 Marek Szyprowski 이(가) 쓴 글: On 2017-11-01 07:26, Inki Dae wrote: 2017년 10월 23일 16:54에 Marek Szyprowski 이(가) 쓴 글: Some hardware modules, like FIMC in Exynos4 series are shared between V4L2 (camera support) and DRM (memory-to-mem

Re: [PATCH 1/3] ASoC: amd: Report accurate hw_ptr during dma

Removing URL links and commit-ready description in v2. On Monday 06 November 2017 09:18 PM, Mark Brown wrote: On Fri, Nov 03, 2017 at 04:35:43PM -0400, Alex Deucher wrote: Signed-off-by: Vijendar Mukunda Signed-off-by: Akshu Agrawal Reviewed-on: https://chromium-review.googlesource.com/6596

Re: [PATCH 15/22] drm/tilcdc: Use drm_fb_cma_fbdev_init/fini()

On 11/04/17 15:04, Noralf Trønnes wrote: > Use drm_fb_cma_fbdev_init() and drm_fb_cma_fbdev_fini() which relies on > the fact that drm_device holds a pointer to the drm_fb_helper structure. > This means that the driver doesn't have to keep track of that. > Also use the drm_fb_helper functions direc

Re: video: atmel_lcdfb: Use common error handling code in atmel_lcdfb_of_init()

On 06/11/2017 at 10:32, SF Markus Elfring wrote: >> Sorry but NACK: the message was malformed and resulted in the >> duplication of the error log that you spotted. >> >> The proper way to fix this is to modify the second occurrence of this >> message. > > * Would you like to achieve that a corres

[PATCH] video: fbdev: aty: radeon_pm: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva --- drivers/video/fbdev/aty/radeon_pm.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/video/fbdev/aty/radeon_pm.c b/drivers/video/fbde

Re: [PATCH 4.9.y 1/3] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

On 11/6/2017 2:57 PM, Greg KH wrote: On Fri, Nov 03, 2017 at 10:10:26AM +0700, Nhan Nguyen wrote: From: John Stultz commit 651e4769ba2a9f20c4b8a823ae2727bf7fa9c9f0 upstream. In chasing down issues with EDID probing, I found some duplicated but incomplete logic used to power the chip on and of

radeon_dp_aux_transfer_native: 74 callbacks suppressed

Hi all, commit 92c177b7947d9c889ea7b024871445015ea74221 Author: Lyude Date: Wed Feb 22 16:34:53 2017 -0500 drm/radeon/dp_auxch: Ratelimit aux transfer debug messages does more harm than good in my opinion. Since this commit, I see several occurrences of the following message in my kernel l

[PATCH] video: fbdev: sm501fb: mark expected switch fall-through in sm501fb_blank_crt

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Signed-off-by: Gustavo A. R. Silva --- drivers/video/fbdev/sm501fb.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/video/fbdev/sm501fb.c b/drivers/video/fbdev/sm501fb.c inde

drm/i915: GPU Hang with kernel v4.14-rc8

Hi, I do not have a bugzilla account and do not intend to register in the bugzilla, therefore, I am sending this e-mail instead. I have got a GPU hang with kernel v4.14-rc8 "GPU HANG: ecode 7:1:0xecdfbff0, in Xorg [761], reason: No progress on bcs0, action: reset". The crash dump is attached. Wit

[PATCH] video: fbdev: cirrusfb: mark expected switch fall-throughs

In preparation to enabling -Wimplicit-fallthrough, mark switch cases where we are expecting to fall through. Notice that in this particular case I placed the "fall through" comment on its own line, which is what GCC is expecting to find. Signed-off-by: Gustavo A. R. Silva --- drivers/video/fbde

Re: linux-next: Tree for Nov 6 (amdgpu_virt.c)

On 11/05/2017 11:30 PM, Stephen Rothwell wrote: > Hi all, > > Changes since 20171103: > on i386, when CONFIG_MODULES is not set: CC drivers/gpu/drm/amd/amdgpu/amdgpu_virt.o In file included from ../arch/x86/include/asm/atomic.h:5:0, from ../include/linux/atomic.h:5,

Re: [PATCH] video: atmel_lcdfb: Use common error handling code in atmel_lcdfb_of_init()

On 05/11/2017 at 14:10, SF Markus Elfring wrote: > From: Markus Elfring > Date: Sun, 5 Nov 2017 14:00:52 +0100 > > Add a jump target so that a specific error message is stored only once > at the end of this function implementation. > Replace two calls of the function "dev_err" by goto statements.

Re: [PATCH 0/4] dma-buf: Silence dma_fence __rcu sparse warnings

Hi Ville, On 3 November 2017 at 13:18, Christian König wrote: > Patch #4 is Reviewed-by: Christian König . > > The rest is Acked-by: Christian König . > > Regards, > Christian. > > > Am 02.11.2017 um 21:03 schrieb Ville Syrjala: >> >> From: Ville Syrjälä >> >> When building drm+i915 I get around