Re: [PULL] mxsfb fixes

On 16 February 2017 at 08:16, Marek Vasut wrote: > Hi, > > I collected the MXSFB fixes, based on top of airlied/drm-fixes: At this stage I'd rather not give these to Linus, can you rebase them onto drm-next, and resend, feel free to add stable cc's. Fixes like this should really

[git pull] drm fixes for v4.10-final

Hi Linus, Just two last minute fixes, one for DP MST oopses and one for a radeon regression. Dave. The following changes since commit 7089db84e356562f8ba737c29e472cc42d530dbc: Linux 4.10-rc8 (2017-02-12 13:03:20 -0800) are available in the git repository at:

Re: [PULL] drm-misc-next-fixes, take 2

On 16 February 2017 at 19:49, Jani Nikula wrote: > > Hi Dave, this one superseeds [1]. Better to flush out the single uapi > fix for v4.11 now so it's not forgotten. Looks like I had already pulled, I just reverted Maarten's patch on top of drm-next. Dave.

Re: [PATCH v3 3/3] drm/amdgpu: simplify reservation handling during buffer creation

On 2017年02月16日 20:08, Christian König wrote: Am 16.02.2017 um 12:39 schrieb Nicolai Hähnle: From: Nicolai Hähnle By using ttm_bo_init_reserved instead of the manual initialization of the reservation object, the reservation lock will be properly unlocked and

[Bug 99484] Crusader Kings 2 - Loading bars, siege bars, morale bars, etc. do not render correctly

https://bugs.freedesktop.org/show_bug.cgi?id=99484 --- Comment #7 from Timothy Arceri --- Bisected the llvm regression to a change in llvm 4.0 commit f991e38d156c4c10c609ca8425a7c31b951ecbed Author: James Molloy Date: Thu Sep 1 10:44:35 2016

Re: [Intel-gfx] [PATCH v3 7/8] drm: Connector helper function to release resources

Daniel Vetter schreef op di 14-02-2017 om 20:51 [+0100]: > On Mon, Feb 13, 2017 at 10:26 PM, Pandiyan, Dhinakaran > wrote: > > On Mon, 2017-02-13 at 09:05 +, Lankhorst, Maarten wrote: > > > Pandiyan, Dhinakaran schreef op do 09-02-2017 om 18:55 [+]: > > > >

Re: [PATCH] drm/ast: Support AST2500

On Thu, 2017-02-16 at 14:24 +1000, Dave Airlie wrote: > On 11 January 2017 at 12:57, Y.C. Chen > wrote: > > From: "Y.C. Chen" > > Please run checkpatch over this patch, it's got a lot of bad > whitespace issues > (4 space and 2 space indents,

Re: [PATCH] drm/ast: Fixed system hanged if disable P2A

On Thu, 2017-01-26 at 09:45 +0800, Y.C. Chen wrote: > From: "Y.C. Chen" > > The original ast driver will access some BMC configuration through > P2A bridge > that can be disabled since AST2300 and after. > It will cause system hanged if P2A bridge is disabled. > Here is

Re: [PATCH] drm/ast: Fixed system hanged if disable P2A

On Thu, 2017-02-16 at 06:34 +, YC Chen wrote: > Hi Ben, > This solution had been proved on x86 platform but I'm not sure if it > works or not on POWER system . It will only work on x86 platforms that haven't configured their PCI Express in "hardened" mode where PCIe errors cause machine

Re: [PATCH] drm/ast: Support AST2500

On Wed, 2017-01-11 at 10:57 +0800, Y.C. Chen wrote: > From: "Y.C. Chen" > > Signed-off-by: Y.C. Chen > --- >  drivers/gpu/drm/ast/ast_drv.h|   2 + >  drivers/gpu/drm/ast/ast_main.c   |  27 ++- >  drivers/gpu/drm/ast/ast_mode.c   |  25 +- >  

Re: [PATCH] gpu: ipu-v3: Stop overwriting pdev->dev.of_node of child devices

On 02/16/2017 07:42 AM, Philipp Zabel wrote: Setting dev->of_node changes the modalias and breaks module autoloading. Since there is an of_node field in the platform data passed to child devices, we don't even need this anymore. Suggested-by: Russell King

Re: [PATCH] gpu: ipu-v3: export ipu_csi_set_downsize

