[PATCH v4 0/3] gpu: drm: exynos_hdmi: Code refactoring on hdmi ddc and phy

Hi, Thanks for your contribution. Seems good to me. Will picked them up soon if no critical issues. Thanks, Inki Dae 2016-08-31 15:14 GMT+09:00 Milo Kim : > v4: > Only DRM patchset is sent, DTS patch was sent separately. > > Milo Kim (3): > gpu: drm: exynos_hdmi: Move DDC logic into

[GIT PULL] exynos-drm-fixes

Hi Dave, Just fixup to runtime pm usage and some cleanups. Please kindly let me know if there is any problem. Ps. We will request git-pull for -next soon if no critical issue, which includes only code refactoring on hdmi ddc and phy. Thanks, Inki Dae The following changes

[drm-exynos:exynos-drm-fixes 6/6] drivers/gpu/drm/exynos/exynos_drm_gsc.c:1763:0: error: unterminated #ifdef

0 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/a15eff4b/attachment-0001.gz>

[Bug 96449] Dying Light reports OpenGL version 3.0 with mesa-git

https://bugs.freedesktop.org/show_bug.cgi?id=96449 --- Comment #7 from Adam Bolte --- MESA_GL_VERSION_OVERRIDE=3.3COMPAT does not work for me. Jan, did it work for you? All I get is either a crash (after the loading screen), or a blank screen with sound playing in the background. The warning

[Bug 97856] Computer restart playing 3D games (possibly overheating)

https://bugs.freedesktop.org/show_bug.cgi?id=97856 Bug ID: 97856 Summary: Computer restart playing 3D games (possibly overheating) Product: DRI Version: XOrg git Hardware: Other OS: All Status:

[Bug 97856] Computer restart playing 3D games (possibly overheating)

https://bugs.freedesktop.org/show_bug.cgi?id=97856 --- Comment #1 from Alex Henry --- Forgot to mention, if relevant: the fglrx driver I'm using on my alternate system is from the AMD website, not from the Debian repositories. The installer file is named

[PATCH v8 9/9] drm/mediatek: add support for Mediatek SoC MT2701

Hi, YT: On Mon, 2016-09-12 at 20:01 +0800, YT Shen wrote: > This patch add support for the Mediatek MT2701 DISP subsystem. > There is only one OVL engine in MT2701. > > Signed-off-by: YT Shen > --- > drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 6 ++ >

[GIT PULL] exynos-drm-fixes

Hi Dave, There was my mistake reported below when I merged one fixup manually. http://www.spinics.net/lists/dri-devel/msg118283.html Fixed. Thanks, Inki Dae 2016년 09월 18일 23:12에 Inki Dae 이(가) 쓴 글: > Hi Dave, > >Just fixup to runtime pm usage and some cleanups. > >

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

L: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/30c21a9b/attachment.html>

[PATCH] drm/rockchip: Cleanup dangling devm pointers

Hi Sean, On Sat, Sep 17, 2016 at 2:22 AM, Sean Paul wrote: > > Instead of assigning device managed resources to local variables, > keep track of them in the vop struct. Why this patch? Is it fixing an issue? Or, is it preparing for some future use of ahb_rst outside of vop_initial? I thought

[PATCH] drm/rockchip: Balance irq refcount on failure

On Sat, Sep 17, 2016 at 2:22 AM, Sean Paul wrote: > If create_crtc fails in vop bind, ensure the irq refcount is zeroed > back out before exiting. > > Signed-off-by: Sean Paul Reviewed-by: Daniel Kurtz > --- > drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 6 +- > 1 file changed, 5

[PATCH -next] drm/i915: Fix non static symbol warning

On Sat, 17 Sep 2016, Wei Yongjun wrote: > From: Wei Yongjun > > Fixes the following sparse warning: > > drivers/gpu/drm/i915/intel_dp.c:1527:5: warning: > symbol 'intel_dp_compute_bpp' was not declared. Should it be static? > > Signed-off-by: Wei Yongjun > --- >

[PATCH] drm/udl: Fix for the X server screen update

On 18.09.2016 19:42, Noralf Trønnes wrote: > > Den 18.09.2016 15:48, skrev poma: >> Fix for DisplayLink GPU USB2.0 device X server screen update >> >> Within X server on top of DisplayLink GPU USB2.0 device, >> screen content is not refreshed i.e. updated, >> which is the most basic

[PATCH v6] drm: bridge/dw_hdmi: add dw hdmi i2c bus adapter support

