From: maxime.ripard@bootlin.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] drm/sun4i: backend: Support interleaved YUV planes
Date: Mon, 19 Mar 2018 22:06:06 +0100 [thread overview]
Message-ID: <20180319210606.svrm3a345736qhwf@flea> (raw)
In-Reply-To: <cover.f0cb3210f2d878853ef16506da152f38ba2e3286.1519931807.git-series.maxime.ripard@bootlin.com>
On Thu, Mar 01, 2018 at 08:18:44PM +0100, Maxime Ripard wrote:
> Hi,
>
> This is an attempt at supporting the interleaved YUV planes in the sun4i
> DRM driver for SoCs that use the DE1.
>
> There's nothing out of the extraordinary there, we just have one more
> constraint in our DRM driver, since we can only have a single YUV plane.
>
> Let me know what you think,
> Maxime
Applied both with Chen-Yu comments fixed.
Maxime
--
Maxime Ripard, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20180319/c3893184/attachment.sig>
prev parent reply other threads:[~2018-03-19 21:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 19:18 [PATCH 0/2] drm/sun4i: backend: Support interleaved YUV planes Maxime Ripard
2018-03-01 19:18 ` [PATCH 1/2] drm/sun4i: backend: Check that we only have a single YUV plane Maxime Ripard
2018-03-15 13:01 ` Chen-Yu Tsai
2018-03-01 19:18 ` [PATCH 2/2] drm/sun4i: backend: Support YUV planes Maxime Ripard
2018-03-15 14:04 ` Chen-Yu Tsai
2018-03-19 21:06 ` 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=20180319210606.svrm3a345736qhwf@flea \
--to=maxime.ripard@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.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