From: Philipp Zabel <p.zabel@pengutronix.de>
To: "Wladimir J. van der Laan" <laanwj@gmail.com>
Cc: dri-devel@lists.freedesktop.org, etnaviv@lists.freedesktop.org
Subject: Re: [PATCH] drm/fourcc: add vivante tiled layout format modifiers
Date: Fri, 27 Jan 2017 10:44:38 +0100 [thread overview]
Message-ID: <1485510278.4426.9.camel@pengutronix.de> (raw)
In-Reply-To: <20170126182913.GA21419@amethyst.visucore.com>
On Thu, 2017-01-26 at 19:29 +0100, Wladimir J. van der Laan wrote:
> Reviewed-By: Wladimir J. van der Laan <laanwj@gmail.com>
Thank you.
> I do wonder whether we'll need the split formats in practice -
> e.g. the GC3000 on the i.MX6qp, for which I suppose this is being done because
> of tiled buffers support in the PRE, has the "single buffer" feature
> which allows rendering to a single buffer with multiple pixel pipes.
> This is what the Vivante driver uses.
>
> But it can't hurt reserving formats for them.
I added them in case it later turns out that avoiding the resolve copy
is advantageous on GC2000 in combination with USB DisplayLink style
outputs, where the CPU could directly process the split-tiled buffers.
regards
Philipp
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-27 9:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 15:32 [PATCH] drm/fourcc: add vivante tiled layout format modifiers Philipp Zabel
2017-01-26 17:24 ` Daniel Vetter
2017-01-26 18:29 ` Wladimir J. van der Laan
2017-01-27 7:34 ` Daniel Vetter
2017-01-27 9:44 ` Philipp Zabel [this message]
2017-01-27 9:09 ` Lucas Stach
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=1485510278.4426.9.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=etnaviv@lists.freedesktop.org \
--cc=laanwj@gmail.com \
/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