Am Freitag, den 16.09.2016, 20:38 +0300 schrieb Vladimir Zapolskiy: > Hi Philipp, [...] > >> as far as I know David accepts pull requests from you, can you please > >> create and send a pull request for v4.9 containing these changes? > >> > >> https://patchwork.kernel.org/patch/9284717/ --

[PULL] topic/drm-misc

Hi Dave, Just random misc stuff that Sean/Sumit picked up while I relaxed. Well except for one commit: commit a988588b1806b40ae115fe1c9ab38706fd1a7c2b Author: Kristian H. Kristensen Date: Tue Sep 13 14:20:45 2016 -0700 drm: Only use compat ioctl for addfb2 on X86/IA64 Pls also

[GIT PULL] bridge/dw-hdmi: I2C master controller support

Hi Dave, this tag contains support for the I2C master controller contained in the HDMI TX IP core, for those boards that don't allow to mux their DDC pins to SoC I2C controllers. This will make the dw-hdmi driver register its internal I2C master if the ddc-i2c-bus property is not set on the

[PATCH v4 0/7] drm/imx: Add active plane reconfiguration support

On Wed, Sep 14, 2016 at 1:05 PM, Philipp Zabel wrote: > Hi Dave, > > Am Montag, den 29.08.2016, 17:44 +0200 schrieb Daniel Vetter: >> On Mon, Aug 29, 2016 at 4:59 PM, Philipp Zabel >> wrote: >> > Am Montag, den 29.08.2016, 12:53 +0200 schrieb Philipp Zabel: >> >> Am Freitag, den 26.08.2016,

[PATCH 0/3] ARM: dts: am335x-* Add blue-and-red-wiring propery to lcdc nodes

On 09/16/16 18:02, Tony Lindgren wrote: > * Jyri Sarha [160916 04:50]: >> > These patches complete the am335x LCDC color errata fix[1]. The >> > functional patches are now queued for v4.9. >> > >> > The patch for am335x-boneblack.dts is delayed until v4.10 or v4.9-rc >> > phase to avoid

[GIT PULL] imx-drm fixes, cleanups, image conversion

Hi Dave, please consider merging this tag containing the latest active plane reconfiguration patches, several fixes and cleanups, and image conversion support for the V4L2 drivers to build upon. The active plane reconfiguration patch (v4) will conflict with the v2 patch that already went into

[PATCH] drm/amd/powerplay/smumgr: mark symbols static where possible

On Monday, September 19, 2016 3:28:39 PM CEST Baoyou Xie wrote: > We get a few warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/tonga_smumgr.c:146:5: warning: > no previous prototype for 'tonga_program_jump_on_start' [-Wmissing-prototypes] >

[GIT PULL] imx-drm fixes, cleanups, image conversion

On 19 September 2016 at 17:31, Philipp Zabel wrote: > Hi Dave, > > please consider merging this tag containing the latest active plane > reconfiguration patches, several fixes and cleanups, and image > conversion support for the V4L2 drivers to build upon. > > The active plane reconfiguration

[PATCH 1/3] ARM: dts: am335x-evm: Add blue-and-red-wiring -property to lcdc node

On 09/17/16 01:17, Nishanth Menon wrote: > On 09/16/2016 06:50 AM, Jyri Sarha wrote: > [..] >> +blue-and-red-wiring = "crossed"; > > Dumb question: Why is this a Linux generic property - does it make sense > to have "blue-and-red-wiring" as a Linux generic property? I mean, it > reminds me

[PATCH] drm/amd/powerplay/smumgr: mark symbols static where possible

Am 19.09.2016 um 09:34 schrieb Arnd Bergmann: > On Monday, September 19, 2016 3:28:39 PM CEST Baoyou Xie wrote: >> We get a few warnings when building kernel with W=1: >> drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/tonga_smumgr.c:146:5: >> warning: no previous prototype for

[PATCH] drm/amd/powerplay/smumgr: mark symbols static where possible

On Monday, September 19, 2016 9:59:56 AM CEST Christian König wrote: > Am 19.09.2016 um 09:34 schrieb Arnd Bergmann: > > On Monday, September 19, 2016 3:28:39 PM CEST Baoyou Xie wrote: > >> We get a few warnings when building kernel with W=1: > >>

[PATCH] drm/amd/powerplay/smumgr: mark symbols static where possible

