From: Eric Anholt <eric@anholt.net>
To: dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, David Airlie <airlied@linux.ie>,
Eric Anholt <eric@anholt.net>
Subject: [GIT PULL] drm-vc4-next for 4.6
Date: Mon, 14 Mar 2016 11:03:44 -0700 [thread overview]
Message-ID: <1457978624-20857-1-git-send-email-eric@anholt.net> (raw)
Merge tag 'drm-vc4-fixes-2016-03-03' of github.com:anholt/linux into drm-next (2016-03-14 09:48:04 +1000)
are available in the git repository at:
git@github.com:anholt/linux.git tags/drm-vc4-next-2016-03-14
for you to fetch changes up to 90d7116061f86c1f8ea460806a0414addea7b58b:
drm/vc4: Recognize a more specific compatible string for V3D. (2016-03-13 18:54:24 -0700)
----------------------------------------------------------------
This pull request covers what's left for 4.6. Notably, it includes a
significant 3D performance improvement and a fix to HDMI hotplug
detection for the Pi2/3.
----------------------------------------------------------------
Dan Carpenter (1):
drm/vc4: Return -EFAULT on copy_from_user() failure
Eric Anholt (4):
drm/vc4: Let gpiolib know that we're OK with sleeping for HPD.
drm/vc4: Respect GPIO_ACTIVE_LOW on HDMI HPD if set in the devicetree.
dt-bindings: Add binding docs for V3D.
drm/vc4: Recognize a more specific compatible string for V3D.
Varad Gautam (1):
drm/vc4: improve throughput by pipelining binning and rendering jobs
.../devicetree/bindings/display/brcm,bcm-vc4.txt | 12 ++
drivers/gpu/drm/vc4/vc4_bo.c | 7 +-
drivers/gpu/drm/vc4/vc4_drv.h | 37 +++++--
drivers/gpu/drm/vc4/vc4_gem.c | 123 +++++++++++++++------
drivers/gpu/drm/vc4/vc4_hdmi.c | 12 +-
drivers/gpu/drm/vc4/vc4_irq.c | 58 ++++++++--
drivers/gpu/drm/vc4/vc4_v3d.c | 1 +
7 files changed, 193 insertions(+), 57 deletions(-)
reply other threads:[~2016-03-14 18:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1457978624-20857-1-git-send-email-eric@anholt.net \
--to=eric@anholt.net \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®