On 02/16/2017 03:40 AM, Philipp Zabel wrote: This function will be used by the media drivers and needs to be exported to allow them to be built as modules. Reported-by: Russell King Fixes: 867341b95891 ("gpu: ipu-v3: add ipu_csi_set_downsize") Signed-off-by: Philipp

[Bug 99136] Blood Effects Total War: Warhammer

https://bugs.freedesktop.org/show_bug.cgi?id=99136 Michel Dänzer changed: What|Removed |Added Attachment #129669|0 |1 is

[Bug 99843] Geometry Shader - Incorrect Output

https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #3 from Ilia Mirkin --- https://github.com/apitrace/apitrace This can be used to record (and replay) all the GL commands sent down to the driver. -- You are receiving this mail because: You are the assignee

[Bug 194579] AMDGPU: Possible size overflow detected by PaX in ttm_bo_handle_move_mem (drivers/gpu/drm/ttm/ttm_bo.c:388)

https://bugzilla.kernel.org/show_bug.cgi?id=194579 Nicolai Hähnle (nhaeh...@gmail.com) changed: What|Removed |Added CC||nhaeh...@gmail.com

[PATCH v2] drm: Add DPCD definitions for DP 1.4 DSC feature

Display stream compression is supported on DP 1.4 DP devices. This patch adds the corersponding DPCD register definitions for DSC. v2: * Rebased on drm-tip Signed-off-by: Manasi Navare Cc: Jani Nikula Cc: Paulo Zanoni

[Bug 194533] Invalid PCI ROM header signature: expecting 0xaa55, got 0x9125

https://bugzilla.kernel.org/show_bug.cgi?id=194533 nuc...@hotmail.com changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug 99843] Geometry Shader - Incorrect Output

https://bugs.freedesktop.org/show_bug.cgi?id=99843 --- Comment #2 from d...@jerber.co.uk --- I've just tried with multiple draw calls using the same VBO and it appears this does also cause the error. However, it appears there has to be 3 or more calls to cause the error (1 and 2 calls produce the

Re: [PATCH 1/9] drm/ast: Handle configuration without P2A bridge

On Fri, 2017-02-17 at 16:32 +1100, Benjamin Herrenschmidt wrote: Make this From: Russell Currey Git ate it when I amended (citool bug) and I forgot to fix it up. > The ast driver configures a window to enable access into BMC > memory space in order to read some

[PATCH 17/35] drivers/gpu: Convert remaining uses of pr_warning to pr_warn

To enable eventual removal of pr_warning This makes pr_warn use consistent for drivers/gpu Prior to this patch, there were 15 uses of pr_warning and 20 uses of pr_warn in drivers/gpu Signed-off-by: Joe Perches --- drivers/gpu/drm/amd/powerplay/hwmgr/smu7_hwmgr.c | 2 +-

[PATCH 7/9] drm/ast: Rename ast_init_dram_2300 to ast_post_chip_2300

The function does more than initializing the DRAM and in turns calls other functions to do the actual init. This will keeping things more consistent with the upcoming AST2500 POST code. Signed-off-by: Benjamin Herrenschmidt --- drivers/gpu/drm/ast/ast_post.c | 6 +++---

[PATCH 2/9] drm/ast: const'ify mode setting tables

And fix some comment alignment & space/tabs while at it Signed-off-by: Benjamin Herrenschmidt --- drivers/gpu/drm/ast/ast_drv.h| 4 +- drivers/gpu/drm/ast/ast_mode.c | 8 +-- drivers/gpu/drm/ast/ast_tables.h | 106 +++ 3

[PATCH 1/9] drm/ast: Handle configuration without P2A bridge

The ast driver configures a window to enable access into BMC memory space in order to read some configuration registers. If this window is disabled, which it can be from the BMC side, the ast driver can't function. Closing this window is a necessity for security if a machine's host side and BMC

[PATCH 6/9] drm/ast: Factor mmc_test code in POST code

There's a lot of duplication for what's essentially N copies of the same loop, so factor it. The upcoming AST2500 POST code adds more of this. Signed-off-by: Benjamin Herrenschmidt --- drivers/gpu/drm/ast/ast_post.c | 76 -- 1

[PATCH 5/9] drm/ast: Base support for AST2500

