From: Daniel Vetter <daniel.vetter@ffwll.ch>
To: Dave Airlie <airlied@gmail.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org
Subject: [PULL] topic/drm-misc
Date: Fri, 4 Dec 2015 11:46:24 +0100 [thread overview]
Message-ID: <20151204104624.GA15248@phenom.ffwll.local> (raw)
Hi Dave,
New -misc pull. Big thing is Thierry's atomic helpers for system suspend
resume, which I'd like to use in i915 too. Hence the pull.
Aside: There's a conflict between your -next and -fixes in imx, pinged you
about it on irc. Would be good if you can backmerge the next -rc after
pulling this in, then I can pull that into i915 trees again too in one go.
Cheers, Daniel
The following changes since commit 87069f4493b2101a71a92b7b9565f488a605a88f:
drm/mm: use list_next_entry (2015-11-25 16:22:58 +0100)
are available in the git repository at:
git://anongit.freedesktop.org/drm-intel tags/topic/drm-misc-2015-12-04
for you to fetch changes up to 4e15f2a1a056ff2695611c3e8d0b162526e84355:
drm: keep connector status change logging human readable (2015-12-04 08:59:41 +0100)
----------------------------------------------------------------
Chris Wilson (2):
drm: Drop dev->event_lock spinlock around faulting copy_to_user()
drm: Serialise multiple event readers
Daniel Vetter (6):
drm/gma500: Use correct unref in the gem bo create function
drm/gma500: Drop dev->struct_mutex from modeset code
drm/gma500: Drop dev->struct_mutex from fbdev init/teardown code
drm/gma500: Drop dev->struct_mutex from mmap offset function
drm/gma500: Add driver private mutex for the fault handler
drm/atomic-helper: Reject attempts at re-stealing encoders
Jani Nikula (1):
drm: keep connector status change logging human readable
Jyri Sarha (1):
drm/atomic_helper: Add drm_atomic_helper_disable_planes_on_crtc()
Thierry Reding (2):
drm: Implement drm_modeset_lock_all_ctx()
drm/atomic-helper: Implement subsystem-level suspend/resume
Ville Syrjälä (1):
drm/edid: Make the detailed timing CEA/HDMI mode fixup accept up to 5kHz clock difference
drivers/gpu/drm/drm_atomic.c | 7 +-
drivers/gpu/drm/drm_atomic_helper.c | 233 ++++++++++++++++++++++++++++++++++-
drivers/gpu/drm/drm_crtc_helper.c | 6 +
drivers/gpu/drm/drm_edid.c | 62 +++++++++-
drivers/gpu/drm/drm_fops.c | 58 +++++----
drivers/gpu/drm/drm_modes.c | 19 ++-
drivers/gpu/drm/drm_modeset_lock.c | 89 ++++++++-----
drivers/gpu/drm/drm_probe_helper.c | 5 +-
drivers/gpu/drm/gma500/framebuffer.c | 12 +-
drivers/gpu/drm/gma500/gem.c | 19 +--
drivers/gpu/drm/gma500/gma_display.c | 13 +-
drivers/gpu/drm/gma500/gtt.c | 1 +
drivers/gpu/drm/gma500/psb_drv.h | 2 +
include/drm/drmP.h | 2 +
include/drm/drm_atomic_helper.h | 8 ++
include/drm/drm_modes.h | 2 +
include/drm/drm_modeset_lock.h | 4 +-
17 files changed, 445 insertions(+), 97 deletions(-)
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2015-12-04 10:47 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-04 10:46 Daniel Vetter [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-11-10 7:16 [PULL] topic/drm-misc Daniel Vetter
2016-10-27 18:53 Daniel Vetter
2016-10-24 7:21 Daniel Vetter
2016-10-13 8:28 Daniel Vetter
2016-10-11 8:03 Daniel Vetter
2016-10-05 9:29 Daniel Vetter
2016-10-03 13:39 Daniel Vetter
2016-10-04 2:48 ` Dave Airlie
2016-09-25 21:26 Daniel Vetter
2016-09-19 7:11 Daniel Vetter
2016-09-08 9:30 Jani Nikula
2016-08-31 16:48 Daniel Vetter
2016-08-23 19:53 Daniel Vetter
2016-08-12 17:18 Daniel Vetter
2016-07-28 12:30 Daniel Vetter
2016-07-22 8:10 Daniel Vetter
2016-07-14 8:32 Daniel Vetter
2016-07-11 5:55 Daniel Vetter
2016-06-22 9:21 Daniel Vetter
2016-06-22 11:13 ` Daniel Vetter
2016-06-22 11:22 ` Daniel Vetter
2016-06-14 21:48 Daniel Vetter
2016-06-15 15:16 ` Daniel Vetter
2016-06-15 15:40 ` Daniel Vetter
2016-06-07 20:00 Daniel Vetter
2016-06-01 7:29 Daniel Vetter
2016-05-18 19:53 Daniel Vetter
2016-05-17 16:49 Daniel Vetter
2016-05-12 22:28 Daniel Vetter
2016-05-08 16:35 Daniel Vetter
2016-05-04 21:25 Daniel Vetter
2016-04-29 8:13 Daniel Vetter
2016-04-21 9:31 Daniel Vetter
2016-04-01 13:11 Daniel Vetter
2016-03-22 14:48 Daniel Vetter
2016-03-09 9:56 Daniel Vetter
2016-03-14 6:47 ` Daniel Vetter
2016-02-18 19:51 Daniel Vetter
2016-02-12 13:21 Daniel Vetter
2016-02-08 10:36 Daniel Vetter
2016-01-17 16:07 Daniel Vetter
2015-12-23 12:43 Daniel Vetter
2015-12-18 16:39 Daniel Vetter
2015-12-14 9:26 Daniel Vetter
2015-11-26 8:17 Daniel Vetter
2015-10-22 19:42 Daniel Vetter
2015-10-19 13:21 Daniel Vetter
2015-10-08 7:37 Daniel Vetter
2015-09-25 12:18 Daniel Vetter
2015-09-22 9:05 Daniel Vetter
2015-09-22 9:17 ` Daniel Vetter
2015-09-14 15:22 Daniel Vetter
2015-09-16 14:45 ` Daniel Vetter
2015-09-21 21:40 ` Dave Airlie
2015-08-13 7:59 Daniel Vetter
2015-07-28 9:03 Daniel Vetter
2015-07-23 7:27 Daniel Vetter
2015-07-13 7:22 Daniel Vetter
2015-06-22 11:50 Daniel Vetter
2015-05-28 6:40 Daniel Vetter
2015-05-19 14:23 Daniel Vetter
2015-05-06 8:24 Daniel Vetter
2015-04-15 12:06 Daniel Vetter
2015-03-31 14:29 Daniel Vetter
2015-03-31 14:31 ` Daniel Vetter
2015-03-18 10:15 Daniel Vetter
2015-03-10 9:21 Daniel Vetter
2015-02-06 7:29 Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20151204104624.GA15248@phenom.ffwll.local \
--to=daniel.vetter@ffwll.ch \
--cc=airlied@gmail.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.