[PATCH] fixing dmi match for hp t5745 and hp st5747 thin client

On Wed, May 02, 2012 at 01:44:15PM -0400, Adam Jackson wrote: > On 5/1/12 1:37 PM, Marc Gariepy wrote: > >Match the correct information which is DMI_PRODUCT_NAME instead of > >DMI_BOARD_NAME > >See dmidecode information on launchpad for both thin client: > > >

Linux 3.4-rc4

On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote: > Hi Luca, Maarten, > > On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote: > > On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis > gmail.com> wrote: > > > On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov > > > > > > wrote: > > >>

[PATCH] nouveau: initialise has_optimus variable.

From: Dave Airlie We should initialise this to 0 really to avoid getting false positives. Signed-off-by: Dave Airlie --- drivers/gpu/drm/nouveau/nouveau_acpi.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/nouveau/nouveau_acpi.c

[PATCH 13/13] gma500: mdfld_dsi_dpi_mode_set() do not corrupt DSPSTRIDE

From: Kirill A. Shutemov The proper stride value set in mdfld__intel_pipe_set_base(). TODO: move tc35876x support to separate driver and get rid of all if (mdfld_get_panel_type(dev, pipe) == TC35876X) { ... } Signed-off-by: Kirill A. Shutemov Signed-off-by:

[PATCH 12/13] gma500: mid-bios: rewrite VBT/GCT handling in a cleaner way

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/mid_bios.c| 295 +++--- drivers/gpu/drm/gma500/oaktrail.h| 25 +--

[PATCH 11/13] gma500: fix -Wmissing-include-dirs warnings

From: Kirill A. Shutemov cc1: warning: include/drm: No such file or directory [enabled by default] It's reproducible if you build with O=/some/obj/dir and W=1. Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/Makefile |

[PATCH 10/13] gma500: cdv_intel_lvds: mark cdv_intel_lvds_enc_funcs as static

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/cdv_intel_lvds.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/gma500/cdv_intel_lvds.c

[PATCH 09/13] gma500: oaktrail_hdmi_i2c_handler(): base should be __iomem

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/oaktrail_hdmi_i2c.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/gma500/oaktrail_hdmi_i2c.c

[PATCH 08/13] gma500: lid_state should be __iomem

From: Kirill A. Shutemov This was mostly already fixed but this one change is needed to match Kirill's original submission Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/opregion.c |2 +- 1 files changed, 1

[PATCH 07/13] gma500: psb_irq_turn_off_dpst() fix bit operation

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/psb_irq.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/gma500/psb_irq.c

[PATCH 06/13] gma500: framebuffer: mark psb_fb_helper_funcs as static

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/framebuffer.c |2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/gma500/framebuffer.c

[PATCH 05/13] gma500: vram_addr should be __iomem

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/framebuffer.c |3 +-- drivers/gpu/drm/gma500/psb_drv.h |2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 04/13] gma500: sgx_reg and vdc_reg should be __iomem

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/psb_drv.h |4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/gma500/psb_drv.h

[PATCH 03/13] gma500: gtt: fix __iomem sparse warnings

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/gtt.c | 11 +++ drivers/gpu/drm/gma500/psb_drv.h |2 +- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git

[PATCH 02/13] gma500: psb_gtt_init(): drop unused variable

From: Kirill A. Shutemov Signed-off-by: Kirill A. Shutemov Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/gtt.c |3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/gma500/gtt.c b/drivers/gpu/drm/gma500/gtt.c index

[PATCH 01/13] gma500: address the lid code

From: Alan Cox We need this for Poulsbo Signed-off-by: Alan Cox --- drivers/gpu/drm/gma500/psb_drv.c |2 +- drivers/gpu/drm/gma500/psb_drv.h |1 - drivers/gpu/drm/gma500/psb_lid.c |2 +- 3 files changed, 2 insertions(+), 3 deletions(-) diff --git

[PATCH 00/13] More GMA500 work

This follows on from the last set and sorts out the lid regression they caused on the Poulsbo devices. It then includes another pile of clean up work and Medfield fixes from Kirill. --- Alan Cox (1): gma500: address the lid code Kirill A. Shutemov (12): gma500:

[PATCH 3/4] drm/radeon: rework fence handling, drop fence list