From: "Y.C. Chen" Add detection and mode setting updates for AST2500 generation chip, code originally from Aspeed and slightly reworked for coding style mostly by Ben. This doesn't contain the BMC DRAM POST code which is in a separate patch. Signed-off-by: Y.C. Chen

[PATCH 8/9] drm/ast: POST code for the new AST2500

From: "Y.C. Chen" This is used when the BMC isn't running any code and thus has to be initialized by the host. The code originates from Aspeed (Y.C. Chen) and has been cleaned up for coding style purposes by BenH. Signed-off-by: Y.C. Chen

[PATCH 4/9] drm/ast: Fix calculation of MCLK

Some braces were missing causing an incorrect calculation. Y.C. Chen from Aspeed provided me with the right formula which I tested on AST2400 and 2500. The MCLK isn't currently used by the driver (it will eventually to filter modes) so the issue isn't catastrophic. Also make the printed value a

[Bug 99136] Blood Effects Total War: Warhammer

https://bugs.freedesktop.org/show_bug.cgi?id=99136 siyia changed: What|Removed |Added Version|13.0|17.0 -- You are

Re: [PATCH v3 22/24] drm/rockchip: dw-mipi-dsi: support non-burst modes

On Thu, 16 Feb 2017 11:01:46 +0800, Chris Zhong wrote: > On 02/01/2017 03:22 AM, Sean Paul wrote: > > On Sun, Jan 29, 2017 at 01:24:42PM +, John Keeping wrote: > > > > Reviewed-by: Sean Paul > > > >> Signed-off-by: John Keeping > >> Reviewed-by:

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

Hello, I was wondering about the following. Wasn't there some strict requirement about code going upstream, which also included that there was a full open-source driver stack for it? I don't see how this is the case for Mali, neither in the kernel, nor in userspace. I'm aware that the Mali

[Bug 99136] Blood Effects Total War: Warhammer

https://bugs.freedesktop.org/show_bug.cgi?id=99136 --- Comment #28 from siyia --- Created attachment 129669 --> https://bugs.freedesktop.org/attachment.cgi?id=129669=edit apitrace of TW warhammer bug happens also with latest mesa stable independently of llvm version.

Re: [PATCH v3 23/24] drm/rockchip: dw-mipi-dsi: add reset control

On Thu, 16 Feb 2017 10:12:33 +0800, Chris Zhong wrote: > On 02/15/2017 08:39 PM, John Keeping wrote: > > On Wed, 15 Feb 2017 11:38:45 +0800, Chris Zhong wrote: > > > >> On 01/29/2017 09:24 PM, John Keeping wrote: > >>> In order to fully reset the state of the MIPI controller we must assert >

[GIT PULL] omapdrm fixes for v4.11

Hi Dave, Please pull these omapdrm fixes for v4.11. Tomi The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442: Merge branch 'drm-next-4.11' of git://people.freedesktop.org/~agd5f/linux into drm-next (2017-02-10 10:13:30 +1000) are available in the git repository at:

[Bug 99136] Blood Effects Total War: Warhammer

https://bugs.freedesktop.org/show_bug.cgi?id=99136 --- Comment #27 from siyia --- (In reply to Samuel Pitoiset from comment #26) > Can you upload the trace somewhere? will try -- You are receiving this mail because: You are the assignee for the

[PULL] drm-misc-next-fixes, take 2

Hi Dave, this one superseeds [1]. Better to flush out the single uapi fix for v4.11 now so it's not forgotten. BR, Jani. [1] 87mvdnpnix.fsf@intel.com">http://mid.mail-archive.com/87mvdnpnix.fsf@intel.com The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442: Merge

[patch] drm/msm/dsi: free first element on error

We want to free msm_host->bus_clks[0] so the > should be >=. Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus clocks from a list") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c b/drivers/gpu/drm/msm/dsi/dsi_host.c index

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

Op 17-01-17 om 02:27 schreef Laurent Pinchart: > 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 >> >>

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

Op 17-01-17 om 02:12 schreef Laurent Pinchart: > 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 >>

Re: [Intel-gfx] [PATCH v3 4/4] drm: Resurrect atomic rmfb code, v3

On Wed, 15 Feb 2017, Sinclair Yeh wrote: > On Wed, Feb 15, 2017 at 03:56:09PM +0200, Jani Nikula wrote: >> On Wed, 25 Jan 2017, Maarten Lankhorst >> wrote: >> > This was somehow lost between v3 and the merged version in Maarten's >> > patch

