From: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
To: imre.deak@intel.com
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 2/3] lib/igt_fb: Use render copy/blit for tiled formats on platforms w/o HW detiling
Date: Tue, 21 Jan 2020 19:59:30 +0200 [thread overview]
Message-ID: <4f43500b-1bb7-4e60-065e-b2a95af4797e@gmail.com> (raw)
In-Reply-To: <20200121163517.GA7975@ideak-desk.fi.intel.com>
On 21.1.2020 18.35, Imre Deak wrote:
> On Tue, Jan 21, 2020 at 06:19:30PM +0200, Juha-Pekka Heikkila wrote:
>> On 21.1.2020 0.03, Imre Deak wrote:
>>> On platforms without HW detiling use render copy or blitting to convert
>>> between a tiled and a linear framebuffer.
>>>
>>> Signed-off-by: Imre Deak <imre.deak@intel.com>
>>> ---
>>> lib/igt_fb.c | 16 +++++++++++++---
>>> 1 file changed, 13 insertions(+), 3 deletions(-)
>>>
>>> diff --git a/lib/igt_fb.c b/lib/igt_fb.c
>>> index c81b9de8..b5b1750e 100644
>>> --- a/lib/igt_fb.c
>>> +++ b/lib/igt_fb.c
>>> @@ -1975,17 +1975,27 @@ static bool blitter_ok(const struct igt_fb *fb)
>>> return true;
>>> }
>>> +static bool hw_can_detile(const struct igt_fb *fb)
>>> +{
>>> + if (fb->modifier == DRM_FORMAT_MOD_NONE)
>>> + return true;
>>> +
>>> + if (!gem_has_legacy_hw_tiling(fb->fd))
>>> + return false;
>>> +
>>> + return fb->modifier != I915_FORMAT_MOD_Yf_TILED;
>>
>> Should above line depend on gen? Like
>> return (gen < 12 || fb->modifier != I915_FORMAT_MOD_Yf_TILED); ?
>
> AFAIK no platform can detile the Yf format (only X or Y), but this
> shouldn't change the logic in any case, except for
> !gem_has_legacy_hw_tiling().
>
You are right.
Reviewed-by: Juha-Pekka Heikkila <juhapekka.heikkila@gmail.com>
>>
>>> +}
>>> +
>>> static bool use_enginecopy(const struct igt_fb *fb)
>>> {
>>> return is_ccs_modifier(fb->modifier) ||
>>> - (fb->modifier == I915_FORMAT_MOD_Yf_TILED &&
>>> - !blitter_ok(fb));
>>> + (!hw_can_detile(fb) && !blitter_ok(fb));
>>> }
>>> static bool use_blitter(const struct igt_fb *fb)
>>> {
>>> return (fb->modifier == I915_FORMAT_MOD_Y_TILED ||
>>> - fb->modifier == I915_FORMAT_MOD_Yf_TILED) &&
>>> + !hw_can_detile(fb)) &&
>>> blitter_ok(fb);
>>> }
>>>
>>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2020-01-21 17:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-20 22:03 [igt-dev] [PATCH i-g-t 1/3] lib/ioctl_wrappers: Query if device supports set/get legacy tiling Imre Deak
2020-01-20 22:03 ` [igt-dev] [PATCH i-g-t 2/3] lib/igt_fb: Use render copy/blit for tiled formats on platforms w/o HW detiling Imre Deak
2020-01-21 16:19 ` Juha-Pekka Heikkila
2020-01-21 16:35 ` Imre Deak
2020-01-21 17:59 ` Juha-Pekka Heikkila [this message]
2020-01-22 6:02 ` Dixit, Ashutosh
2020-01-22 9:34 ` Imre Deak
2020-01-20 22:03 ` [igt-dev] [PATCH i-g-t 3/3] lib/igt_fb: Fix creating FBs " Imre Deak
2020-01-21 16:21 ` Juha-Pekka Heikkila
2020-01-21 4:27 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/3] lib/ioctl_wrappers: Query if device supports set/get legacy tiling Patchwork
2020-01-21 19:26 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=4f43500b-1bb7-4e60-065e-b2a95af4797e@gmail.com \
--to=juhapekka.heikkila@gmail.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=imre.deak@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