[Bug 76761] radeon DPM breaks suspend to disk and resume from RAM in 3.14

https://bugzilla.kernel.org/show_bug.cgi?id=76761 --- Comment #11 from Vitaliy Filippov --- Thanks, I'll wait for the inclusion :-) -- You are receiving this mail because: You are watching the assignee of the bug.

[PATCH 1/4] drm/radeon: rename alt_domain to allowed_domains

Thanks. This patch is: Reviewed-by: Marek Ol??k Marek On Mon, Jun 2, 2014 at 5:33 PM, Christian K?nig wrote: > From: Christian K?nig > > And also domain to prefered_domains. That matches better > what those values represent. > > Signed-off-by: Christian K?nig > Cc: Marek Ol??k > --- >

[PATCH 1/2] x86, ia64: Move EFI_FB vga_default_device() initialization to pci_vga_fixup()

With commit b4aa0163056b ("efifb: Implement vga_default_device() (v2)") Matthew Garrett introduced a efifb vga_default_device() so that EFI systems that do not load shadow VBIOS or setup VGA get proper value for boot_vga PCI sysfs attribute on the corresponding PCI device. Xorg is refusing to

[PATCH 2/2] x86, ia64: Merge common vga fixup code

The fixup code for PCI VGA devices in ia64 and x86 is mostly identical. Merge it into a single function called from both sides. The common code is moved to vgaarb.c which makes in dependant on CONFIG_VGA_ARB. Signed-off-by: Bruno Pr?mont --- arch/ia64/pci/fixup.c| 77

[Patch] x86, ia64, efifb: Move boot_vga fixup from pci to vgaarb

On Tue, 27 May 2014 Bjorn Helgaas wrote: > On Wed, May 14, 2014 at 10:43:39PM +0200, Bruno Pr?mont wrote: > > With commit b4aa0163056b6c70029b6e8619ce07c274351f42 Matthew Garret > > I think there's an emerging convention to use reference commits as > <12-char-SHA1> ("subject"), i.e., > >

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

On 2014? 06? 02? 18:42, Rahul Sharma wrote: > On 2 June 2014 14:41, Andrzej Hajda wrote: >> Hi Rahul, >> >> On 05/28/2014 08:11 AM, Rahul Sharma wrote: >>> System hangs when FIMD registers are accessed to disable >>> hardware overlays. This is because of the clocks which are >>> not enabled

[Bug 79564] New: glamor with dual radeon segfaults

ing this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/efd53947/attachment.html>

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

Hi Rahul, On 06/02/2014 06:42 PM, Rahul Sharma wrote: > On 2 June 2014 14:41, Andrzej Hajda wrote: >> Hi Rahul, >> >> On 05/28/2014 08:11 AM, Rahul Sharma wrote: >>> System hangs when FIMD registers are accessed to disable >>> hardware overlays. This is because of the clocks which are >>> not

[Bug 79223] extra vsync when reading back pixels in xbmc

attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/f8dcf690/attachment.html>

[Bug 79223] extra vsync when reading back pixels in xbmc

next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/6f1c6aa6/attachment.html>

[Intel-gfx] [PATCH] drivers/gpu/drm/i915/dma: style fixes

On Mon, Jun 02, 2014 at 05:21:32PM +0200, Daniel Vetter wrote: > On Mon, Jun 02, 2014 at 04:10:08PM +0100, Damien Lespiau wrote: > > On Mon, Jun 02, 2014 at 04:59:39PM +0200, Robin Schroer wrote: > > > Fixed several double space pointer notations, and added one newline > > > > > > Signed-off-by:

i915 power management documentation

On Mon, Jun 02, 2014 at 06:45:59PM +0200, Daniel Vetter wrote: > The hw guys don't yet allow us to publish docs for this. We're working on > it. For now your best guess is to look at the code or ask around on the > #intel-gfx irc channel. Fear of US patent trolls? regards, -- Sylvain

[pull] radeon drm-next-3.16

Hi Dave, This is the first pull request for radeon for 3.16. Christian has a few other patches that depend on some fixes from 3.15 so I'll wait to send those out until you sort out the 3.15 merge. Highlights: - GPUVM opimtizations - HDMI audio cleanups - Deep color HDMI support - more bug

