<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/drivers/gpu/drm/drm_fops.c, branch linux-4.7.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.7.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.7.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-04-27T08:16:17Z</updated>
<entry>
<title>drm: Protect dev-&gt;filelist with its own mutex</title>
<updated>2016-04-27T08:16:17Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-04-26T17:29:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1d2ac403ae3bfde7c50328ee0d39d3fb3d8d9823'/>
<id>urn:sha1:1d2ac403ae3bfde7c50328ee0d39d3fb3d8d9823</id>
<content type='text'>
amdgpu gained dev-&gt;struct_mutex usage, and that's because it's walking
the dev-&gt;filelist list. Protect that list with it's own lock to take
one more step towards getting rid of struct_mutex usage in drivers
once and for all.

While doing the conversion I noticed that 2 debugfs files in i915
completely lacked appropriate locking. Fix that up too.

v2: don't forget to switch to drm_gem_object_unreference_unlocked.

Cc: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1461691808-12414-9-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm: Put legacy lastclose work into drm_legacy_dev_reinit</title>
<updated>2016-04-27T06:42:26Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-04-26T17:29:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=68dfbebab131146b460550cebf8c38667c490a04'/>
<id>urn:sha1:68dfbebab131146b460550cebf8c38667c490a04</id>
<content type='text'>
Except for the -&gt;lasclose driver callback evrything in drm_lastclose()
is all legacy cruft and can be hidden. Which means another
dev-&gt;struct_mutex site disappears entirely for modern drivers!

Also while at it change the return value of drm_lastclose to void
since it will always succeed. No one checks the return value of
close() anyway, ever.

v2: Move misplaced hunk, spotted by 0day.

Cc: Thierry Reding &lt;thierry.reding@gmail.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1461691808-12414-3-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm: Give drm_agp_clear drm_legacy_ prefix</title>
<updated>2016-04-27T06:41:34Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-04-26T17:29:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=366884b17fae7d2a7517eea60e64d6d6754fa9db'/>
<id>urn:sha1:366884b17fae7d2a7517eea60e64d6d6754fa9db</id>
<content type='text'>
It has a  DRIVER_MODESET check to sure make it's not creating havoc
for drm drivers. Make that clear in the name too.

v2: Move misplaced hunk, spotted by 0day and Thierry.

Cc: Thierry Reding &lt;thierry.reding@gmail.com&gt;
Reviewed-by: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;
Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1461691808-12414-2-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm: Nuke vblank event file cleanup code</title>
<updated>2016-02-08T08:55:47Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-25T21:16:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7eb98020b73e20ce18d3ed704d7b7988ddad5dfd'/>
<id>urn:sha1:7eb98020b73e20ce18d3ed704d7b7988ddad5dfd</id>
<content type='text'>
The core code now takes care of unlinking drm_events from the file in
a generic way, so this code isn't needed any more.

For those wondering where the drm_vblank_put went to: With the new
logic events only get unlinked, but still exist. Hence any resources
(like vblank counters) don't need to be released since the event user
will still process the event normally. In this case this is the
callsites of send_vblank_event, which of course already have a
drm_vblank_put.

Cc: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Acked-by: Daniel Stone &lt;daniels@collabora.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1453756616-28942-3-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm: Clean up pending events in the core</title>
<updated>2016-02-08T08:55:46Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-25T21:16:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=681047b48601841c8380abd406301648c3590592'/>
<id>urn:sha1:681047b48601841c8380abd406301648c3590592</id>
<content type='text'>
There's really no reason to not do so, instead of replicating this
for every use-case and every driver. Now we can't just nuke the events,
since that would still mean that all drm_event users would need to know
when that has happened, since calling e.g. drm_send_event isn't allowed
any more. Instead just unlink them from the file, and detect this case
and handle it appropriately in all functions.

v2: Adjust existing kerneldoc too.

v3: Improve wording of the kerneldoc and split out vblank cleanup (Laurent).

Cc: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Acked-by: Daniel Stone &lt;daniels@collabora.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt; (v1)
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1453756616-28942-2-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm/vblank: Use drm_event_reserve_init</title>
<updated>2016-02-08T08:54:54Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-28T11:01:04Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4020b220edb3419975c0d9322ee0e0c07e09f6bf'/>
<id>urn:sha1:4020b220edb3419975c0d9322ee0e0c07e09f6bf</id>
<content type='text'>
Well we can't use that directly since that code must hold
dev-&gt;event_lock already. Extract an _unlocked version.

