drm: rockchip: CONFIG_DRM_FBDEV_EMULATION will crash the HDMI down sometimes

Hello: I want to enable the video output at RK3288 Firefly board, but I found if I enable CONFIG_DRM_FBDEV_EMULATION, the HDMI would crash down sometimes but sometimes it works. After disable that opinion, I never meet a problem. I have not verified it with eDP as I meet a big problem in

Re: [patch] drm/vc4: fix a bounds check

On Mon, Jan 16, 2017 at 11:40:10PM +, Eric Engestrom wrote: > > diff --git a/drivers/gpu/drm/vc4/vc4_render_cl.c > > b/drivers/gpu/drm/vc4/vc4_render_cl.c > > index 08886a3..5cdd003 100644 > > --- a/drivers/gpu/drm/vc4/vc4_render_cl.c > > +++ b/drivers/gpu/drm/vc4/vc4_render_cl.c > > @@

Re: [PATCH v3 1/7] drm/atomic: Add new iterators over all state, v3.

Op 17-01-17 om 00:11 schreef Laurent Pinchart: > Hi Maarten, > > Thank you for the patch. > > On Monday 16 Jan 2017 10:37:38 Maarten Lankhorst wrote: >> Add for_each_(old)(new)_(plane,connector,crtc)_in_state iterators to >> replace the old for_each_xxx_in_state ones. This is useful for >1 flip >>

[Bug 99418] DRI3 Stuttering while scrolling in Chromium/Chrome with VBLANK off

https://bugs.freedesktop.org/show_bug.cgi?id=99418 --- Comment #1 from Michel Dänzer --- Please attach the corresponding Xorg log file and output of glxinfo. -- You are receiving this mail because: You are the assignee for the

Re: [PATCH] drm/exynos: use atomic helper commit

2017년 01월 17일 05:34에 Laurent Pinchart 이(가) 쓴 글: > Hi Inki, > > Thank you for the patch. > > On Monday 16 Jan 2017 18:13:22 Inki Dae wrote: >> This patch relpaces specific atomic commit function >> with atomic helper commit one, which also includes >> atomic_commit_tail callback for Exynos SoC

Re: [PATCH] drm/exynos: use atomic helper commit

2017년 01월 16일 20:22에 Tobias Jakobi 이(가) 쓴 글: > Inki Dae wrote: >> This patch relpaces specific atomic commit function >> with atomic helper commit one, which also includes >> atomic_commit_tail callback for Exynos SoC becasue >> crtc devices on Exynos SoC uses power domain device >> so

[Bug 93760] radeonsi vaapi mpeg2 decode slightly corrupt or asserts.

https://bugs.freedesktop.org/show_bug.cgi?id=93760 Nayan Deshmukh changed: What|Removed |Added Assignee|dri-devel@lists.freedesktop

Re: [PATCH] drm/exynos: remove unnecessary codes

2017년 01월 16일 18:37에 Andrzej Hajda 이(가) 쓴 글: > On 16.01.2017 10:13, Inki Dae wrote: >> This patch removes exynos_drm_crtc_cancel_page_flip call >> when drm is closed because at that time, events will be released >> by drm_events_release function. >> >> Change-Id:

[PATCH v2 1/3] drm/atomic: Save flip flags in drm_plane_state

Allows using atomic flip helpers for drivers using ASYNC flip. Remove ASYNC_FLIP restriction in helpers and caches the page flip flags in drm_plane_state to be used in the low level drivers. v2: Resending the patch since the original was broken. Remove comment about not supporting ASYNC flips.

Re: [PATCH v11 06/12] drm/mediatek: update display module connections

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > update connections for OVL, RDMA, BLS, DSI > > Signed-off-by: YT Shen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_drm_ddp.c | 25 + > 1 file changed, 25

[PATCH v2 2/3] drm/amd/display: Switch to using atomic_helper for flip.

Signed-off-by: Andrey Grodzovsky --- drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h | 1 - .../drm/amd/display/amdgpu_dm/amdgpu_dm_types.c| 92 ++ 2 files changed, 6 insertions(+), 87 deletions(-) diff --git

[PATCH v2 3/3] drm/nouveau/kms/nv50: Switch to using atomic helper for flip.

Change-Id: I5a3189c03e389af2ff6c13d870a7d28282b7b0ee Signed-off-by: Andrey Grodzovsky --- drivers/gpu/drm/nouveau/nv50_display.c | 77 +++--- 1 file changed, 5 insertions(+), 72 deletions(-) diff --git

[PATCH v2 0/3] Allow ASYNC flip with atomic helpers.