On 5/2/12 4:20 PM, j.glisse at gmail.com wrote: > + /* there is small chance that we overwritte a bigger last_emited > + * value, but in normal usage this > + */ Seems unfinished. Also "overwrite". - ajax

[PATCH] nouveau: initialise has_optimus variable.

On 5/2/12 3:24 PM, Dave Airlie wrote: > From: Dave Airlie > > We should initialise this to 0 really to avoid getting false positives. > > Signed-off-by: Dave Airlie Reviewed-by: Adam Jackson - ajax

[PATCH] drm/radeon: avoid leaking const ib (not used yet on si and newer GPU)

On Wed, May 2, 2012 at 4:24 PM, wrote: > From: Jerome Glisse > > Signed-off-by: Jerome Glisse Reviewed-by: Alex Deucher > --- > ?drivers/gpu/drm/radeon/radeon_cs.c | ? ?5 + > ?1 files changed, 5 insertions(+), 0 deletions(-) > > diff --git a/drivers/gpu/drm/radeon/radeon_cs.c >

[Bug 30383] [RADEON:KMS::R600C] GPU lockup / driver hang when playing ufoai

https://bugs.freedesktop.org/show_bug.cgi?id=30383 T?r?k Edwin changed: What|Removed |Added Status|NEW |RESOLVED

[PATCH] drm/radeon: avoid leaking const ib (not used yet on si and newer GPU)

From: Jerome Glisse Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_cs.c |5 + 1 files changed, 5 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_cs.c b/drivers/gpu/drm/radeon/radeon_cs.c index 82f2e7b0..b3800cb 100644 ---

[PATCH 4/4] drm/radeon: improve sa allocator to agressivly free idle bo

From: Jerome Glisse With fence rework it's now easier to agressivly free idle bo when there is no hole to satisfy current allocation request. The hit of some cs ioctl to have to go through the sa bo list and free them is minimal, it happens once in while and avoid some fence

[PATCH 3/4] drm/radeon: rework fence handling, drop fence list

From: Jerome Glisse Using 64bits fence sequence we can directly compare sequence number to know if a fence is signaled or not. Thus the fence list became useless, so does the fence lock that mainly protected the fence list. Things like ring.ready are no longer behind a lock,

[PATCH 2/4] drm/radeon: convert fence to uint64_t

From: Jerome Glisse This convert fence to use uint64_t sequence number intention is to use the fact that uin64_t is big enough that we don't need to care about wrap around. Tested with and without writeback using 0xF000 as initial fence sequence and thus allowing to test

[PATCH 1/4] drm/radeon: allow to allocate adjacent scratch reg

From: Jerome Glisse This add the number of adjacent scratch reg you want to allocate or free to the scratch alloc/free function. Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/r100.c | 12 ++-- drivers/gpu/drm/radeon/r420.c |4 ++--

[RFC] Convert fence to use 64bits sequence

So this patchset convert the fence to use 64bits sequence and simplify the fence code (dropping fence lock). I am still convinced that the best solution is to have the various helper code deals with fence cleanup/processing. The last patch show an example of what can be done to improve sa

[PATCH] dri2proto: Fix documented opcodes

On Wed, May 2, 2012 at 3:03 PM, Chad Versace wrote: > Fix the documented opcodes in dri2proto.txt to be consistent with the > actual opcode values in dri2proto.h and in xcb/proto:src/dri2.xml. (It > looks like the opcodes were incorrect due to copy-paste errors). Looks correct to me. Kristian

[PATCH 17/17] drm/radeon: remove cayman_gpu_is_lockup

Since it is now identical to evergreen_gpu_is_lockup. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/ni.c | 19 --- drivers/gpu/drm/radeon/radeon_asic.c | 12 ++-- drivers/gpu/drm/radeon/radeon_asic.h |1 - 3 files

[PATCH 16/17] drm/radeon: remove r300_gpu_is_lockup

Since it is now identical to r100_gpu_is_lockup. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/r300.c| 14 -- drivers/gpu/drm/radeon/radeon_asic.c | 16 drivers/gpu/drm/radeon/radeon_asic.h |1 - 3 files

[PATCH 15/17] drm/radeon: make forcing ring activity a common function

