[PATCH v3 1/3] drm: add SimpleDRM driver

Den 16.08.2016 17:25, skrev Daniel Vetter: > On Tue, Aug 16, 2016 at 02:58:38PM +0200, Noralf Trønnes wrote: >> Den 15.08.2016 08:59, skrev Daniel Vetter: >>> On Sun, Aug 14, 2016 at 06:52:04PM +0200, Noralf Trønnes wrote: The SimpleDRM driver binds to simple-framebuffer devices and

[Bug 97371] AMDGPU/Iceland amdgpu: failed testing IB on ring 9/10

for the bug. -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160816/7f2be3df/attachment.html>

[PATCH v2 0/6] drm/rockchip: Some patches to update the PSR series

>> drivers/gpu/drm/rockchip/rockchip_drm_drv.c | 2 +- >> drivers/gpu/drm/rockchip/rockchip_drm_drv.h | 2 +- >> drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 90 - >> drivers/gpu/drm/rockchip/rockchip_drm_vop.c | 15 +++-- >> 5 files changed, 69 insertions(+), 59 deletions(-) >> > > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160816/53708a28/attachment-0001.html>

[Bug 93475] Saints Row IV causes GPU lockup on Linux

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/20160816/6c4bed54/attachment.html>

[Bug 97371] AMDGPU/Iceland amdgpu: failed testing IB on ring 9/10

org/archives/dri-devel/attachments/20160816/2b103ec0/attachment.html>

[Bug 97371] AMDGPU/Iceland amdgpu: failed testing IB on ring 9/10

ing 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/20160816/24b08efb/attachment-0001.html>

[Bug 97369] AMDGPU/Iceland hangs kernel 4.8-rc2

org/archives/dri-devel/attachments/20160816/cae764da/attachment.html>

[Bug 97039] The Talos Principle and Serious Sam 3 GPU faults

e on Kabini? -- 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/20160816/74a76d00/attachment.html>

[PATCH v2 6/6] drm/rockchip: Enable vblank without event

vblank should be enabled regardless of whether an event is expected back. This is especially important for a cursor plane. Signed-off-by: Sean Paul --- Changes in v2: - Rebased on https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=for-next

[PATCH v2 5/6] drm/rockchip: Improve analogix-dp psr handling

Remove the delayed worker, opting instead for the non-delayed variety. Also introduce a lock to ensure we don't have races with the worker and psr_state. Finally, cancel and wait for the worker to finish when disabling the bridge. Signed-off-by: Sean Paul --- Changes in v2: - Rebased on

[PATCH v2 4/6] drm/rockchip: A couple small fixes to psr

A few things that need tidying up, no functional changes. Signed-off-by: Sean Paul --- Changes in v2: - Introduced drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 19 +++ 1 file changed, 7 insertions(+), 12 deletions(-) diff --git

[PATCH v2 3/6] drm/rockchip: Use a spinlock to protect psr state

The handling of psr state is racey, shore that up with a per-psr driver lock. Signed-off-by: Sean Paul --- Changes in v2: - Rebased on https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=for-next drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 26 +- 1 file

[PATCH v2 2/6] drm/rockchip: Don't use a delayed worker for psr state changes

The delayed worker isn't needed and is racey. Remove it and do the state change in line. Signed-off-by: Sean Paul --- Changes in v2: - Rebased on https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=for-next drivers/gpu/drm/rockchip/rockchip_drm_psr.c | 38

[PATCH v2 1/6] drm/rockchip: Convert psr_list_mutex to spinlock and use it

This patch converts the psr_list_mutex to a spinlock and locks all access to psr_list to avoid races (however unlikely they were). Signed-off-by: Sean Paul --- Changes in v2: - Rebased on https://cgit.freedesktop.org/~seanpaul/dogwood/log/?h=for-next

[PATCH v2 0/6] drm/rockchip: Some patches to update the PSR series

This is a follow-on set to Yakir's original PSR set here: https://lkml.org/lkml/2016/7/24/34 and applies to the for-next branch at: https://cgit.freedesktop.org/~seanpaul/dogwood There are a few issues with the code that needed to be shored up. (1) The use of mutexes instead of

