From: Mark yao <mark.yao@rock-chips.com>
To: David Airlie <airlied@linux.ie>, Heiko Stuebner <heiko@sntech.de>,
dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] drm/rockchip: vop: support afbc format for rk3399 vop
Date: Sat, 10 Sep 2016 11:12:26 +0800 [thread overview]
Message-ID: <57D37A1A.6050500@rock-chips.com> (raw)
In-Reply-To: <1473476852-25707-1-git-send-email-mark.yao@rock-chips.com>
Sorry, wrong title on this mail, ignore this mail. I had resent it.
On 2016年09月10日 11:07, Mark Yao wrote:
> Rk3399 vop big can support one afbc decoder, the afbc decoder
> can select which overlay window use it.
>
> on vop hardware, we call afbc decoder as afbdc.
>
> afbdc window has some limit:
> 1, not support offset on source buffer.
> 2, if feed non-afbc buffer to afbc decoder, afbc decoder hardware
> would die, we need take care of using it.
>
> AFBC is a compressed format, means lower bandwidth consume,
> it's useful to improve performance.
>
> Signed-off-by: Mark Yao<mark.yao@rock-chips.com>
> ---
--
Ｍark Yao
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2016-09-10 3:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-10 2:29 [PATCH 1/3] drm/rockchip: vop: move dma_addr to plane atomic check Mark Yao
2016-09-10 2:29 ` [PATCH 2/3] drm: add ARM vendor format afbc Mark Yao
2016-09-13 14:13 ` Brian Starkey
2016-09-10 2:29 ` [PATCH 3/3] drm/rockchip: vop: support afdc for rk3399 vop Mark Yao
2016-09-10 3:07 ` [PATCH] drm/rockchip: vop: support afbc format " Mark Yao
2016-09-10 3:12 ` Mark yao [this message]
2016-09-10 3:10 ` [PATCH 3/3 v1.1] " Mark Yao
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=57D37A1A.6050500@rock-chips.com \
--to=mark.yao@rock-chips.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@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