From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Neil Armstrong <narmstrong@baylibre.com>,
Ayan Kumar Halder <ayan.halder@arm.com>,
liviu.dudau@arm.com, brian.starkey@arm.com, malidp@foss.arm.com,
airlied@linux.ie, dri-devel@lists.freedesktop.org,
linux-kernel@vger.kernel.org, nd@arm.com
Subject: Re: [PATCH v2 0/4] Add support for Arm Framebuffer Compression(AFBC)
Date: Mon, 10 Sep 2018 15:26:49 +0300 [thread overview]
Message-ID: <20180910122649.GO5565@intel.com> (raw)
In-Reply-To: <20180909120357.GA19774@phenom.ffwll.local>
On Sun, Sep 09, 2018 at 02:03:57PM +0200, Daniel Vetter wrote:
> On Sat, Sep 08, 2018 at 03:58:53PM +0200, Neil Armstrong wrote:
> > Hi Ayan,
> >
> > On 10/07/2018 15:18, Ayan Kumar Halder wrote:
> > > In the current series of patches, we are trying to add support for AFBC
> > > modifiers in malidp. AFBC modifiers adds some constraints to framebuffer
> > > size, alignment, pitch, formats, etc. Here we are trying to add support
> > > for one combination of AFBC modifier ie AFBC_FORMAT_MOD_BLOCK_SIZE_16x16 |
> > > AFBC_FORMAT_MOD_SPARSE | AFBC_FORMAT_MOD_YTR.
> > > In future, we intend to add support for more combination of AFBC modifiers.
> > > Currently, we are trying to enable a basic support of AFBC in malidp.
> >
> > Thanks for pushing AFBC support, this will help supporting it on other SoCs implementing support
> > like Amlogic, Rockchip or Samsung.
> >
> > I have one question, is there a way to generate such AFBC buffers without the Mali GPU ?
> > I mean, is there a way to generate some sample buffers with some of the modifier features
> > to validate it without having the complete Mali GPU -> DRM chain ?
>
> An igt would be perfect. We've done that for i915 compressed buffers. Note
> that it just needs to be an afbc buffer, not actually compressed. Setting
> all the bits to indicate "uncompressed" for each block is what we did for
> the i915 test.
Actually no. The i915 test does try to put some compressed data into the
buffer.
I have also a pending patch series [1] that allows us to render to
compressed buffers with cairo by compressing the results using the
GPU.
[1] https://patchwork.freedesktop.org/series/46876/
--
Ville Syrjälä
Intel
prev parent reply other threads:[~2018-09-10 12:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 13:18 [PATCH v2 0/4] Add support for Arm Framebuffer Compression(AFBC) Ayan Kumar Halder
2018-07-10 13:18 ` [PATCH v2 1/4] drm/arm/malidp: Add modifier definitions for describing Arm Framebuffer Compression (AFBC) Ayan Kumar Halder
2018-07-10 13:18 ` [PATCH v2 2/4] drm/arm/malidp: Implemented the size validation for AFBC framebuffers Ayan Kumar Halder
2018-07-11 9:29 ` Liviu Dudau
2018-07-10 13:18 ` [PATCH v2 3/4] drm/arm/malidp: Set the AFBC register bits if the framebuffer has AFBC modifier Ayan Kumar Halder
2018-07-11 9:32 ` Liviu Dudau
2018-07-10 13:18 ` [PATCH v2 4/4] drm/arm/malidp: Added support for AFBC modifiers for all layers except DE_SMART Ayan Kumar Halder
2018-07-11 9:33 ` Liviu Dudau
2018-09-08 13:58 ` [PATCH v2 0/4] Add support for Arm Framebuffer Compression(AFBC) Neil Armstrong
2018-09-09 12:03 ` Daniel Vetter
2018-09-10 12:26 ` Ville Syrjälä [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=20180910122649.GO5565@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=airlied@linux.ie \
--cc=ayan.halder@arm.com \
--cc=brian.starkey@arm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liviu.dudau@arm.com \
--cc=malidp@foss.arm.com \
--cc=narmstrong@baylibre.com \
--cc=nd@arm.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;
as well as URLs for NNTP newsgroup(s).