Hi Baoyou, On Mon, Sep 19, 2016 at 03:28:39PM +0800, Baoyou Xie wrote: > We get a few warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/../powerplay/smumgr/tonga_smumgr.c:146:5: warning: > no previous prototype for 'tonga_program_jump_on_start' [-Wmissing-prototypes] >

[GIT PULL] imx-drm fixes, cleanups, image conversion

Am Montag, den 19.09.2016, 17:37 +1000 schrieb Dave Airlie: > On 19 September 2016 at 17:31, Philipp Zabel > wrote: > > Hi Dave, > > > > please consider merging this tag containing the latest active plane > > reconfiguration patches, several fixes and cleanups, and image > > conversion support

[git pull] drm fixes for 4.8

On Mon, 19 Sep 2016, Dave Airlie wrote: > Hi Linus, > > One important drm 32/64 ABI fix came in so I'll dequeue what I have, the rest > is > just exynos runtime pm fixes, but the net removal of code seems like a > win to me. > > I'm going to be sporadic this week due to school holidays, so if

[PULL] drm-intel-next

at: git://anongit.freedesktop.org/drm-intel tags/drm-intel-next-2016-09-19 for you to fetch changes up to 6e05f3d3b9298a56d6f1acb474a75cf14a17c31e: drm/i915: Update DRIVER_DATE to 20160919 (2016-09-19 09:26:08 +0200) - refactor

[git pull] drm fixes for 4.8

On Mon, 19 Sep 2016, Jani Nikula wrote: > On Mon, 19 Sep 2016, Dave Airlie wrote: >> Hi Linus, >> >> One important drm 32/64 ABI fix came in so I'll dequeue what I have, the >> rest is >> just exynos runtime pm fixes, but the net removal of code seems like a >> win to me. >> >> I'm going to be

[PATCH v3 1/4] drm/bridge: Add RGB to VGA bridge support

be feasible to combine the two, and support both devices > with a single driver ? I don't see why not. But converting the renesas DRM driver seems a bit out of scope, and the ADV compatible can definitely be added later. Maxime -- Maxime Ripard, Free Electrons Embedded Linux and Kernel engineering http://free-electrons.com -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/22fa2cec/attachment-0001.sig>

[PATCH] drm/amdgpu: add missing header dependencies

Am 18.09.2016 um 15:12 schrieb Baoyou Xie: > We get 6 warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/dce_v8_0.c:629:6: warning: no previous prototype > for 'dce_v8_0_disable_dce' [-Wmissing-prototypes] > drivers/gpu/drm/amd/amdgpu/dce_v10_0.c:730:6: warning: no previous

[PATCH] drm/amdgpu: amend amdgpu_gfx_parse_disable_cu() declaration

Am 18.09.2016 um 15:37 schrieb Baoyou Xie: > In amdgpu_gfx.h, the declaration of amdgpu_gfx_parse_disable_cu() > is incorrect. > > Signed-off-by: Baoyou Xie Ups, nice catch. Patch is Reviewed-by: Christian König . Regards, Christian. > --- > drivers/gpu/drm/amd/amdgpu/amdgpu_gfx.c | 4 +++-

[PATCH] drm/amdgpu: mark symbols static where possible

Am 18.09.2016 um 16:09 schrieb Baoyou Xie: > We get 7 warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/amdgpu_device.c:1990:5: warning: no previous > prototype for 'amdgpu_pre_soft_reset' [-Wmissing-prototypes] > drivers/gpu/drm/amd/amdgpu/amdgpu_connectors.c:1548:5: warning:

[Bug 97806] GPU lockup with mesa-git and llvm-svn with rx 470 on Unigine Heaven and TombRaider 2013

3c494a57e2ee9] [AMDGPU] Refactor MUBUF/MTBUF instructions -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/e58dbf67/attachment.html>

[PATCH] drm/amdgpu: remove unused functions

Am 18.09.2016 um 16:13 schrieb Baoyou Xie: > We get 2 warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/amdgpu_amdkfd.c:146:5: warning: no previous > prototype for 'pool_to_domain' [-Wmissing-prototypes] > drivers/gpu/drm/amd/amdgpu/cz_smc.c:104:5: warning: no previous

[PATCH] drm/amdgpu: add function declaration in amdgpu.h

Am 18.09.2016 um 16:29 schrieb Baoyou Xie: > We get 2 warnings when building kernel with W=1: > drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c:502:10: warning: no previous prototype > for 'init_cond_exec' [-Wmissing-prototypes] > drivers/gpu/drm/amd/amdgpu/sdma_v3_0.c:514:6: warning: no previous

