mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Chen-Yu Tsai <wens@csie.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, narmstrong@baylibre.com,
	thomas@vitsch.nl
Subject: Re: [PATCH v4 00/13] drm/sun4i: Support the Display Engine frontend
Date: Mon, 22 Jan 2018 15:27:30 +0100	[thread overview]
Message-ID: <20180122142730.lsfxdhgeetmavwpj@flea.lan> (raw)
In-Reply-To: <cover.671c2fcad4ca649d65bd2b9982a8361befa8bfd1.1516613040.git-series.maxime.ripard@free-electrons.com>

[-- Attachment #1: Type: text/plain, Size: 785 bytes --]

On Mon, Jan 22, 2018 at 10:25:14AM +0100, 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.

Applied the DRM patches to drm-misc-next, and queued the dt patch for 4.17.

Maxime

-- 
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      parent reply	other threads:[~2018-01-22 14:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-22  9:25 Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 01/13] drm/sun4i: backend: Move line stride setup to buffer setup function Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 02/13] drm/sun4i: backend: Document the engine operations Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 03/13] drm/sun4i: backend: Allow a NULL plane pointer to retrieve the format Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 04/13] drm/sun4i: backend: Add a custom plane state Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 05/13] drm/sun4i: engine: Add a custom crtc atomic_check Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 06/13] drm/sun4i: engine: Add a VBLANK quirk callback Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 07/13] drm/sun4i: engine: Create an atomic_begin callback Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 08/13] drm/sun4i: Add a driver for the display frontend Maxime Ripard
2018-01-22 13:28   ` Chen-Yu Tsai
2018-01-22  9:25 ` [PATCH v4 09/13] drm/sun4i: backend: Wire in the frontend Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 10/13] drm/sun4i: backend: Add a custom atomic_check for " Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 11/13] drm/sun4i: backend: Use runtime_pm variant of atomic_commit_tail Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 12/13] drm/sun4i: backend: Make sure we don't have a commit pending Maxime Ripard
2018-01-22  9:25 ` [PATCH v4 13/13] ARM: dts: sun8i: a33 Enable our display frontend Maxime Ripard
2018-01-22 14:27 ` Maxime Ripard [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=20180122142730.lsfxdhgeetmavwpj@flea.lan \
    --to=maxime.ripard@free-electrons.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=thomas@vitsch.nl \
    --cc=wens@csie.org \
    /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

all inboxes | Powered by JetHome®