This series is a folow-up on https://patchwork.kernel.org/patch/9501787/ The first patch makes changes to atomic helpers to allow for drives with ASYNC flip support to use them. Patch 2 is to use this in AMDGPU/DC. Patch 3 is possible cleanup in nouveau/kms who seems to have to duplicate the

Re: [PATCH v11 05/12] drm/mediatek: add BLS component

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > Add BLS component for PWM + GAMMA function > > Signed-off-by: YT Shen Acked-by: CK Hu > --- > drivers/gpu/drm/mediatek/mtk_drm_ddp_comp.c | 5 - >

[PATCH v2 4/8] drm/msm/mdp5: Configure COLOR3_OUT propagation

In MDP5 Layer Mixer HW, the blender output is only the blended color components (i.e R, G and B, or COLOR0/1/2 in MDP5 HW terminology). This is fed to the BG input of the next blender. We also need to provide an alpha (COLOR3) value for the BG input at the next stage. This is configured via using

[PATCH v2 7/8] drm/msm/mdp5: Refactor mdp5_plane_atomic_check

In mdp5_plane_atomic_check, we get crtc_state from drm_plane_state. Later, for cursor planes, we'll populate the update_plane() func that takes a fast asynchronous path to implement cursor movements. There, we would need to call a similar atomic_check func to validate the plane state, but

[PATCH v2 8/8] HACK: drm/msm/mdp5: Add support for legacy cursor updates

This code has been more or less picked up from the vc4 and intel implementations of update_plane() funcs for cursor planes. The update_plane() func is usually the drm_atomic_helper_update_plane func that will issue an atomic commit with the plane updates. Such commits are not intended to be done

[PATCH v2 6/8] drm/msm/mdp5: Add cursor planes

Register cursor drm_planes. The loop in modeset_init that inits the planes and crtcs has to be refactored a bit. We first iterate all the hwpipes to find the cursor planes. Then, we loop again to create crtcs. In msm_atomic_wait_for_commit_done, remove the check which bypasses waiting for vsyncs

[PATCH v2 1/8] drm/msm/mdp5: cfg: Add pipe_cursor block

Define the block in advance so that the generated mdp5.xml.h doesn't break build. Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h

[PATCH v2 5/8] drm/msm/mdp5: Misc cursor plane bits

These are various changes added in preparation for cursor planes: - Add a pipe_cursor block for 8x96 in mdp5_cfg. - Add a new pipe CAP called MDP_PIPE_CAP_CURSOR. Use this to ensure we assign a cursor SSPP for a drm_plane with type DRM_PLANE_TYPE_CURSOR. - Update

[PATCH v2 0/8] drm/msm/mdp5: Cursor plane stuff

This series does some mdp5_plane related clean ups (use plane helpers for clipping etc), adds MDP5 bits needed for cursor plane blocks, and then add cursor planes. On older MDP5 versions, we had cursor HW in Layer Mixer blocks, and that's implemented in mdp5_crtc.c. With newer hardware, the

[PATCH v2 2/8] drm/msm/mdp5: Prepare CRTC/LM for empty stages

Use SSPP_NONE in mdp5_plane_pipe() if there is now hwpipe allocated for the drm_plane. Returning '0' means we are returning VIG0 pipe. Also, use the mdp5_pipe enum to pass around the stage array. Initialize the stage to SSPP_NONE by default. We do the above because 1) Cursor plane has to be

[PATCH v2 3/8] drm/msm/mdp5: Use plane helpers to configure src/dst rectangles

The MDP5 plane's atomic_check ops doesn't perform clipping tests. This didn't hurt us much in the past, but clipping becomes important with cursor planes. Use drm_plane_helper_check_state, the way rockchip/intel/mtk drivers already do. Use these drivers as reference. Clipping requires knowledge

[PATCH] drm/exynos: g2d: fix overflow of cmdlist size

The size of cmdlist is integer type, so it can be overflowed by cmd and cmd_buf that has too big size. This patch will fix overflow issue as checking maximum size of cmd and cmd_buf. Signed-off-by: Joonyoung Shim --- drivers/gpu/drm/exynos/exynos_drm_g2d.c | 9 -

RE: [PATCH 1/4] drm/atomic: Save flip flags in drm_plane_state

> -Original Message- > From: Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com] > Sent: Monday, January 16, 2017 5:18 PM > To: dri-devel@lists.freedesktop.org > Cc: Grodzovsky, Andrey; nouv...@lists.freedesktop.org; amd- > g...@lists.freedesktop.org; Deucher, Alexander;

[PATCH v2 4/6] drm/msm/mdp5: Create single encoder per interface (INTF)