[Bug 96449] Dying Light reports OpenGL version 3.0 with mesa-git

he assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/d25f8ab5/attachment.html>

[PATCH 4/6] drm: provide management functions for drm_file

On Thu, Sep 01, 2016 at 02:48:35PM +0200, David Herrmann wrote: > Rather than doing drm_file allocation/destruction right in the fops, lets > provide separate helpers. This decouples drm_file management from the > still-mandatory drm-fops. It prepares for use of drm_file without the > fops, both

[PATCH 0/6] DRM Core Cleanups

On Thu, Sep 01, 2016 at 02:48:31PM +0200, David Herrmann wrote: > Hey > > The remaining cleanup patches pending on dri-devel in one batch. Random > cleanups > all over the place. Should all be straightforward. Except for patch 4 all applied to drm-misc, thanks. -Daniel > > Thanks > David > >

[PATCH 0/6] DRM Core Cleanups

On Mon, Sep 19, 2016 at 01:56:56PM +0200, Daniel Vetter wrote: > On Thu, Sep 01, 2016 at 02:48:31PM +0200, David Herrmann wrote: > > Hey > > > > The remaining cleanup patches pending on dri-devel in one batch. Random > > cleanups > > all over the place. Should all be straightforward. > > Except

[PATCH v3 01/20] drm: omapdrm: fb: Limit number of planes per framebuffer to two

The only multi-planar format supported by the driver is NV12, there will thus never be more than two planes per framebuffer. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_fb.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH v3 00/20] OMAP DRM fixes and improvements

Hello, Here's the third version of my current stack of pending patches for the omapdrm driver. All comments received for v2 have been considered and patches updated where applicable. Changes since v2 include - Rebased on top of Dave's latest drm-next branch - Replaced "drm: omapdrm: Use atomic

[PATCH v3 02/20] drm: omapdrm: fb: Use format information provided by the DRM core

The driver stores in a custom structure named format several pieces of information about the format that are available in the DRM core. Remove them and get the information from the DRM core instead. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_fb.c | 91

[PATCH v3 05/20] drm: omapdrm: fb: Turn framebuffer creation error messages into debug

Don't print userspace parameters validation failures as error messages to avoid giving userspace the ability to flood the kernel log. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_fb.c | 12 ++-- 1 file changed, 6 insertions(+), 6

[PATCH v3 06/20] drm: omapdrm: Handle FIFO underflow IRQs internally

As the FIFO underflow IRQ handler just prints an error message to the kernel log, simplify the code by not registering one IRQ handler per plane but print the messages directly from the main IRQ handler. Signed-off-by: Laurent Pinchart --- Changes since v1: - Only register error IRQs that exist

[PATCH v3 11/20] drm: omapdrm: Check DSS manager state in the enable/disable helpers

The omapdrm DSS manager enable/disable operations check the DSS manager state to avoid double enabling/disabling. Move that code to the DSS manager to decrease the dependency of the DRM layer to the DSS layer. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/dss/dispc.c | 1 -

[PATCH v3 10/20] drm: omapdrm: Only commit planes on active CRTCs

The DRM core supports skipping plane update for inactive CRTCs for hardware that don't need it or can't cope with it. That's our case, so use the DRM core infrastructure instead of reinventing it. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_crtc.c | 8 +++-

[PATCH v3 13/20] drm: omapdrm: Use a spinlock to protect the CRTC pending flag

The flag will need to be accessed atomically in the vblank interrupt handler, memory barriers won't be enough. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_crtc.c | 28 +--- 1 file changed, 21 insertions(+), 7 deletions(-) diff --git

[PATCH v3 18/20] drm: omapdrm: Make pipe2vbl function static

The function is only used in omap_irq.c, move it there and make it static. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_crtc.c | 7 --- drivers/gpu/drm/omapdrm/omap_drv.h | 1 - drivers/gpu/drm/omapdrm/omap_irq.c | 7 ++- 3 files changed, 6 insertions(+), 9

[PATCH v3 09/20] drm: omapdrm: Replace DSS manager state check with omapdrm CRTC state

Instead of conditioning planes update based on the DD manager state, use the enabled field newly added to the omap_crtc structure. This reduces the dependency from the DRM layer to the DSS layer. The enabled field is a transitory measure, the implementation should use the CRTC atomic state

[PATCH v3 08/20] drm: omapdrm: Handle OCP error IRQ directly