Embarrassingly I've totally forgotten about this patch and any kind of
event-based vblank wait totally blew up, killing the kernel.

v2: Pick the right base struct, someone didn't noticed that gcc was
unhappy. No bug since the addresses at least matched (Daniel Stone)

Cc: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: Daniel Stone &lt;daniels@collabora.com&gt;
Cc: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Reviewed-by: Daniel Stone &lt;daniels@collabora.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1453978864-1513-1-git-send-email-daniel.vetter@ffwll.ch
</content>
</entry>
<entry>
<title>drm: Create drm_send_event helpers</title>
<updated>2016-01-25T18:34:43Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-11T21:40:59Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fb740cf2492cc1e8f2216bc5ad9f5b2c49a32752'/>
<id>urn:sha1:fb740cf2492cc1e8f2216bc5ad9f5b2c49a32752</id>
<content type='text'>
Use them in the core vblank code and exynos/vmwgfx drivers.

Note that the difference between wake_up_all and _interruptible in
vmwgfx doesn't matter since the only waiter is the core code in
drm_fops.c. And that is interruptible.

v2: Adjust existing kerneldoc too.

Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt; (v1)
Acked-by: Daniel Stone &lt;daniels@collabora.com&gt;
Cc: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;
Cc: Inki Dae &lt;inki.dae@samsung.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1452548477-15905-6-git-send-email-daniel.vetter@ffwll.ch
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
[danvet: Squash in compile fixup, spotted by 0-day.]
Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;
</content>
</entry>
<entry>
<title>drm: Add functions to setup/tear down drm_events.</title>
<updated>2016-01-25T07:40:09Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-11T21:40:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2dd500f1870e3d852488c9b30c4ecec91c6e2eea'/>
<id>urn:sha1:2dd500f1870e3d852488c9b30c4ecec91c6e2eea</id>
<content type='text'>
An attempt at not spreading out the file_priv-&gt;event_space stuff out
quite so far and wide.  And I think fixes something in ipp_get_event()
that is broken (or if they are doing something more weird/subtle, then
breaks it in a fun way).

Based upon a patch from Rob Clark, rebased and polished.

v2: Spelling fixes (Alex).

Cc: Alex Deucher &lt;alexdeucher@gmail.com&gt;
Acked-by: Daniel Stone &lt;daniels@collabora.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Cc: Rob Clark &lt;robdclark@gmail.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1452548477-15905-3-git-send-email-daniel.vetter@ffwll.ch
Reviewed-by: Laurent Pinchart &lt;laurent.pinchart@ideasonboard.com&gt;
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
</content>
</entry>
<entry>
<title>drm: kerneldoc for drm_fops.c</title>
<updated>2016-01-25T07:39:58Z</updated>
<author>
<name>Daniel Vetter</name>
</author>
<published>2016-01-11T21:40:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bcb877e4dcf21c3ba486fd7cc563126f08c39b8a'/>
<id>urn:sha1:bcb877e4dcf21c3ba486fd7cc563126f08c39b8a</id>
<content type='text'>
Just prep work before I throw more drm_event refactorings on top.

Acked-by: Daniel Stone &lt;daniels@collabora.com&gt;
Reviewed-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;
Link: http://patchwork.freedesktop.org/patch/msgid/1452548477-15905-2-git-send-email-daniel.vetter@ffwll.ch
Signed-off-by: Daniel Vetter &lt;daniel.vetter@intel.com&gt;
</content>
</entry>
<entry>
<title>Back merge tag 'v4.4-rc4' into drm-next</title>
<updated>2015-12-08T01:04:26Z</updated>
<author>
<name>Dave Airlie</name>
</author>
<published>2015-12-08T01:04:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e876b41ab074561d65f213bf5e0fc68cf5bc7380'/>
<id>urn:sha1:e876b41ab074561d65f213bf5e0fc68cf5bc7380</id>
<content type='text'>
We've picked up a few conflicts and it would be nice
to resolve them before we move onwards.
</content>
</entry>
</feed>
