From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Icenowy Zheng <icenowy@aosc.io>
Cc: Rob Herring <robh+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-sunxi@googlegroups.com
Subject: Re: [PATCH v7 03/13] dt-bindings: add bindings for DE2 on V3s SoC
Date: Mon, 15 May 2017 11:24:28 +0200 [thread overview]
Message-ID: <20170515092428.dby2cw62gfbfq3ry@flea.home> (raw)
In-Reply-To: <20170514163045.40366-4-icenowy@aosc.io>
[-- Attachment #1: Type: text/plain, Size: 459 bytes --]
On Mon, May 15, 2017 at 12:30:35AM +0800, Icenowy Zheng wrote:
> Allwinner V3s SoC have a display engine which have a different pipeline
> with older SoCs.
>
> Add document for it (new compatibles and the new "mixer" part).
>
> Signed-off-by: Icenowy Zheng <icenowy@aosc.io>
> Acked-by: Rob Herring <robh@kernel.org>
Applied, thanks!
maxime
--
Maxime Ripard, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2017-05-15 9:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-14 16:30 [PATCH v7 00/13] Initial Allwinner Display Engine 2.0 Support Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 01/13] dt-bindings: add binding for the Allwinner DE2 CCU Icenowy Zheng
2017-05-15 8:40 ` Maxime Ripard
2017-05-14 16:30 ` [PATCH v7 02/13] clk: sunxi-ng: add support for " Icenowy Zheng
2017-05-15 8:40 ` Maxime Ripard
2017-05-14 16:30 ` [PATCH v7 03/13] dt-bindings: add bindings for DE2 on V3s SoC Icenowy Zheng
2017-05-15 9:24 ` Maxime Ripard [this message]
2017-05-14 16:30 ` [PATCH v7 04/13] drm/sun4i: return only planes for layers created Icenowy Zheng
2017-05-15 9:24 ` Maxime Ripard
2017-05-14 16:30 ` [PATCH v7 05/13] drm/sun4i: abstract a engine type Icenowy Zheng
2017-05-15 9:20 ` Maxime Ripard
2017-05-15 9:35 ` [linux-sunxi] " Icenowy Zheng
2017-05-16 12:14 ` Maxime Ripard
2017-05-14 16:30 ` [PATCH v7 06/13] drm/sun4i: add a dedicated module for sun4i-backend and sun4i-layer Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 07/13] drm/sun4i: add a Kconfig option for sun4i-backend Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 08/13] drm/sun4i: add support for Allwinner DE2 mixers Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 09/13] drm/sun4i: Add compatible string for V3s display engine Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 10/13] drm/sun4i: tcon: add support for V3s TCON Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 11/13] ARM: sun8i: v3s: add device nodes for DE2 display pipeline Icenowy Zheng
2017-05-15 9:24 ` Maxime Ripard
2017-05-17 9:27 ` icenowy
2017-05-17 9:32 ` icenowy
2017-05-14 16:30 ` [PATCH v7 12/13] ARM: sun8i: v3s: add pinmux for LCD pins of V3s SoC Icenowy Zheng
2017-05-14 16:30 ` [PATCH v7 13/13] [DO NOT MERGE] ARM: sun8i: v3s: enable LCD panel of Lichee Pi Zero Icenowy Zheng
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=20170515092428.dby2cw62gfbfq3ry@flea.home \
--to=maxime.ripard@free-electrons.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=icenowy@aosc.io \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@googlegroups.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).