Instead of going through a complicated registration mechanism, just call the OCP error IRQ handler directly from the main IRQ handler. Signed-off-by: Laurent Pinchart --- Changes since v1: - Rename IRQ handler to omap_irq_ocp_error_handler() - Replace hex error value with "OCP error" message

[PATCH v3 14/20] drm: omapdrm: Keep vblank interrupt enabled while CRTC is active

Instead of going through a complicated private IRQ registration mechanism, handle the vblank interrupt activation with the standard drm_crtc_vblank_get() and drm_crtc_vblank_put() mechanism. This will let the DRM core keep the vblank interrupt enabled as long as needed to update the frame counter.

[PATCH v3 15/20] drm: omapdrm: Don't expose the omap_irq_(un)register() functions

The IRQ registration functions are not used outside of their compilation unit, make them static. As the __omap_irq_(un)register() functions are only called by their omap_irq_(un)register() counterparts, merge them together. Signed-off-by: Laurent Pinchart --- Changes since v1: - Split the

[PATCH v3 19/20] drm: omapdrm: Simplify IRQ wait implementation

Now that the IRQ list is used for IRQ wait only we can merge omap_drm_irq and omap_irq_wait and simplify the implementation. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_drv.h | 17 +-- drivers/gpu/drm/omapdrm/omap_irq.c | 94 ++ 2

[PATCH v3 20/20] drm: omapdrm: Remove global variables

Move the list of pending IRQ wait instances to the omap_drm_private structure and the wait queue head to the IRQ wait structure. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_drv.h | 3 ++- drivers/gpu/drm/omapdrm/omap_irq.c | 42 -- 2

[PATCH v3 03/20] drm: omapdrm: fb: Simplify objects lookup when creating framebuffer

Merge the single-user objects_lookup inline function into its caller, allowing reuse of the error code path. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_drv.h | 25 - drivers/gpu/drm/omapdrm/omap_fb.c | 29

[PATCH v3 04/20] drm: omapdrm: fb: Simplify mode command checks when creating framebuffer

The hardware requires all planes to have an identical pitch in number of pixels. Given that all supported formats use the same number of bytes per pixel in all planes, framebuffer creation checks can be simplified. The implementations assumes that no format use more than two planes which is true

[PATCH v3 07/20] drm: omapdrm: Handle CRTC error IRQs directly

Instead of going through a complicated registration mechanism, just expose the CRTC error IRQ function and call it directly from the main IRQ handler. Signed-off-by: Laurent Pinchart Reviewed-by: Tomi Valkeinen --- drivers/gpu/drm/omapdrm/omap_crtc.c | 12 ++--

[PATCH v3 12/20] drm: omapdrm: Prevent processing the same event multiple times

The vblank interrupt is disabled after one occurrence, preventing the atomic update event from being processed twice. However, this also prevents the software frame counter from being updated correctly that would require vblank interrupts to be kept enabled while the CRTC is active. In

[PATCH v3 17/20] drm: omapdrm: Don't call DISPC power handling in IRQ wait functions

The IRQ wait functions are called from the DSS enable and disable operations only, where the DISPC is guaranteed to be enabled. There's no need for manual DISPC power management there. Signed-off-by: Laurent Pinchart --- drivers/gpu/drm/omapdrm/omap_irq.c | 4 1 file changed, 4

[PATCH v3 16/20] drm: omapdrm: Remove unused parameter from omap_drm_irq handler

The only omap_drm_irq handler doesn't use the irqstatus parameter passed to the function. Remove it. Signed-off-by: Laurent Pinchart --- Changes since v1: - New patch --- drivers/gpu/drm/omapdrm/omap_drv.h | 2 +- drivers/gpu/drm/omapdrm/omap_irq.c | 4 ++-- 2 files changed, 3 insertions(+), 3

[PATCH] drm: include linux/seq_file.h as needed

The addition of the debugfs info created references to seq_puts() and seq_printf(), but relied on the debugfs header to be included implicitly, which apparently doesn't happen all the time, as seen from this randconfig build output: drivers/gpu/drm/drm_dp_helper.c: In function

[Intel-gfx] [PATCH 04/10] drm: Extract drm_plane.[hc]

On Tue, Sep 06, 2016 at 12:59:31PM -0400, Sean Paul wrote: > On Wed, Aug 31, 2016 at 12:09 PM, Daniel Vetter > wrote: > > Just pure code movement, cleanup and polish will happen in later > > patches. > > > > v2: Don't forget all the ioctl! To extract those cleanly I decided to > > put

