From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753297AbdLMQQ0 (ORCPT ); Wed, 13 Dec 2017 11:16:26 -0500 Received: from PrakOutbound.VEHosting.nl ([85.17.51.155]:59890 "EHLO Prakkezator.VEHosting.nl" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752550AbdLMQQY (ORCPT ); Wed, 13 Dec 2017 11:16:24 -0500 Subject: Re: [PATCH 0/8] drm/sun4i: Support the Display Engine frontend To: Maxime Ripard , Daniel Vetter , David Airlie , Chen-Yu Tsai Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Thomas Petazzoni References: <1513181781-0808628882.0a9bc10eb7@prakkezator.vehosting.nl> From: Thomas van Kleef Organization: Vitsch Electronics Message-ID: <407ed605-6c02-fae5-7cc8-e6119b26d49f@vitsch.nl> Date: Wed, 13 Dec 2017 17:16:22 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit x-ve-auth-version: mi-1.3.0 2017-09-05 - Copyright (c) 2008, 2011-2012, 2014, 2016-2017 - Daan Vreeken - VEHosting x-ve-auth: authenticated as 'thomas@vitsch.nl' on Prakkezator.VEHosting.nl Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 13-12-17 16:33, Maxime Ripard wrote: > Hi, > > This is a first serie to enable the display engine frontend. > > This hardware block is found in the first generation Display Engine from > Allwinner. Its role is to implement more advanced features that the > associated backend, even though the backend alone can be used (and was used > so far) for basic composition. > > Among those features, we will find hardware scaling, that is supported in > this serie, colorspace conversions, or more exotic formats support such as > the one output by the VPU. So, if I have read the code correctly. The frontend will be used whenever the input size differs from the output size. > > Let me know what you think, > Maxime > > Maxime Ripard (8): > drm/sun4i: backend: Move line stride setup to buffer setup function > drm/sun4i: backend: Allow a NULL plane pointer to retrieve the format > drm/sun4i: sun4i_layer: Add a custom plane state > drm/sun4i: crtc: Add a custom crtc atomic_check > drm/sun4i: Add a driver for the display frontend > drm/sun4i: sun4i_layer: Wire in the frontend > drm/sun4i: sun4i_layer: Add a custom atomic_check for the frontend > ARM: dts: sun8i: a33 Enable our display frontend > > arch/arm/boot/dts/sun8i-a33.dtsi | 1 +- > drivers/gpu/drm/sun4i/Makefile | 3 +- > drivers/gpu/drm/sun4i/sun4i_backend.c | 139 +++++++++- > drivers/gpu/drm/sun4i/sun4i_backend.h | 6 +- > drivers/gpu/drm/sun4i/sun4i_crtc.c | 14 +- > drivers/gpu/drm/sun4i/sun4i_drv.c | 16 +- > drivers/gpu/drm/sun4i/sun4i_drv.h | 1 +- > drivers/gpu/drm/sun4i/sun4i_frontend.c | 377 ++++++++++++++++++++++++++- > drivers/gpu/drm/sun4i/sun4i_frontend.h | 102 +++++++- > drivers/gpu/drm/sun4i/sun4i_layer.c | 75 ++++- > drivers/gpu/drm/sun4i/sun4i_layer.h | 11 +- > drivers/gpu/drm/sun4i/sunxi_engine.h | 2 +- > 12 files changed, 727 insertions(+), 20 deletions(-) > create mode 100644 drivers/gpu/drm/sun4i/sun4i_frontend.c > create mode 100644 drivers/gpu/drm/sun4i/sun4i_frontend.h > > base-commit: 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323 > From mboxrd@z Thu Jan 1 00:00:00 1970 From: thomas@vitsch.nl (Thomas van Kleef) Date: Wed, 13 Dec 2017 17:16:22 +0100 Subject: [PATCH 0/8] drm/sun4i: Support the Display Engine frontend In-Reply-To: References: <1513181781-0808628882.0a9bc10eb7@prakkezator.vehosting.nl> Message-ID: <407ed605-6c02-fae5-7cc8-e6119b26d49f@vitsch.nl> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, On 13-12-17 16:33, Maxime Ripard wrote: > Hi, > > This is a first serie to enable the display engine frontend. > > This hardware block is found in the first generation Display Engine from > Allwinner. Its role is to implement more advanced features that the > associated backend, even though the backend alone can be used (and was used > so far) for basic composition. > > Among those features, we will find hardware scaling, that is supported in > this serie, colorspace conversions, or more exotic formats support such as > the one output by the VPU. So, if I have read the code correctly. The frontend will be used whenever the input size differs from the output size. > > Let me know what you think, > Maxime > > Maxime Ripard (8): > drm/sun4i: backend: Move line stride setup to buffer setup function > drm/sun4i: backend: Allow a NULL plane pointer to retrieve the format > drm/sun4i: sun4i_layer: Add a custom plane state > drm/sun4i: crtc: Add a custom crtc atomic_check > drm/sun4i: Add a driver for the display frontend > drm/sun4i: sun4i_layer: Wire in the frontend > drm/sun4i: sun4i_layer: Add a custom atomic_check for the frontend > ARM: dts: sun8i: a33 Enable our display frontend > > arch/arm/boot/dts/sun8i-a33.dtsi | 1 +- > drivers/gpu/drm/sun4i/Makefile | 3 +- > drivers/gpu/drm/sun4i/sun4i_backend.c | 139 +++++++++- > drivers/gpu/drm/sun4i/sun4i_backend.h | 6 +- > drivers/gpu/drm/sun4i/sun4i_crtc.c | 14 +- > drivers/gpu/drm/sun4i/sun4i_drv.c | 16 +- > drivers/gpu/drm/sun4i/sun4i_drv.h | 1 +- > drivers/gpu/drm/sun4i/sun4i_frontend.c | 377 ++++++++++++++++++++++++++- > drivers/gpu/drm/sun4i/sun4i_frontend.h | 102 +++++++- > drivers/gpu/drm/sun4i/sun4i_layer.c | 75 ++++- > drivers/gpu/drm/sun4i/sun4i_layer.h | 11 +- > drivers/gpu/drm/sun4i/sunxi_engine.h | 2 +- > 12 files changed, 727 insertions(+), 20 deletions(-) > create mode 100644 drivers/gpu/drm/sun4i/sun4i_frontend.c > create mode 100644 drivers/gpu/drm/sun4i/sun4i_frontend.h > > base-commit: 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323 >