[Bug 97369] AMDGPU/Iceland hangs kernel 4.8-rc2

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

[Bug 97369] AMDGPU/Iceland hangs kernel 4.8-rc2

:01:00.0 on minor 1 Radeon R7 M340 Hybrid Graphics, Topaz/Iceland. -- 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/2016

[PATCH v4] drm: Introduce DRM_DEV_* log messages

On Tue, Aug 16, 2016 at 09:18:34AM -0700, Sean Paul wrote: > On Tue, Aug 16, 2016 at 5:28 AM, Eric Engestrom > wrote: > > On Mon, Aug 15, 2016 at 04:18:04PM -0700, Sean Paul wrote: > >> This patch consolidates all the various log functions/macros into > >> one uber function, drm_log. It also

[PATCH V2] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

On Tue, Aug 16, 2016 at 03:34:37PM +0200, Lothar Waßmann wrote: > Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in > the kerneldoc comments and add kerneldoc comments to the new function > drm_bus_flags_from_videomode(). > > Signed-off-by: Lothar Waßmann Applied to

[PATCH v3 2/3] drm: simpledrm: add fbdev fallback support

On Tue, Aug 16, 2016 at 03:10:06PM +0200, Noralf Trønnes wrote: > > Den 15.08.2016 08:48, skrev Daniel Vetter: > > On Sun, Aug 14, 2016 at 06:52:05PM +0200, Noralf Trønnes wrote: > > > Create a simple fbdev device during SimpleDRM setup so legacy user-space > > > and fbcon can use it. > > > >

[PATCH v3 1/3] drm: add SimpleDRM driver

On Tue, Aug 16, 2016 at 02:58:38PM +0200, Noralf Trønnes wrote: > > Den 15.08.2016 08:59, skrev Daniel Vetter: > > On Sun, Aug 14, 2016 at 06:52:04PM +0200, Noralf Trønnes wrote: > > > The SimpleDRM driver binds to simple-framebuffer devices and provides a > > > DRM/KMS API. It provides only a

[PATCH V4 2/4] Documentation/devicetree/bindings: b850v3_lvds_dp

On 04/08/16 23:36, Peter Senna Tschudin wrote: > Devicetree bindings documentation for the GE B850v3 LVDS/DP++ > display bridge. > > Cc: Javier Martinez Canillas > Cc: Enric Balletbo i Serra > Cc: Philipp Zabel > Cc: Rob Herring > Cc: Fabio Estevam > Signed-off-by: Peter Senna Tschudin

[PATCH V4 1/4] drm/imx-ldb: Add support to drm-bridge

On 04/08/16 23:36, Peter Senna Tschudin wrote: > Add support to attach a drm_bridge to imx-ldb in addition to > existing support to attach a LVDS panel. > > This patch does a simple code refactoring by moving code > from for_each_child_of_node iterator to a new function named >

[PATCH] dma-buf: fix kernel-doc warning and typos

From: Randy Dunlap Fix dma-buf kernel-doc warning and 2 minor typos in fence_array_create(). Fixes this warning: ..//drivers/dma-buf/fence-array.c:124: warning: No description found for parameter 'signal_on_any' Signed-off-by: Randy Dunlap Cc: Sumit Semwal Cc:

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

On 16/08/16 04:00 PM, Deng, Emily wrote: >> From: amd-gfx [mailto:amd-gfx-bounces at lists.freedesktop.org] On Behalf Of >> Michel D?nzer >> Sent: Tuesday, August 16, 2016 2:43 PM >> On 16/08/16 03:28 PM, Deng, Emily wrote: From: Michel Dänzer [mailto:michel at daenzer.net] Sent:

[Bug 97099] Regression in 9ef8537e6 "drm/radeon: don't use fractional dividers on RS[78]80 if SS is enabled" (RV620)

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/20160816/e0e9001d/attachment.html>

[PATCH v3 01/11] drm/i915: Add i915 perf infrastructure

On Tue, Aug 16, 2016 at 03:59:24PM +0100, Robert Bragg wrote: >On Mon, Aug 15, 2016 at 3:57 PM, Chris Wilson > Alternatively you could follow the standard pattern for read. Dare I ask > what is going to go into state that needs the obfuscation? > >I had dug around a bit when I