[PATCH] gpu: drm: radeon: r600_cp.c: Cleaning up uninitialized variables

Hi Thanks for your response! No, it does not sound like it's worth changing anything. Although in the worst case with this patch you probably have a more consistent error :) Best regards Rickard Strandqvist 2014-06-02 9:48 GMT+02:00 Christian K?nig : > Am 01.06.2014 01:10, schrieb Rickard

i915 power management documentation

On Mon, Jun 02, 2014 at 04:15:11PM +0200, G?bor Bereczki wrote: > Hello DRM developers, > > I am looking after some documentation of the performance management of the > GPU hardware, like registers > > #define > GEN6_RPNSWREQ 0xA008 > >

[PATCH v2 1/5] gpu: ipu-v3: Move i.MX IPUv3 core driver out of staging

Am Mittwoch, den 28.05.2014, 14:13 -0700 schrieb Greg Kroah-Hartman: > On Mon, May 26, 2014 at 04:19:39PM +0200, Philipp Zabel wrote: > > The i.MX Image Processing Unit (IPU) contains a number of image processing > > blocks that sit right in the middle between DRM and V4L2. Some of the > >

[PATCH 4/4] drm/radeon: add debugfs file to trigger GPU reset

From: Christian K?nig Signed-off-by: Christian K?nig --- drivers/gpu/drm/radeon/radeon_fence.c | 22 +- 1 file changed, 21 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/radeon_fence.c b/drivers/gpu/drm/radeon/radeon_fence.c

[PATCH 3/4] drm/radeon: make vm_block_size a module parameter

From: Christian K?nig Signed-off-by: Christian K?nig --- drivers/gpu/drm/radeon/cik.c | 2 +- drivers/gpu/drm/radeon/ni.c| 2 +- drivers/gpu/drm/radeon/radeon.h| 8 ++-- drivers/gpu/drm/radeon/radeon_device.c | 16

[PATCH 2/4] drm/radeon: make VM size a module parameter

From: Christian K?nig Signed-off-by: Christian K?nig --- drivers/gpu/drm/radeon/cik.c | 2 +- drivers/gpu/drm/radeon/ni.c| 3 ++- drivers/gpu/drm/radeon/radeon.h| 2 +- drivers/gpu/drm/radeon/radeon_device.c | 27

[PATCH 1/4] drm/radeon: rename alt_domain to allowed_domains

From: Christian K?nig And also domain to prefered_domains. That matches better what those values represent. Signed-off-by: Christian K?nig Cc: Marek Ol??k --- drivers/gpu/drm/radeon/radeon.h| 4 ++-- drivers/gpu/drm/radeon/radeon_cs.c | 8

[Intel-gfx] [PATCH] drivers/gpu/drm/i915/dma: style fixes

On Mon, Jun 02, 2014 at 04:10:08PM +0100, Damien Lespiau wrote: > On Mon, Jun 02, 2014 at 04:59:39PM +0200, Robin Schroer wrote: > > Fixed several double space pointer notations, and added one newline > > > > Signed-off-by: Robin Schroer > > Reviewed-by: Damien Lespiau Queued for -next,

[PATCH] drm/radeon/dpm: resume fixes for some systems

Am 02.06.2014 17:14, schrieb Alex Deucher: > On Mon, Jun 2, 2014 at 4:10 AM, Christian K?nig > wrote: >> Am 02.06.2014 05:39, schrieb Dave Airlie: >> I've just added this to my 3.15 queue, but it looks like Linus is going to tag 3.15 tomorrow and Dave already send out his most

[Bug 79551] DRI_PRIME not working

|--- |NOTABUG -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/0880e343/attachment.html>

[PATCH] drm: Don't export internal module variables

On Mon, Jun 02, 2014 at 12:08:39PM +0200, David Herrmann wrote: > Hi > > On Mon, Jun 2, 2014 at 10:01 AM, Daniel Vetter wrote: > > On Sun, Jun 01, 2014 at 02:04:45PM +0200, David Herrmann wrote: > >> Hi > >> > >> On Thu, May 29, 2014 at 7:25 PM, Daniel Vetter > >> wrote: > >> > Drivers really

