<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/omapdrm, branch linux-3.15.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.15.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.15.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2014-04-15T13:40:01Z</updated>
<entry>
<title>drm/omap: fix the handling of fb ref counts</title>
<updated>2014-04-15T13:40:01Z</updated>
<author>
<name>Tomi Valkeinen</name>
</author>
<published>2014-04-15T13:26:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f2d022aa421ca903a30f63b04528064b7eceaf5e'/>
<id>urn:sha1:f2d022aa421ca903a30f63b04528064b7eceaf5e</id>
<content type='text'>
With the recent primary-plane changes for drm, the primary plane's
framebuffer needs to be ref counted the same way as for
non-primary-planes. This was not done by the omapdrm driver, which
caused the ref count to drop to 0 too early, causing problems.

This patch moves the fb unref and ref from omap_plane_update to
omap_plane_mode_set. This way the fb refs are updated for both primary
and non-primary cases, as omap_plane_update calls omap_plane_mode_set.

Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: protect omap_crtc's event with event_lock spinlock</title>
<updated>2014-04-15T10:35:29Z</updated>
<author>
<name>Archit Taneja</name>
</author>
<published>2014-04-11T07:23:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=38e5597a03d2d1499a785230031c4f48e1d9c6b7'/>
<id>urn:sha1:38e5597a03d2d1499a785230031c4f48e1d9c6b7</id>
<content type='text'>
The vblank_cb callback and the page_flip ioctl can occur together in different
CPU contexts. vblank_cb uses takes tje drm device's event_lock spinlock when
sending the vblank event and updating omap_crtc-&gt;event and omap_crtc-&gt;od_fb.

Use the same spinlock in page_flip, to make sure the above omap_crtc parameters
are configured sequentially.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: Use old_fb to synchronize between successive page flips</title>
<updated>2014-04-15T10:35:28Z</updated>
<author>
<name>Archit Taneja</name>
</author>
<published>2014-04-11T07:23:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bc905aced30e48a39af7c452bf46228d7c6188b9'/>
<id>urn:sha1:bc905aced30e48a39af7c452bf46228d7c6188b9</id>
<content type='text'>
omap_crtc-&gt;old_fb is used to check whether the previous page flip has completed
or not. However, it's never initialized to anything, so it's always NULL. This
results in the check to always succeed, and the page_flip to proceed.

Initialize old_fb to the fb that we intend to flip to through page_flip, and
therefore prevent a future page flip to proceed if the last one didn't
complete.

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: Fix crash when using LCD3 overlay manager</title>
<updated>2014-04-15T10:35:28Z</updated>
<author>
<name>Archit Taneja</name>
</author>
<published>2014-04-11T07:23:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=71b6667765c7019f3fd5ea5e0c02f65f7331f3e1'/>
<id>urn:sha1:71b6667765c7019f3fd5ea5e0c02f65f7331f3e1</id>
<content type='text'>
The channel_names list didn't have a string populated for LCD3 manager, this
results in a crash when the display's output is connected to LCD3. Add an entry
for LCD3.

Reported-by: Somnath Mukherjee &lt;somnath@ti.com&gt;
Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: gem sync: wait on correct events</title>
<updated>2014-04-15T10:35:28Z</updated>
<author>
<name>Archit Taneja</name>
</author>
<published>2014-04-11T07:23:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f2cff0f34ff2c51f703880a2b883ea0c9de4a5ac'/>
<id>urn:sha1:f2cff0f34ff2c51f703880a2b883ea0c9de4a5ac</id>
<content type='text'>
A waiter of the type OMAP_GEM_READ should wait for a buffer to be completely
written, and only then proceed with reading it. A similar logic applies for
waiters with OMAP_GEM_WRITE flag.

Currently the function is_waiting() waits on the read_complete/read_target
counts in the sync object.

This should be the other way round, as a reader should wait for users who are
'writing' to this buffer, and vice versa.

Make readers of the buffer(OMAP_GEM_READ) wait on the write counters, and
writers to the buffer(OMAP_GEM_WRITE) wait on the read counters in is_waiting()

Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: Fix memory leak in omap_gem_op_async</title>
<updated>2014-04-15T10:35:27Z</updated>
<author>
<name>Subhajit Paul</name>
</author>
<published>2014-04-11T07:23:30Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=15ec2ca964d7a52e7e0a452fe0f9c409d2f3eec6'/>
<id>urn:sha1:15ec2ca964d7a52e7e0a452fe0f9c409d2f3eec6</id>
<content type='text'>
In omap_gem_op_async(), if a waiter is not added to the wait list, it needs to
be free'd in the function itself.

Make sure we free the waiter for this case.

Signed-off-by: Subhajit Paul &lt;subhajit_paul@ti.com&gt;
Signed-off-by: Archit Taneja &lt;archit@ti.com&gt;
Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: remove warn from debugfs</title>
<updated>2014-04-15T10:35:27Z</updated>
<author>
<name>Tomi Valkeinen</name>
</author>
<published>2014-04-10T05:57:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b841aedfcfd543d836c856bfde5a17c51cab6b26'/>
<id>urn:sha1:b841aedfcfd543d836c856bfde5a17c51cab6b26</id>
<content type='text'>
Patch dfe96ddcfa22b44100814b9435770f6ff1309d37 (omapdrm: simplify locking in
the fb debugfs file) removed taking locks when using omapdrm's debugfs
to dump fb objects.

However, in omap_gem_describe we give a WARN is the lock has not been
taken, so that WARN is now seen every time omapdrm debugfs is used.

So, presuming the removal of locks is ok, we can also remove the WARN.

Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: remove extra plane-&gt;destroy from crtc destroy</title>
<updated>2014-04-15T10:35:27Z</updated>
<author>
<name>Tomi Valkeinen</name>
</author>
<published>2014-04-09T11:51:01Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=772cdc9777403f10c4229c49645024a502dfd783'/>
<id>urn:sha1:772cdc9777403f10c4229c49645024a502dfd783</id>
<content type='text'>
All the planes, including primary planes, are now destroyed by the drm
framework. Thus we no longer need the explicit call to plane-&gt;destroy
from the crtc's destroy function.

This patch removes the call, thus fixing the crash caused by double
freeing the plane.

remove omap_crtc-&gt;plane-&gt;funcs-&gt;destroy(omap_crtc-&gt;plane)

Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: print warning when rotating non-TILER fb</title>
<updated>2014-04-15T10:35:14Z</updated>
<author>
<name>Tomi Valkeinen</name>
</author>
<published>2014-04-08T13:18:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5ac96345899be859529e05af42f708ae7bd65782'/>
<id>urn:sha1:5ac96345899be859529e05af42f708ae7bd65782</id>
<content type='text'>
Print a warning when the user tries to rotate a non-TILER framebuffer.

Also set the rotation to 0, to avoid constant flood of the warnings in
case of page flipping.

Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
<entry>
<title>drm/omap: fix missing unref to fb's buf object</title>
<updated>2014-04-14T09:34:37Z</updated>
<author>
<name>Tomi Valkeinen</name>
</author>
<published>2014-04-08T12:25:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5e19c06d0e570a347669acc2b850c2f730090b60'/>
<id>urn:sha1:5e19c06d0e570a347669acc2b850c2f730090b60</id>
<content type='text'>
omap_fbdev_create() takes a reference to the fb's gem object with
omap_gem_get_paddr(). However, it never releases it with
omap_gem_put_paddr().

This patch adds the missing omap_gem_put_paddr() to omap_fbdev_free().

Signed-off-by: Tomi Valkeinen &lt;tomi.valkeinen@ti.com&gt;
</content>
</entry>
</feed>
