From: Brian Starkey <Brian.Starkey@arm.com>
To: "james qian wang (Arm Technology China)" <james.qian.wang@arm.com>
Cc: "Ville Syrjälä" <ville.syrjala@linux.intel.com>, nd <nd@arm.com>,
"Lowry Li (Arm Technology China)" <Lowry.Li@arm.com>,
"Tiannan Zhu (Arm Technology China)" <Tiannan.Zhu@arm.com>,
"airlied@linux.ie" <airlied@linux.ie>,
"Liviu Dudau" <Liviu.Dudau@arm.com>,
"Jonathan Chai (Arm Technology China)" <Jonathan.Chai@arm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"Julien Yin (Arm Technology China)" <Julien.Yin@arm.com>,
"Yiqi Kang (Arm Technology China)" <Yiqi.Kang@arm.com>,
"thomas Sun (Arm Technology China)" <thomas.Sun@arm.com>,
"Ayan Halder" <Ayan.Halder@arm.com>,
"sean@poorly.run" <sean@poorly.run>
Subject: Re: [PATCH] drm/komeda: Added AFBC support for komeda driver
Date: Tue, 28 May 2019 15:26:43 +0000 [thread overview]
Message-ID: <20190528152641.yljgau26hhd6mr2d@DESKTOP-E1NTVVP.localdomain> (raw)
In-Reply-To: <20190527065110.GA29041@james-ThinkStation-P300>
Hi James,
On Mon, May 27, 2019 at 07:51:18AM +0100, james qian wang (Arm Technology China) wrote:
> Hi Brian & Ville:
>
> komed has a format+modifier check before the fb size check.
> and for komeda_fb_create, the first step is do the format+modifier
> check, the size check is the furthur check after the such format
> valid check. and the detailed fb_create is like:
Thanks for the detail, it sounds good.
-Brian
prev parent reply other threads:[~2019-05-28 15:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 11:06 [PATCH] drm/komeda: Added AFBC support for komeda driver james qian wang (Arm Technology China)
2019-05-16 13:57 ` Ayan Halder
2019-05-21 8:45 ` james qian wang (Arm Technology China)
2019-05-24 11:10 ` Brian Starkey
2019-05-24 12:12 ` Ville Syrjälä
2019-05-27 6:51 ` james qian wang (Arm Technology China)
2019-05-27 13:19 ` Ville Syrjälä
2019-05-28 15:26 ` Brian Starkey [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=20190528152641.yljgau26hhd6mr2d@DESKTOP-E1NTVVP.localdomain \
--to=brian.starkey@arm.com \
--cc=Ayan.Halder@arm.com \
--cc=Jonathan.Chai@arm.com \
--cc=Julien.Yin@arm.com \
--cc=Liviu.Dudau@arm.com \
--cc=Lowry.Li@arm.com \
--cc=Tiannan.Zhu@arm.com \
--cc=Yiqi.Kang@arm.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=james.qian.wang@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nd@arm.com \
--cc=sean@poorly.run \
--cc=thomas.Sun@arm.com \
--cc=ville.syrjala@linux.intel.com \
/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).