<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/gpu/drm/Makefile, branch v3.2.2</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/gpu/drm/Makefile?h=v3.2.2</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/gpu/drm/Makefile?h=v3.2.2'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2011-10-05T09:27:31Z</updated>
<entry>
<title>DRM: add DRM Driver for Samsung SoC EXYNOS4210.</title>
<updated>2011-10-05T09:27:31Z</updated>
<author>
<name>Inki Dae</name>
<email>inki.dae@samsung.com</email>
</author>
<published>2011-10-04T10:19:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1c248b7d2960faec3e1b8f3f9c5d9d0df28e0a3c'/>
<id>urn:sha1:1c248b7d2960faec3e1b8f3f9c5d9d0df28e0a3c</id>
<content type='text'>
This patch is a DRM Driver for Samsung SoC Exynos4210 and now enables
only FIMD yet but we will add HDMI support also in the future.

this patch is based on git repository below:
git://people.freedesktop.org/~airlied/linux.git
branch name: drm-next
commit-id: 88ef4e3f4f616462b78a7838eb3ffc3818d30f67

you can refer to our working repository below:
http://git.infradead.org/users/kmpark/linux-2.6-samsung
branch name: samsung-drm

We tried to re-use lowlevel codes of the FIMD driver(s3c-fb.c
based on Linux framebuffer) but couldn't so because lowlevel codes
of s3c-fb.c are included internally and so FIMD module of this driver has
its own lowlevel codes.

We used GEM framework for buffer management and DMA APIs(dma_alloc_*)
for buffer allocation so we can allocate physically continuous memory
for DMA through it and also we could use CMA later if CMA is applied to
mainline.

Refer to this link for CMA(Continuous Memory Allocator):
http://lkml.org/lkml/2011/7/20/45

this driver supports only physically continuous memory(non-iommu).

Links to previous versions of the patchset:
v1: &lt; https://lwn.net/Articles/454380/ &gt;
v2: &lt; http://www.spinics.net/lists/kernel/msg1224275.html &gt;
v3: &lt; http://www.spinics.net/lists/dri-devel/msg13755.html &gt;
v4: &lt; http://permalink.gmane.org/gmane.comp.video.dri.devel/60439 &gt;
v5: &lt; http://comments.gmane.org/gmane.comp.video.dri.devel/60802 &gt;

Changelog v2:
DRM: add DRM_IOCTL_SAMSUNG_GEM_MMAP ioctl command.

    this feature maps user address space to physical memory region
    once user application requests DRM_IOCTL_SAMSUNG_GEM_MMAP ioctl.

DRM: code clean and add exception codes.

Changelog v3:
DRM: Support multiple irq.

    FIMD and HDMI have their own irq handler but DRM Framework can regiter
    only one irq handler this patch supports mutiple irq for Samsung SoC.

DRM: Consider modularization.

    each DRM, FIMD could be built as a module.

DRM: Have indenpendent crtc object.

    crtc isn't specific to SoC Platform so this patch gets a crtc
    to be used as common object.
    created crtc could be attached to any encoder object.

DRM: code clean and add exception codes.

Changelog v4:
DRM: remove is_defult from samsung_fb.

    is_default isn't used for default framebuffer.

DRM: code refactoring to fimd module.
    this patch is be considered with multiple display objects and
    would use its own request_irq() to register a irq handler instead of
    drm framework's one.

DRM: remove find_samsung_drm_gem_object()

DRM: move kernel private data structures and definitions to driver folder.

    samsung_drm.h would contain only public information for userspace
    ioctl interface.

DRM: code refactoring to gem modules.
    buffer module isn't dependent of gem module anymore.

DRM: fixed security issue.

DRM: remove encoder porinter from specific connector.

    samsung connector doesn't need to have generic encoder.

DRM: code clean and add exception codes.

Changelog v5:
DRM: updated fimd(display controller) driver.
    added various pixel formats, color key and pixel blending features.

DRM: removed end_buf_off from samsung_drm_overlay structure.
    this variable isn't used and end buffer address would be
    calculated by each sub driver.

DRM: use generic function for mmap_offset.
    replaced samsung_drm_gem_create_mmap_offset() and
    samsung_drm_free_mmap_offset() with generic ones applied
    to mainline recentrly.

DRM: removed unnecessary codes and added exception codes.

DRM: added comments and code clean.

Changelog v6:
DRM: added default config options.

DRM: added padding for 64-bit align.

DRM: changed prefix 'samsung' to 'exynos'

Signed-off-by: Inki Dae &lt;inki.dae@samsung.com&gt;
Signed-off-by: Joonyoung Shim &lt;jy0922.shim@samsung.com&gt;
Signed-off-by: Seung-Woo Kim &lt;sw0312.kim@samsung.com&gt;
Signed-off-by: Kyungmin Park &lt;kyungmin.park@samsung.com&gt;
Reviewed-by: Konrad Rzeszutek Wilk &lt;konrad.wilk@oracle.com&gt;
Reviewed-by: Dave Airlie &lt;airlied@redhat.com&gt;
Reviewed-by: Rob Clark &lt;robdclark@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: add usb framework</title>
<updated>2011-02-07T03:09:42Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@gmail.com</email>
</author>
<published>2010-12-14T21:13:55Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a250b9fdc53a286d32e22f21170382a46b3a3ef5'/>
<id>urn:sha1:a250b9fdc53a286d32e22f21170382a46b3a3ef5</id>
<content type='text'>
This adds an initial framework to plug USB graphics devices
into the drm/kms subsystem.