[PATCH 3/5] drm/i915: use shmem helpers if possible

On Sun, May 25, 2014 at 02:34:10PM +0200, David Herrmann wrote: > Instead of shuffling gfp-masks all the time, use the > shmem_read_mapping_page() helper. Note that __GFP_IO and __GFP_WAIT are > set in mapping_gfp_mask() for i915, so the behavior is still the same. > > Cc: Daniel Vetter > Cc:

[PATCH] drivers/gpu/drm/i915/dma: style fixes

Fixed several double space pointer notations, and added one newline Signed-off-by: Robin Schroer --- drivers/gpu/drm/i915/i915_dma.c | 30 -- 1 file changed, 16 insertions(+), 14 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_dma.c

[drm] INFO: possible recursive locking detected

On Mon, Jun 02, 2014 at 11:04:35AM +0300, Jani Nikula wrote: > On Fri, 30 May 2014, Jet Chen wrote: > > Hi Jesse, > > > > 0day kernel testing robot got the below dmesg and the first bad commit is > > > > git://people.freedesktop.org/~jbarnes/linux async-fb-probe > > Do I understand correctly

[Bug 79551] DRI_PRIME not working

ext part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/eac073df/attachment.html>

[Bug 66871] Radeon multi-screen intermittent display failure

https://bugzilla.kernel.org/show_bug.cgi?id=66871 --- Comment #9 from Erik Edwards --- (In reply to Alex Deucher from comment #8) > Can you use git to bisect what commit caused the regression? Google for git > bisect howto. 3.12.5 Found a workaround: Allow nromal boot to graphical

i915 power management documentation

... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/42afd1b3/attachment.html>

[Intel-gfx] [PATCH] drivers/gpu/drm/i915/dma: style fixes

On Mon, Jun 02, 2014 at 04:59:39PM +0200, Robin Schroer wrote: > Fixed several double space pointer notations, and added one newline > > Signed-off-by: Robin Schroer Reviewed-by: Damien Lespiau -- Damien

[Bug 79551] DRI_PRIME not working

in output stream: 18 -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/529da696/attachment.html>

[Bug 79223] extra vsync when reading back pixels in xbmc

part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/3fba7862/attachment.html>

[RFC PATCH v1.3 08/16 1/2] drm/radeon: add timeout argument to radeon_fence_wait_seq

Am 02.06.2014 15:14, schrieb Maarten Lankhorst: > This makes it possible to wait for a specific amount of time, > rather than wait until infinity. > > Signed-off-by: Maarten Lankhorst > --- > Splitted out version, I've noticed that I forgot to convert > radeon_fence_wait_empty to long r, fixed.

[GIT PULL] exynos-drm-next

Hi Dave, This pull request resolves hdmi dt broken issue, probe order and deferred probe issues, and consolidates hdmi and ipp drivers, and also includes fixups and cleanups. Summary: - Resolve probe order and deferred probe issue with component framework support. - Resolve hdmi dt

[pull] radeon drm-fixes-3.15

Hi Dave, since Linus delayed the release of 3.15 a bit more it gives me the opportunity to submit three more patches that otherwise would have needed a Cc stable in 3.16. The first one is a one liner fixing a stupid typo in the VM handling code and is only relevant if play with one of the VM

[RFC PATCH v1.3 08/16 2/2] drm/radeon: use common fence implementation for fences

Signed-off-by: Maarten Lankhorst --- Oops, changed unsigned long in __radeon_fence_wait to long, fixing a subtle bug. drivers/gpu/drm/radeon/radeon.h| 15 +-- drivers/gpu/drm/radeon/radeon_device.c | 60 - drivers/gpu/drm/radeon/radeon_fence.c | 223

[RFC PATCH v1.3 08/16 1/2] drm/radeon: add timeout argument to radeon_fence_wait_seq

This makes it possible to wait for a specific amount of time, rather than wait until infinity. Signed-off-by: Maarten Lankhorst --- Splitted out version, I've noticed that I forgot to convert radeon_fence_wait_empty to long r, fixed. drivers/gpu/drm/radeon/radeon_fence.c | 60

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