[PATCH v3 01/11] drm/i915: Add i915 perf infrastructure

userspace to ask us * to overrun its buffer, but the user knows best: * * http://yarchive.net/comp/linux/partial_reads_writes.html */ return state.read ?: (ret ?: -EAGAIN); Searching for another reference, I also just found the linux device drivers book talks about the same kind of convention: http://www.makelinux.net/ldd3/chp-3-sect-7 "Both the read and write methods return a negative value if an error occurs. A return value greater than or equal to 0, instead, tells the calling program how many bytes have been successfully transferred. If some data is transferred correctly and then an error happens, the return value must be the count of bytes successfully transferred, and the error does not get reported until the next time the function is called. Implementing this convention requires, of course, that your driver remember that the error has occurred so that it can return the error status in the future." - Robert > -Chris > > -- > Chris Wilson, Intel Open Source Technology Centre > -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160816/510e1aa5/attachment.html>

[Bug 97260] [bisected] R9 290 low performance in Linux 4.7

haven't missed any open question. Let me know if you need anything else. -- 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/20160816/d6e250f6/attachment.html>

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

On 16/08/16 03:28 PM, Deng, Emily wrote: >> From: Michel Dänzer [mailto:michel at daenzer.net] >> Sent: Tuesday, August 16, 2016 12:01 PM >> On 16/08/16 12:49 PM, Deng, Emily wrote: >>> Hi Michel, Thanks, I still couldn't see the issue that use a variable >>> to calculate the vblank count when

[PATCH V2] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in the kerneldoc comments and add kerneldoc comments to the new function drm_bus_flags_from_videomode(). Signed-off-by: Lothar Waßmann --- Changes vs. v1: - added missing characters drivers/gpu/drm/drm_modes.c | 10

[PATCH] gpu: ipu-v3: fix a possible NULL dereference

of_match_device could return NULL, and so cause a NULL pointer dereference later. For fixing this problem, we use of_device_get_match_data(), this will simplify the code a little by using a standard function for getting the match data. Signed-off-by: LABBE Corentin ---

[PATCH v3 2/3] drm: simpledrm: add fbdev fallback support

Den 15.08.2016 08:48, skrev Daniel Vetter: > On Sun, Aug 14, 2016 at 06:52:05PM +0200, Noralf Trønnes wrote: >> Create a simple fbdev device during SimpleDRM setup so legacy user-space >> and fbcon can use it. >> >> Original work by David Herrmann. >> >> Cc: dh.herrmann at gmail.com >>

[PATCH v2] drm: drop DRIVER_HAVE_IRQ flag for some drivers

Since commit 4984979b9b90 ("drm/irq: simplify irq checks in drm_wait_vblank"), the drm driver feature flag DRIVER_HAVE_IRQ is only required for drivers that have an IRQ handler managed by the DRM core. Some drivers, armada, etnaviv, kirin and sti, set this flag without .irq_handler setup in

[PATCH v3 1/3] drm: add SimpleDRM driver

Den 15.08.2016 08:59, skrev Daniel Vetter: > On Sun, Aug 14, 2016 at 06:52:04PM +0200, Noralf Trønnes wrote: >> The SimpleDRM driver binds to simple-framebuffer devices and provides a >> DRM/KMS API. It provides only a single CRTC+encoder+connector combination >> plus one initial mode. >> >>

[PATCH] drm: drop DRIVER_HAVE_IRQ flag for some drivers

On Fri, Aug 12, 2016 at 03:03:31PM +0100, Russell King - ARM Linux wrote: > On Fri, Aug 12, 2016 at 01:15:37PM +0800, Shawn Guo wrote: > > The drm driver feature flag DRIVER_HAVE_IRQ is used to indicates whether > > the driver has an IRQ handler managed by the DRM core. Some drivers, > > armada,

[PATCH] drm/rockchip: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Tue, 16 Aug 2016 14:25:35 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring ---

[PATCH] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

On Tue, Aug 16, 2016 at 2:35 PM, Lothar Waßmann wrote: > On Tue, 16 Aug 2016 13:41:20 +0200 Lucas Stach wrote: >> Hi Lothar, >> >> Am Dienstag, den 16.08.2016, 13:12 +0200 schrieb Lothar Waßmann: >> > Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in >> > the kerneldoc

