[PATCH v4] drm/i2c: tda998x: fix sync generation and calculation

On 06/20/2013 10:06 PM, Russell King - ARM Linux wrote: > On Thu, Jun 20, 2013 at 09:46:03PM +0200, Sebastian Hesselbarth wrote: >> +ref_pix = 3 + mode->hsync_start - mode->hdisplay; >> +de_pix_s = mode->htotal - mode->hdisplay; >> +de_pix_e = de_pix_s + mode->hdisplay; >>

MTRR use in drivers

An awful lot of drivers, mostly DRI drivers, are still mucking with MTRRs directly as opposed to using ioremap_wc() or similar interfaces. In addition to the architecture dependency, this is really undesirable because MTRRs are a limited resource, whereas page table attributes are not.

[PATCH v4] drm/i2c: tda998x: fix sync generation and calculation

This fixes the wrong sync generation and sync calculation. It has only been tested for progressive and interlaced modes. Sync timings for a bunch of modes have also been verified with an oscilloscope near-end (TDA998x input) and far-end (DVI receiver output). Signed-off-by: Sebastian Hesselbarth

[PATCH 0/5] clk/exynos5420: add clocks for hdmi subsystem

Quoting Kukjin Kim (2013-06-19 07:01:17) > On 06/19/13 13:04, Rahul Sharma wrote: > > + mike > > > Mike, I'm waiting for your reply on this. If you're OK, let me take this > series on top of exynos5420 stuff in samsung tree. > > Of course, if any concerns, please let me know. I never got these

[PATCH v4] drm/i2c: tda998x: fix sync generation and calculation

On Thu, Jun 20, 2013 at 09:46:03PM +0200, Sebastian Hesselbarth wrote: > + ref_pix = 3 + mode->hsync_start - mode->hdisplay; > + de_pix_s = mode->htotal - mode->hdisplay; > + de_pix_e = de_pix_s + mode->hdisplay; > + hs_pix_s = mode->hsync_start - mode->hdisplay; >

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

> -Original Message- > From: Lucas Stach [mailto:l.stach at pengutronix.de] > Sent: Thursday, June 20, 2013 7:11 PM > To: Inki Dae > Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho'; > 'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm- > kernel at

[PATCH v2 8/8] of/documentation: update with clock information for exynos hdmi subsystem

Adding information about clocks to the binding documentation for exynos mixer and hdmi. Signed-off-by: Rahul Sharma --- Documentation/devicetree/bindings/video/exynos_hdmi.txt | 14 +- Documentation/devicetree/bindings/video/exynos_mixer.txt |4 2 files changed, 17

[PATCH v2 7/8] of/documentation: Update hpd gpio property for exynos_hdmi

From: Sachin Kamat Exynos SoCs use pinctrl to configure GPIOs. Update the document to reflect this change. Signed-off-by: Sachin Kamat Signed-off-by: Rahul Sharma --- Documentation/devicetree/bindings/video/exynos_hdmi.txt |6 ++ 1 file changed, 2

[PATCH v2 6/8] ARM: dts: exynos5420: add hdmi hpd gpio pinctrl node

Add pinctrl node for hdmi-hpd gpio pin to exynos5420 device tree files. Signed-off-by: Rahul Sharma --- arch/arm/boot/dts/exynos5420-smdk5420.dts | 11 +++ 1 file changed, 11 insertions(+) diff --git a/arch/arm/boot/dts/exynos5420-smdk5420.dts

[PATCH v2 5/8] ARM: dts: exynos5420: add clocks for hdmi subsystem

Add clocks for hdmi and mixer for exynos5420 SoC. Signed-off-by: Rahul Sharma --- 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 index 93caef7..5fa4093 100644 ---

[PATCH v2 4/8] ARM: dts: exynos5420: add dt nodes for hdmi subsystem