For the DSI interfaces, the mdp5_kms core creates 2 encoders for video and command modes. Create only a single encoder per interface. When creating the encoder, set the interface type to MDP5_INTF_MODE_NONE. It's the bridge (DSI/HDMI/eDP) driver's responsibility to set a different interface type.

[PATCH v2 5/6] drm/msm/mdp5: cfg: Change count to unsigned int

Count can't be non-zero. Changing to uint will also prevent future warnings. Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/msm/mdp/mdp5/mdp5_cfg.h

[PATCH v2 6/6] drm/msm/mdp5: Create only as many CRTCs as we need

We currently create CRTCs equaling to the # of Layer Mixer blocks we have on the MDP5 HW. This number is generally more than the # of encoders (INTFs) we have in the MDSS HW. The number of encoders connected to displays on the platform (as described by DT) would be even lesser. Create only N

[PATCH v2 0/6] drm/msm/mdp5: Encoder related cleanups

The MDP5 and DSI drivers created 2 drm_encoders for a DSI interface (one for each mode of operation). This set creates one encoder per DSI interface. This is needed by the updated drm_bridge API. Now, with the # encoders equal to the # of displays, we can create the right # of CRTCs. We

[PATCH v2 3/6] drm/msm/mdp5: Prepare for merging video and command encoders

Rename the mdp5_encoder_* ops for active displays to mdp5_vid_encoder_* ops. Signed-off-by: Archit Taneja --- drivers/gpu/drm/msm/mdp/mdp5/mdp5_encoder.c | 31 ++--- drivers/gpu/drm/msm/mdp/mdp5/mdp5_kms.c | 3 ++-

[PATCH v2 1/6] drm/msm: Construct only one encoder for DSI

We currently create 2 encoders for DSI interfaces, one for command mode and other for video mode operation. This isn't needed as we can't really use both the encoders at the same time. It also makes connecting bridges harder. Switch to creating a single encoder. For now, we assume that the

[PATCH v2 2/6] drm/msm: Set encoder's mode of operation using a kms func

The mdp5 kms driver currently sets up multiple encoders per interface (INTF), one for each kind of mode of operation it supports. We create 2 drm_encoders for DSI, one for Video Mode and the other for Command Mode operation. The reason behind this approach could have been that we aren't aware of

Request API: stateless VPU: the buffer mechanism and DPB management

Hello all: I have recently finish the learning of the H.264 codec and ready to write the driver. Although I have not get deep in syntax of H.264 but I think I just need to reuse and extended the VA-API H264 Parser from gstreamer. The whole plan in userspace is just injecting a parsing

Request API: stateless VPU: the buffer mechanism and DPB management

Hello all: I have recently finish the learning of the H.264 codec and ready to write the driver. Although I have not get deep in syntax of H.264 but I think I just need to reuse and extended the VA-API H264 Parser from gstreamer. The whole plan in userspace is just injecting a parsing

Re: [PATCH v11 04/12] drm/mediatek: add shadow register support

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > We need to acquire mutex before using the resources, > and need to release it after finished. > So we don't need to write registers in the blanking period. > > Signed-off-by: YT Shen Acked-by: CK Hu

Re: [PATCH v11 03/12] drm/mediatek: add *driver_data for different hardware settings

Hi, YT: On Wed, 2017-01-11 at 14:51 +0800, YT Shen wrote: > There are some hardware settings changed, between MT8173 & MT2701: > DISP_OVL address offset changed, color format definition changed. > DISP_RDMA fifo size changed. > DISP_COLOR offset changed. > MIPI_TX pll setting changed. > And add

