From: Maxime Ripard <maxime.ripard@bootlin.com>
To: Jernej Skrabec <jernej.skrabec@siol.net>
Cc: sboyd@kernel.org, mturquette@baylibre.com,
linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, airlied@linux.ie, wens@csie.org,
daniel@ffwll.ch, linux-clk@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] drm/sun4i: DE2/DE3 improvements
Date: Fri, 1 Mar 2019 15:59:21 +0100 [thread overview]
Message-ID: <20190301145921.ryjofwp57pjp2g4n@flea> (raw)
In-Reply-To: <20190228200329.11128-1-jernej.skrabec@siol.net>
[-- Attachment #1.1: Type: text/plain, Size: 494 bytes --]
On Thu, Feb 28, 2019 at 09:03:26PM +0100, Jernej Skrabec wrote:
> DE2 and DE3 VI channels support coarse scaling to overcome VI scaler
> limitations. That is especially useful for downscaling big planes, for
> example 4K to 1080p.
>
> Following patches were tested on H3 and A64 with 4K video playback on
> 1080p monitor. Without them, picture was mangled.
Applied all three, thanks!
Maxime
--
Maxime Ripard, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-03-01 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-28 20:03 [PATCH 0/3] drm/sun4i: DE2/DE3 improvements Jernej Skrabec
2019-02-28 20:03 ` [PATCH 1/3] clk: sunxi-ng: Allow DE clock to set parent rate Jernej Skrabec
2019-02-28 20:03 ` [PATCH 2/3] drm/sun4i: Add VI scaler line size quirk for DE2/DE3 Jernej Skrabec
2019-02-28 20:03 ` [PATCH 3/3] drm/sun4i: Improve VI scaling " Jernej Skrabec
2019-03-01 14:59 ` 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=20190301145921.ryjofwp57pjp2g4n@flea \
--to=maxime.ripard@bootlin.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@siol.net \
--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=mturquette@baylibre.com \
--cc=sboyd@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