[PATCH 05/10] drm/doc: Polish for drm_plane.[hc]

On Fri, Sep 02, 2016 at 03:00:38PM +0530, Archit Taneja wrote: > > > On 8/31/2016 9:39 PM, Daniel Vetter wrote: > > Big thing is untangling and carefully documenting the different uapi > > types of planes. I also sprinkled a few more cross references around > > to make this easier to discover. >

[PATCH] drm: include linux/seq_file.h as needed

On Mon, 19 Sep 2016, Arnd Bergmann wrote: > The addition of the debugfs info created references to seq_puts() and > seq_printf(), but relied on the debugfs header to be included implicitly, > which apparently doesn't happen all the time, as seen from this randconfig > build output: > >

[PATCH 00/14] drm: Fix a bunch of sparse warnings

From: Ville Syrjälä I got a bit fed up from the sparse noise during a full build, so I tried to shut some of it up. Mostly missing statics or function declarations. I didn't touch the main offender (radeon/amdgpu) since there was enough of this stuff in the

[PATCH 01/14] drm/atomic-helper: Fix sparse warnings

From: Ville Syrjälä drm/drm_atomic_helper.c:1696:6: warning: symbol 'plane_crtc_active' was not declared. Should it be static? Cc: Daniel Vetter Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_atomic_helper.c | 2 +- 1 file changed, 1 insertion(+), 1

[PATCH 02/14] drm/blend: Fix sparse warnings

From: Ville Syrjälä drm/drm_blend.c:207:5: warning: symbol 'drm_atomic_normalize_zpos' was not declared. Should it be static? Cc: Marek Szyprowski Cc: Benjamin Gaignard Cc: Laurent Pinchart Signed-off-by: Ville Syrjälä --- drivers/gpu/drm/drm_blend.c | 2

[PATCH 05/14] drm/ast: Fix sparse warnings

From: Ville Syrjälä drm/ast/ast_drv.c:36:5: warning: symbol 'ast_modeset' was not declared. Should it be static? drm/ast/ast_ttm.c:227:22: warning: symbol 'ast_bo_driver' was not declared. Should it be static? Cc: Dave Airlie Signed-off-by: Ville Syrjälä

[PATCH 10/14] drm/nouveau: Fix sparse warnings

From: Ville Syrjälä drm/nouveau/dispnv04/overlay.c:496:1: warning: symbol 'nouveau_overlay_init' was not declared. Should it be static? drm/nouveau/nouveau_connector.c:63:5: warning: symbol 'nouveau_hdmimhz' was not declared. Should it be static?

[PATCH 03/14] drm/fb-helper: Fix sparse warnings

From: Ville Syrjälä drm/drm_fb_helper.c:2306:12: warning: symbol 'drm_fb_helper_modinit' was not declared. Should it be static? While at it, move the lefover static inline to the right place. Cc: Daniel Vetter Cc: Sean Paul Signed-off-by: Ville Syrjälä

[PATCH 06/14] drm/bochs: Fix sparse warnings

From: Ville Syrjälä drm/bochs/bochs_mm.c:196:22: warning: symbol 'bochs_bo_driver' was not declared. Should it be static? drm/bochs/bochs_kms.c:181:5: warning: symbol 'bochs_connector_get_modes' was not declared. Should it be static? Cc: Gerd Hoffmann

[PATCH 07/14] drm/cirrus: Fix sparse warnings

From: Ville Syrjälä drm/cirrus/cirrus_drv.c:18:5: warning: symbol 'cirrus_modeset' was not declared. Should it be static? drm/cirrus/cirrus_ttm.c:227:22: warning: symbol 'cirrus_bo_driver' was not declared. Should it be static? Cc: Dave Airlie Signed-off-by:

[PATCH 08/14] drm/mgag200: Fix sparse warnings

From: Ville Syrjälä drm/mgag200/mgag200_drv.c:24:5: warning: symbol 'mgag200_modeset' was not declared. Should it be static? drm/mgag200/mgag200_ttm.c:227:22: warning: symbol 'mgag200_bo_driver' was not declared. Should it be static? Cc: Dave Airlie

[PATCH 09/14] drm/msm: Fix sparse warnings

From: Ville Syrjälä drm/msm/mdp/mdp4/mdp4_lcdc_encoder.c:96:22: warning: symbol 'get_connector' was not declared. Should it be static? drm/msm/mdp/mdp4/mdp4_plane.c:84:5: warning: symbol 'mdp4_plane_set_property' was not declared. Should it be static?