[PATCH] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

Hi, On Tue, 16 Aug 2016 13:41:20 +0200 Lucas Stach wrote: > Hi Lothar, > > Am Dienstag, den 16.08.2016, 13:12 +0200 schrieb Lothar Waßmann: > > Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in > > the kerneldoc comments and add kerneldoc comments to the new function > >

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #27 from Kontantin Ivanov --- See my previous message for "4.4.0-34 DRI_PRIME=1 glxgears (stderr)" There is not any attachment for this. -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #26 from Kontantin Ivanov --- When I start glxgears (on integrated Intel graphic card) the gears shown stdout is: Running synchronized to the vertical refresh. The framerate should be approximately the same as the monitor refresh

[PATCH v2] drm: drop DRIVER_HAVE_IRQ flag for some drivers

On Tue, Aug 16, 2016 at 03:06:08PM +0800, Shawn Guo wrote: > Since commit 4984979b9b90 ("drm/irq: simplify irq checks in > drm_wait_vblank"), the drm driver feature flag DRIVER_HAVE_IRQ is only > required for drivers that have an IRQ handler managed by the DRM core. > Some drivers, armada,

[FIXUP] drm: remove `const` attribute to hint at caller that they now own the memory

On Tue, Aug 16, 2016 at 02:04:21PM +0300, Jani Nikula wrote: > > Reviewed-by: Jani Nikula Applied to drm-misc, thanks. -Daniel > > > On Mon, 15 Aug 2016, Eric Engestrom wrote: > > Signed-off-by: Eric Engestrom > > --- > > drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 2 +- > >

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #25 from Kontantin Ivanov --- Created attachment 229111 --> https://bugzilla.kernel.org/attachment.cgi?id=229111=edit 4.4.0-34 DRI_PRIME=1 glxinfo (descret Radeon graphic card) stderr is empty -- You are receiving this mail

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #24 from Kontantin Ivanov --- Created attachment 229101 --> https://bugzilla.kernel.org/attachment.cgi?id=229101=edit 4.4.0-34 glxinfo (integraded Intel graphic card) -- You are receiving this mail because: You are watching the

[FIXUP] drm: remove `const` attribute to hint at caller that they now own the memory

Reviewed-by: Jani Nikula On Mon, 15 Aug 2016, Eric Engestrom wrote: > Signed-off-by: Eric Engestrom > --- > drivers/gpu/drm/amd/amdgpu/dce_v10_0.c | 2 +- > drivers/gpu/drm/amd/amdgpu/dce_v11_0.c | 2 +- > drivers/gpu/drm/amd/amdgpu/dce_v8_0.c | 2 +- >

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #23 from Kontantin Ivanov --- Created attachment 229091 --> https://bugzilla.kernel.org/attachment.cgi?id=229091=edit 4.4.0-34 Xorg.0.log -- You are receiving this mail because: You are watching the assignee of the bug.

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #22 from Kontantin Ivanov --- Created attachment 229081 --> https://bugzilla.kernel.org/attachment.cgi?id=229081=edit 4.4.0-34 dmesg 4.4.0-34 dmesg after system start & login -- You are receiving this mail because: You are

[Bug 153121] UVD not responding, trying to reset the VCPU, ATI Mobility Radeon HD 5650

https://bugzilla.kernel.org/show_bug.cgi?id=153121 --- Comment #21 from Kontantin Ivanov --- Sorry for late reply. So. I reinstall my Kubuntu completely to be sure that some install/purge ppa/firmware/etc doesn't affect the system. Now `uname -a` is: Linux hpg6 4.4.0-34-generic #53-Ubuntu SMP

[PATCH] drm/bridge: dw-hdmi: Delete unnecessary assignment for the field "owner"

From: Markus Elfring Date: Tue, 16 Aug 2016 13:52:19 +0200 The field "owner" is set by the core. Thus delete an unneeded initialisation. Generated by: scripts/coccinelle/api/platform_no_drv_owner.cocci Signed-off-by: Markus Elfring ---

[PATCH] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