On 2 June 2014 14:41, Andrzej Hajda wrote: > Hi Rahul, > > On 05/28/2014 08:11 AM, Rahul Sharma wrote: >> System hangs when FIMD registers are accessed to disable >> hardware overlays. This is because of the clocks which are >> not enabled before register access. >> >> 'Hardware overlay disable'

[PATCH 4/5] drm/omap: use __GFP_DMA32 for shmem-backed gem

Hi Tomi Any chance you could give this a spin on an omap device? It shouldn't affect any 32bit devices, so this is mostly a cosmetic change. However, I'd really like to get rid of that 'TODO' item. So a "Tested-by:" would be really nice. Thanks David On Sun, May 25, 2014 at 2:34 PM, David

[Bug 79551] DRI_PRIME not working

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/7c6c6aa1/attachment.html>

[PATCH v3 15/15] ARM: dts: exynos5420: add dsi node

This patch adds common part of dsi node. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5420.dtsi | 14 ++ 1 file changed, 14 insertions(+) diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi

[PATCH v3 14/15] ARM: dts: exynos5420: add mipi-phy node

This patch adds mipi-phy node for MIPI DSI device. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5420.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git a/arch/arm/boot/dts/exynos5420.dtsi b/arch/arm/boot/dts/exynos5420.dtsi

[PATCH v3 13/15] ARM: dts: exynos5: add system register support

This patch adds sysreg device node, and sysreg property to fimd device node which is required to use I80 interface. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos5.dtsi |6 ++ 1 file changed, 6 insertions(+) diff --git

[PATCH v3 12/15] ARM: dts: exynos4: add system register node

This patch adds sysreg property to fimd device node which is required to use I80 interface. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- arch/arm/boot/dts/exynos4.dtsi |1 + 1 file changed, 1 insertion(+) diff --git a/arch/arm/boot/dts/exynos4.dtsi

[PATCH v3 11/15] drm/panel: add S6E3FA0 driver

This patch adds MIPI DSI command mode based S6E3FA0 AMOLED LCD Panel driver. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- drivers/gpu/drm/panel/Kconfig |7 + drivers/gpu/drm/panel/Makefile|1 + drivers/gpu/drm/panel/panel-s6e3fa0.c | 568

[PATCH v3 10/15] ARM: dts: s6e3fa0: add DT bindings

This patch adds DT bindings for s6e3fa0 panel. The bindings describes panel resources and display timings. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/panel/samsung,s6e3fa0.txt | 46 1 file changed, 46

[PATCH v3 09/15] drm/exynos: dsi: add driver data to support Exynos5420

The offset of register DSIM_PLLTMR_REG in Exynos5420 is different from the one in Exynos4 SoC. In case of Exynos5420 SoC, there is no frequency band bit in DSIM_PLLCTRL_REG, and it uses DSIM_PHYCTRL_REG and DSIM_PHYTIMING*_REG instead. So this patch adds driver data to distinguish it.

[PATCH v3 08/15] ARM: dts: exynos_dsim: add exynos5420 compatible to DT bindings

This patch adds relevant to exynos5420 compatible for exynos5420 SoC support. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/video/exynos_dsim.txt |4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git

[PATCH v3 07/15] drm/exynos: fimd: support LCD I80 interface

To support MIPI command mode based I80 interface panel, FIMD should do followings: - Sets LCD I80 interface timings configuration. - Uses "lcd_sys" as an IRQ resource and sets relevant IRQ configuration. - Sets LCD block configuration for I80 interface. - Sets ideal(pixel) clock is 2 times faster

[PATCH v3 06/15] drm/exynos: dsi: add TE handler to support LCD I80 interface

To support LCD I80 interface, the DSI host calls this handler to notify the panel tearing effect synchronization signal to the CRTC device manager to trigger to transfer video image. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park ---

[PATCH v3 05/15] drm/exynos: add TE handler to support LCD I80 interface

