[drm-intel:drm-intel-nightly 902/919] drivers/gpu/drm/drm_fb_cma_helper.c:312:20: error: 'struct drm_framebuffer' has no member named 'fomat'

t was scrubbed... Name: .config.gz Type: application/gzip Size: 38581 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/068967cf/attachment-0001.gz>

[bug report] drm/i915: Small compaction of the engine init code

Hello Tvrtko Ursulin, The patch a19d6ff29a82: "drm/i915: Small compaction of the engine init code" from Jun 23, 2016, leads to the following static checker warning: drivers/gpu/drm/i915/intel_lrc.c:1973 logical_render_ring_init() warn: passing freed memory 'engine'

[drm-tip:drm-tip 891/920] htmldocs: drivers/gpu/drm/drm_modeset_helper.c:74: warning: No description found for parameter 'dev'

plication/gzip Size: 6425 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/b8a7dfad/attachment-0001.gz>

Radeon X200M device suspend problem

I have a laptop with a Radeon X200M card in it. I use Radeon DRM driver for graphics, and it makes the system hang with display off when trying to suspend (either to disk or to RAM). Using /sys/power/pm_test interface revealed that it freezes when suspending devices. I have tried both Debian

[drm-tip:drm-tip 902/918] drivers/gpu/drm/drm_fb_cma_helper.c:312:20: error: 'struct drm_framebuffer' has no member named 'fomat'; did you mean 'format'?

Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation -- next part -- A non-text attachment was scrubbed... Name: .config.gz Type: application/gzip Size: 30762 bytes Desc: not available URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/d337150a/attachment-0001.gz>

[PATCH v3 2/2] drm/panel: simple: Add support BOE nv101wxmn51

Reviewed-by: Stéphane Marchesin On Tue, Dec 13, 2016 at 7:19 PM, Caesar Wang wrote: > 10.1WXGA is a color active matrix TFT LCD module using amorphous silicon > TFT's as an active switching devices. It can be supported by the > simple-panel driver. > > Read the panel default edid information:

[bug report] drm/i915: Small compaction of the engine init code

On Thu, Dec 15, 2016 at 11:44:13PM +0300, Dan Carpenter wrote: > Hello Tvrtko Ursulin, > > The patch a19d6ff29a82: "drm/i915: Small compaction of the engine > init code" from Jun 23, 2016, leads to the following static checker > warning: > > drivers/gpu/drm/i915/intel_lrc.c:1973

[PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless

Hi Greg, On Thu, Dec 15, 2016 at 8:10 PM, Greg KH wrote: > I'll take it after 4.10-rc1 is out, thanks. Thank you! Jason

[PATCH] drm: Fix kernel docs for drm_helper_mode_fill_fb_struct()

On Thu, Dec 15, 2016 at 05:12:26PM +, Deucher, Alexander wrote: > > -Original Message- > > From: ville.syrjala at linux.intel.com [mailto:ville.syrjala at > > linux.intel.com] > > Sent: Thursday, December 15, 2016 12:01 PM > > To: dri-devel at lists.freedesktop.org > > Cc: Laurent

[PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless

On most platforms, there exists this ifdef: #define atomic_inc_not_zero(v) atomic_add_unless((v), 1, 0) This makes this patch functionally useless. However, on PPC, there is actually an explicit definition of atomic_inc_not_zero with its own assembly that is slightly more optimized than

[PATCH] drm: Fix kernel docs for drm_helper_mode_fill_fb_struct()

Hi Ville, Thank you for the patch. On Thursday 15 Dec 2016 19:01:28 ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > drm_modeset_helper.c:74: warning: No description found for parameter 'dev' > > Cc: Laurent Pinchart > Cc: Alex Deucher > Fixes: a3f913ca9892 ("drm: Pass

Question about Radeon DRM and fan speed control

... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/0738ef98/attachment.html>

[PATCH] drm: Fix kernel docs for drm_helper_mode_fill_fb_struct()

From: Ville Syrjälä drm_modeset_helper.c:74: warning: No description found for parameter 'dev' Cc: Laurent Pinchart Cc: Alex Deucher Fixes: a3f913ca9892 ("drm: Pass 'dev' to drm_helper_mode_fill_fb_struct()") Signed-off-by: Ville Syrjälä ---

[PATCH v2] drm/amd/amdgpu: add check that shadow page tables are GPU-accessible

From: Nicolai Hähnle Skip amdgpu_gem_va_update_vm otherwise. Also clean up the check for the non-shadow page tables using the new helper function. This fixes a crash with the stack trace: amdgpu_gem_va_update_vm -> amdgpu_vm_update_page_directory -> amdgpu_ttm_bind

[PATCH 5/5] drm/amd/amdgpu: add check that shadow page tables are GPU-accessible

From: Nicolai Hähnle Skip amdgpu_gem_va_update_vm otherwise. Also clean up the check for the non-shadow page tables using the new helper function. This fixes a crash with the stack trace: amdgpu_gem_va_update_vm -> amdgpu_vm_update_page_directory -> amdgpu_ttm_bind

[PATCH 4/5] drm/amd/amdgpu: add check that shadow page directory is GPU-accessible

From: Nicolai Hähnle Skip amdgpu_gem_va_update_vm when shadow the page directory is swapped out. Clean up the check for non-shadow BOs as well using the new helper function. This fixes a crash with the stack trace: amdgpu_gem_va_update_vm ->

[PATCH 3/5] drm/amd/amdgpu: add amdgpu_bo_gpu_accessible helper function

From: Nicolai Hähnle Signed-off-by: Nicolai Hähnle --- drivers/gpu/drm/amd/amdgpu/amdgpu_object.h | 9 + 1 file changed, 9 insertions(+) diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h b/drivers/gpu/drm/amd/amdgpu/amdgpu_object.h index

[PATCH 2/5] drm/amd/amdgpu: move eviction counting to amdgpu_bo_move_notify

From: Nicolai Hähnle This catches evictions of shadow page tables from the GART. Since shadow page tables are always stored in system memory, amdgpu_bo_move is never called for them. This fixes a crash during command submission that occurs when only a shadow page table

[PATCH 1/5] drm/ttm: add evict parameter to ttm_bo_driver::move_notify

From: Nicolai Hähnle Ensure that the driver can listen to evictions even when they don't take the path through ttm_bo_driver::move. This is crucial for amdgpu, which relies on an eviction counter to skip re-binding page tables when possible. Signed-off-by: Nicolai

[PATCH 0/5] drm/ttm, amdgpu: fix crashes due to shadow page table evictions

Fix a bunch of related crashes in amdgpu that occur when shadow page tables are kicked out of the GART. One of the issues was that during command submission, we rely on a device-global evictions counter to skip some of the work of page-table validation. The driver was never informed of evictions

[PATCH v2 3/6] drm/atomic: Clean up wait_for_vblanks, v2.

Op 15-12-16 om 16:55 schreef Daniel Vetter: > On Thu, Dec 15, 2016 at 12:51:42PM +0100, Maarten Lankhorst wrote: >> Stop relying on a per crtc_state last_vblank_count, we shouldn't touch >> crtc_state after commit. Move it to atomic_state->crtcs. >> >> Also stop re-using new_crtc_state->enable, we

[PATCH] drm: Fix kernel docs for drm_helper_mode_fill_fb_struct()

> -Original Message- > From: ville.syrjala at linux.intel.com [mailto:ville.syrjala at > linux.intel.com] > Sent: Thursday, December 15, 2016 12:01 PM > To: dri-devel at lists.freedesktop.org > Cc: Laurent Pinchart; Deucher, Alexander > Subject: [PATCH] drm: Fix kernel docs for

[PATCH] drm/mediatek: Support UYVY and YUYV format for overlay

Hi Bibby, On Wed, Dec 14, 2016 at 1:14 PM, Bibby Hsieh wrote: > > MT8173 overlay can support UYVY and YUYV format, > we add the format in DRM driver. > > Signed-off-by: Bibby Hsieh > --- > drivers/gpu/drm/mediatek/mtk_disp_ovl.c | 6 ++ > drivers/gpu/drm/mediatek/mtk_drm_plane.c | 2 ++ >

[PATCH] drm: Convert all helpers to drm_connector_list_iter

Mostly nothing special (except making sure that really all error paths and friends call iter_put). v2: Don't forget the raw connector_list walking in drm_helper_move_panel_connectors_to_head. That one unfortunately can't be converted to the iterator helpers, but since it's just some list splicing

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

. So when reading the code, I skip the WARN_ONs. Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/a142350b/attachment.sig>

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

On Thu, 15 Dec 2016, Laurent Pinchart wrote: > Hi Ville, > > Thank you for the patch. > > On Thursday 15 Dec 2016 16:29:27 ville.syrjala at linux.intel.com wrote: >> From: Ville Syrjälä >> >> Apparently my arm .config had reverted to CMA=n at some point, so I >> failed to notice that I

[PATCH v2 3/6] drm/atomic: Clean up wait_for_vblanks, v2.

On Thu, Dec 15, 2016 at 12:51:42PM +0100, Maarten Lankhorst wrote: > Stop relying on a per crtc_state last_vblank_count, we shouldn't touch > crtc_state after commit. Move it to atomic_state->crtcs. > > Also stop re-using new_crtc_state->enable, we can now simply set a > bitmask with

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

Hi Tomi, On Thursday 15 Dec 2016 14:52:47 Tomi Valkeinen wrote: > On 14/12/16 02:27, Laurent Pinchart wrote: > > Instead of going through a complicated private IRQ registration > > mechanism, handle the vblank interrupt activation with the standard > > drm_crtc_vblank_get() and

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

On Thu, Dec 15, 2016 at 04:31:58PM +0200, Laurent Pinchart wrote: > Hi Ville, > > Thank you for the patch. > > On Thursday 15 Dec 2016 16:29:27 ville.syrjala at linux.intel.com wrote: > > From: Ville Syrjälä > > > > Apparently my arm .config had reverted to CMA=n at some point, so I > >

[RFC] Using DC in amdgpu for upcoming GPU

Hi, I have been reading the ongoing discussion about what to do about AMD DC (Display Core) with great interest since I have started to put more time into developing OpenChrome DRM for VIA Technologies Chrome IGP. I particularly enjoyed reading what Tony Cheng wrote about what is going on

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

On Thu, Dec 15, 2016 at 04:31:58PM +0200, Laurent Pinchart wrote: > Hi Ville, > > Thank you for the patch. > > On Thursday 15 Dec 2016 16:29:27 ville.syrjala at linux.intel.com wrote: > > From: Ville Syrjälä > > > > Apparently my arm .config had reverted to CMA=n at some point, so I > >

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

On Thu, Dec 15, 2016 at 04:31:58PM +0200, Laurent Pinchart wrote: > Hi Ville, > > Thank you for the patch. > > On Thursday 15 Dec 2016 16:29:27 ville.syrjala at linux.intel.com wrote: > > From: Ville Syrjälä > > > > Apparently my arm .config had reverted to CMA=n at some point, so I > >

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

Hi Ville, Thank you for the patch. On Thursday 15 Dec 2016 16:29:27 ville.syrjala at linux.intel.com wrote: > From: Ville Syrjälä > > Apparently my arm .config had reverted to CMA=n at some point, so I > failed to notice that I typoed the code. Fix it up so that the > cma helper will compile

[PATCH] drm/cma: Fix compile fail due to fomat->format typo

From: Ville Syrjälä Apparently my arm .config had reverted to CMA=n at some point, so I failed to notice that I typoed the code. Fix it up so that the cma helper will compile again. Reported-by: kbuild test robot Cc: Laurent Pinchart Fixes: ca984a998ad3

[Intel-gfx] [PATCH 1/4] drm/atomic: Delete wrong comment.

On Thu, Dec 15, 2016 at 03:29:42PM +0100, Maarten Lankhorst wrote: > drm_atomic_state_put is called unconditionally, so TEST_ONLY is no > different from commit. > > Signed-off-by: Maarten Lankhorst I think it'd be good to update the kerneldoc for the atomic_commit callback to mention that

[PATCH] drivers/gpu/drm/ast: Fix infinite loop if read fails

ast_get_dram_info() configures a window in order to access BMC memory. A BMC register can be configured to disallow this, and if so, causes an infinite loop in the ast driver which renders the system unusable. Fix this by erroring out if an error is detected. On powerpc systems with EEH, this

[PATCH] MAINTAINERS: add myself as maintainer of fbdev

I would like to help with fbdev maintenance. I can dedicate some time for reviewing and handling patches but won't have time for much more. The subsystem will remain in maintenance mode (no new drivers will be added to it). Cc: Tomi Valkeinen Cc: Daniel Vetter Signed-off-by: Bartlomiej

[Intel-gfx] [PATCH v2 00/37] drm: Deduplicate fb format information (v2)

On Wed, Dec 14, 2016 at 11:37:46PM +0200, Ville Syrjälä wrote: > On Fri, Nov 18, 2016 at 09:52:36PM +0200, ville.syrjala at linux.intel.com > wrote: > > From: Ville Syrjälä > > > > Second installment of my effort to remove the duplicated > > depth/bpp/pixel_format from drm_framebuffer and

[PATCH 4/4] drm: Resurrect atomic rmfb code, v2

From: Daniel Vetter This was somehow lost between v3 and the merged version in Maarten's patch merged as: commit f2d580b9a8149735cbc4b59c4a8df60173658140 Author: Maarten Lankhorst Date: Wed May 4 14:38:26 2016 +0200 drm/core: Do not preserve framebuffer on rmfb,

[PATCH 3/4] drm/i915: Disable all crtcs during driver unload.

We may keep the crtc's enabled when userspace unsets all framebuffers but keeps the crtc active. This exposes a WARN in fbc_global disable, and a lot of bugs in our hardware readout code. Solve this by disabling all crtc's for now. Signed-off-by: Maarten Lankhorst ---

[PATCH 2/4] drm/i915: Fix POWER_DOMAIN_AUDIO refcounting.

If the crtc was brought up with audio before the driver loads, then crtc_disable will remove a refcount to audio that doesn't exist before. Fortunately we already set power domains on readout, so we can just add the power domain handling to get_crtc_power_domains, which will update the power

[PATCH 1/4] drm/atomic: Delete wrong comment.

drm_atomic_state_put is called unconditionally, so TEST_ONLY is no different from commit. Signed-off-by: Maarten Lankhorst --- drivers/gpu/drm/drm_atomic.c | 4 1 file changed, 4 deletions(-) diff --git a/drivers/gpu/drm/drm_atomic.c b/drivers/gpu/drm/drm_atomic.c index

[PATCH 0/4] drm: Resurrect atomic rmfb code.

There were some issues in i915 preventing rmfb from working correctly. A lot of them are related to hw readout, some others due to keeping crtc active during driver unload: https://intel-gfx-ci.01.org/CI/Trybot_394/ I fixed the POWER_DOMAIN_AUDIO issue because it was easy to do so, but ignored

[PATCH 1/1] drm/amd/amdgpu: get maximum and used UVD handles (v3)

Am 15.12.2016 um 13:33 schrieb Nath, Arindam: >> -Original Message- >> From: Grazvydas Ignotas [mailto:notasas at gmail.com] >> Sent: Thursday, December 15, 2016 5:52 PM >> To: Nath, Arindam >> Cc: Emil Velikov; David Airlie; Deucher, Alexander; ML dri-devel; amd-gfx >> mailing list;

[PATCH] drm/bridge: analogix_dp: set the DPCD600 during disabling the psr

On 12/14/2016 03:30 PM, Sean Paul wrote: > On Wed, Dec 14, 2016 at 12:03 AM, Archit Taneja > wrote: >> Hi, >> >> On 12/12/2016 08:28 PM, Sean Paul wrote: >>> >>> On Fri, Dec 9, 2016 at 9:49 PM, Caesar Wang wrote: Look likes, the BOE panel FW didn't ack the DPCD600 signal from the

Passing multi-screen layout to KMS driver

Hello Gerd, 14.12.2016 11:11, Gerd Hoffmann wrote: >> So I would be interested to know whether anyone else has thought about >> this problem, and possibly even about an interface to let the compositor >> pass the information. If not, would people be open to the idea? I >> would much rather have

[PATCH v4 21/22] drm: omapdrm: Use sizeof(*var) instead of sizeof(type) for structures

ertions(+), 8 deletions(-) Reviewed-by: Tomi Valkeinen Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/

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

l signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/6c1985fc/attachment.sig>

[PATCH v4 16/22] drm: omapdrm: Remove unused parameter from omap_drm_irq handler

Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/24bc7262/attachment-0001.sig>

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

5 insertions(+), 22 deletions(-) Reviewed-by: Tomi Valkeinen Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/54eba3d3/attachment.sig>

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

DBG("%s: GO", omap_crtc->name); > > + dispc_mgr_go(omap_crtc->channel); > + > + WARN_ON(drm_crtc_vblank_get(crtc) != 0); I don't like this style very much. I think WARN()s should be without side effects. Also, WARN only gives benefit when we don't know what the call stack is. Afaik, there's only one way omap_crtc_atomic_flush can be called, so it's just extra spam and dev_err or dev_warn should be enough. Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/059ad801/attachment.sig>

[PATCH 20/34] drm/i915: Build DRM range manager selftests for CI

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Build the struct drm_mm selftests so that we can trivially run them > within our CI. > > Signed-off-by: Chris Wilson "Enable debug, become developer." Reviewed-by: Joonas Lahtinen Regards, Joonas -- Joonas Lahtinen Open Source

[PATCH] drm: Limit individual events to 1 KiB

On Thu, 15 Dec 2016, Thierry Reding wrote: > From: Thierry Reding > > Ever since support for vblank handling and event processing was added to > libdrm (v2.4.16), events were read in 1 KiB chunks in drmHandleEvent(). > In addition, the implementation of drm_read() will not unqueue events if >

[PATCH 33/34] drm: Fix drm_mm search and insertion

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > The drm_mm range manager claimed to support top-down insertion, but it > was neither searching for the top-most hole that could fit the > allocation request nor fitting the request to the hole correctly. > > In order to search the range

[PATCH 1/1] drm/amd/amdgpu: get maximum and used UVD handles (v3)

On Thu, Dec 15, 2016 at 1:47 PM, Nath, Arindam wrote: >>-Original Message- >>From: Emil Velikov [mailto:emil.l.velikov at gmail.com] >>Sent: Thursday, December 15, 2016 5:01 PM >>To: Nath, Arindam >>Cc: David Airlie; Deucher, Alexander; amd-gfx mailing list; ML dri-devel; >>Koenig,

[PATCH v4 12/22] drm: omapdrm: Prevent processing the same event multiple times

re Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/52a6e22e/attachment.sig>

BUG: 'list_empty(>free_vbufs)' is true!

On 11/16/2016, 02:12 PM, Gerd Hoffmann wrote: > On Fr, 2016-11-11 at 17:28 +0100, Jiri Slaby wrote: >> On 11/09/2016, 09:01 AM, Gerd Hoffmann wrote: >>> On Di, 2016-11-08 at 22:37 +0200, Michael S. Tsirkin wrote: On Mon, Nov 07, 2016 at 09:43:24AM +0100, Jiri Slaby wrote: > Hi, >

[PATCH] drm: Limit individual events to 1 KiB

On Thu, Dec 15, 2016 at 12:48:34PM +0100, Thierry Reding wrote: > From: Thierry Reding > > Ever since support for vblank handling and event processing was added to > libdrm (v2.4.16), events were read in 1 KiB chunks in drmHandleEvent(). > In addition, the implementation of drm_read() will not

[PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 10:34:00AM +, Nicholas Mc Guire wrote: > On Thu, Dec 15, 2016 at 12:20:01PM +0200, Jani Nikula wrote: > > On Thu, 15 Dec 2016, Ville Syrjälä > > wrote: > > > On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote: > > >> On Thu, 15 Dec 2016, Nicholas Mc Guire

[PATCH] drm/i915: use udelay for very short delays

On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > On Thu, Dec 15, 2016 at 12:20:01PM +0200, Jani Nikula wrote: >> On Thu, 15 Dec 2016, Ville Syrjälä >> wrote: >> > On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote: >> >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> >> > On Thu,

[PATCH v2] drm/etnaviv: Set up initial PULSE_EATER register

Set up the PULSE_EATER register (0x0010C) in etnaviv_gpu_hw_init. This ports three mostly undocumented model/revision-specific register overrides from the Vivante kernel driver. This is relevant as at least the "disable internal DFS" for revisions > 0x5420 has shown to have a huge impact on

[PATCH] drm: Fix typo in drm_event_reserve_init() kerneldoc

On Thu, Dec 15, 2016 at 12:36:02PM +0100, Thierry Reding wrote: > From: Thierry Reding > > drm_event_reserve_init_locked() is the correct function to call when > already holding the dev->event_lock lock. > > Signed-off-by: Thierry Reding Pushed to drm-misc-next, thanks. -Daniel > --- >

[PATCH/RFC 0/7] Remove the omapdrm device from platform code

ture.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/29af53df/attachment.sig>

[PATCH 17/34] drm: kselftest for drm_mm and color adjustment

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Check that after applying the driver's color adjustment, fitting of the > node and its alignment are still correct. > > Signed-off-by: Chris Wilson > +static void no_color_touching(struct drm_mm_node *node, > +    

[PATCH v2] drm/etnaviv: Add new GC3000 sensitive states

- Add PS.INST_ADDR (0x01028) and VS.INST_ADDR (0x0086C): GC3000 loads shader code from these addresses if ICACHE is used. - Add new NFE vertex stream addresses (0x14600). - Add PE Multple Render Target pipe addresses (0x14800). - Add TS Multiple Render Target pipe addresses (0x017C0, 0x17E0).

[PATCH 33/34] drm: Fix drm_mm search and insertion

On Thu, Dec 15, 2016 at 02:28:32PM +0200, Joonas Lahtinen wrote: > On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > > @@ -799,7 +706,7 @@ bool drm_mm_scan_add_block(struct drm_mm_scan *scan, > >   if (adj_end <= adj_start || adj_end - adj_start < scan->size) > >   return false;

[PATCH v2 3/6] drm/atomic: Clean up wait_for_vblanks, v2.

Stop relying on a per crtc_state last_vblank_count, we shouldn't touch crtc_state after commit. Move it to atomic_state->crtcs. Also stop re-using new_crtc_state->enable, we can now simply set a bitmask with crtc_crtc_mask. Changes since v1: - Keep last_vblank_count in __drm_crtc_state. --- diff

[PATCH] drm: Limit individual events to 1 KiB

From: Thierry Reding Ever since support for vblank handling and event processing was added to libdrm (v2.4.16), events were read in 1 KiB chunks in drmHandleEvent(). In addition, the implementation of drm_read() will not unqueue events if they can't be successfully passed to

[Intel-gfx] [PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 11:51 AM, Nicholas Mc Guire wrote: > On Thu, Dec 15, 2016 at 10:27:59AM +0100, Daniel Vetter wrote: >> On Thu, Dec 15, 2016 at 10:25:19AM +0100, Daniel Vetter wrote: >> > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: >> > > On Thu, 15 Dec 2016, Nicholas Mc

[PATCH] drm: Fix typo in drm_event_reserve_init() kerneldoc

From: Thierry Reding drm_event_reserve_init_locked() is the correct function to call when already holding the dev->event_lock lock. Signed-off-by: Thierry Reding --- drivers/gpu/drm/drm_fops.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[PATCH] drm/etnaviv: Set up initial PULSE_EATER register

Am Mittwoch, den 14.12.2016, 09:39 +0100 schrieb Wladimir J. van der Laan: > Set up the PULSE_EATER register (0x0010C) in etnaviv_gpu_hw_init. This > ports three mostly undocumented model/revision-specific register > overrides from the Vivante kernel driver. > > This is relevant as at least the

[PATCH] drm/etnaviv: Add new GC3000 sensitive states

Am Mittwoch, den 14.12.2016, 09:53 +0100 schrieb Wladimir J. van der Laan: > - Add PS.INST_ADDR and VS.INST_ADDR: GC3000 loads shader code from these > addresses if ICACHE > is enabled. > > - Add new NFE vertex stream addresses. Please resend with a proper Signed-off-by line. I can't take a

[PATCH] drm/i915: use udelay for very short delays

On Thu, 15 Dec 2016, Ville Syrjälä wrote: > On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote: >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: >> >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> >> > Even on fast

[PATCH] fbdev: remove current maintainer

On Thu, 8 Dec 2016 10:34:12 +0200 Tomi Valkeinen wrote: > Remove Tomi Valkeinen from fbdev maintainer and mark fbdev as orphan. > > ... > > I just don't have time to even pretend I maintain fbdev, so mark it as Orphan. > > Anyone want to pick fbdev maintainership? I'll keep an eye on the

[PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote: > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: > >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > >> > Even on fast systems a 2 microsecond delay is most likely more

[PATCH/RFC 0/7] Remove the omapdrm device from platform code

Hi Tomi, On Thursday 15 Dec 2016 10:08:47 Tomi Valkeinen wrote: > On 14/12/16 17:05, Tony Lindgren wrote: > > * Laurent Pinchart [161213 15:38]: > >> The series will be annoying to merge given how interleaved the ARM and > >> driver patches are. The easiest solution would be to merge everything

[PATCH] drm/i915: use udelay for very short delays

On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> > Even on fast systems a 2 microsecond delay is most likely more efficient >> > as a busy-wait loop. The overhead of a hrtimer does not

[PATCH 14/34] drm: kselftest for drm_mm and range restricted eviction

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Check that we add arbitrary blocks to a restrited eviction scanner in > order to find the first minimal hole that matches our request. > > Signed-off-by: Chris Wilson > +static int igt_evict_range(void *ignored) > +{ > +

[PATCH 1/1] drm/amd/amdgpu: get maximum and used UVD handles (v3)

>-Original Message- >From: Emil Velikov [mailto:emil.l.velikov at gmail.com] >Sent: Thursday, December 15, 2016 5:01 PM >To: Nath, Arindam >Cc: David Airlie; Deucher, Alexander; amd-gfx mailing list; ML dri-devel; >Koenig, Christian >Subject: Re: [PATCH 1/1] drm/amd/amdgpu: get maximum and

[PATCH] drm/i915: use udelay for very small delays

On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > On Thu, Dec 15, 2016 at 10:47:57AM +0200, Jani Nikula wrote: >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> > usleep_range() is intended for delays in the 10us to 10ms range that need >> > good precision. a useleep_range(1, will effectively be

[PATCH] drm: Convert all helpers to drm_connector_list_iter

Reviewed-by: Harry Wentland: On 2016-12-15 10:58 AM, Daniel Vetter wrote: > Mostly nothing special (except making sure that really all error paths > and friends call iter_put). > > v2: Don't forget the raw connector_list walking in > drm_helper_move_panel_connectors_to_head. That one

[PATCH 1/1] drm/amd/amdgpu: get maximum and used UVD handles (v3)

On 15 December 2016 at 07:30, Nath, Arindam wrote: >>-Original Message- >>From: Emil Velikov [mailto:emil.l.velikov at gmail.com] >>Sent: Wednesday, December 14, 2016 9:26 PM >>To: Nath, Arindam >>Cc: David Airlie; Deucher, Alexander; amd-gfx mailing list; ML dri-devel; >>Koenig,

[PATCH 13/34] drm: kselftest for drm_mm and eviction

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Check that we add arbitrary blocks to the eviction scanner in order to > find the first minimal hole that matches our request. > > Signed-off-by: Chris Wilson > + if ((int)tmp.start % n || tmp.size != nsize || >

[PATCH v2.2 2/4] drm/atomic: Add accessor macros for the current state, v3.

With checks! This will allow safe access to the current state, while ensuring that the correct locks are held. Changes since v1: - Constify returned states. - Require plane lock to return plane state, don't allow crtc_lock to be sufficient. Changes since v2: - Include drmP.h for drm_device,

[PATCH] kref: prefer atomic_inc_not_zero to atomic_add_unless

On Thu, Dec 15, 2016 at 07:55:54PM +0100, Jason A. Donenfeld wrote: > On most platforms, there exists this ifdef: > > #define atomic_inc_not_zero(v) atomic_add_unless((v), 1, 0) > > This makes this patch functionally useless. However, on PPC, there is > actually an explicit definition of

[PATCH] drm/i915: use udelay for very short delays

On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > Even on fast systems a 2 microsecond delay is most likely more efficient > as a busy-wait loop. The overhead of a hrtimer does not seem warranted - > change this to a udelay(2). Similar concerns as in [1]. We don't need the accuracy of udelay()

[PATCH v4 06/22] drm: omapdrm: Handle FIFO underflow IRQs internally

defined as something else > on > another platform and be mistaken. > > Given that we already take the same lock in the IRQ handler to call the wait > handlers, do you think this is really an issue ? Yep, I think it's fine for the time being. Reviewed-by: Tomi Valkeinen Tomi -- next part -- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/f0fa6071/attachment.sig>

[PATCH 12/34] drm: kselftest for drm_mm and alignment

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Check that we can request alignment to any power-of-two or prime using a > plain drm_mm_node_insert(), and also handle a reasonable selection of > primes. > > Signed-off-by: Chris Wilson > +static int igt_align(void *ignored) > +{ > +

[PATCH] drm/i915: use udelay for very small delays

On Thu, 15 Dec 2016, Jani Nikula wrote: > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: >> usleep_range() is intended for delays in the 10us to 10ms range that need >> good precision. a useleep_range(1, will effectively be no more than an >> imprecise udelay with some added cache disruption as

[PATCH 1/2] drm/panel: Add support for S6E3HA2 panel driver on TM2 board

On 12/14/2016 11:14 PM, Andrzej Hajda wrote: > On 14.12.2016 07:04, Hoegeun Kwon wrote: >> This patch add support for MIPI-DSI based S6E3HA2 AMOLED panel >> driver. This panel has 1440x2560 resolution in 5.7-inch physical >> panel in the TM2 device. >> >> Signed-off-by: Donghwa Lee >>

[Intel-gfx] [PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 10:27:59AM +0100, Daniel Vetter wrote: > On Thu, Dec 15, 2016 at 10:25:19AM +0100, Daniel Vetter wrote: > > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: > > > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > > > > Even on fast systems a 2 microsecond delay

[PATCH] drm/i915: use udelay for very small delays

On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > usleep_range() is intended for delays in the 10us to 10ms range that need > good precision. a useleep_range(1, will effectively be no more than an > imprecise udelay with some added cache disruption as it will fire more or > less immediately - use

[PATCH 07/13] drm: Clean up connectors by unreferencing them

On 2016-12-13 06:08 PM, Daniel Vetter wrote: > Only static connectors should be left at this point, and we should be > able to clean them out by simply dropping that last reference still > around from drm_connector_init. > > If that leaves anything behind then we have a driver bug. > > Doing the

[PATCH 11/34] drm: kselftest for drm_mm_insert_node_in_range()

On ma, 2016-12-12 at 11:53 +, Chris Wilson wrote: > Exercise drm_mm_insert_node_in_range(), check that we only allocate from > the specified range. > > Signed-off-by: Chris Wilson With the stylistic changes I proposed to whole series; Reviewed-by: Joonas Lahtinen Regards, Joonas --

[PATCH 12/23] drm: omapdrm: plane: update fifo size on atomic update

on-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: OpenPGP digital signature URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20161215/9979dc4b/attachment-0001.sig>

[Bug 96600] [RV630]: a lot of artifacts appears on a screen playing some videos through VDPAU with hardware acceleration

tps://lists.freedesktop.org/archives/dri-devel/attachments/20161215/5d6ac1fb/attachment.html>

[PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 12:20:01PM +0200, Jani Nikula wrote: > On Thu, 15 Dec 2016, Ville Syrjälä wrote: > > On Thu, Dec 15, 2016 at 11:52:34AM +0200, Jani Nikula wrote: > >> On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > >> > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: > >>

[Intel-gfx] [PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 10:25:19AM +0100, Daniel Vetter wrote: > On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: > > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > > > Even on fast systems a 2 microsecond delay is most likely more efficient > > > as a busy-wait loop. The overhead of

[Intel-gfx] [PATCH] drm/i915: use udelay for very short delays

On Thu, Dec 15, 2016 at 11:08:49AM +0200, Jani Nikula wrote: > On Thu, 15 Dec 2016, Nicholas Mc Guire wrote: > > Even on fast systems a 2 microsecond delay is most likely more efficient > > as a busy-wait loop. The overhead of a hrtimer does not seem warranted - > > change this to a udelay(2). >

[PATCH v2 0/4] drm/atomic: Add accessor macros for all atomic state.

Op 14-12-16 om 14:17 schreef Daniel Vetter: > On Wed, Nov 16, 2016 at 02:58:04PM +0100, Maarten Lankhorst wrote: >> Second approach. Instead of trying to convert all drivers straight away, >> implement all macros that are required to get state working. >> >> Current situation: >> Use obj->state,

  1   2   >