Nothing chipset or ring specific with it, so also move it to radon_ring. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/evergreen.c | 10 +- drivers/gpu/drm/radeon/ni.c | 11 +-- drivers/gpu/drm/radeon/r100.c| 10

[PATCH 14/17] drm/radeon: unlock the ring mutex while waiting for the next fence

Fixing just another deadlock problem with gpu reset tests. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_ring.c |2 ++ 1 files changed, 2 insertions(+), 0 deletions(-) diff --git a/drivers/gpu/drm/radeon/radeon_ring.c

[PATCH 13/17] drm/radeon: make lockup timeout a module param

Don't hard code the 10 seconds timeout. Compute jobs can run much longer. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |1 + drivers/gpu/drm/radeon/radeon_drv.c |4 drivers/gpu/drm/radeon/radeon_ring.c |2 +- 3 files

[PATCH 12/17] drm/radeon: move lockup detection code into radeon_ring.c

It isn't chipset specific, so it makes no sense to have that inside r100.c. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/evergreen.c |5 +-- drivers/gpu/drm/radeon/ni.c |5 +-- drivers/gpu/drm/radeon/r100.c| 57

[PATCH 11/17] drm/radeon: rework recursive gpu reset handling

Instead of all this humpy pumpy with recursive mutex (which also fixes only halve of the problem) move the actual gpu reset out of the fence code, return -EDEADLK and then reset the gpu in the calling ioctl function. v2: Split removal of radeon_mutex into separate patch. Return -EAGAIN if

[PATCH 10/17] drm/radeon: fix a bug with the ring syncing code

Rings need to lock in order, otherwise the ring subsystem can deadlock. v2: fix error handling and number of locked doublewords. v3: stop creating unneeded semaphores. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |4 ++

[PATCH 09/17] drm/radeon: don't keep list of created fences.

It's never used and so practically superfluous. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |1 - drivers/gpu/drm/radeon/radeon_fence.c |7 --- 2 files changed, 0 insertions(+), 8 deletions(-) diff --git

[PATCH 08/17] drm/radeon: rename fence_wait_last to fence_wait_empty

As discussed with Michel that name better describes the behavior of this function. Signed-off-by: Christian K?nig Reviewed-by: Michel D?nzer Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h|2 +- drivers/gpu/drm/radeon/radeon_device.c |2 +-

[PATCH 07/17] drm/radeon: return -ENOENT in fence_wait_next v2

We should signal the caller that we haven't waited at all. v2: only change fence_wait_next not fence_wait_last. Signed-off-by: Christian K?nig Reviewed-by: Michel D?nzer Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_fence.c |2 +- 1 files changed, 1 insertions(+), 1

[PATCH 06/17] drm/radeon: fix a bug in the SA code

Aligning offset can make it bigger than tmp->offset leading to an overrun bug in the following subtraction. v2: Against initial suspicions this can't happen in mainline, so no need to push it into stable. Signed-off-by: Christian K?nig Reviewed-by: Michel D?nzer Reviewed-by: Jerome Glisse

[PATCH 05/17] drm/radeon: rework gpu lockup detection and processing

Previusly multiple rings could trigger multiple GPU resets at the same time. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |3 +- drivers/gpu/drm/radeon/radeon_fence.c | 146 + 2 files changed, 75

[PATCH 04/17] drm/radeon: use central function for IB testing

Removing all the different error messages and having just one standard behaviour over all chipset generations. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/evergreen.c |7 ++- drivers/gpu/drm/radeon/ni.c |

[PATCH 03/17] drm/radeon: register ring debugfs handlers on init

Just register the debugfs files on init instead of checking the chipset type multiple times. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_ring.c | 31 +++ 1 files changed, 19 insertions(+),

[PATCH 02/17] drm/radeon: replace gpu_lockup with ring->ready flag

It makes no sense at all to have more than one flag. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/r100.c |1 - drivers/gpu/drm/radeon/r300.c |1 - drivers/gpu/drm/radeon/radeon.h|1 -

[PATCH 01/17] drm/radeon: make radeon_gpu_is_lockup a per ring function

Different rings have different criteria to test if they are stuck. v2: rebased on current drm-next Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |4 +- drivers/gpu/drm/radeon/radeon_asic.c | 44

Include request for reset-rework branch v4