To support LCD I80 interface, the panel should generates Tearing Effect synchronization signal between MCU and FB to display video images. And the display controller should trigger to transfer video image at this signal. So the panel receives the TE IRQ, then calls this handler chains to notify it

[PATCH v3 04/15] ARM: dts: samsung-fimd: add LCD I80 interface specific properties

In case of using MIPI DSI based I80 interface panel, the relevant registers should be set. So this patch adds relevant DT bindings. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/video/samsung-fimd.txt | 28 1 file

[PATCH v3 03/15] ARM: dts: sysreg: add exynos5 compatible to DT bindings

This patch adds relevant to exynos5 compatible for exynos5 SoCs. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park --- .../devicetree/bindings/arm/samsung/sysreg.txt |1 + 1 file changed, 1 insertion(+) diff --git

[PATCH v3 02/15] drm/exynos: use wait_event_timeout() for safety usage

There could be the case that the page flip operation isn't finished correctly with some abnormal condition such as panel reset. So this patch replaces wait_event() with wait_event_timeout() to avoid waiting for page flip completion infinitely. And clears exynos_crtc->pending_flip in

[PATCH v3 01/15] drm/exynos: dsi: move the EoT packets configuration point

This configuration could be used in MIPI DSI command mode also. Signed-off-by: YoungJun Cho Acked-by: Inki Dae Acked-by: Kyungmin Park Reviewed-by: Andrzej Hajda --- drivers/gpu/drm/exynos/exynos_drm_dsi.c |5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git

[PATCH v3 00/15] drm/exynos: support LCD I80 interface display

Hi, This series adds LCD I80 interface display support for Exynos DRM driver. The FIMD(display controller) specification describes it as "LCD I80 interface" and the DSI specification describes it as "Command mode interface". This is based on exynos-drm-next branch. The previous patches, RFC:

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

On 06/02/2014 12:42 PM, Andrzej Hajda wrote: > On 06/02/2014 12:11 PM, Tomasz Figa wrote: >> Hi Rahul, Andrzej, >> >> On 02.06.2014 11:42, Rahul Sharma wrote: >>> On 2 June 2014 14:41, Andrzej Hajda wrote: Hi Rahul, On 05/28/2014 08:11 AM, Rahul Sharma wrote: > System hangs

[PATCH] drm/radeon/dpm: resume fixes for some systems

> > I've just added this to my 3.15 queue, but it looks like Linus is going to > tag 3.15 tomorrow and Dave already send out his most likely last pull > request. > > Going to send out another pull request in the evening if I can get the VM > crashes resolved as well, but I doubt it will be

[Bug 79551] New: DRI_PRIME not working

ppa. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/18d2a298/attachment-0001.html>

[RFC PATCH v1.2 08/16] drm/radeon: use common fence implementation for fences

Am 02.06.2014 12:09, schrieb Maarten Lankhorst: > Changes since v1: > - Fixed interaction with reset handling. > + Use exclusive_lock, either with trylock or blocking. > + Bump sw irq refcount in the recovery function to prevent fiddling > with irq registers during gpu recovery. > - Add

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

On 06/02/2014 12:11 PM, Tomasz Figa wrote: > Hi Rahul, Andrzej, > > On 02.06.2014 11:42, Rahul Sharma wrote: >> On 2 June 2014 14:41, Andrzej Hajda wrote: >>> Hi Rahul, >>> >>> On 05/28/2014 08:11 AM, Rahul Sharma wrote: System hangs when FIMD registers are accessed to disable hardware

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

Hi Rahul, Andrzej, On 02.06.2014 11:42, Rahul Sharma wrote: > On 2 June 2014 14:41, Andrzej Hajda wrote: >> Hi Rahul, >> >> On 05/28/2014 08:11 AM, Rahul Sharma wrote: >>> System hangs when FIMD registers are accessed to disable >>> hardware overlays. This is because of the clocks which are >>>

[RFC PATCH v1.2 08/16] drm/radeon: use common fence implementation for fences

Changes since v1: - Fixed interaction with reset handling. + Use exclusive_lock, either with trylock or blocking. + Bump sw irq refcount in the recovery function to prevent fiddling with irq registers during gpu recovery. - Add radeon lockup detection to the default fence wait function.

