dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: David Airlie <airlied@linux.ie>
Cc: kernel@pengutronix.de, dri-devel@lists.freedesktop.org
Subject: [GIT PULL] imx-drm: scanout burst lock support
Date: Wed, 19 Jul 2017 17:23:16 +0200	[thread overview]
Message-ID: <1500477796.2364.58.camel@pengutronix.de> (raw)

Hi Dave,

please consider merging this tag which improvemes for scanout memory
access patterns on i.MX and contains a small cleanup for
ipu_plane_atomic_update.

regards
Philipp

The following changes since commit 5771a8c08880cdca3bfb4a3fc6d309d6bba20877:

  Linux v4.13-rc1 (2017-07-15 15:22:10 -0700)

are available in the git repository at:

  git://git.pengutronix.de/git/pza/linux.git tags/imx-drm-next-2017-07-18

for you to fetch changes up to 790cb4c7c9545953d22d3d425e49b36a711bae5b:

  drm/imx: lock scanout transfers for consecutive bursts (2017-07-17 12:58:11 +0200)

----------------------------------------------------------------
imx-drm: lock scanout transfers for consecutive bursts

- Lock the IDMAC scanout channel for multiple back-to-back bursts if possible,
  to improve memory bandwidth utilisation.
- Replace a few occurences of state->fb with the already existing local fb
  variable in ipu_plane_atomic_update

----------------------------------------------------------------
Philipp Zabel (2):
      drm/imx: ipuv3-plane: use fb local variable instead of state->fb
      drm/imx: lock scanout transfers for consecutive bursts

 drivers/gpu/drm/imx/ipuv3-plane.c | 53 +++++++++++++++++++++++++++++++--------
 1 file changed, 42 insertions(+), 11 deletions(-)

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2017-07-19 15:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 15:23 Philipp Zabel [this message]
2017-08-18 10:41 ` [GIT PULL] imx-drm: scanout burst lock support Philipp Zabel

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=1500477796.2364.58.camel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=kernel@pengutronix.de \
    /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