I've started writing a displaylink driver using this interface.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: remove i830 driver</title>
<updated>2011-02-07T02:14:18Z</updated>
<author>
<name>Arnd Bergmann</name>
<email>arnd@arndb.de</email>
</author>
<published>2011-01-25T22:17:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7f50684717511d30bba180902105c4cd4efca732'/>
<id>urn:sha1:7f50684717511d30bba180902105c4cd4efca732</id>
<content type='text'>
This driver is one of the last users of the big kernel
lock, which is going away. All the hardware supported
by this driver also works with the newer i915 driver,
and recent X.org releases only work with that driver
anyway.

Signed-off-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Cc: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Cc: dri-devel@lists.freedesktop.org
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: replace drawable ioctl by noops</title>
<updated>2010-08-29T23:39:11Z</updated>
<author>
<name>Daniel Vetter</name>
<email>daniel.vetter@ffwll.ch</email>
</author>
<published>2010-08-23T20:53:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8f879194f88742d9c452f669482b6d6abdc1e1e7'/>
<id>urn:sha1:8f879194f88742d9c452f669482b6d6abdc1e1e7</id>
<content type='text'>
The information supplied by userspace through these ioctls is only
accessible by dev-&gt;drw_idr. But there's no in-tree user of that.
Also userspace does not really care about return values of these ioctls,
either. Only hw/xfree86/dri/dri.c from the xserver actually checks the
return from adddraw and keeps on trying to create a kernel drawable
every time somebody creates a dri drawable. But since that's now a noop,
who cares.

Therefore it's safe to replace these three ioctls with noops and rip
out the implementation.

Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Reviewed-by: Kristian Høgsberg &lt;krh@bitplanet.net&gt;
Reviewed-by: Michel Dänzer &lt;michel@daenzer.net&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: move ttm global code to core drm</title>
<updated>2010-08-03T23:46:06Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2010-03-09T00:56:52Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ba4420c224c2808f2661cf8428f43ceef7a73a4a'/>
<id>urn:sha1:ba4420c224c2808f2661cf8428f43ceef7a73a4a</id>
<content type='text'>
I wrote this for the prime sharing work, but I also noticed other external
non-upstream drivers from a large company carrying a similiar patch, so I
may as well ship it in master.

Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'drm-tracepoints' into drm-testing</title>
<updated>2010-07-07T08:38:44Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2010-07-07T08:38:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=102e73463e1bb921b3a829a1392a29dba16bbabd'/>
<id>urn:sha1:102e73463e1bb921b3a829a1392a29dba16bbabd</id>
<content type='text'>
</content>
</entry>
<entry>
<title>drm: add vblank event trace point</title>
<updated>2010-07-02T04:02:44Z</updated>
<author>
<name>Jesse Barnes</name>
<email>jbarnes@virtuousgeek.org</email>
</author>
<published>2010-07-01T23:47:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=ac2874b980e05ed7a4ea8fed7b0a92428b51ce58'/>
<id>urn:sha1:ac2874b980e05ed7a4ea8fed7b0a92428b51ce58</id>
<content type='text'>
Emit a trace point for vblank events.  This can be helpful for mapping
drawing activity against the vblank frequency and period.

Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Add support for platform devices to register as DRM devices</title>
<updated>2010-06-01T00:07:39Z</updated>
<author>
<name>Jordan Crouse</name>
<email>jcrouse@codeaurora.org</email>
</author>
<published>2010-05-27T19:40:25Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=dcdb167402cbdca1d021bdfa5f63995ee0a79317'/>
<id>urn:sha1:dcdb167402cbdca1d021bdfa5f63995ee0a79317</id>
<content type='text'>
Allow platform devices without PCI resources to be DRM devices.

[airlied: fixup warnings with dev pointers]

Signed-off-by: Jordan Crouse &lt;jcrouse@codeaurora.org&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>drm: Add generic multipart buffer.</title>
<updated>2010-02-22T23:46:20Z</updated>
<author>
<name>Pauli Nieminen</name>
<email>suokkos@gmail.com</email>
</author>
<published>2010-02-01T17:11:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7a9f0dd9c49425e2b0e39ada4757bc7a38c84873'/>
<id>urn:sha1:7a9f0dd9c49425e2b0e39ada4757bc7a38c84873</id>
<content type='text'>
Allocating multiple pages of memory for data that is coming
from user space may fail. To fix memory allocation failures
the buffer object should be split to multiple independ pages.

drm buffer provides generic interface to copy and process
large data arrays from user space.

Interface includes allocation and free functions to allocate
the buffer object and data storage pages.

All access operations are performed relative to a internal
pointer which is advanced with drm_buffer_advance function.

The buffer can be accessed using drm_buffer_pointer_to_XXX
functions if it is known that requested object doesn't split
over a page boundary. These functions don't do any error
checking to maximize performance.

If there is large object which could be split there is special
drm_buffer_read_object function. drm_buffer_read_object takes
a pointer as argument which is used as temporary store for
data if it is split over boundary in the buffer.

Signed-off-by: Pauli Nieminen &lt;suokkos@gmail.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;
</content>
</entry>
<entry>
<title>Merge remote branch 'korg/drm-vmware-staging' into drm-core-next</title>
<updated>2009-12-17T23:53:50Z</updated>
<author>
<name>Dave Airlie</name>
<email>airlied@redhat.com</email>
</author>
<published>2009-12-17T23:53:50Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=cbc8cc049aefd571ebc3c255dc3e265f736751c0'/>
<id>urn:sha1:cbc8cc049aefd571ebc3c255dc3e265f736751c0</id>
<content type='text'>
</content>
</entry>
</feed>