[PATCH] drm: Don't export internal module variables

Hi On Mon, Jun 2, 2014 at 10:01 AM, Daniel Vetter wrote: > On Sun, Jun 01, 2014 at 02:04:45PM +0200, David Herrmann wrote: >> Hi >> >> On Thu, May 29, 2014 at 7:25 PM, Daniel Vetter >> wrote: >> > Drivers really have no business touching these. Noticed because >> > exynose _did_ touch the

[PATCH 1/4] drm/radeon: rename alt_domain to allowed_domains

On Mon, Jun 2, 2014 at 11:33 AM, Christian K?nig wrote: > From: Christian K?nig > > And also domain to prefered_domains. That matches better > what those values represent. > > Signed-off-by: Christian K?nig > Cc: Marek Ol??k A couple of comments on 2/4, but other than that, the series is:

[PATCH 2/4] drm/radeon: make VM size a module parameter

On Mon, Jun 2, 2014 at 11:33 AM, Christian K?nig wrote: > From: Christian K?nig > > Signed-off-by: Christian K?nig > --- > drivers/gpu/drm/radeon/cik.c | 2 +- > drivers/gpu/drm/radeon/ni.c| 3 ++- > drivers/gpu/drm/radeon/radeon.h| 2 +- >

[PATCH 0/8] prepare for preparing for atomic (v2)

On Mon, Jun 2, 2014 at 4:11 AM, Daniel Vetter wrote: > On Fri, May 30, 2014 at 01:12:02PM -0400, Rob Clark wrote: >> As suggested by Daniel, splitting out ww_mutex conversion and a few >> other bits out. Updated connection_mutex which fixes a few things, >> plus split up addition of extended

[PATCH 3/3] drm/radeon: use the CP DMA on CIK

From: Christian K?nig The SDMA sometimes doesn't seem to work reliable. Signed-off-by: Christian K?nig Cc: stable at vger.kernel.org --- drivers/gpu/drm/radeon/radeon_asic.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 2/3] drm/radeon: sync page table updates

From: Christian K?nig Only necessary if we don't use the same engine for buffer moves and table updates. Signed-off-by: Christian K?nig --- drivers/gpu/drm/radeon/radeon_vm.c | 9 +++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git

[PATCH 1/3] drm/radeon: fix vm buffer size estimation

From: Christian K?nig Only relevant if we got VM_BLOCK_SIZE>9, but better save than sorry. Signed-off-by: Christian K?nig --- drivers/gpu/drm/radeon/radeon_vm.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/radeon_vm.c

[PATCH 14/9] drm: Kick start vblank interrupts at drm_vblank_on()

From: Ville Syrj?l? If the user is interested in getting accurate vblank sequence numbers all the time they may disable the vblank disable timer entirely. In that case it seems appropriate to kick start the vblank interrupts already from drm_vblank_on().

[PATCH 13/9] drm: Fix race between drm_vblank_off() and drm_queue_vblank_event()

From: Ville Syrj?l? Currently it's possible that the following will happen: 1. drm_wait_vblank() calls drm_vblank_get() 2. drm_vblank_off() gets called 3. drm_wait_vblank() calls drm_queue_vblank_event() which adds the event to the queue event though vblank

[PATCH 12/9] drm: Fix deadlock between event_lock and vbl_lock/vblank_time_lock

From: Ville Syrj?l? Currently both drm_irq.c and several drivers call drm_vblank_put() while holding event_lock. Now that drm_vblank_put() can disable the vblank interrupt directly it may need to grab vbl_lock and vblank_time_lock. That causes deadlocks since we

[PATCH] drm/radeon/dpm: resume fixes for some systems

On Mon, Jun 2, 2014 at 4:10 AM, Christian K?nig wrote: > Am 02.06.2014 05:39, schrieb Dave Airlie: > >>> I've just added this to my 3.15 queue, but it looks like Linus is going >>> to >>> tag 3.15 tomorrow and Dave already send out his most likely last pull >>> request. >>> >>> Going to send out

[PATCH] drm/exynos: remove hardware overlays disable from fimd probe