Add hdmi, mixer, ddc device tree nodes for Exynos 5420 SoC. Signed-off-by: Rahul Sharma --- arch/arm/boot/dts/exynos5420-smdk5420.dts | 20 arch/arm/boot/dts/exynos5420.dtsi |8 2 files changed, 28 insertions(+) diff --git

[PATCH v2 3/8] ARM: dts: exynos5250: move common hdmi properties to exynos5 dtsi

Hdmi Subsystem nodes shares many properties across exynos5 SoCs (exynos5250 and exyno5420). Common code is moved to exynos5.dtsi which is included in exyno5250 and exynos5420 SoC files. It also renames the hdmi and mixer nodes as per dt naming convention in the format name at phy_add.

[PATCH v2 2/8] ARM: dts: exynos5420: add i2c device nodes

From: Andrew Bresticker This adds device-tree nodes for the i2c busses on Exynos 5420 platforms. Signed-off-by: Andrew Bresticker Signed-off-by: Rahul Sharma --- arch/arm/boot/dts/exynos5420.dtsi | 32 1 file changed, 32 insertions(+)

[PATCH v2 1/8] ARM: dts: exynos5250: move common i2c properties to exynos5 dtsi

I2C nodes shares many properties across exynos5 SoCs (exynos5250 and exyno5420). Common code is moved to exynos5.dtsi which is included in exyno5250 and exynos5420 SoC files. Signed-off-by: Rahul Sharma --- arch/arm/boot/dts/exynos5.dtsi| 36 +

[PATCH v2 0/8] ARM: dts: exynos5420: add support for hdmi subsystem

Common properties for I2C and Hdmi Subsystem is moved to exynos5 dtsi file. It also adds Device tree nodes and clocks information for exynos5420 SoC. It adds pinctrl node for hdmi hpd gpio and update binding documents. This patch is based on v3.11-next/soc-exynos5420-pinctrl branch at

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

> -Original Message- > From: Lucas Stach [mailto:l.stach at pengutronix.de] > Sent: Thursday, June 20, 2013 4:47 PM > To: Inki Dae > Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho'; > 'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm- > kernel at

[PATCH] drm: Improve manual IRQ installation documentation

On Thu, Jun 20, 2013 at 01:00:36PM +0200, Thierry Reding wrote: > On Thu, Jun 20, 2013 at 12:46:21PM +0200, Laurent Pinchart wrote: > > Hi Thierry, > > > > On Thursday 20 June 2013 12:40:26 Thierry Reding wrote: > > > On Thu, Jun 20, 2013 at 12:17:25PM +0200, Laurent Pinchart wrote: > > > > On

[PATCH v3] drm: Renesas R-Car Display Unit DRM driver

On Wed, Jun 19, 2013 at 01:45:45AM +0200, Laurent Pinchart wrote: > Hello Adam, > > Ping ? > > Daniel, would it help getting the driver in v3.11 if I resubmit it now with a > get_modes operation that just returns 0 ? Yeah, I guess that works, too. -Daniel > > On Friday 14 June 2013 16:03:19

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

> -Original Message- > From: dri-devel-bounces+inki.dae=samsung.com at lists.freedesktop.org > [mailto:dri-devel-bounces+inki.dae=samsung.com at lists.freedesktop.org] On > Behalf Of Russell King - ARM Linux > Sent: Thursday, June 20, 2013 3:29 AM > To: Inki Dae > Cc: linux-fbdev; DRI

[pull] radeon drm-fixes-3.10

From: Alex Deucher Hi Dave, Just one more fix for radeon. Patch from Jerome to avoid GPU resets due to false positives when the ring is empty. The following changes since commit c139b1ee4e36374af705660af6172d7477352792: drm/radeon: fix UVD on big endian

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

* Maarten Lankhorst wrote: > Well they've helped me with some of the changes and contributed some > code and/or fixes, but if acked-by is preferred I'll use that.. Such contributions can be credited in the changelog, and/or copyright notices, and/or the code itself. The signoff chain on the

[PATCH] drm/shmobile: Drop usage of removed drm_plane enabled field