Hi Dave, there still seems to be the need for some further discussion about the SA code, so I again split that out of the patchset and tested the result a bit. Most of the stuff still works fine without those offending changes, so to avoid mailing around unrelated and already reviewed patches, I

[PATCH] fixing dmi match for hp t5745 and hp st5747 thin client

On 5/1/12 1:37 PM, Marc Gariepy wrote: > Match the correct information which is DMI_PRODUCT_NAME instead of > DMI_BOARD_NAME > See dmidecode information on launchpad for both thin client: > > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/911920 >

[PATCH] drm/kms: driver for virtual cirrus under qemu

On 5/2/12 6:27 AM, Dave Airlie wrote: > From: Dave Airlie > > This is the initial driver for emulated cirrus GPU found in qemu. > This driver only supports the emulated GPU and doesn't attempt > to bind to any real cirrus GPUs. In particular, > +/* only bind to the cirrus chip in qemu */ >

Include request for reset-rework branch v3

On 02.05.2012 12:32, Dave Airlie wrote: > On Wed, May 2, 2012 at 10:04 AM, Christian K?nig > wrote: >> On 02.05.2012 06:04, Jerome Glisse wrote: >>> On Wed, May 2, 2012 at 12:00 AM,wrote: Ok so i reread stuff and the : drm/radeon: add general purpose fence signaled callback is

Include request for reset-rework branch v3

2012/5/2 Christian K?nig : > On 02.05.2012 06:04, Jerome Glisse wrote: >> >> On Wed, May 2, 2012 at 12:00 AM, ?wrote: >>> >>> Ok so i reread stuff and the : >>> drm/radeon: add general purpose fence signaled callback >>> is a big NAK actually. It change the paradigm. Moving most of >>> the

[PATCH] drm/radeon: add connector table for SAM440ep embedded board

From: Alex Deucher RV250 found on ppc embedded boards. Cc: Hans Verkuil Signed-off-by: Alex Deucher --- drivers/gpu/drm/radeon/radeon_combios.c | 66 +++ drivers/gpu/drm/radeon/radeon_mode.h|1 + 2 files changed, 67

[PATCH] dri2proto: Fix documented opcodes

Fix the documented opcodes in dri2proto.txt to be consistent with the actual opcode values in dri2proto.h and in xcb/proto:src/dri2.xml. (It looks like the opcodes were incorrect due to copy-paste errors). CC: Kristian H?gsberg --- dri2proto.txt | 18 +- 1 file changed, 9

Include request for reset-rework branch v4

On Wed, May 2, 2012 at 9:11 AM, Christian K?nig wrote: > Hi Dave, > > there still seems to be the need for some further discussion about the SA > code, > so I again split that out of the patchset and tested the result a bit. > > Most of the stuff still works fine without those offending

[PATCH 3/3] drm/radeon: rework ib and semaphore to take advantage of sa allocator

From: Jerome Glisse Both ib and semaphore are always associated with a fence, rework the sa allocator to store the fence in the sa_bo allowing sa allocator to wait for a fence and retry allocation. This also simplify the ib & semaphore code. Simpify semaphore code to use the

[PATCH 2/3] drm/radeon: rip out the ib pool v4

From: Christian K?nig It isn't necessary any more and the suballocator seems to perform even better. v2: ignore ERESTARTSYS in error reporting, split fence changes into seperate patch, use try_free SA callback to avoid lockups v3: rebase on top of sa manager new

[PATCH 1/3] drm/radeon: improve sa allocator (add fence and make it self contain)

From: Jerome Glisse This patch is ground work for having the sa allocator as a standalone self contained helper. Each sa_bo can be associated with a fence and when allocating new one you can ask to block until there is room for satisfying your request. It also change the sa

Include request for reset-rework branch v4 PART2

So here are sa improvement, ib pool cleanup and semaphore cleanup. Those are Christian patches rebased on top of its last 17 patchset and on top of sa allocator change. The idea is that the sa_bo struct is not free until associated fence is signaled. Meanwhile the ib structure or the

Include request for reset-rework branch v3