Hi Lothar, Am Dienstag, den 16.08.2016, 13:12 +0200 schrieb Lothar Waßmann: > Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in > the kerneldoc comments and add kerneldoc comments to the new function > drm_bus_flags_from_videomode(). > > Signed-off-by: Lothar Waßmann >

[PATCH] exynos-drm: Fix display manager failing to start without IOMMU problem

Hi Shuah, 2016년 08월 13일 02:52에 Shuah Khan 이(가) 쓴 글: > On 08/12/2016 11:28 AM, Shuah Khan wrote: >> On 08/10/2016 05:05 PM, Shuah Khan wrote: >>> On 08/10/2016 04:59 PM, Inki Dae wrote: Hi Shuah, 2016년 08월 11일 02:30에 Shuah Khan 이(가) 쓴 글: > Fix

[PATCH v4] drm: Introduce DRM_DEV_* log messages

On Mon, Aug 15, 2016 at 04:18:04PM -0700, Sean Paul wrote: > This patch consolidates all the various log functions/macros into > one uber function, drm_log. It also introduces some new DRM_DEV_* > variants that print the device name to delineate multiple devices > of the same type. > >

[Bug 119831] "nomodeset" required to boot - MSI laptop G72 6QE, nouveau graphics

https://bugzilla.kernel.org/show_bug.cgi?id=119831 --- Comment #14 from Pierre Moreau --- Eh sorry, completely forgot that you answered. So, you usually have a Xorg.0.log and a Xorg.0.log.old, with the former one being the log for the current session, and the latter one, of the previous

[PATCH] drm: update kerneldoc for changes introduced by commits "16fadc2568e9" and "9671e228fb78"

Describe the new parameter 'bus_flags' to of_get_drm_display_mode() in the kerneldoc comments and add kerneldoc comments to the new function drm_bus_flags_from_videomode(). Signed-off-by: Lothar Waßmann --- drivers/gpu/drm/drm_modes.c | 10 ++ 1 file changed, 10 insertions(+) diff

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

On 16/08/16 12:49 PM, Deng, Emily wrote: > Hi Michel, Thanks, I still couldn't see the issue that use a variable > to calculate the vblank count when vsync timer interrupt occurs. I > just think it only emulates the hardware behavior. And the code > change will only in virtual display files which

[PATCH 4/4] ARM: dts: am335x-boneblack: Convert BGR from LCDC to RGB in tda19988

Convert BGR from LCDC to RGB in tda19988 with video-ports property. The red and blue components are reversed between 24 and 16 bit modes on color output of am335x LCDC. On BBB the 16 bit video output is by default RGB and 24 is BGR. This patch reverts that using tda19988 so we have a 24 bit RGB

[PATCH 3/4] drm/tilcdc: Choose console BPP that supports RGB

Choose console BPP that supports RGB and remove the old fbdev bpp selection code. LCDC on AM335x has red and blue wires switched between 24 bit and 16 bit colors. If 24 format is wired for RGB colors, the 16 bit format is wired for BGR. drm_fbdev_cma_init() does not currently like anything else

[PATCH 2/4] drm/tilcdc: Add blue-and-red-wiring -device tree property

Add "blue-and-red-wiring"-device tree property and update devicetree binding document. The red and blue components are reversed between 24 and 16 bit modes on am335x LCDC output pins. To get 24 RGB format the red and blue wires has to be crossed and this in turn causes 16 colors output to be in

[PATCH 1/4] drm/tilcdc: Remove drm_helper_disable_unused_functions() call

drm_helper_disable_unused_functions() should not be called by atomic drivers. Signed-off-by: Jyri Sarha --- drivers/gpu/drm/tilcdc/tilcdc_drv.c | 2 -- 1 file changed, 2 deletions(-) diff --git a/drivers/gpu/drm/tilcdc/tilcdc_drv.c b/drivers/gpu/drm/tilcdc/tilcdc_drv.c index 3404d24..e45c268

[PATCH 0/4] drm/tilcdc: Address LCDC rev 2 color errata

The first patch ("drm/tilcdc: Remove drm_helper_disable_unused_functions() call") is completely independent fix. The red and blue components are reversed between 24 and 16 bit modes on am335x LCDC output pins. To get 24 RGB format the wires red and blue wires has to be crossed and this in turn

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

