From: boris.brezillon@free-electrons.com (Boris Brezillon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PULL] drm: atmel-hlcdc: various improvements
Date: Wed, 13 Apr 2016 11:45:14 +0200 [thread overview]
Message-ID: <20160413114514.710e85b3@bbrezillon> (raw)
Hi,
Here is a pull request containing several improvement and cleanup patches
for the atmel-hlcdc driver to be applied on drm-next (targeting 4.7).
Best Regards,
Boris
The following changes since commit c1cc68ae84bcce64e63d81b3531296728d407a16:
drm: atmel-hlcdc: add a ->cleanup_fb() operation (2016-04-13 10:49:13 +0200)
are available in the git repository at:
https://github.com/bbrezillon/linux-at91.git cba06c6
for you to fetch changes up to cba06c65983250d991b87eeade86b089c6bf2bc4:
drm: atmel-hlcdc: route DMA accesses through AHB interfaces (2016-04-13 10:49:18 +0200)
----------------------------------------------------------------
Boris Brezillon (8):
drm: atmel-hlcdc: support asynchronous atomic commit operations
drm: atmel-hlcdc: fix connector and encoder types
drm: atmel-hlcdc: remove leftovers from atomic mode setting migration
drm: atmel-hlcdc: support extended timing ranges on sama5d4 and sama5d2
drm: atmel-hlcdc: move output mode selection in CRTC implementation
drm: atmel-hlcdc: rework the output code to support drm bridges
drm: atmel-hlcdc: check display mode validity in crtc->mode_fixup()
drm: atmel-hlcdc: route DMA accesses through AHB interfaces
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_crtc.c | 158 +++++++++++++-
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.c | 123 ++++++++++-
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_dc.h | 15 ++
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_output.c | 249 ++++++++++-------------
drivers/gpu/drm/atmel-hlcdc/atmel_hlcdc_plane.c | 43 +++-
5 files changed, 432 insertions(+), 156 deletions(-)
next reply other threads:[~2016-04-13 9:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-13 9:45 Boris Brezillon [this message]
2016-04-14 3:10 ` [PULL] drm: atmel-hlcdc: various improvements Dave Airlie
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=20160413114514.710e85b3@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).