[PATCH 11/14] drm/rockchip: Fix sparse warnings

From: Ville Syrjälä drm/rockchip/rockchip_drm_drv.c:312:6: warning: symbol 'rockchip_drm_fb_suspend' was not declared. Should it be static? drm/rockchip/rockchip_drm_drv.c:321:6: warning: symbol 'rockchip_drm_fb_resume' was not declared. Should it be static?

[PATCH 12/14] drm/sti: Fix sparse warnings

From: Ville Syrjälä drm/sti/sti_mixer.c:361:6: warning: symbol 'sti_mixer_set_matrix' was not declared. Should it be static? drm/sti/sti_gdp.c:476:5: warning: symbol 'sti_gdp_field_cb' was not declared. Should it be static? drm/sti/sti_gdp.c:885:24: warning:

[PATCH 13/14] drm/sun4i: Fix sparse warnings

From: Ville Syrjälä drm/sun4i/sun4i_tv.c:181:21: warning: symbol 'ntsc_video_levels' was not declared. Should it be static? drm/sun4i/sun4i_tv.c:185:21: warning: symbol 'pal_video_levels' was not declared. Should it be static? drm/sun4i/sun4i_tv.c:189:21:

[PATCH 14/14] drm/tilcdc: Fix sparse warnings

From: Ville Syrjälä drm/tilcdc/tilcdc_tfp410.c:385:24: warning: symbol 'tfp410_driver' was not declared. Should it be static? drm/tilcdc/tilcdc_tfp410.c:395:12: warning: symbol 'tilcdc_tfp410_init' was not declared. Should it be static?

[PATCH 04/14] drm/arm: Fix sparse warnings

From: Ville Syrjälä drm/arm/malidp_planes.c:49:24: warning: symbol 'malidp_duplicate_plane_state' was not declared. Should it be static? drm/arm/malidp_planes.c:66:6: warning: symbol 'malidp_destroy_plane_state' was not declared. Should it be static? Cc: Liviu

[PATCH 09/14] drm/msm: Fix sparse warnings