On Thu, Jun 20, 2013 at 12:45 AM, Laurent Pinchart wrote: > The enabled field has been removed from struct drm_plane. Don't use it > in the driver. Applied to -next, Dave.

[PATCH 1/1] gpu:drm:tilcdc: get preferred_bpp value from DT

>> >> Signed-off-by: Benoit Parrot > > Acked-by: Rob Clark Applied to -next, thanks, Dave.

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

Op 20-06-13 13:55, Ingo Molnar schreef: > * Maarten Lankhorst wrote: > >> Changes since RFC patch v1: >> - Updated to use atomic_long instead of atomic, since the reservation_id >> was a long. >> - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow >> - removed

[Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor

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

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

* Maarten Lankhorst wrote: > +The algorithm that TTM came up with for dealing with this problem is quite > +simple. [...] 'TTM' here reads like a person - but in reality it's the TTM graphics subsystem, right? Please clarify this portion of the text. Thanks, Ingo

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

|| -- 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/20130620/2ec56af5/attachment.html>

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

* Maarten Lankhorst wrote: > Changes since RFC patch v1: > - Updated to use atomic_long instead of atomic, since the reservation_id was > a long. > - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow > - removed mutex_locked_set_reservation_id (or w/e it was called) > Changes

[Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor

was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/6fee18aa/attachment.html>

[Bug 65958] GPU Lockup on Trinity 7500G

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/1823eb33/attachment.html>

[PATCH v5 7/7] locking-selftests: handle unexpected failures more strictly

When CONFIG_PROVE_LOCKING is not enabled, more tests are expected to pass unexpectedly, but there no tests that should start to fail that pass with CONFIG_PROVE_LOCKING enabled. Signed-off-by: Maarten Lankhorst --- lib/locking-selftest.c |8 +--- 1 file changed, 5 insertions(+), 3

[PATCH v5 6/7] mutex: add more ww tests to test EDEADLK path handling

Signed-off-by: Maarten Lankhorst --- lib/locking-selftest.c | 264 +++- 1 file changed, 261 insertions(+), 3 deletions(-) diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c index 37faefd..d554f3f 100644 --- a/lib/locking-selftest.c +++

[PATCH v5 5/7] mutex: add more tests to lib/locking-selftest.c

None of the ww_mutex codepaths should be taken in the 'normal' mutex calls. The easiest way to verify this is by using the normal mutex calls, and making sure o.ctx is unmodified. Signed-off-by: Maarten Lankhorst --- lib/locking-selftest.c | 62

[PATCH v5 4/7] mutex: Add ww tests to lib/locking-selftest.c. v5

This stresses the lockdep code in some ways specifically useful to ww_mutexes. It adds checks for most of the common locking errors. Changes since v1: - Add tests to verify reservation_id is untouched. - Use L() and U() macros where possible. Changes since v2: - Use the ww_mutex api directly.

[PATCH v5 3/7] mutex: w/w mutex slowpath debugging

From: Daniel Vetter Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

Changes since RFC patch v1: - Updated to use atomic_long instead of atomic, since the reservation_id was a long. - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow - removed mutex_locked_set_reservation_id (or w/e it was called) Changes since RFC patch v2: - remove use of

[PATCH v5 1/7] arch: make __mutex_fastpath_lock_retval return whether fastpath succeeded or not.

This will allow me to call functions that have multiple arguments if fastpath fails. This is required to support ticket mutexes, because they need to be able to pass an extra argument to the fail function. Originally I duplicated the functions, by adding __mutex_fastpath_lock_retval_arg. This

[PATCH v5 0/7] add mutex wait/wound/style style locks

Changes since v4: - Some documentation cleanups. - Added a lot more tests to cover all the DEBUG_LOCKS_WARN_ON cases. - Added EDEADLK tests. - Split off the normal mutex tests to a separate patch. - Added a patch to not allow tests to fail that succeed with PROVE_LOCKING enabled. --- Daniel

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

-- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/ef7d0ab4/attachment-0001.html>

[PATCH] drm: Improve manual IRQ installation documentation

solved by making the DRM_WAIT_ON() condition drop the > > !dev->irq_enabled in case DRIVER_HAVE_IRQ isn't set. > > Or we could force drivers to set drm->irq_enabled, I'm fine with that as > well. > I can fix the documentation if that would be the preferred solution. Thinking about it some more, the latter seems more appropriate. Consider some driver that doesn't set DRIVER_HAVE_IRQ but also doesn't initialize interrupts manually. If so it'll cause DRM_IOCTL_WAIT_VBLANK to block indefinitely. On the other hand perhaps the check at the beginning of drm_wait_vblank should be improved. Maybe make it something like this: if (drm_core_check_feature(dev, DRIVER_HAVE_IRQ)) if (!drm_dev_to_irq(dev)) return -EINVAL; if (!dev->irq_enabled) return -EINVAL; Thierry -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/2d9f4896/attachment.pgp>

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

her textures is already starting. -- 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/20130620/21da2ace/attachment.html>

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

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

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/1b611fdd/attachment.html>

[Bug 65968] New: Massive memory corruption in Planetary Annihilation Alpha

ent was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/5bce7ee3/attachment.html>

[PATCH] drm: Improve manual IRQ installation documentation

gt; you also need to manually set drm->irq_enabled = 1, as otherwise things > > > like DRM_IOCTL_WAIT_VBLANK won't work properly. > > > > That's only needed if DRIVER_HAVE_IRQ is set, otherwise the > > drm_wait_vblank() function skips the irq_enabled check. > > No

[PATCH] drm: Improve manual IRQ installation documentation

herwise the drm_wait_vblank() > function skips the irq_enabled check. Not quite. There's another check for dev->irq_enabled in the DRM_WAIT_ON() so it'll never actually block. Arguably this could be solved by making the DRM_WAIT_ON() condition drop the !dev->irq_enabled in case DRIVER_HAVE_IRQ isn't set. I'll see if I can find the time to come up with a patch. Thierry -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/dac54ffe/attachment-0001.pgp>

[PULL] drm-tegra-fixes

ves/dri-devel/attachments/20130620/3fe39495/attachment.pgp>

[GIT PULL FOR v3.11] shmob-drm patches

Hi Dave, Could you please pull the following four shmob-drm patches for v3.11 ? The following changes since commit dc28aa072f502433b6adc5c9ae8f56955c07580a: gpu:drm:tilcdc: get preferred_bpp value from DT (2013-06-20 14:08:01 +1000) are available in the git repository at:

[PATCH] drm: Improve manual IRQ installation documentation

his should mention that if you handle IRQ installation manually > you also need to manually set drm->irq_enabled = 1, as otherwise things > like DRM_IOCTL_WAIT_VBLANK won't work properly. That's only needed if DRIVER_HAVE_IRQ is set, otherwise the drm_wait_vblank() function skips the irq_en

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 17:24 +0900 schrieb Inki Dae: [...] > > > In addition, please see the below more detail examples. > > > > > > The conventional way (without dmabuf-sync) is: > > > Task A > > > > > > 1. CPU accesses buf > > > 2. Send the buf to Task B >

[PATCH] drm: Improve manual IRQ installation documentation

as otherwise things like DRM_IOCTL_WAIT_VBLANK won't work properly. Thierry -- next part -- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/47a949f9/attachment.pgp>

[PATCH 2/2] drm/qxl: add support for cursor hotspot.

From: Dave Airlie This uses the cursor hotspot info from userspace and passes it to the qxl hw layer. Signed-off-by: Dave Airlie --- drivers/gpu/drm/qxl/qxl_display.c | 16 1 file changed, 8 insertions(+), 8 deletions(-) diff --git

[PATCH 1/2] drm: add hotspot support for cursors.

From: Dave Airlie So it looks like for virtual hw cursors on QXL we need to inform the "hw" device what the cursor hotspot parameters are. This makes sense if you think the host has to draw the cursor and interpret clicks from it. However the current modesetting interface

[PATCH v3 2/3] drm/exynos: add support for exynos5420 mixer

Hello Rahul, This patch is exactly same with v2 2/4 and only rebased on v3 1/3, so my ack is valid for this patch. On 2013? 06? 19? 21:51, Rahul Sharma wrote: > Add support for exynos5420 mixer IP in the drm mixer driver. > > Signed-off-by: Rahul Sharma Acked-by: Seung-Woo Kim Anyway, this

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 09:17 +0100 schrieb Russell King - ARM Linux: > On Thu, Jun 20, 2013 at 09:47:07AM +0200, Lucas Stach wrote: > > Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae: > > > > > > > -Original Message- > > > > From:

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae: > > > -Original Message- > > From: dri-devel-bounces+inki.dae=samsung.com at lists.freedesktop.org > > [mailto:dri-devel-bounces+inki.dae=samsung.com at lists.freedesktop.org] On > > Behalf Of Russell King - ARM Linux > > Sent:

[PATCH v3 1/3] drm/exynos: add new compatible strings for hdmi subsystem

Hi Rahul, On Thursday 20 of June 2013 07:41:53 Rahul Sharma wrote: > Hi Tomasz, Lucas, > > How does this patch look to you ? Please share your views. Looks fine now. Have my Reviewed-by: Tomasz Figa for the whole series. Best regards, Tomasz > regards, > Rahul Sharma. > > On Wed, Jun 19,

[Bug 65958] GPU Lockup on Trinity 7500G

art -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/5d354bf6/attachment-0001.html>

[Bug 65958] New: GPU Lockup on Trinity 7500G

TML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/c4274402/attachment.html>

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

On Thu, Jun 20, 2013 at 09:47:07AM +0200, Lucas Stach wrote: > Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae: > > > > > -Original Message- > > > From: dri-devel-bounces+inki.dae=samsung.com at lists.freedesktop.org > > > [mailto:dri-devel-bounces+inki.dae=samsung.com at

[PATCH -next] drm/i915: fix potential NULL pointer dereference in i915_gem_context_get_hang_stats()

From: Wei Yongjun The dereference should be moved below the NULL test. Signed-off-by: Wei Yongjun --- drivers/gpu/drm/i915/i915_gem_context.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/drivers/gpu/drm/i915/i915_gem_context.c

[PATCH v3 1/3] drm/exynos: add new compatible strings for hdmi subsystem

Hi Tomasz, Lucas, How does this patch look to you ? Please share your views. regards, Rahul Sharma. On Wed, Jun 19, 2013 at 6:21 PM, Rahul Sharma wrote: > This patch adds new combatible strings for hdmi, mixer, ddc > and hdmiphy. It follows the convention of using compatible string > which

[Bug 58021] [BISECTED] nouveau, nv50: External VGA not detected anymore

https://bugzilla.kernel.org/show_bug.cgi?id=58021 wippbox at gmx.net changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

[RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

, there is no good idea: I had implemented the user interfaces in dma-buf framework but that was just to show you so ugly. The eventual purpose of my approach is to integrate sync interfaces with dmabuf sync, and this approach can be used commonly for v4l2, drm drivers, user processes, and so on: as I already mentioned in document file, this approach is for DMA devices using system memory as DMA buffer, especially most ARM SoCs. Thanks, Inki Dae > Regards, > Lucas > > -- > Pengutronix e.K. | Lucas Stach | > Industrial Linux Solutions | http://www.pengutronix.de/ | > Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-5076 | > Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | > > ___ > dri-devel mailing list > dri-devel at lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/dri-devel > -- next part -- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/dri-devel/attachments/20130620/7eb4db6c/attachment-0001.html>

[PATCH 0/5] clk/exynos5420: add clocks for hdmi subsystem

On 06/19/13 13:04, Rahul Sharma wrote: > + mike > Mike, I'm waiting for your reply on this. If you're OK, let me take this series on top of exynos5420 stuff in samsung tree. Of course, if any concerns, please let me know. Thanks, - Kukjin > On Tue, Jun 18, 2013 at 8:03 PM, Rahul Sharma >

RE: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

-Original Message- From: dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org [mailto:dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org] On Behalf Of Russell King - ARM Linux Sent: Thursday, June 20, 2013 3:29 AM To: Inki Dae Cc: linux-fbdev; DRI mailing list;

Re: [PATCH v3 1/3] drm/exynos: add new compatible strings for hdmi subsystem

Hi Rahul, On Thursday 20 of June 2013 07:41:53 Rahul Sharma wrote: Hi Tomasz, Lucas, How does this patch look to you ? Please share your views. Looks fine now. Have my Reviewed-by: Tomasz Figa t.f...@samsung.com for the whole series. Best regards, Tomasz regards, Rahul Sharma. On

[Bug 58021] [BISECTED] nouveau, nv50: External VGA not detected anymore

https://bugzilla.kernel.org/show_bug.cgi?id=58021 wipp...@gmx.net changed: What|Removed |Added Status|NEW |RESOLVED Resolution|

Re: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae: -Original Message- From: dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org [mailto:dri-devel-bounces+inki.dae=samsung@lists.freedesktop.org] On Behalf Of Russell King - ARM Linux Sent: Thursday, June

RE: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

-Original Message- From: Lucas Stach [mailto:l.st...@pengutronix.de] Sent: Thursday, June 20, 2013 4:47 PM To: Inki Dae Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho'; 'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm-

Re: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 09:17 +0100 schrieb Russell King - ARM Linux: On Thu, Jun 20, 2013 at 09:47:07AM +0200, Lucas Stach wrote: Am Donnerstag, den 20.06.2013, 15:43 +0900 schrieb Inki Dae: -Original Message- From:

[Bug 65958] New: GPU Lockup on Trinity 7500G

https://bugs.freedesktop.org/show_bug.cgi?id=65958 Priority: medium Bug ID: 65958 Assignee: dri-devel@lists.freedesktop.org Summary: GPU Lockup on Trinity 7500G Severity: normal Classification: Unclassified OS: Linux (All)

[Bug 65958] GPU Lockup on Trinity 7500G

https://bugs.freedesktop.org/show_bug.cgi?id=65958 --- Comment #1 from Mike Lothian m...@fireburn.co.uk --- Created attachment 81099 -- https://bugs.freedesktop.org/attachment.cgi?id=81099action=edit Lspci -- You are receiving this mail because: You are the assignee for the bug.

Re: [PATCH] drm: Improve manual IRQ installation documentation

On Wed, Jun 19, 2013 at 02:00:45PM +0200, Laurent Pinchart wrote: Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com --- Documentation/DocBook/drm.tmpl | 14 -- 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/Documentation/DocBook/drm.tmpl

Re: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

Am Donnerstag, den 20.06.2013, 17:24 +0900 schrieb Inki Dae: [...] In addition, please see the below more detail examples. The conventional way (without dmabuf-sync) is: Task A 1. CPU accesses buf 2. Send the buf to Task B 3. Wait for the buf

Re: [PATCH] drm: Improve manual IRQ installation documentation

Hi Thierry, On Thursday 20 June 2013 12:10:47 Thierry Reding wrote: On Wed, Jun 19, 2013 at 02:00:45PM +0200, Laurent Pinchart wrote: Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com --- Documentation/DocBook/drm.tmpl | 14 -- 1 file changed, 8

[GIT PULL FOR v3.11] shmob-drm patches

Hi Dave, Could you please pull the following four shmob-drm patches for v3.11 ? The following changes since commit dc28aa072f502433b6adc5c9ae8f56955c07580a: gpu:drm:tilcdc: get preferred_bpp value from DT (2013-06-20 14:08:01 +1000) are available in the git repository at:

[PULL] drm-tegra-fixes

Hi Dave, The following changes since commit c7788792a5e7b0d5d7f96d0766b4cb6112d47d75: Linux 3.10-rc2 (2013-05-20 14:37:38 -0700) are available in the git repository at: git://anongit.freedesktop.org/tegra/linux.git drm/fixes for you to fetch changes up to

Re: [PATCH] drm: Improve manual IRQ installation documentation

On Thu, Jun 20, 2013 at 12:17:25PM +0200, Laurent Pinchart wrote: Hi Thierry, On Thursday 20 June 2013 12:10:47 Thierry Reding wrote: On Wed, Jun 19, 2013 at 02:00:45PM +0200, Laurent Pinchart wrote: Signed-off-by: Laurent Pinchart laurent.pinchart+rene...@ideasonboard.com ---

Re: [PATCH] drm: Improve manual IRQ installation documentation

Hi Thierry, On Thursday 20 June 2013 12:40:26 Thierry Reding wrote: On Thu, Jun 20, 2013 at 12:17:25PM +0200, Laurent Pinchart wrote: On Thursday 20 June 2013 12:10:47 Thierry Reding wrote: On Wed, Jun 19, 2013 at 02:00:45PM +0200, Laurent Pinchart wrote: Signed-off-by: Laurent Pinchart

Re: [PATCH] drm: Improve manual IRQ installation documentation

On Thu, Jun 20, 2013 at 12:46:21PM +0200, Laurent Pinchart wrote: Hi Thierry, On Thursday 20 June 2013 12:40:26 Thierry Reding wrote: On Thu, Jun 20, 2013 at 12:17:25PM +0200, Laurent Pinchart wrote: On Thursday 20 June 2013 12:10:47 Thierry Reding wrote: On Wed, Jun 19, 2013 at

RE: [RFC PATCH v2] dmabuf-sync: Introduce buffer synchronization framework

-Original Message- From: Lucas Stach [mailto:l.st...@pengutronix.de] Sent: Thursday, June 20, 2013 7:11 PM To: Inki Dae Cc: 'Russell King - ARM Linux'; 'Inki Dae'; 'linux-fbdev'; 'YoungJun Cho'; 'Kyungmin Park'; 'myungjoo.ham'; 'DRI mailing list'; linux-arm-

[PATCH v5 1/7] arch: make __mutex_fastpath_lock_retval return whether fastpath succeeded or not.

This will allow me to call functions that have multiple arguments if fastpath fails. This is required to support ticket mutexes, because they need to be able to pass an extra argument to the fail function. Originally I duplicated the functions, by adding __mutex_fastpath_lock_retval_arg. This

[PATCH v5 0/7] add mutex wait/wound/style style locks

Changes since v4: - Some documentation cleanups. - Added a lot more tests to cover all the DEBUG_LOCKS_WARN_ON cases. - Added EDEADLK tests. - Split off the normal mutex tests to a separate patch. - Added a patch to not allow tests to fail that succeed with PROVE_LOCKING enabled. --- Daniel

[PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

Changes since RFC patch v1: - Updated to use atomic_long instead of atomic, since the reservation_id was a long. - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow - removed mutex_locked_set_reservation_id (or w/e it was called) Changes since RFC patch v2: - remove use of

[PATCH v5 4/7] mutex: Add ww tests to lib/locking-selftest.c. v5

This stresses the lockdep code in some ways specifically useful to ww_mutexes. It adds checks for most of the common locking errors. Changes since v1: - Add tests to verify reservation_id is untouched. - Use L() and U() macros where possible. Changes since v2: - Use the ww_mutex api directly.

[PATCH v5 3/7] mutex: w/w mutex slowpath debugging

From: Daniel Vetter daniel.vet...@ffwll.ch Injects EDEADLK conditions at pseudo-random interval, with exponential backoff up to UINT_MAX (to ensure that every lock operation still completes in a reasonable time). This way we can test the wound slowpath even for ww mutex users where contention is

[PATCH v5 5/7] mutex: add more tests to lib/locking-selftest.c

None of the ww_mutex codepaths should be taken in the 'normal' mutex calls. The easiest way to verify this is by using the normal mutex calls, and making sure o.ctx is unmodified. Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com --- lib/locking-selftest.c | 62

[PATCH v5 6/7] mutex: add more ww tests to test EDEADLK path handling

Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com --- lib/locking-selftest.c | 264 +++- 1 file changed, 261 insertions(+), 3 deletions(-) diff --git a/lib/locking-selftest.c b/lib/locking-selftest.c index 37faefd..d554f3f 100644 ---

[PATCH v5 7/7] locking-selftests: handle unexpected failures more strictly

When CONFIG_PROVE_LOCKING is not enabled, more tests are expected to pass unexpectedly, but there no tests that should start to fail that pass with CONFIG_PROVE_LOCKING enabled. Signed-off-by: Maarten Lankhorst maarten.lankho...@canonical.com --- lib/locking-selftest.c |8 +--- 1 file

Re: [PATCH v5 2/7] mutex: add support for wound/wait style locks, v5

Op 20-06-13 13:55, Ingo Molnar schreef: * Maarten Lankhorst maarten.lankho...@canonical.com wrote: Changes since RFC patch v1: - Updated to use atomic_long instead of atomic, since the reservation_id was a long. - added mutex_reserve_lock_slow and mutex_reserve_lock_intr_slow - removed

[Bug 65968] New: Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 Priority: medium Bug ID: 65968 Assignee: dri-devel@lists.freedesktop.org Summary: Massive memory corruption in Planetary Annihilation Alpha Severity: normal

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 --- Comment #2 from Andreas Ringlstetter andreas.ringlstet...@gmail.com --- Created attachment 81107 -- https://bugs.freedesktop.org/attachment.cgi?id=81107action=edit glxinfo log -- You are receiving this mail because: You are the assignee

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 Andreas Ringlstetter andreas.ringlstet...@gmail.com changed: What|Removed |Added Attachment #81105|0 |1

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 --- Comment #4 from Andreas Ringlstetter andreas.ringlstet...@gmail.com --- PS: I will not be able to test with 9.0 or 9.1 since one of the shaders causes a segfault while compiling in these version. This has only recently (last 1-2 months) been

[Bug 65958] GPU Lockup on Trinity 7500G

https://bugs.freedesktop.org/show_bug.cgi?id=65958 --- Comment #2 from Alex Deucher ag...@yahoo.com --- Does setting the env var RADEON_VA=0 in your /etc/environment fix the issue? This looks like a mesa issue. -- You are receiving this mail because: You are the assignee for the bug.

[Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor

https://bugs.freedesktop.org/show_bug.cgi?id=65963 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Assignee|xorg-driver-...@lists.x.org

[Bug 65968] Massive memory corruption in Planetary Annihilation Alpha

https://bugs.freedesktop.org/show_bug.cgi?id=65968 Alex Deucher ag...@yahoo.com changed: What|Removed |Added Attachment #81105|text/plain |image/jpeg mime

[Bug 65963] screen goes blank, Linux hangs - Radeon 7870, Gallium, Glamor

https://bugs.freedesktop.org/show_bug.cgi?id=65963 --- Comment #2 from Damian Nowak nowa...@geozone.pl --- Thanks for taking a look at it. Package versions as follows. Pasting a PKGBUILDs so you can see the flags for compilation. extra/mesa 9.1.3-1

Re: [PATCH v3] drm: Renesas R-Car Display Unit DRM driver

On Wed, Jun 19, 2013 at 01:45:45AM +0200, Laurent Pinchart wrote: Hello Adam, Ping ? Daniel, would it help getting the driver in v3.11 if I resubmit it now with a get_modes operation that just returns 0 ? Yeah, I guess that works, too. -Daniel On Friday 14 June 2013 16:03:19 Daniel

  1   2   >