From: Neil Armstrong <narmstrong@baylibre.com>
To: 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
Cc: nd@arm.com
Subject: Re: [PATCH v2 0/4] Add support for Arm Framebuffer Compression(AFBC)
Date: Sat, 8 Sep 2018 15:58:53 +0200 [thread overview]
Message-ID: <0e22e63c-6981-9e5d-ed2d-2ad1dfbccd4f@baylibre.com> (raw)
In-Reply-To: <1531228737-5450-1-git-send-email-ayan.halder@arm.com>
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 ?
Thanks in advance,
Neil
>
> Changes from v2:
> - Added ack by Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> for patch 1. However, this has been kept in this series in order to help
> reviewers review the other patches (which are related to patch 1)
> - For patches 2 and 4, replaced DRM_ERROR() with DRM_DEBUG_KMS()
> - For patch 3, reworked malidp_de_set_plane_afbc() so as to consolidate
> all afbc specific register configuration in this.
>
> Ayan Kumar Halder (4):
> drm/arm/malidp: Add modifier definitions for describing Arm
> Framebuffer Compression (AFBC).
> drm/arm/malidp: Implemented the size validation for AFBC framebuffers
> drm/arm/malidp: Set the AFBC register bits if the framebuffer has AFBC
> modifier
> drm/arm/malidp: Added support for AFBC modifiers for all layers except
> DE_SMART
>
> drivers/gpu/drm/arm/malidp_drv.c | 129 +++++++++++++++++++++++++++++++++++-
> drivers/gpu/drm/arm/malidp_hw.c | 27 +++++---
> drivers/gpu/drm/arm/malidp_hw.h | 7 ++
> drivers/gpu/drm/arm/malidp_planes.c | 129 +++++++++++++++++++++++++++++++++---
> drivers/gpu/drm/arm/malidp_regs.h | 20 ++++++
> include/uapi/drm/drm_fourcc.h | 83 +++++++++++++++++++++++
> 6 files changed, 373 insertions(+), 22 deletions(-)
>
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-08 13:58 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 ` Neil Armstrong [this message]
2018-09-09 12:03 ` [PATCH v2 0/4] Add support for Arm Framebuffer Compression(AFBC) Daniel Vetter
2018-09-10 12:26 ` Ville Syrjälä
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=0e22e63c-6981-9e5d-ed2d-2ad1dfbccd4f@baylibre.com \
--to=narmstrong@baylibre.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=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).