On Wed, May 2, 2012 at 10:04 AM, Christian K?nig wrote: > On 02.05.2012 06:04, Jerome Glisse wrote: >> >> On Wed, May 2, 2012 at 12:00 AM, ?wrote: >>> >>> Ok so i reread stuff and the : >>> drm/radeon: add general purpose fence signaled callback >>> is a big NAK actually. It change the paradigm.

[PATCH] drm/kms: driver for virtual cirrus under qemu

From: Dave Airlie This is the initial driver for emulated cirrus GPU found in qemu. This driver only supports the emulated GPU and doesn't attempt to bind to any real cirrus GPUs. This driver is intended to be used with xf86-video-modesetting in userspace. This follow the

Include request for reset-rework branch v3

On 02.05.2012 06:04, Jerome Glisse wrote: > On Wed, May 2, 2012 at 12:00 AM, wrote: >> Ok so i reread stuff and the : >> drm/radeon: add general purpose fence signaled callback >> is a big NAK actually. It change the paradigm. Moving most of >> the handling into the irq process which is something

[PATCH] drm/radeon: Original Radeons had PCI GART, not PCIe GART.

From: Michel D?nzer Just a cosmetic fix to make dmesg a little less confusing. Signed-off-by: Michel D?nzer --- drivers/gpu/drm/radeon/r100.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/r100.c

[PATCH 07/27] drm/radeon: add proper locking to the SA v3

On 01.05.2012 19:19, j.glisse at gmail.com wrote: > From: Christian K?nig > > Make the suballocator self containing to locking. > > v2: split the bugfix into a seperate patch. > v3: Jerome Glisse use mutex, no reason to use spinlock that > are more heavyweight than mutex NAK,

Include request for reset-rework branch v3

On Wed, May 2, 2012 at 7:25 AM, Christian K?nig wrote: > On 02.05.2012 12:32, Dave Airlie wrote: >> >> On Wed, May 2, 2012 at 10:04 AM, Christian K?nig >> ?wrote: >>> >>> On 02.05.2012 06:04, Jerome Glisse wrote: On Wed, May 2, 2012 at 12:00 AM, ? ?wrote: > > Ok so i reread

Linux 3.4-rc4

Hi Luca, Maarten, On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote: > On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis > wrote: > > On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov > > > > wrote: > >> On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick Bowler wrote: > >>> On 2012-04-28

[PATCH] drm/radeon: Original Radeons had PCI GART, not PCIe GART.

2012/5/2 Michel D?nzer : > From: Michel D?nzer > > Just a cosmetic fix to make dmesg a little less confusing. > > Signed-off-by: Michel D?nzer Reviewed-by: Alex Deucher > --- > ?drivers/gpu/drm/radeon/r100.c | ? ?2 +- > ?1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git

Include request for reset-rework branch v3

On Wed, May 2, 2012 at 12:00 AM, wrote: > Ok so i reread stuff and the : > drm/radeon: add general purpose fence signaled callback > is a big NAK actually. It change the paradigm. Moving most of > the handling into the irq process which is something i am intimatly > convinced we should avoid. >

[PATCH 13/13] drm/radeon: add fence and retry to sa allocator v2

From: Jerome Glisse This allow to associate a fence with sa bo and retry and wait if sa bo alloc can block. v2: bug fixes Signed-off-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h | 10 ++- drivers/gpu/drm/radeon/radeon_cs.c|4 +-

[PATCH 12/13] drm/radeon: don't keep list of created fences.

From: Christian K?nig It's never used and so practically superfluous. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |1 - drivers/gpu/drm/radeon/radeon_fence.c |7 --- 2 files changed, 0 insertions(+),

[PATCH 11/13] drm/radeon: rename fence_wait_last to fence_wait_empty

From: Christian K?nig As discussed with Michel that name better describes the behavior of this function. Signed-off-by: Christian K?nig Reviewed-by: Michel D?nzer Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h|2 +-

[PATCH 10/13] drm/radeon: return -ENOENT in fence_wait_next v2

From: Christian K?nig We should signal the caller that we haven't waited at all. v2: only change fence_wait_next not fence_wait_last. Signed-off-by: Christian K?nig Reviewed-by: Michel D?nzer Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_fence.c |

[PATCH 09/13] drm/radeon: improve sa allocator v2

