From: Alyssa Rosenzweig <alyssa@rosenzweig.io>
To: Brian Starkey <Brian.Starkey@arm.com>
Cc: nd <nd@arm.com>,
"lima@lists.freedesktop.org" <lima@lists.freedesktop.org>,
Maxime Ripard <maxime.ripard@bootlin.com>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
David Airlie <airlied@linux.ie>, Qiang Yu <yuq825@gmail.com>,
Ayan Halder <Ayan.Halder@arm.com>, Sean Paul <sean@poorly.run>
Subject: Re: [PATCH v3] drm/fourcc: add ARM GPU tile modifier
Date: Tue, 19 Mar 2019 07:35:51 -0700 [thread overview]
Message-ID: <20190319143551.GA6036@rosenzweig.io> (raw)
In-Reply-To: <20190318181423.qn6bcjph34mx7e45@DESKTOP-E1NTVVP.localdomain>
> We don't know if this is a "category" per-se, or just a single Utgard
> tiling format - as discussed I'm trying to get an answer for that.
FWIW, as I think I mentioned on an message, this format is used on
Midgard as well, and presumably also Bifrost.
On Midgard, when a texture is uploaded (just as a plain bitmap), the
driver tiles it in this format and uploads that, to improve cache
locality.
That said, unlike on Lima/Utgard, Panfrost does not need this exposed in
kernel space, since I don't believe the format is renderable on Midgard.
Any time Qiang would need to import/export something in this tiled
format, I would just use AFBC for the same effect + bw savings.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2019-03-19 14:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-14 11:13 [PATCH v3] drm/fourcc: add ARM GPU tile modifier Qiang Yu
2019-03-14 23:00 ` Alyssa Rosenzweig
2019-03-18 18:14 ` Brian Starkey
2019-03-19 12:05 ` Qiang Yu
2019-03-19 12:10 ` Brian Starkey
2019-03-19 14:35 ` Alyssa Rosenzweig [this message]
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=20190319143551.GA6036@rosenzweig.io \
--to=alyssa@rosenzweig.io \
--cc=Ayan.Halder@arm.com \
--cc=Brian.Starkey@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=lima@lists.freedesktop.org \
--cc=maxime.ripard@bootlin.com \
--cc=nd@arm.com \
--cc=sean@poorly.run \
--cc=yuq825@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