Hi Rahul, On 05/28/2014 08:11 AM, Rahul Sharma wrote: > System hangs when FIMD registers are accessed to disable > hardware overlays. This is because of the clocks which are > not enabled before register access. > > 'Hardware overlay disable' is cleaned from the FIMD probe. > > Signed-off-by:

[drm] INFO: possible recursive locking detected

On Fri, 30 May 2014, Jet Chen wrote: > Hi Jesse, > > 0day kernel testing robot got the below dmesg and the first bad commit is > > git://people.freedesktop.org/~jbarnes/linux async-fb-probe Do I understand correctly that this is only present in one of Jesse's personal branches? The distribution

[PATCH 08/11] apple-gmux: Add support for the switch_ddc callback

On Sun, Jun 1, 2014 at 12:38 PM, Matthew Garrett wrote: > We can switch DDC pins in a way that ought (with luck) to work for LVDS. > This isn't sufficient for eDP, which is addressed in later patches. > > Signed-off-by: Matthew Garrett FWIW, on AMD muxed PX systems, there are separate muxes for

[PATCH 7/7] drm/edid: Add quirk for Sony PVM-2541A to get 12 bpc hdmi deep color.

From: Mario Kleiner The Sony PVM-2541A OLED high precision color display supports both 10 bpc and 12 bpc hdmi deep color input, but its edid does not signal any deep color support. Add a quirk to force it being treated as a 12 bpc panel. Signed-off-by: Mario Kleiner

[PATCH 6/7] drm/edid: Parse and handle HDMI deep color modes.

From: Mario Kleiner Check the HDMI cea block for deep color mode bits. If available, assign the highest supported bpc for a hdmi display, corresponding to the given deep color modes. Signed-off-by: Mario Kleiner Signed-off-by: Alex Deucher ---

[PATCH 5/7] drm/radeon: Limit hdmi deep color bit depth to 12 bpc.

From: Mario Kleiner DCE-4/5/6 can't support more than 12 bpc deep color over hdmi, so clamp to 12 bpc when a hdmi deep color capable display is connected. This even makes sense on DCE-8+, which could do up to 16 bpc, as driving with more than 12 bpc would only waste

[PATCH 4/7] drm/radeon: Setup HDMI_CONTROL for hdmi deep color gcp's (v2)

Program HDMI_CONTROL to send general control packets for hdmi deep color mode signalling at every video frame if bpc > 8. This is only supported on evergreen / DCE-4 and later. v2: rebase Signed-off-by: Mario Kleiner Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/evergreen_hdmi.c |

[PATCH 3/7] drm/radeon: fix pll setup for hdmi deep color (v5)

Need to adjust the pll up for deep color modes. Additionally, the atom bpc defines were wrong in certain cases. v2: set the adjusted clock to the pll clock for hdmi deep color. This fixes display and audio issues with deep color as reported by Andy Furniss v3: set crtc_clock as well v4:

[PATCH 2/7] drm/radeon: use hw cts/n values for deep color

I'm not really sure how these should be calculated for deep color. The hw generated values seem to work. Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/evergreen_hdmi.c | 18 +++--- 1 file changed, 15 insertions(+), 3 deletions(-) diff --git

[PATCH 1/7] drm/radeon: only apply hdmi bpc pll flags when encoder mode is hdmi

May fix display issues with non-HDMI displays. Signed-off-by: Alex Deucher Cc: stable at vger.kernel.org --- drivers/gpu/drm/radeon/atombios_crtc.c | 48 ++ 1 file changed, 26 insertions(+), 22 deletions(-) diff --git a/drivers/gpu/drm/radeon/atombios_crtc.c

[PATCH 0/8] prepare for preparing for atomic (v2)

On Fri, May 30, 2014 at 01:12:02PM -0400, Rob Clark wrote: > As suggested by Daniel, splitting out ww_mutex conversion and a few > other bits out. Updated connection_mutex which fixes a few things, > plus split up addition of extended property types from adding object > property and pull in

[PATCH] drm/radeon/dpm: resume fixes for some systems