From: Jerome Glisse The sa allocator is suppose to be a ring allocator, ie allocation happen first at the end and if there is no more room we start at the begining again. This patch make the code match this design. sa_manager keep track of the start & end hole, it first try

[PATCH 08/13] drm/radeon: add sub allocator debugfs file

From: Christian K?nig Dumping the current allocations. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_object.h |5 + drivers/gpu/drm/radeon/radeon_ring.c | 22 ++

[PATCH 07/13] drm/radeon: add proper locking to the SA

From: Christian K?nig Make the suballocator self containing to locking. v2: split the bugfix into a seperate patch. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h|1 + drivers/gpu/drm/radeon/radeon_sa.c | 17

[PATCH 06/13] drm/radeon: fix a bug in the SA code

From: Christian K?nig Aligning offset can make it bigger than tmp->offset leading to an overrun bug in the following subtraction. v2: Against initial suspicions this can't happen in mainline, so no need to push it into stable. Signed-off-by: Christian K?nig

[PATCH 05/13] drm/radeon: rework gpu lockup detection and processing

From: Christian K?nig Previusly multiple rings could trigger multiple GPU resets at the same time. Signed-off-by: Christian K?nig Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |3 +- drivers/gpu/drm/radeon/radeon_fence.c | 150

[PATCH 04/13] drm/radeon: use central function for IB testing

From: Christian K?nig Removing all the different error messages and having just one standard behaviour over all chipset generations. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/evergreen.c |7

[PATCH 03/13] drm/radeon: register ring debugfs handlers on init

From: Christian K?nig Just register the debugfs files on init instead of checking the chipset type multiple times. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon_ring.c | 31

[PATCH 02/13] drm/radeon: replace gpu_lockup with ring->ready flag

From: Christian K?nig It makes no sense at all to have more than one flag. Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/r100.c |1 - drivers/gpu/drm/radeon/r300.c |1 -

[PATCH 01/13] drm/radeon: make radeon_gpu_is_lockup a per ring function

From: Christian K?nig Different rings have different criteria to test if they are stuck. v2: rebased on current drm-next Signed-off-by: Christian K?nig Reviewed-by: Alex Deucher Reviewed-by: Jerome Glisse --- drivers/gpu/drm/radeon/radeon.h |4 +-

Include request for reset-rework branch v3

Ok so i reread stuff and the : drm/radeon: add general purpose fence signaled callback is a big NAK actually. It change the paradigm. Moving most of the handling into the irq process which is something i am intimatly convinced we should avoid. Here is the patchset up to ib pool cleanup. I have

Re: [PATCH 07/27] drm/radeon: add proper locking to the SA v3

On 01.05.2012 19:19, j.gli...@gmail.com wrote: From: Christian Königdeathsim...@vodafone.de Make the suballocator self containing to locking. v2: split the bugfix into a seperate patch. v3: Jerome Glisse use mutex, no reason to use spinlock that are more heavyweight than mutex NAK,

[PATCH] drm/radeon: Original Radeons had PCI GART, not PCIe GART.

From: Michel Dänzer michel.daen...@amd.com Just a cosmetic fix to make dmesg a little less confusing. Signed-off-by: Michel Dänzer michel.daen...@amd.com --- drivers/gpu/drm/radeon/r100.c |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/radeon/r100.c

Re: Linux 3.4-rc4

Hi Luca, Maarten, On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote: On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com wrote: On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov dmitry.torok...@gmail.com wrote: On Sat, Apr 28, 2012 at 11:33:50AM -0400, Nick

Re: Re: Include request for reset-rework branch v3

On 02.05.2012 06:04, Jerome Glisse wrote: On Wed, May 2, 2012 at 12:00 AM,j.gli...@gmail.com wrote: Ok so i reread stuff and the : drm/radeon: add general purpose fence signaled callback is a big NAK actually. It change the paradigm. Moving most of the handling into the irq process which is

[PATCH] drm/kms: driver for virtual cirrus under qemu

From: Dave Airlie airl...@redhat.com This is the initial driver for emulated cirrus GPU found in qemu. This driver only supports the emulated GPU and doesn't attempt to bind to any real cirrus GPUs. This driver is intended to be used with xf86-video-modesetting in userspace. This follow the

Re: Re: Include request for reset-rework branch v3