Re: [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

Hi Maarten, One more thing. On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > Fourth iteration. Instead of trying to convert all drivers straight away, > implement all macros that are required to get state working. > > Old situation: > Use obj->state, which can refer to old or new

Re: [PATCH v3 6/7] drm/atomic: Convert get_existing_state callers to get_old/new_state, v2.

Hi Maarten, One more thing. On Monday 16 Jan 2017 10:37:43 Maarten Lankhorst wrote: > This is a straightforward conversion that converts all the users of > get_existing_state in atomic core to use get_old_state or get_new_state > > Changes since v1: > - Fix using the wrong state in >

Re: [PATCH v3 7/7] drm/blend: Use new atomic iterator macros.

Hi Maarten, Thank you for the patch. On Monday 16 Jan 2017 10:37:44 Maarten Lankhorst wrote: Could we please get a commit message ? Apart from that, Reviewed-by: Laurent Pinchart > Signed-off-by: Maarten Lankhorst > ---

Re: [PATCH v3 6/7] drm/atomic: Convert get_existing_state callers to get_old/new_state, v2.

Hi Maarten, Thank you for the patch. I don't think you need the "v2" at the end of the subject line. On Monday 16 Jan 2017 10:37:43 Maarten Lankhorst wrote: > This is a straightforward conversion that converts all the users of > get_existing_state in atomic core to use get_old_state or

Re: [PATCH v3 5/7] drm/atomic: Add macros to access existing old/new state

Hi Maarten, Thank you for the patch. On Monday 16 Jan 2017 10:37:42 Maarten Lankhorst wrote: > After atomic commit, these macros should be used in place of > get_existing_state. Also after commit get_xx_state should no longer > be used because it may not have the required locks. Should this be

Re: [PATCH v3 4/7] drm/atomic: Fix atomic helpers to use the new iterator macros.

Hi Maarten, (CC'ing Daniel) Thank you for the patch. On Monday 16 Jan 2017 10:37:41 Maarten Lankhorst wrote: > Signed-off-by: Maarten Lankhorst > --- > drivers/gpu/drm/drm_atomic_helper.c | 293 +--- > 1 file changed, 152

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

Hi Dave, Today's linux-next merge of the drm tree got a conflict in: include/drm/drm_atomic.h between commit: 7e9081c5aac7 ("drm/fence: fix memory overwrite when setting out_fence fd") from the drm-misc-fixes tree and commit: bdc571464c49 ("drm/atomic: Clean up wait_for_vblanks, v2.")

[PATCH 3/6] drm/bridge: adv7511: Enable HPD interrupts to support hotplug and improve monitor detection

From: Archit Taneja On some adv7511 implementations, we can get some spurious disconnect signals which can cause monitor probing to fail. This patch enables HPD (hot plug detect) interrupt support which allows the monitor to be properly re-initialized when the spurious

[PATCH 2/6] drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event()

In chasing down a previous issue with EDID probing from calling drm_helper_hpd_irq_event() from irq context, Laurent noticed that the DRM documentation suggests that drm_kms_helper_hotplug_event() should be used instead. Thus this patch replaces drm_helper_hpd_irq_event() with

[PATCH 4/6] drm/bridge: adv7511: Rework adv7511_power_on/off() so they can be reused internally

In chasing down issues with EDID probing, I found some duplicated but incomplete logic used to power the chip on and off. This patch refactors the adv7511_power_on/off functions, so they can be used for internal needs. Cc: David Airlie Cc: Archit Taneja

[PATCH 5/6] drm/bridge: adv7511: Reuse __adv7511_power_on/off() when probing EDID

Thus this patch changes the EDID probing logic so that we re-use the __adv7511_power_on/off() calls instead of duplciating logic. This does change behavior slightly as it adds the HPD signal pulse to the EDID probe path, but Archit has had a patch to add HPD signal pulse to the EDID probe path

[PATCH 6/6] drm/bridge: adv7511: Re-write the i2c address before EDID probing

I've found that by just turning the chip on and off via the POWER_DOWN register, I end up getting i2c_transfer errors on HiKey. Investigating further, it seems some of the register state in the regmap cache is getting lost, likely as the device registers were reset during power off. Thus this

[PATCH 0/6 v4] adv7511 EDID probing improvements

Wanted to re-send out v4 of this patch set, integrating some changes suggested by Laurent, for consideration for merging for v4.11 The first three patches are fixups that are hopefully straight forward, integrating feedback I got from Laurant, with minimal change from the previous versions. The

[PATCH 1/6] drm/bridge: adv7511: Use work_struct to defer hotplug handing to out of irq context

I was recently seeing issues with EDID probing, where the logic to wait for the EDID read bit to be set by the IRQ wasn't happening and the code would time out and fail. Digging deeper, I found this was due to the fact that IRQs were disabled as we were running in IRQ context from the HPD signal.

Re: [PATCH v4 0/3] Generic HDMI codec: Add channel mapping control

Hello, Any comments on this patch-set? what about the introduction of pcm new callback in DAI ops to use chmap helpers? Is it something reasonable, or should i come back on V1? Regards Arnaud > 2017-01-03 16:52 GMT+01:00 Arnaud Pouliquen : > Aim of this patch is to add

Re: [PATCH V7 1/4] Documentation/devicetree/bindings: b850v3_lvds_dp

On Tue, Jan 10, 2017 at 11:04:58PM +0200, Laurent Pinchart wrote: > Hi Peter, Laurent! > > On Saturday 07 Jan 2017 01:29:52 Peter Senna Tschudin wrote: > > On 04 January, 2017 21:39 CET, Rob Herring wrote: > > > On Tue, Jan 3, 2017 at 5:34 PM, Peter Senna Tschudin wrote: > > >> On 03 January,

Re: [PATCH 1/4] ARM: EXYNOS: Remove Exynos4415 driver (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the mach code. > >

Re: [PATCH 1/3] drm: bridge: dw-hdmi: Define and use macros for PHY register addresses

Hi Laurent, 在 2017年01月13日 21:46, Laurent Pinchart 写道: On Friday 13 Jan 2017 09:32:54 Nickey.Yang wrote: 在 2017年01月12日 23:26, Laurent Pinchart 写道: On Thursday 12 Jan 2017 09:45:31 Nickey.Yang wrote: 在 2017年01月12日 07:49, Laurent Pinchart 写道: Replace the hardcoded register address numerical

Re: [RFC] drm: Parse HDMI 2.0 YCbCr 4:2:0 VDB and VCB

Hi Ville, Sorry for the late reply. On 11-01-2017 11:36, Ville Syrjälä wrote: > On Wed, Jan 11, 2017 at 10:27:03AM +, Jose Abreu wrote: >> Hi Ville, >> >> >> On 10-01-2017 17:21, Ville Syrjälä wrote: >> >> [snip] >> But we already have color_formats field in drm_display_info

Re: [PATCH 0/3] dw-hdmi: miscellaneous cleanups and fixes

Hi Laurent, Sorry for the late review. On 11-01-2017 23:49, Laurent Pinchart wrote: > Hello, > > These three small patches add to the 20 dw-hdmi patches previously submitted > in the "[PATCH v2 00/29] R-Car Gen3 HDMI output support" series. As only > patches 1 to 16 from that series have been

Re: [PATCH v1 6/7] ARM: dts: stm32429i-eval: Enable ltdc & simple panel on Eval board

Hi On 01/16/2017 02:29 PM, Yannick Fertre wrote: Enable ltdc & enable am-480272h3tmqw-t01h panel. Signed-off-by: Yannick Fertre --- Can you please change commit header with: "ARM: dts: stm32: Enable ltdc & simple panel on stm32f429-Eval board"

Re: [PATCH v1 7/7] ARM: configs: Add STM32 LTDC support in STM32 defconfig

Hi On 01/16/2017 02:29 PM, Yannick Fertre wrote: Signed-off-by: Yannick Fertre --- commit header "ARM: configs: stm32: ADD LDTC support" arch/arm/configs/stm32_defconfig | 5 + 1 file changed, 5 insertions(+) diff --git a/arch/arm/configs/stm32_defconfig

rockchip: edp: Meet a problem with supporting eDP panel at firefly release

Hello: I meet a problem when I want to add support for a lg,lp079qx1-sp0v eDP panel at firefly release rk3288 platform. I could hardly make the eDP work both on firefly release and firefly reload. Does you have any idea about that? [ 11.136586] i2c i2c-6: of_i2c: modalias failure on

Re: [PATCH 2/4] clk: samsung: Remove Exynos4415 driver (SoC not supported anymore)

Hi, On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

RE: [Intel-gfx] [PATCH] drm: Fix for invalid pruning of modes in dual display cases

> -Original Message- > From: Ville Syrjälä [mailto:ville.syrj...@linux.intel.com] > Sent: Tuesday, December 13, 2016 9:17 PM > To: Jani Nikula > Cc: Chris Wilson ; Srinivas, Vidya > ;

Re: [PATCH 3/4] pinctrl: samsung: Remove support for Exynos4415 (SoC not supported anymore)

On 2017년 01월 14일 21:36, Krzysztof Kozlowski wrote: > Support for Exynos4415 is going away because there are no internal nor > external users. > > Since commit 46dcf0ff0de3 ("ARM: dts: exynos: Remove exynos4415.dtsi"), > the platform cannot be instantiated so remove also the drivers. > >

Re: [PATCH v1 5/7] ARM: dts: stm32f429: Add ltdc support

Hi, On 01/16/2017 02:29 PM, Yannick Fertre wrote: Add LTDC (Lcd-tft Display Controller) support. Signed-off-by: Yannick Fertre Can you change commit header by: "ARM: dts: stm32: Add ltdc support on stm32f429 MCU" please --- arch/arm/boot/dts/stm32f429.dtsi | 25

[PATCH] Revert "drm/vmwgfx: Replace numeric parameter like 0444 with macro"

This reverts commit 2d8e60e8b0742b7a5cddc806fe38bb81ee876c33. The commit belongs to the series of 1285 patches sent to LKML on 2016-08-02. The general consensus was that the changes does not increase readability, quite the opposite; 0600 is easier to parse mentally than S_IRUSR | S_IWUSR. It

Re: [PATCH v3 0/7] drm/atomic: Add accessor macros for all atomic state.

Hi Maarten, Thank you for the patches. On Monday 16 Jan 2017 10:37:37 Maarten Lankhorst wrote: > Fourth iteration. Instead of trying to convert all drivers straight away, > implement all macros that are required to get state working. > > Old situation: > Use obj->state, which can refer to old

Re: [PATCH v3 3/7] drm/atomic: Use new atomic iterator macros.

Hi Maarten, Thank you for the patch. On Monday 16 Jan 2017 10:37:40 Maarten Lankhorst wrote: Could we please get a description ? Apart from that, Reviewed-by: Laurent Pinchart > Signed-off-by: Maarten Lankhorst > --- >

Re: [patch] drm/vc4: fix a bounds check

On Friday, 2017-01-13 10:49:00 +0300, Dan Carpenter wrote: > We accidentally return success even if vc4_full_res_bounds_check() fails. > > Fixes: d5b1a78a772f ("drm/vc4: Add support for drawing 3D frames.") > Signed-off-by: Dan Carpenter > --- > Not tested. It would be

Re: [RFC][PATCH] drm/bridge: adv7511: Re-write the i2c address as it may have been lost

On Mon, Jan 16, 2017 at 3:36 PM, Laurent Pinchart wrote: > Hi John, > > Thank you for the patch. > > On Monday 16 Jan 2017 15:16:51 John Stultz wrote: >> Laurent: Would something like the following be preferred? Seems >> to work as well for me.. > > That looks

Re: [RFC][PATCH] drm/bridge: adv7511: Re-write the i2c address as it may have been lost

Hi John, Thank you for the patch. On Monday 16 Jan 2017 15:16:51 John Stultz wrote: > Laurent: Would something like the following be preferred? Seems > to work as well for me.. That looks good to me. Feel free to still de-duplicate the power on/off code if you want (but of course without

Re: [PATCH v3 2/7] drm/atomic: Make add_affected_connectors look at crtc_state.

Hi Maarten, Thank you for the patch. On Monday 16 Jan 2017 10:37:39 Maarten Lankhorst wrote: > This kills another dereference of connector->state. connector_mask > holds all unchanged connectors at least and any changed connectors > are already in state anyway. > > Signed-off-by: Maarten

[RFC][PATCH] drm/bridge: adv7511: Re-write the i2c address as it may have been lost

Laurent: Would something like the following be preferred? Seems to work as well for me.. thanks -john I've found that by just turning the chip on and off via the POWER_DOWN register, I end up getting i2c_transfer errors on HiKey. Investigating further, it seems some of the register state in

Re: [PATCH v3 1/7] drm/atomic: Add new iterators over all state, v3.

Hi Maarten, Thank you for the patch. On Monday 16 Jan 2017 10:37:38 Maarten Lankhorst wrote: > Add for_each_(old)(new)_(plane,connector,crtc)_in_state iterators to > replace the old for_each_xxx_in_state ones. This is useful for >1 flip > depth and getting rid of all xxx->state dereferences. >

Re: Unix Device Memory Allocation project

Thanks for all the feedback. Things are much clearer now. Yeah, we can use the BO modifiers for simple 2D images / planes if that's the general direction. I think we can even stuff the compression data buffer offset into those 64 bits, considering it's not very large (e.g. below 4GB and low bits

Re: [PATCH 5/5 v3] drm/bridge: adv7511: Reuse __adv7511_power_on/off() when probing EDID

Hi John, On Monday 16 Jan 2017 12:14:48 John Stultz wrote: > On Mon, Jan 16, 2017 at 8:03 AM, Laurent Pinchart wrote: > > On Tuesday 03 Jan 2017 11:41:42 John Stultz wrote: > >> I've found that by just turning the chip on and off via the > >> POWER_DOWN register, I end up getting i2c_transfer

Re: [PATCH] drm/fence: fix memory overwrite when setting out_fence fd

2017-01-13 Chad Versace : > On Fri 13 Jan 2017, Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Currently if the userspace declares a int variable to store the out_fence > > fd and pass it to OUT_FENCE_PTR the kernel will

Re: [PATCH 1/4] drm/atomic: Save flip flags in drm_plane_state

Hi Andrey, Thank you for the patch. On Monday 16 Jan 2017 10:44:55 Andrey Grodzovsky wrote: > Allows using atomic flip helpers for drivers > using ASYNC flip. > Remove ASYNC_FLIP restriction in helpers and > caches the page flip flags in drm_plane_state > to be used in the low level drivers. >

Re: [PATCH 3/4] drm/amd/display: Switch to using atomic_helper for flip.

Hi Andrey, Thank you for the patch. On Monday 16 Jan 2017 10:44:57 Andrey Grodzovsky wrote: > Change-Id: Iad3e0b9b3546e4e4dc79be9233daf4fe4dba83e0 > Signed-off-by: Andrey Grodzovsky > --- > .../drm/amd/display/amdgpu_dm/amdgpu_dm_types.c| 92 ++ >

Re: [PATCH 2/4] drm/amdgpu: Remove flip_flag from amdgpu_crtc

Hi Andrey, Thank you for the patch. On Monday 16 Jan 2017 10:44:56 Andrey Grodzovsky wrote: > Follwing introduction of pflip_flags in drm_plane_state > this is not needed anymore. > > Signed-off-by: Andrey Grodzovsky > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_mode.h

Re: [PATCH 0/4] Allow ASYNC flip with atomic helpers.

Hi Harry, On Monday 16 Jan 2017 16:13:39 Harry Wentland wrote: > On 2017-01-16 03:39 PM, Laurent Pinchart wrote: > > On Monday 16 Jan 2017 10:44:54 Andrey Grodzovsky wrote: > >> This series is a folow-up on > >> https://patchwork.kernel.org/patch/9501787/ > >> > >> The first patch makes changes

Re: [PATCH] drm/armada: Include current dir on CFLAGS for armada trace

Hi Gustavo, (CC'ing Steven) On Monday 16 Jan 2017 19:12:58 Gustavo Padovan wrote: > 2017-01-16 Laurent Pinchart : > > On Monday 16 Jan 2017 18:13:30 Gustavo Padovan wrote: > >> From: Gustavo Padovan > >> > >> Otherwise

Re: [PATCH -next] drm/atomic: make release_crtc_commit() static

Hi Wei, 2017-01-12 Wei Yongjun : > From: Wei Yongjun > > Fixes the following sparse warning: > > drivers/gpu/drm/drm_atomic_helper.c:1360:6: warning: > symbol 'release_crtc_commit' was not declared. Should it be static? > > Signed-off-by: Wei

[Bug 96488] [r600g]OpenCL driver causes segfault in ImageMagick's Histogram kernel

https://bugs.freedesktop.org/show_bug.cgi?id=96488 --- Comment #10 from Jan Vesely --- (In reply to nixscripter from comment #9) > I have downloaded LLVM r290690 which contains your first diff, manually > applied your 2nd diff, and compiled it. The resulting

Re: [PATCH -next] drm/hisilicon/hibmc: Fix wrong pointer passed to PTR_ERR()

Hi Wei, 2017-01-12 Wei Yongjun : > From: Wei Yongjun > > PTR_ERR should access the value just tested by IS_ERR, otherwise > the wrong error code will be returned. > > Fixes: d1667b86795a ("drm/hisilicon/hibmc: Add support for frame buffer") >

Re: [PATCH 0/4] Allow ASYNC flip with atomic helpers.

On 2017-01-16 03:39 PM, Laurent Pinchart wrote: Hi Andrey, Thank you for the patches. On Monday 16 Jan 2017 10:44:54 Andrey Grodzovsky wrote: This series is a folow-up on https://patchwork.kernel.org/patch/9501787/ The first patch makes changes to atomic helpers to allow for drives with

Re: [PATCH 2/3] drm: qxl: Open code probing sequence for qxl

Hi Gabriel, 2017-01-12 Gabriel Krisman Bertazi : > This avoids using the deprecated drm_get_pci_dev() and load() hook > interfaces in the qxl driver. > > The only tricky part is to ensure TTM debugfs initialization > happens after the debugfs root node is created, which

Re: [PATCH] drm/armada: Include current dir on CFLAGS for armada trace

2017-01-16 Laurent Pinchart : > Hi Gustavo, > > Thank you for the patch. > > On Monday 16 Jan 2017 18:13:30 Gustavo Padovan wrote: > > From: Gustavo Padovan > > > > Otherwise compilation fails like this: > > > > In file

[Bug 99275] Kernel 4.9: amdgpu regression; gui flickers; amd radeon rx 460

https://bugs.freedesktop.org/show_bug.cgi?id=99275 --- Comment #10 from Reimar Imhof --- I've just tried kernel 4.9.4 from download.opensuse.org/repositories/Kernel:/stable/standard/ Same bug. Do you have any news? -- You are receiving this mail because: You are the

RE: [PATCH 1/4] drm/atomic: Save flip flags in drm_plane_state

> -Original Message- > From: Gustavo Padovan [mailto:gust...@padovan.org] > Sent: Monday, January 16, 2017 3:22 PM > To: Grodzovsky, Andrey > Cc: dri-devel@lists.freedesktop.org; nouv...@lists.freedesktop.org; amd- > g...@lists.freedesktop.org; Deucher, Alexander; daniel.vet...@intel.com

Re: [PATCH 0/4] Allow ASYNC flip with atomic helpers.

Hi Andrey, Thank you for the patches. On Monday 16 Jan 2017 10:44:54 Andrey Grodzovsky wrote: > This series is a folow-up on > https://patchwork.kernel.org/patch/9501787/ > > The first patch makes changes to atomic helpers > to allow for drives with ASYNC flip support to use them. > Patches 2

Re: [PATCH] drm/armada: Include current dir on CFLAGS for armada trace

Hi Gustavo, Thank you for the patch. On Monday 16 Jan 2017 18:13:30 Gustavo Padovan wrote: > From: Gustavo Padovan > > Otherwise compilation fails like this: > > In file included from drivers/gpu/drm/armada/armada_trace.h:66:0, > from

Re: [PATCH] drm/exynos: use atomic helper commit

Hi Inki, Thank you for the patch. On Monday 16 Jan 2017 18:13:22 Inki Dae wrote: > This patch relpaces specific atomic commit function > with atomic helper commit one, which also includes > atomic_commit_tail callback for Exynos SoC becasue > crtc devices on Exynos SoC uses power domain device >

Re: [PATCH v1 1/7] dt-bindings: display: add STM32 LTDC driver

Hi Yannick, Thank you for the patch. On Monday 16 Jan 2017 14:28:58 Yannick Fertre wrote: > Signed-off-by: Yannick Fertre > --- > .../devicetree/bindings/display/st,ltdc.txt| 57 ++ > 1 file changed, 57 insertions(+) > create mode 100644

Re: [PATCH 1/4] drm/atomic: Save flip flags in drm_plane_state

Hi Andrey, 2017-01-16 Andrey Grodzovsky : > Allows using atomic flip helpers for drivers > using ASYNC flip. > Remove ASYNC_FLIP restriction in helpers and > caches the page flip flags in drm_plane_state > to be used in the low level drivers. > > Signed-off-by: Andrey

Re: [PATCH 5/5 v3] drm/bridge: adv7511: Reuse __adv7511_power_on/off() when probing EDID

On Mon, Jan 16, 2017 at 8:03 AM, Laurent Pinchart wrote: > Hi John, > > Thank you for the patch. > > On Tuesday 03 Jan 2017 11:41:42 John Stultz wrote: >> I've found that by just turning the chip on and off via the >> POWER_DOWN register, I end up getting

[PATCH] drm/armada: Include current dir on CFLAGS for armada trace

From: Gustavo Padovan Otherwise compilation fails like this: In file included from drivers/gpu/drm/armada/armada_trace.h:66:0, from drivers/gpu/drm/armada/armada_trace.c:3: ./include/trace/define_trace.h:88:43: fatal error: ./armada_trace.h: No

Re: [PATCH] drm: Clean up the 1366x768 fixup codes

On Mon, 16 Jan 2017 20:16:04 +0100, Gustavo Padovan wrote: > > Hi Takashi, > > 2017-01-16 Takashi Iwai : > > > This is just a cleanup, no functional change. > > > > The fixup code for 1366x768 in drm_mode_create_from_cmdline_mode() is > > basically a copy of the existing code in

Re: [PATCH 2/5 v3] drm/bridge: adv7511: Switch to using drm_kms_helper_hotplug_event()

On Mon, Jan 16, 2017 at 7:56 AM, Laurent Pinchart wrote: > On Monday 16 Jan 2017 17:47:46 Laurent Pinchart wrote: >> Hi John, >> >> Thank you for the patch. >> >> On Tuesday 03 Jan 2017 11:41:39 John Stultz wrote: >> > In chasing down a previous issue with EDID

Re: [PATCH] drm: Clean up the 1366x768 fixup codes

Hi Takashi, 2017-01-16 Takashi Iwai : > This is just a cleanup, no functional change. > > The fixup code for 1366x768 in drm_mode_create_from_cmdline_mode() is > basically a copy of the existing code in drm_edid.c. Make the latter > code public so that it can be called from the

Re: [PATCH] drm/exynos: use atomic helper commit

Hi Inki, 2017-01-16 Inki Dae : > This patch relpaces specific atomic commit function > with atomic helper commit one, which also includes > atomic_commit_tail callback for Exynos SoC becasue > crtc devices on Exynos SoC uses power domain device > so

[Bug 99310] Ubuntu 16.04/16.10 AMD Radeonsi - wrong colors (oibaf ppa) in XFCE and eog.

https://bugs.freedesktop.org/show_bug.cgi?id=99310 --- Comment #2 from baptiste.fa...@orange.fr --- Same problem with me : reddish icons and blue tint for jpegs. Using ubuntu 16.10 with mesa 13.0 (paolo dias package) and a amd r390. -- You are receiving this mail

  1   2   >