On 15/08/16 03:45 PM, Deng, Emily wrote: >> From: Michel Dänzer [mailto:michel at daenzer.net] >> Sent: Monday, August 15, 2016 9:46 AM >> On 11/08/16 12:46 PM, Emily Deng wrote: >>> The adev->ddev->vblank[crtc].count couldn't be used here, so define >>> another variable to compute the vblank

[PATCH 4/6] drm/radeon: Provide page_flip_target hook

On 16/08/16 09:35 AM, Mario Kleiner wrote: > Hi Michel, > > sorry for the super-late reply, i was just catching up with all the > mails and discussions, starting in June, leading to this patch set. > > Looks all pretty good. > > I'll look at this radeon patch and 2/6 for amdgpu later this week

[PATCH 6/6] drm: Add DRM_MODE_PAGE_FLIP_TARGET_ABSOLUTE/RELATIVE flags v2

On 16/08/16 10:32 AM, Mario Kleiner wrote: > Cc'ing Daniel Stone and Pekka Paalanen, because this relates to wayland. > > Wrt. having a new pageflip parameter struct, i wonder if it wouldn't > make sense to then already prepare some space in it for specifying an > absolute target time, e.g., in

[Bug 97362] Low performance after suspend on RX 480

next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160816/9f5f67ed/attachment.html>

rst htmldocs on kernel.org

Hi Jonathan, [+cc Konstantin] On Mon, Aug 15, 2016 at 04:21:15PM -0600, Jonathan Corbet wrote: > On Thu, 11 Aug 2016 21:13:29 +0200 Lukas Wunner wrote: > > not sure if this is already on your radar or if you're at all the > > right person to contact, but I just noticed that the gpu htmldocs > >

[PATCH V5 3/4] drm/bridge: Add driver for GE B850v3 LVDS/DP++ Bridge

Hi, On 08/09/2016 10:11 PM, Peter Senna Tschudin wrote: > Add a driver that create a drm_bridge and a drm_connector for the LVDS > to DP++ display bridge of the GE B850v3. > > There are two physical bridges on the video signal pipeline: a > STDP4028(LVDS to DP) and a STDP2690(DP to DP++). The

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

Hi Michel and Daniel, I just tryed Michel's advice: return 0 in vblank_get_counter, and set dev->max_vblank_count = 0 , and found the adev->ddev->vblank[crtc].count also can increase which makes the 3D app with vsync can work properly as well. But I don't know the principle. Anyway I will

[Bug 150731] amdgpu: segfault on unbind in sysfs; card becomes nonresponsive

https://bugzilla.kernel.org/show_bug.cgi?id=150731 --- Comment #10 from Jimi --- Sorry, autocorrect typos. Thing #1 is supposed to say that it's going to be a problem when I'm able to successfully unbind my card from amdgpu and will need to be able to rescan PCI devices without it auto-binding

[Bug 150731] amdgpu: segfault on unbind in sysfs; card becomes nonresponsive

https://bugzilla.kernel.org/show_bug.cgi?id=150731 --- Comment #9 from Jimi --- Over at the X bug report, I've figured out that when X has AutoAddGPU turned off, it doesnt crash (meaning that bug is not related to this bug), however, the card is still automatically bound to amdgpu before I can

[PATCH v4] drm: Introduce DRM_DEV_* log messages

On Tue, Aug 16, 2016 at 5:28 AM, Eric Engestrom wrote: > On Mon, Aug 15, 2016 at 04:18:04PM -0700, Sean Paul wrote: >> This patch consolidates all the various log functions/macros into >> one uber function, drm_log. It also introduces some new DRM_DEV_* >> variants that print the device name to

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

On Tue, Aug 16, 2016 at 03:43:07PM +0900, Michel Dänzer wrote: > On 16/08/16 03:28 PM, Deng, Emily wrote: > >> From: Michel Dänzer [mailto:michel at daenzer.net] > >> Sent: Tuesday, August 16, 2016 12:01 PM > >> On 16/08/16 12:49 PM, Deng, Emily wrote: > >>> Hi Michel, Thanks, I still couldn't

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