Re: [PATCH 2/2] drm/ast: Support AST2500

On Thu, 2017-02-16 at 20:09 +1100, Benjamin Herrenschmidt wrote: > From: "Y.C. Chen" > > Add detection and POST code for AST2500 generation chip, > code originally from Aspeed and slightly reworked for > coding style mostly by Ben. I just noticed there's still a bunch of

[PATCH v3 3/3] drm/amdgpu: simplify reservation handling during buffer creation

From: Nicolai Hähnle By using ttm_bo_init_reserved instead of the manual initialization of the reservation object, the reservation lock will be properly unlocked and destroyed when the TTM BO initialization fails. Actual deadlocks caused by the missing unlock should

[PATCH v3 1/3] drm/ttm: fix the documentation of ttm_bo_init

From: Nicolai Hähnle As the comment says: callers of ttm_bo_init cannot rely on having the only reference to the BO when the function returns successfully. Signed-off-by: Nicolai Hähnle --- include/drm/ttm/ttm_bo_api.h | 6 +- 1 file

[PATCH v3 2/3] drm/ttm: add ttm_bo_init_reserved

From: Nicolai Hähnle This variant of ttm_bo_init returns the validated buffer object with the reservation lock held when resv == NULL. This is convenient for callers that want to use the BO immediately, e.g. for initializing its contents. Signed-off-by: Nicolai Hähnle

[PATCH] gpu: ipu-v3: export ipu_csi_set_downsize

This function will be used by the media drivers and needs to be exported to allow them to be built as modules. Reported-by: Russell King Fixes: 867341b95891 ("gpu: ipu-v3: add ipu_csi_set_downsize") Signed-off-by: Philipp Zabel ---

Re: [patch v2] drm/msm/dsi: free first element on error

On Thu, 16 Feb 2017, Rob Clark wrote: > On Thu, Feb 16, 2017 at 7:00 AM, Dan Carpenter > wrote: >> We're off by one here. We free something that wasn't allocated and we >> don't free msm_host->bus_clks[]. >> >> Fixes: 6e0eb52eba9e ("drm/msm/dsi:

Re: [patch] drm/msm/dsi: free first element on error

On Thu, 16 Feb 2017, walter harms wrote: > Am 16.02.2017 12:53, schrieb Dan Carpenter: >> On Thu, Feb 16, 2017 at 01:27:47PM +0200, Jani Nikula wrote: >>> On Thu, 16 Feb 2017, Dan Carpenter wrote: We want to free msm_host->bus_clks[0] so the > should

[PATCH 1/3] drm: move edid property update and add modes out of edid firmware loader

Make the firmware loader more generic and generally useful. Signed-off-by: Jani Nikula --- drivers/gpu/drm/drm_edid_load.c| 17 - drivers/gpu/drm/drm_probe_helper.c | 8 +++- include/drm/drm_edid.h | 7 --- 3 files changed, 15

[PATCH 0/3] drm: handle override/firmware edid at the lowest level

This is a simplified version of the perhaps too ambitious RFC [1]. Here we simply handle debugfs override edid and the firmware edid at the drm_do_get_edid() level, not at the probe helper level. With this, everything from EDID gets transparently overridden. BR, Jani. [1]

[PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

Handle debugfs override edid and firmware edid at the low level to transparently and completely replace the real edid. Previously, we practically only used the modes from the override EDID, and none of the other data. This also prevents actual EDID reads when the EDID is to be overridden, but

[PATCH] drm/msm/dsi: Fix bug in dsi_mgr_phy_enable

A recent commit introduces a bug in dsi_mgr_phy_enable. In the non dual DSI mode, we reset the mdsi (master DSI) PHY. This isn't right since master and slave DSI exist only in dual DSI mode. For the normal mode of operation, we should simply reset the PHY of the DSI device (i.e. msm_dsi)

[PATCH 2/2] drm/ast: Support AST2500

From: "Y.C. Chen" Add detection and POST code for AST2500 generation chip, code originally from Aspeed and slightly reworked for coding style mostly by Ben. Signed-off-by: Y.C. Chen Signed-off-by: Benjamin Herrenschmidt

Re: [PATCH v2] drm/omapdrm: dispc: Refuse x-decimation above 4 for all but 8-bit formats

On 08/02/17 16:08, Jyri Sarha wrote: > Let's disable all scaling that requires horizontal decimation with > higher factor than 4, until we have better estimates of what we can > and can not do. However, NV12 color format appears to work Ok with > all decimation factors. > > When decimating

[PATCH 1/2] drm/ast: Support reading configuration values

From: Russell Currey The ast driver configures a window to enable access into BMC memory space in order to read some configuration registers. If this window is disabled, which it can be from the BMC side, the ast driver can't function. Closing this window is a necessity for

Re: [Intel-gfx] [PATCH v3 4/4] drm: Resurrect atomic rmfb code, v3

Op 16-02-17 om 10:45 schreef Jani Nikula: > On Wed, 15 Feb 2017, Sinclair Yeh wrote: >> On Wed, Feb 15, 2017 at 03:56:09PM +0200, Jani Nikula wrote: >>> On Wed, 25 Jan 2017, Maarten Lankhorst >>> wrote: This was somehow lost between v3

Re: [patch] drm/msm/dsi: free first element on error

On Thu, 16 Feb 2017, Dan Carpenter wrote: > We want to free msm_host->bus_clks[0] so the > should be >=. > > Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus clocks from a list") > Signed-off-by: Dan Carpenter > > diff --git

Re: [PATCH v3 3/3] drm/amdgpu: simplify reservation handling during buffer creation

Am 16.02.2017 um 12:39 schrieb Nicolai Hähnle: From: Nicolai Hähnle By using ttm_bo_init_reserved instead of the manual initialization of the reservation object, the reservation lock will be properly unlocked and destroyed when the TTM BO initialization fails. Actual

Re: [PATCH v2 3/3] drm/amdgpu: fix lock cleanup during buffer creation

On 16.02.2017 02:00, Michel Dänzer wrote: On 16/02/17 04:10 AM, Nicolai Hähnle wrote: From: Nicolai Hähnle Open-code the initial ttm_bo_validate call, so that we can properly unlock the reservation lock when it fails. Also, properly destruct the reservation object

[patch v2] drm/msm/dsi: free first element on error

We're off by one here. We free something that wasn't allocated and we don't free msm_host->bus_clks[]. Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus clocks from a list") Signed-off-by: Dan Carpenter diff --git a/drivers/gpu/drm/msm/dsi/dsi_host.c

[PATCH] drm/ast: Fix mclk calculation

The very large values observed were the result of a bug in the calculation. Y.C. Chen gave me the right formula so here is a patch fixing it. Thankfully nothing seem to use that unless you try to POST the chip. Signed-off-by: Benjamin Herrenschmidt -- diff --git

[PATCH 3/3] drm: handle override edid and firmware adid at drm_do_get_edid()

Handle override edid and firmware edid at the low level to transparently and completely replace the real edid. This also prevents actual edid reads for them, but retains ddc probe. FIXME: validate override edid, deduplicate firmware edid validation. Signed-off-by: Jani Nikula

[PATCH 2/3] drm: reset ELD if NULL edid is passed to drm_edid_to_eld

Make the function useful for resetting, not just setting, the ELD. Signed-off-by: Jani Nikula --- drivers/gpu/drm/drm_edid.c | 3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c index 24e7b282f16c..362036360724

Re: [patch] drm/msm/dsi: free first element on error

Am 16.02.2017 12:53, schrieb Dan Carpenter: > On Thu, Feb 16, 2017 at 01:27:47PM +0200, Jani Nikula wrote: >> On Thu, 16 Feb 2017, Dan Carpenter wrote: >>> We want to free msm_host->bus_clks[0] so the > should be >=. >>> >>> Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus

[Bug 194559] amdgpu problems loading 2 firmwares on multi-smp system

https://bugzilla.kernel.org/show_bug.cgi?id=194559 --- Comment #9 from Janpieter Sollie (janpieter.sol...@dommel.be) --- additional comment: works on 4.10-rc8, so necessary patch is already integrated thank you kernel developers! -- You are receiving this mail because: You are watching the

Re: [PULL] drm-misc-next-fixes

On Wed, 15 Feb 2017, Jani Nikula wrote: > Hi Dave, a couple of drm core fixes for the v4.11 merge window. Dave, stop the press, please don't pull this one. Turns out Maarten's commit regresses. Sorry, Jani. > > BR, > Jani. > > The following changes since commit

Re: i915: Dealing with 90° rotated display ?

Hi, On 15-02-17 15:59, Ville Syrjälä wrote: On Wed, Feb 15, 2017 at 03:54:17PM +0100, Hans de Goede wrote: Hi Jani, As discussed here: https://bugs.freedesktop.org/show_bug.cgi?id=94894 I've a mini-laptop which uses a phone-screen, so the native orientation of the screen is portrait, where

Re: [PATCH 3/3] drm: handle override edid and firmware adid at drm_do_get_edid()

On Thu, 16 Feb 2017, Jani Nikula wrote: > Handle override edid and firmware edid at the low level to transparently > and completely replace the real edid. This also prevents actual edid > reads for them, but retains ddc probe. Please ignore this stray patch, and look at

Re: [patch] drm/msm/dsi: free first element on error

On Thu, Feb 16, 2017 at 01:27:47PM +0200, Jani Nikula wrote: > On Thu, 16 Feb 2017, Dan Carpenter wrote: > > We want to free msm_host->bus_clks[0] so the > should be >=. > > > > Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus clocks from a list") > > Signed-off-by: Dan

Re: [patch] drm/msm/dsi: free first element on error

On Thu, Feb 16, 2017 at 7:03 AM, walter harms wrote: > > > Am 16.02.2017 12:53, schrieb Dan Carpenter: >> On Thu, Feb 16, 2017 at 01:27:47PM +0200, Jani Nikula wrote: >>> On Thu, 16 Feb 2017, Dan Carpenter wrote: We want to free msm_host->bus_clks[0]

Re: [patch v2] drm/msm/dsi: free first element on error

On Thu, Feb 16, 2017 at 7:00 AM, Dan Carpenter wrote: > We're off by one here. We free something that wasn't allocated and we > don't free msm_host->bus_clks[]. > > Fixes: 6e0eb52eba9e ("drm/msm/dsi: Parse bus clocks from a list") > Signed-off-by: Dan Carpenter

Re: [PATCH] drm/msm/dsi: Fix bug in dsi_mgr_phy_enable

On Thu, Feb 16, 2017 at 5:59 AM, Archit Taneja wrote: > A recent commit introduces a bug in dsi_mgr_phy_enable. In the non > dual DSI mode, we reset the mdsi (master DSI) PHY. This isn't right > since master and slave DSI exist only in dual DSI mode. For the normal > mode

Re: [PATCH v2 1/2] drm/cma-helper: Add multi buffer support for cma fbdev

Hello, I'm not sure if I'm missing something here, but I don't see how this is supposed to work. This just multiplies the height of the drm_mode_fb_cmd2 object with the number of buffers. Let's say I have width=1024, height=768, then now I have a framebuffer which has height=2304 (in the

[PATCH v4 4/5] drm/atomic: Convert get_existing_state callers to get_old/new_state, v3.

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 drm_atomic_helper_update_legacy_modeset_state. Changes since v2: - Use the correct state in

[PATCH v4 1/5] drm/atomic: Fix atomic helpers to use the new iterator macros, v2.

There are new iterator macros that annotate whether the new or old state should be used. This is better than using a state that depends on whether it's called before or after swap. For clarity, also rename the variables from $obj_state to (old,new)_$obj_state as well. Changes since v1: - Use

[PATCH] gpu: ipu-v3: Stop overwriting pdev->dev.of_node of child devices

Setting dev->of_node changes the modalias and breaks module autoloading. Since there is an of_node field in the platform data passed to child devices, we don't even need this anymore. Suggested-by: Russell King Signed-off-by: Philipp Zabel ---

Re: [PATCH 2/3] drm: reset ELD if NULL edid is passed to drm_edid_to_eld

On Thu, Feb 16, 2017 at 12:36:43PM +0200, Jani Nikula wrote: > Make the function useful for resetting, not just setting, the ELD. > > Signed-off-by: Jani Nikula > --- > drivers/gpu/drm/drm_edid.c | 3 +++ > 1 file changed, 3 insertions(+) > > diff --git

[PATCH v4 2/5] drm/atomic: Make drm_atomic_plane_disabling easier to understand.

This function becomes a lot simpler when having passed both the old and new state to it. Looking at all callers, it seems that old_plane_state is never NULL so the check can be dropped. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic_helper.c |

[PATCH v4 5/5] drm/blend: Use new atomic iterator macros.

There are new iterator macros that annotate whether the new or old state should be used. This is better than using a state that depends on whether it's called before or after swap. For clarity, also rename the variables from $obj_state to (old,new)_$obj_state as well. Signed-off-by: Maarten

[PATCH v4 0/5] drm/atomic: Add accessor macros for all atomic state.

Fifth 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 state. Use drm_atomic_get_(existing_)obj_state, which can refer to new or old state. Use

[PATCH v4 3/5] drm/atomic: Add macros to access existing old/new state, v2.

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. The calls to drm_atomic_get_existing_$obj_state should no longer be used, and converted over to these new calls.

Re: [PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

On Thu, Feb 16, 2017 at 12:36:45PM +0200, Jani Nikula wrote: > Handle debugfs override edid and firmware edid at the low level to > transparently and completely replace the real edid. Previously, we > practically only used the modes from the override EDID, and none of the > other data. This also

Re: [PATCH] drm/virtio: call drm_plane_cleanup() at destroy phase

On Mi, 2017-02-15 at 16:00 -0200, Gustavo Padovan wrote: > From: Gustavo Padovan > > virtio was missing this call to clean up core plane usage. > > Signed-off-by: Gustavo Padovan > --- > drivers/gpu/drm/virtio/virtgpu_plane.c |

Re: [PATCH] drm/amdgpu: fix warning on older gcc releases

On Fri, Feb 3, 2017 at 11:47 AM, Arnd Bergmann wrote: > gcc-4.8 warns about '{0}' being used an an initializer for nested structures: > > drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c: In function > ‘gfx_v8_0_ring_emit_ce_meta_init’: > drivers/gpu/drm/amd/amdgpu/gfx_v8_0.c:7263:2:

Re: [PATCH v3 0/2] drm: Support framebuffer panning

On 02/15/2017 05:19 PM, Maxime Ripard wrote: > Hi, > > This is a respin of the previous serie called "Support fast framebuffer > panning for i.MX6" made by Stefan 6 monthes ago. The imx6 bits have been > removed, and the comments that were made at that time fixed (hopefully). > > Let me know

Re: [PATCH 0/8] ARM: sun8i: a33: Mali improvements

On 16 February 2017 at 12:43, Tobias Jakobi wrote: > Hello, > > I was wondering about the following. Wasn't there some strict > requirement about code going upstream, which also included that there > was a full open-source driver stack for it? > > I don't see how

Re: [PATCH 2/2] drm/ast: Support AST2500

On 16 February 2017 at 09:09, Benjamin Herrenschmidt wrote: > From: "Y.C. Chen" > > Add detection and POST code for AST2500 generation chip, > code originally from Aspeed and slightly reworked for > coding style mostly by Ben. > > Signed-off-by:

[pull] radeon drm-fixes-4.10

Hi Dave, Just one regression fix interlaced modes on radeon. The following changes since commit 697d3a21615672b2bf7724a65755799260325dda: Merge tag 'drm-intel-fixes-2017-02-09' of git://anongit.freedesktop.org/git/drm-intel into drm-fixes (2017-02-10 10:14:24 +1000) are available in the

[PATCH] drm: Always prepare null framebuffer in transitional helper

Despite the documentation claim that cleanup_fb will match prior calls to prepare_fb, in case of NULL framebuffers in the transitional helpers, the code will skip the call to prepare_fb but not the corresponding cleanup_fb call. This asymmetry in semantics is unnecessarily surprising for

[pull] amdgpu drm-next-4.11

Hi Dave, Fixes for 4.11. Highlights: - fix >2 displays on asics with 3 or 5 crtcs - fix SI headless asics - powerplay fixes for new polaris variants - misc fixes The following changes since commit 13f62f54d174d3417c3caaafedf5e22a0a03e442: Merge branch 'drm-next-4.11' of

[Bug 99780] Flickering artifacts in radeonsi driver with divergent texture reads.

https://bugs.freedesktop.org/show_bug.cgi?id=99780 --- Comment #12 from Matias N. Goldberg --- I can confirm applying the patch you uploaded (plus LLVM's patch of course) fixes the problem. Thank you. -- You are receiving this mail because: You are the assignee for

Re: [PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

On Thu, 16 Feb 2017, Ville Syrjälä wrote: > On Thu, Feb 16, 2017 at 12:36:45PM +0200, Jani Nikula wrote: >> Handle debugfs override edid and firmware edid at the low level to >> transparently and completely replace the real edid. Previously, we >> practically only

Re: [PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

On Thu, Feb 16, 2017 at 07:54:00PM +0200, Jani Nikula wrote: > On Thu, 16 Feb 2017, Ville Syrjälä wrote: > > On Thu, Feb 16, 2017 at 12:36:45PM +0200, Jani Nikula wrote: > >> Handle debugfs override edid and firmware edid at the low level to > >> transparently and

Re: [PATCH v3 12/12] drm/i915: Listen for PMIC bus access notifications

On Fri, Feb 10, 2017 at 11:28:02AM +0100, Hans de Goede wrote: > Listen for PMIC bus access notifications and get FORCEWAKE_ALL while > the bus is accessed to avoid needing to do any forcewakes, which need > PMIC bus access, while the PMIC bus is busy: > > This fixes errors like these showing up

[Bug 99843] Geometry Shader - Incorrect Output

https://bugs.freedesktop.org/show_bug.cgi?id=99843 Bug ID: 99843 Summary: Geometry Shader - Incorrect Output Product: Mesa Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

[Bug 97879] [amdgpu] Rocket League: long hangs (several seconds) when loading assets (models/textures/shaders?)

https://bugs.freedesktop.org/show_bug.cgi?id=97879 --- Comment #92 from libgra...@gmail.com --- Working great here now guys - latest RL build and Mesa git. Thanks to all involved - great cooperation :) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC

[Bug 99780] Flickering artifacts in radeonsi driver with divergent texture reads.

https://bugs.freedesktop.org/show_bug.cgi?id=99780 --- Comment #11 from Nicolai Hähnle --- Created attachment 129675 --> https://bugs.freedesktop.org/attachment.cgi?id=129675=edit Mesa patch Yes, you need this patch for Mesa as well. I'm going to pick up the LLVM patch

Re: i915: Dealing with 90° rotated display ?

On Thu, Feb 16, 2017 at 11:01:29AM +0100, Hans de Goede wrote: > Hi, > > On 15-02-17 15:59, Ville Syrjälä wrote: > > On Wed, Feb 15, 2017 at 03:54:17PM +0100, Hans de Goede wrote: > >> Hi Jani, > >> > >> As discussed here: > >> > >> https://bugs.freedesktop.org/show_bug.cgi?id=94894 > >> > >>

Re: [PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

On Thu, 16 Feb 2017, Ville Syrjälä wrote: > On Thu, Feb 16, 2017 at 07:54:00PM +0200, Jani Nikula wrote: >> On Thu, 16 Feb 2017, Ville Syrjälä wrote: >> > On Thu, Feb 16, 2017 at 12:36:45PM +0200, Jani Nikula wrote: >> >> Handle

Re: [PATCH v3 12/12] drm/i915: Listen for PMIC bus access notifications

On Thu, 16 Feb 2017, Ville Syrjälä wrote: > On Fri, Feb 10, 2017 at 11:28:02AM +0100, Hans de Goede wrote: >> Listen for PMIC bus access notifications and get FORCEWAKE_ALL while >> the bus is accessed to avoid needing to do any forcewakes, which need >> PMIC bus

Re: [PATCH 3/3] drm: handle override edid and firmware EDID at drm_do_get_edid() level

On Thu, Feb 16, 2017 at 08:59:13PM +0200, Jani Nikula wrote: > On Thu, 16 Feb 2017, Ville Syrjälä wrote: > > On Thu, Feb 16, 2017 at 07:54:00PM +0200, Jani Nikula wrote: > >> On Thu, 16 Feb 2017, Ville Syrjälä wrote: > >> > On Thu,

Re: [PATCH 2/2] drm/ast: Support AST2500

On Thu, 2017-02-16 at 17:33 +, Emil Velikov wrote: > On 16 February 2017 at 09:09, Benjamin Herrenschmidt > wrote: > > From: "Y.C. Chen" > > > > Add detection and POST code for AST2500 generation chip, > > code originally from Aspeed and

  1   2   >