On 19 September 2016 at 14:33, wrote: > --- a/drivers/gpu/drm/msm/msm_fb.c > +++ b/drivers/gpu/drm/msm/msm_fb.c > @@ -132,7 +132,7 @@ const struct msm_format *msm_framebuffer_format(struct > drm_framebuffer *fb) > struct drm_framebuffer *msm_framebuffer_create(struct drm_device *dev, >

[RFC 0/2] drm/exynos: mixer: small optimisations

Hello, I had these two patches in my private tree for some time. Might as well ask if there is any interested in merging these. The first is just some unification on how booleans are used in the mixer code. The second one reduces register manipulation by moving stuff to the atomic flush call.

[RFC 1/2] drm/exynos: mixer: convert booleans to flags in mixer context

The mixer context struct already has a 'flags' field, so we can use it to store the 'interlace', 'vp_enabled' and 'has_sclk' booleans. We use the non-atomic helper functions to access these bits. Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_mixer.c | 54

[PATCH] drm/amdgpu: add function declaration in amdgpu.h

> -Original Message- > From: Baoyou Xie [mailto:baoyou.xie at linaro.org] > Sent: Sunday, September 18, 2016 10:29 AM > To: Deucher, Alexander; Koenig, Christian; airlied at linux.ie; Zhou, > David(ChunMing); Liu, Monk; Zhu, Rex; Huang, JinHuiEric; Cui, Flora > Cc: dri-devel at

[PATCH 4/5] drm/amdgpu: Rename a jump label in amdgpu_device_init()

> -Original Message- > From: SF Markus Elfring [mailto:elfring at users.sourceforge.net] > Sent: Sunday, September 18, 2016 12:53 PM > To: dri-devel at lists.freedesktop.org; Deucher, Alexander; Koenig, Christian; > Zhou, David(ChunMing); David Airlie; Liu, Monk; StDenis, Tom > Cc: LKML;

[RFC 2/2] drm/exynos: mixer: configure layers once in mixer_atomic_flush()

Only manipulate the MXR_CFG and MXR_LAYER_CFG registers once in mixer_cfg_layer(). Trigger this via atomic flush. Signed-off-by: Tobias Jakobi --- drivers/gpu/drm/exynos/exynos_mixer.c | 104 ++ drivers/gpu/drm/exynos/regs-mixer.h | 2 + 2 files changed, 69

[PATCH 03/10] drm: Move all decl for drm_edid.c to drm_edid.h

On Tue, Sep 06, 2016 at 12:59:39PM -0400, Sean Paul wrote: > On Wed, Aug 31, 2016 at 12:09 PM, Daniel Vetter > wrote: > > Some were still left in drm_crtc.h. Also include drm_edid.h in the > > rst files. > > > > Signed-off-by: Daniel Vetter > > Reviewed-by: Sean Paul Merged up to this patch,

[Intel-gfx] [PATCH] drm: fix implicit declaration build error on ia64

On Fri, Sep 16, 2016 at 01:06:36PM +0300, Jani Nikula wrote: >drivers/gpu/drm/drm_dp_helper.c: In function 'drm_dp_downstream_debug': > >> drivers/gpu/drm/drm_dp_helper.c:551:2: error: implicit declaration of > >> function 'seq_printf' [-Werror=implicit-function-declaration] >

[PATCH 03/14] drm/fb-helper: Fix sparse warnings

On Mon, Sep 19, 2016 at 04:33:44PM +0300, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > drm/drm_fb_helper.c:2306:12: warning: symbol 'drm_fb_helper_modinit' was not > declared. Should it be static? > > While at it, move the lefover static inline to the right place. > >

[PATCH 12/14] drm/sti: Fix sparse warnings

Acked-by: Vincent Abriou On 09/19/2016 03:33 PM, ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > drm/sti/sti_mixer.c:361:6: warning: symbol 'sti_mixer_set_matrix' was not > declared. Should it be static? > drm/sti/sti_gdp.c:476:5: warning: symbol 'sti_gdp_field_cb' was not

[Bug 97838] Hang on resume [AMD/ATI] RV515/M54 [Mobility Radeon X1400]

org/archives/dri-devel/attachments/20160919/e6d00c1c/attachment-0001.html>

[Bug 97861] [amdgpu SI] purple line is visible on left side of the screen connected by HDMI

ps://lists.freedesktop.org/archives/dri-devel/attachments/20160919/61aca785/attachment.html>

[Bug 97861] [amdgpu SI] purple line is visible on left side of the screen connected by HDMI

You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/12916da5/attachment.html>

[Bug 97838] Hang on resume [AMD/ATI] RV515/M54 [Mobility Radeon X1400]

dri-devel/attachments/20160919/3e20a7e9/attachment.html>

[Intel-gfx] Skylake graphics regression: projector failure with 4.8-rc3

On Sun, 2016-09-18 at 13:35 +0200, Thorsten Leemhuis wrote: > Hi! James & Paulo: What's the current status of this? No, the only interaction has been the suggestion below for a revert, which didn't fix the problem. > Was this issue discussed elsewhere or even fixed in between? Just > asking,

[Bug 97856] Computer restart playing 3D games (possibly overheating)

. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160919/73bd5f34/attachment.html>

[PATCH 09/14] drm/msm: Fix sparse warnings

On Mon, 19 Sep 2016, Emil Velikov wrote: > On 19 September 2016 at 14:33, wrote: > >> --- a/drivers/gpu/drm/msm/msm_fb.c >> +++ b/drivers/gpu/drm/msm/msm_fb.c >> @@ -132,7 +132,7 @@ const struct msm_format *msm_framebuffer_format(struct >> drm_framebuffer *fb) >> struct drm_framebuffer

[PATCH 0/5] GPU-DRM: Fine-tuning for four function implementations

From: Markus Elfring Date: Mon, 19 Sep 2016 17:47:37 +0200 A few update suggestions were taken into account from static source code analysis. Markus Elfring (5): Use kmalloc_array() in drm_legacy_addbufs_pci() Replace two kzalloc() calls by kcalloc() in

[PATCH 1/5] GPU-DRM: Use kmalloc_array() in drm_legacy_addbufs_pci()

From: Markus Elfring Date: Mon, 19 Sep 2016 17:07:06 +0200 A multiplication for the size determination of a memory allocation indicated that an array data structure should be processed. Thus use the corresponding function "kmalloc_array". This issue was detected

[PATCH 2/5] GPU-DRM: Replace two kzalloc() calls by kcalloc() in drm_legacy_addbufs_pci()

From: Markus Elfring Date: Mon, 19 Sep 2016 17:17:34 +0200 The script "checkpatch.pl" can point information out like the following. WARNING: Prefer kcalloc over kzalloc with multiply Thus fix the affected source code places. Signed-off-by: Markus Elfring ---

  1   2   >