Hi Michel and Daniel, Return the fake vblank count or return 0 in vblank_get_counter is only the virtual display feature's behavior, and the virtual display feature need to be enabled by set module parameter, so won't affect normal case. And I think the vblank counter will be increased

[PATCH 12/21] drm/doc: Update drm_framebuffer docs

On Fri, Aug 12, 2016 at 1:48 PM, Daniel Vetter wrote: > - Move the intro section into a DOC comment, and update it slightly. > - kernel-doc for struct drm_framebuffer! > > v2: > - Copypaste fail (Sean). > - Explain the linear @offsets clearer (Ville). > > Cc: Sean Paul > Cc: Ville Syrjälä >

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

> -Original Message- > From: amd-gfx [mailto:amd-gfx-bounces at lists.freedesktop.org] On Behalf Of > Michel D?nzer > Sent: Tuesday, August 16, 2016 2:43 PM > To: Deng, Emily > Cc: dri-devel at lists.freedesktop.org; amd-gfx at lists.freedesktop.org > Subject: Re: [PATCH] drm/amdgpu: For

[PATCH 01/21] drm/doc: Fix more kerneldoc/sphinx warnings

ject_reference(struct drm_gem_object *obj) > * drm_gem_object_unreference_unlocked(). > * > * Drivers should never call this directly in their code. Instead they should > - * wrap it up into a driver_gem_object_unreference(struct driver_gem_object > - * *obj) wrapper function, and use that. Shared code should never call this, to > + * wrap it up into a ``driver_gem_object_unreference(struct driver_gem_object > + * *obj)`` wrapper function, and use that. Shared code should never call this, to > * avoid breaking drivers by accident which still depend upon dev->struct_mutex > * locking. > */ > -- > 2.8.1 > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/dri-devel -- next part -- An HTML attachment was scrubbed... URL: <https://lists.freedesktop.org/archives/dri-devel/attachments/20160816/a461c39f/attachment-0001.html>

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

> -Original Message- > From: Michel Dänzer [mailto:michel at daenzer.net] > Sent: Tuesday, August 16, 2016 12:01 PM > To: Deng, Emily > Cc: dri-devel at lists.freedesktop.org; amd-gfx at lists.freedesktop.org > Subject: Re: [PATCH] drm/amdgpu: For virtual_display feature, define a >

[Bug 97260] [bisected] R9 290 low performance in Linux 4.7

it with vblank_mode=3 -- 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/20160816/d9848207/attachment.html>

[Bug 97260] [bisected] R9 290 low performance in Linux 4.7

edesktop.org/archives/dri-devel/attachments/20160816/7ec0c0a0/attachment.html>

[PATCH] drm/amdgpu: For virtual_display feature, define a variable for vblank count of cpu vsync timer.

Hi Michel, Thanks, I still couldn't see the issue that use a variable to calculate the vblank count when vsync timer interrupt occurs. I just think it only emulates the hardware behavior. And the code change will only in virtual display files which won't touch drm layer. I incline to not

[PATCH 6/6] drm: Add DRM_MODE_PAGE_FLIP_TARGET_ABSOLUTE/RELATIVE flags v2

Cc'ing Daniel Stone and Pekka Paalanen, because this relates to wayland. Wrt. having a new pageflip parameter struct, i wonder if it wouldn't make sense to then already prepare some space in it for specifying an absolute target time, e.g., in u64 microseconds? Or make this part of the atomic

[PATCH 4/6] drm/radeon: Provide page_flip_target hook

Hi Michel, sorry for the super-late reply, i was just catching up with all the mails and discussions, starting in June, leading to this patch set. Looks all pretty good. I'll look at this radeon patch and 2/6 for amdgpu later this week when i have a fresh brain and enough "obsessive

[Bug 97303] battery mode for dpm state froze

|| -- 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/20160816/53631441/attachment.html>

[Bug 119631] RadeonSI get a huge performance dip with used with the nine state tracker

https://bugzilla.kernel.org/show_bug.cgi?id=119631 --- Comment #18 from Michel Dänzer --- (In reply to John Brooks from comment #17) > Looks like it may actually have been a kernel regression. > https://bugs.freedesktop.org/show_bug.cgi?id=97260#c12 We can't be sure about that until the