On Wed, May 2, 2012 at 10:04 AM, Christian König deathsim...@vodafone.de wrote: On 02.05.2012 06:04, Jerome Glisse wrote: On Wed, May 2, 2012 at 12:00 AM,j.gli...@gmail.com  wrote: Ok so i reread stuff and the : drm/radeon: add general purpose fence signaled callback is a big NAK actually.

Re: Include request for reset-rework branch v3

On 02.05.2012 12:32, Dave Airlie wrote: On Wed, May 2, 2012 at 10:04 AM, Christian König deathsim...@vodafone.de wrote: On 02.05.2012 06:04, Jerome Glisse wrote: On Wed, May 2, 2012 at 12:00 AM,j.gli...@gmail.comwrote: Ok so i reread stuff and the : drm/radeon: add general purpose fence

Re: Linux 3.4-rc4

On Wed, 2012-05-02 at 09:54 +0200, Jean Delvare wrote: Hi Luca, Maarten, On Monday 30 April 2012 01:01:30 pm Luca Tettamanti wrote: On Mon, Apr 30, 2012 at 11:07 AM, Maarten Maathuis madman2...@gmail.com wrote: On Mon, Apr 30, 2012 at 12:37 AM, Dmitry Torokhov

Include request for reset-rework branch v4

Hi Dave, there still seems to be the need for some further discussion about the SA code, so I again split that out of the patchset and tested the result a bit. Most of the stuff still works fine without those offending changes, so to avoid mailing around unrelated and already reviewed patches, I

[PATCH 02/17] drm/radeon: replace gpu_lockup with ring-ready flag

It makes no sense at all to have more than one flag. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Alex Deucher alexander.deuc...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/r100.c |1 - drivers/gpu/drm/radeon/r300.c

[PATCH 01/17] drm/radeon: make radeon_gpu_is_lockup a per ring function

Different rings have different criteria to test if they are stuck. v2: rebased on current drm-next Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Alex Deucher alexander.deuc...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon.h |

[PATCH 03/17] drm/radeon: register ring debugfs handlers on init

Just register the debugfs files on init instead of checking the chipset type multiple times. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Alex Deucher alexander.deuc...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon_ring.c | 31

[PATCH 06/17] drm/radeon: fix a bug in the SA code

Aligning offset can make it bigger than tmp-offset leading to an overrun bug in the following subtraction. v2: Against initial suspicions this can't happen in mainline, so no need to push it into stable. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Michel Dänzer

[PATCH 04/17] drm/radeon: use central function for IB testing

Removing all the different error messages and having just one standard behaviour over all chipset generations. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Alex Deucher alexander.deuc...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com ---

[PATCH 05/17] drm/radeon: rework gpu lockup detection and processing

Previusly multiple rings could trigger multiple GPU resets at the same time. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon.h |3 +- drivers/gpu/drm/radeon/radeon_fence.c | 146

[PATCH 09/17] drm/radeon: don't keep list of created fences.

It's never used and so practically superfluous. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon.h |1 - drivers/gpu/drm/radeon/radeon_fence.c |7 --- 2 files changed, 0 insertions(+), 8

[PATCH 07/17] drm/radeon: return -ENOENT in fence_wait_next v2

We should signal the caller that we haven't waited at all. v2: only change fence_wait_next not fence_wait_last. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Michel Dänzer michel.daen...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com ---

[PATCH 08/17] drm/radeon: rename fence_wait_last to fence_wait_empty

As discussed with Michel that name better describes the behavior of this function. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Michel Dänzer michel.daen...@amd.com Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon.h|2 +-

[PATCH 10/17] drm/radeon: fix a bug with the ring syncing code

Rings need to lock in order, otherwise the ring subsystem can deadlock. v2: fix error handling and number of locked doublewords. v3: stop creating unneeded semaphores. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Jerome Glisse jgli...@redhat.com ---

[PATCH 13/17] drm/radeon: make lockup timeout a module param

Don't hard code the 10 seconds timeout. Compute jobs can run much longer. Signed-off-by: Christian König deathsim...@vodafone.de Reviewed-by: Jerome Glisse jgli...@redhat.com --- drivers/gpu/drm/radeon/radeon.h |1 + drivers/gpu/drm/radeon/radeon_drv.c |4

  1   2   >