public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: Maxime Ripard <maxime.ripard@bootlin.com>, igt-dev@lists.freedesktop.org
Cc: Petri Latvala <petri.latvala@intel.com>,
	eben@raspberrypi.org,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [igt-dev] [PATCH i-g-t v4 05/14] igt: fb: Move size computation to the common path
Date: Tue, 22 Jan 2019 16:46:23 +0100	[thread overview]
Message-ID: <26bfcb982055a76c34baa9eaf5ae81f485f206e3.camel@bootlin.com> (raw)
In-Reply-To: <20190122142844.20899-6-maxime.ripard@bootlin.com>

Hi,

On Tue, 2019-01-22 at 15:28 +0100, Maxime Ripard wrote:
> In order to properly support the YUV buffer on non-i915 platforms, we need
> to run calc_fb_size for the dumb buffers allocation path too. Move it out
> of the special case and in the common code path.
> 
> Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
> ---
>  lib/igt_fb.c | 12 +++++-------
>  1 file changed, 5 insertions(+), 7 deletions(-)
> 
> diff --git a/lib/igt_fb.c b/lib/igt_fb.c
> index d69c3fb2d38d..a1368ec4703a 100644
> --- a/lib/igt_fb.c
> +++ b/lib/igt_fb.c
> @@ -528,16 +528,14 @@ static void clear_yuv_buffer(struct igt_fb *fb)
>  /* helpers to create nice-looking framebuffers */
>  static int create_bo_for_fb(struct igt_fb *fb)
>  {
> +	uint64_t size = calc_fb_size(fb);
>  	int fd = fb->fd;
>  
> -	if (fb->tiling || fb->size || fb->strides[0] || igt_format_is_yuv(fb->drm_format)) {
> -		uint64_t size;
> +	/* respect the size requested by the caller */
> +	if (fb->size == 0)
> +		fb->size = size;
>
> -		size = calc_fb_size(fb);
> -
> -		/* respect the size requested by the caller */
> -		if (fb->size == 0)
> -			fb->size = size;
> +	if (fb->tiling || fb->size || igt_format_is_yuv(fb->drm_format)) {

So in this case, fb->size would also never be zero (it's always set a
few lines before). Looking back at all this, we lose the ability to set
an arbitrary stride and size (unless it's Intel and tiled or YUV),
which is a bit problematic.

I think those things are definitely good to allow and keep, so I guess
we should hit the driver-specific GEM allocation when they occur (as
was the case until now).

In cases where we don't have any driver-specific implementation that
might allow a specific size/stride, I think it would be best to produce
an error rather than falling back on dumb alloc that won't honor what
was requested.

So that implies keeping stride = 0 and size = 0 intact when going
through this function.

I should probably have thought this up on the previous revision before
advising to remove the check on the stride though, sorry.

What do you think?

Cheers,

Paul

>  		fb->is_dumb = false;
>  
-- 
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-01-22 15:46 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-22 14:28 [igt-dev] [PATCH i-g-t v4 00/14] igt: chamelium: Test YUV buffers using the Chamelium Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 01/14] igt: fb: Add subsampling parameters to the formats Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 02/14] igt: fb: Reduce tile size alignment for non intel platforms Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 03/14] igt: fb: generic YUV convertion function Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 04/14] igt: fb: Move i915 YUV buffer clearing code to a function Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 05/14] igt: fb: Move size computation to the common path Maxime Ripard
2019-01-22 15:46   ` Paul Kocialkowski [this message]
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 06/14] igt: fb: Refactor dumb buffer allocation path Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 07/14] igt: fb: Account for all planes bpp Maxime Ripard
2019-01-22 15:46   ` Paul Kocialkowski
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 08/14] igt: fb: Don't pass the stride when allocating a dumb, multi-planar buffer Maxime Ripard
2019-01-22 15:48   ` Paul Kocialkowski
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 09/14] igt: fb: Clear YUV dumb buffers Maxime Ripard
2019-01-22 15:48   ` Paul Kocialkowski
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 10/14] igt: fb: Rework YUV i915 allocation path Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 11/14] igt: fb: Add a bunch of new YUV formats Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 12/14] igt: tests: chamelium: Start to unify tests Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 13/14] igt: tests: chamelium: Convert VGA tests to do_test_display Maxime Ripard
2019-01-22 14:28 ` [igt-dev] [PATCH i-g-t v4 14/14] igt: tests: chamelium: Add YUV formats tests Maxime Ripard
2019-01-22 14:52 ` [igt-dev] ✓ Fi.CI.BAT: success for igt: chamelium: Test YUV buffers using the Chamelium (rev6) Patchwork
2019-01-22 17:23 ` [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=26bfcb982055a76c34baa9eaf5ae81f485f206e3.camel@bootlin.com \
    --to=paul.kocialkowski@bootlin.com \
    --cc=eben@raspberrypi.org \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maxime.ripard@bootlin.com \
    --cc=petri.latvala@intel.com \
    --cc=thomas.petazzoni@bootlin.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