Am 02.06.2014 05:39, schrieb Dave Airlie: >> I've just added this to my 3.15 queue, but it looks like Linus is going to >> tag 3.15 tomorrow and Dave already send out his most likely last pull >> request. >> >> Going to send out another pull request in the evening if I can get the VM >> crashes

[PULL] topic/core-stuff

Hi Dave, Just flushing out my pile of random drm patches for the merge window, nothing big. And it all hung around in drm-intel trees for a while (only just rebased now). Cheers, Daniel The following changes since commit 182407a6ed5333fc37dd980a8de91a8f826a94f6: drm: add DP MST encoder type

[PATCH v2 1/5] gpu: ipu-v3: Move i.MX IPUv3 core driver out of staging

On Mon, Jun 02, 2014 at 06:36:22PM +0200, Philipp Zabel wrote: > Am Mittwoch, den 28.05.2014, 14:13 -0700 schrieb Greg Kroah-Hartman: > > On Mon, May 26, 2014 at 04:19:39PM +0200, Philipp Zabel wrote: > > > The i.MX Image Processing Unit (IPU) contains a number of image processing > > > blocks

[PATCH] drm: Don't export internal module variables

On Sun, Jun 01, 2014 at 02:04:45PM +0200, David Herrmann wrote: > Hi > > On Thu, May 29, 2014 at 7:25 PM, Daniel Vetter > wrote: > > Drivers really have no business touching these. Noticed because > > exynose _did_ touch the vblank off delay, which could potentially > > affect other drivers. >

[PATCH] gpu: drm: radeon: r600_cp.c: Cleaning up uninitialized variables

Am 01.06.2014 01:10, schrieb Rickard Strandqvist: > There is a risk that the variable will be used without being initialized. > > This was largely found by using a static code analysis program called > cppcheck. > > Signed-off-by: Rickard Strandqvist On the one hand it looks like a valid fix to

[Bug 79504] LLVM error on fragment shader

bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/37000717/attachment.html>

[Bug 79504] LLVM error on fragment shader

this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/a5ec3050/attachment.html>

[PATCH resend 2/4] backlight: Add backlight device (un)registration notification

On Sun, 01 Jun 2014, Rafael J. Wysocki wrote: > On Tuesday, May 27, 2014 10:20:33 AM Lee Jones wrote: > > > On 05/26/2014 01:03 PM, Rafael J. Wysocki wrote: > > > > On Monday, May 26, 2014 12:03:43 PM Jingoo Han wrote: > > > >> On Thursday, May 22, 2014 6:02 PM, Lee Jones wrote: > > > >>> On

[PULL] drm-intel-next

Hi Dave, drm-intel-next-2014-05-23: - prep refactoring for execlists (Oscar Mateo) - corner-case fixes for runtime pm (Imre) - tons of vblank improvements from Ville - prep work for atomic plane/sprite updates (Ville) - more chv code, now almost complete (tons of different people) - refactoring

[Bug 79504] LLVM error on fragment shader

ert and raycast.frag to be in the working directory. -- You are receiving this mail because: You are the assignee for the bug. -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/bfff5541/attachment.html>

[pull] drm/msm: msm-next for 3.16-rc1

Dave, Pretty small pull this time around for msm. Adds some useful debugfs I'd been carrying around on a branch for a while, plus few fixes. And Kconfig update for the great ARCH_MSM -> ARCH_QCOM split. The following changes since commit 182407a6ed5333fc37dd980a8de91a8f826a94f6: drm: add DP

[Bug 77181] New: radeon -- GPU lockup when hibernating or waking up

https://bugzilla.kernel.org/show_bug.cgi?id=77181 Bug ID: 77181 Summary: radeon -- GPU lockup when hibernating or waking up Product: Drivers Version: 2.5 Kernel Version: 3.15.0-rc8 Hardware: x86-64 OS: Linux

[Bug 79223] extra vsync when reading back pixels in xbmc

L attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20140602/343feb8e/attachment.html>

[Bug 79520] mpv 0.3.10-1 shows no video after mesa and ati-dri update to version 10.2.0rc5-1

org/archives/dri-devel/attachments/20140602/b1274423/attachment.html>

  1   2   >