summaryrefslogtreecommitdiffstats
path: root/sys/dev/drm/drm_irq.c
Commit message (Collapse)AuthorAgeFilesLines
* fix atomic_set_xxx misuse in drmavg2010-12-111-1/+1
| | | | | | | It seems that atomic_set_xxx and atomic_store_xxx were confused. Reviewed by: jhb MFC after: 3 weeks
* Keep track of the hardware counter more aggressively while interruptsrnoland2009-06-251-0/+4
| | | | | | | are enabled. This should help to reduce cases where the hardware counter reference jumps by large amounts. MFC after: 3 days
* Fix one use of atomic for refcount missed in last commit.rnoland2009-06-251-1/+1
| | | | MFC after: 3 days
* Additional vblank cleanups.rnoland2009-06-251-26/+29
| | | | | | | | | Use the vbl_lock when maniputlating the refcount. Eventually I want to convert this to use our internal refcount code. Continue to use atomic ops for manipulating vblank count since we access it often just for reading. MFC after: 3 days
* Ensure that we always hold the lock when calling vblank_disable_fn()rnoland2009-06-251-0/+5
| | | | MFC after: 3 days
* Using signals for vblank events is prone to issues. There have neverrnoland2009-06-231-48/+1
| | | | | | | been any consumers and likely will never be. Furthermore, we have never enabled the code for it, so just get rid of it. MFC after: 3 days
* Given that vblanks generally occur 60 times a second, waiting 3 secondsrnoland2009-06-231-1/+1
| | | | | | seems rather excessive. MFC after: 3 days
* vblank[crtc].last represents the hardware counter while request.sequencernoland2009-06-231-1/+0
| | | | | | represents the software counter. Don't currupt things here. MFC after: 3 days
* Fix up waiting on vblank again... This reverts a last minute change thatrnoland2009-03-261-5/+8
| | | | | | I made on the last patch, it seems to upset suspend/resume and shutdown. MFC after: 3 days
* Rework the management of vblank interrupts a bit.rnoland2009-03-251-22/+31
| | | | | | | | | | | | | | | When a vt switch occurs the irq handler is uninstalled. Interrupts and the state tracking of what was enabled/disabled wasn't working properly. This should resolve the reports of "slow windows" after a vt switch, among other things. The radeon 2d driver seems to work a bit more correctly than the Intel driver. With the Intel driver, vblank interrupts will be enabled at system startup and will only be disabled after an additional modeset (vt switch, dpms, randr event). With this patch, I am able to run glxgears synced to vblank and vt switch while it is running without ill effects. MFC after: 3 days
* Only issue the wakeup and store the counter if vblank is enabled onrnoland2009-03-201-4/+6
| | | | | | the pipe. MFC after: 3 days
* Rework vblank handling to try to resolve some reports of "slow" windowsrnoland2009-03-191-19/+36
| | | | | | | | after vt switch or suspend. I can't really test this on Intel right now but I think I've heard reports of it on radeon as well. I can't break it on the radeon here. MFC after: 3 days
* Initialize the vblank structures at load time. Previously we did thisrnoland2009-02-281-3/+1
| | | | | | | | | | | | at irq install/uninstall time, but when we vt switch, we uninstall the irq handler. When the irq handler is reinstalled, the modeset ioctl happens first. The modeset ioctl is supposed to tell us that we can disable vblank interrupts if there are no active consumers. This will fail after a vt switch until another modeset ioctl is called via dpms or xrandr. Leading to cases where either interrupts are on and can't be disabled, or worse, no interrupts at all. MFC after: 2 weeks
* Turn on MSI if the card supports it. There is a blacklist for chipsrnoland2009-02-251-17/+1
| | | | | | which report that they are capable of MSI, but don't work correctly. MFC after: 2 weeks
* Add some vblank related debugging and replace the DRM_WAIT_ON macrornoland2009-02-251-9/+23
| | | | | | with a localized version. MFC after: 2 weeks
* The i915 driver was the only consumer of locked task support.rnoland2009-02-251-46/+0
| | | | | | | Now that it doesn't use it anymore, get right of the taskqueue and locked task support. MFC after: 2 weeks
* Rework memory allocation to allocate memory with different type names. Thisrnoland2008-10-131-6/+5
| | | | | | | | | | | will ease the identification of memory leaks as the OS will be able to track allocations for us by malloc type. vmstat -m will show all of the allocations. Convert the calls to drm_alloc() and friends, which are used in shared code to static __inline__ while we are here. Approved by: jhb (mentor)
* resync to git masterrnoland2008-10-031-55/+35
| | | | | | | | | | | | | | | | | | | | | | This reverts a private patch which is causing issues with many Intel chipsets. I will review that patch and see what we need to do to fix it up later, but for the time being, we will just get these chips working again. This update contains a lot of code cleanup and is post gem merge (no, we don't have gem support). It should prove much easier to read the code now. A lot of thanks goes to vehemens for that work. I have adapted the code to use cdevpriv for tracking per open file data. That alleviates the old ugly hack that we used to try and accomplish the task and helped to clean up the open / close behavior a good bit. This also replaces the hack that was put in place a year or so ago to prevent radeons from locking up with AIGLX enabled. I have had a couple of radeon testers report that it still works as expected, though I no longer have radeon hardware to test with myself. Other various fixes from the linux crew and Intel, many of which are muddled in with the gem merge. Approved by: jhb (mentor) Obtained from: mesa/drm git master MFC after: 2 weeks
* Update drm kernel drivers.rnoland2008-08-231-66/+345
| | | | | | | | | | This is a sync to mesa/drm pre-gem, with a few fixes on top of that. It also contains one local patch supplied by kib@ that I can't apply to git.master shared code. Approved by: flz Obtained from: mesa/drm git.master MFC after: 2 weeks
* o break newbus api: add a new argument of type driver_filter_t topiso2007-02-231-1/+1
| | | | | | | | | | | | | bus_setup_intr() o add an int return code to all fast handlers o retire INTR_FAST/IH_FAST For more info: http://docs.freebsd.org/cgi/getmsg.cgi?fetch=465712+0+current/freebsd-current Reviewed by: many Approved by: re@
* Update DRM to CVS snapshot as of 2005-11-28. Notable changes:anholt2005-11-281-12/+21
| | | | | | | | | | | | | - S3 Savage driver ported. - Added support for ATI_fragment_shader registers for r200. - Improved r300 support, needed for latest r300 DRI driver. - (possibly) r300 PCIE support, needs X.Org server from CVS. - Added support for PCI Matrox cards. - Software fallbacks fixed for Rage 128, which used to render badly or hang. - Some issues reported by WITNESS are fixed. - i915 module Makefile added, as the driver may now be working, but is untested. - Added scripts for copying and preprocessing DRM CVS for inclusion in the kernel. Thanks to Daniel Stone for getting me started on that.
* Update to DRM CVS as of 2005-04-12, bringing many changes:anholt2005-04-161-0/+285
- Split core DRM routines back into their own module, rather than using the nasty templated system like before. - Development-class R300 support in radeon driver (requires userland pieces, of course). - Mach64 driver (haven't tested in a while -- my mach64s no longer fit in the testbox). Covers Rage Pros, Rage Mobility P/M, Rage XL, and some others. - i915 driver files, which just need to get drm_drv.c fixed to allow attachment to the drmsub device. Covers i830 through i915 integrated graphics. - savage driver files, which should require minimal changes to work. Covers the Savage3D, Savage IX/MX, Savage 4, ProSavage. - Support for color and texture tiling and HyperZ features of Radeon. Thanks to: scottl (much p4 handholding) Jung-uk Kim (helpful prodding) PR: [1] kern/76879, [2] kern/72548 Submitted by: [1] Alex, lesha at intercaf dot ru [2] Shaun Jurrens, shaun at shamz dot net
OpenPOWER on IntegriCloud