From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Eric Anholt <eric@anholt.net>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 1/2] drm/vc4: Fix negative X/Y positioning on SAND planes
Date: Thu, 6 Dec 2018 20:29:19 +0100 [thread overview]
Message-ID: <20181206202919.43fce719@bbrezillon> (raw)
In-Reply-To: <87woomqy62.fsf@anholt.net>
On Thu, 06 Dec 2018 10:59:17 -0800
Eric Anholt <eric@anholt.net> wrote:
> > +
> > + /*
> > + * SCALER_PITCH0_SINK_PIX does not seem to work for SAND
> > + * formats. Specify a negative START_X instead, even if it's
> > + * less efficient.
> > + */
> > + if (x_off)
> > + vc4_state->crtc_x = -x_off;
>
> Wait. If we were supposed to start at a nonzero x position within the
> FB, then we instead put the image off the left hand side of the screen?
> That seems wrong.
Yep, I overlooked this case.
>
> Did you test if we can just vc4_state->offsets[i] += x_off * cpp?
Yep, I tried, and it doesn't seem to work. We have to tell the HVS that
some pixels must be skipped at the beginning of each line of the first
tile. That's what SINK_PIX(x_off) is supposed to do, but it seems to be
broken for 2 reasons:
1/ the max value of SINK_PIX is 63, but the HVS supports 128 and 256
bytes tiles.
2/ looks like the UV plane is truncated when we specify a SINK_PIX!=0.
Don't know why exactly.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-12-06 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 16:45 [PATCH v2 1/2] drm/vc4: Fix negative X/Y positioning on SAND planes Boris Brezillon
2018-12-05 16:45 ` [PATCH v2 2/2] drm/vc4: Add support for X/Y reflection Boris Brezillon
2018-12-06 19:00 ` Eric Anholt
2018-12-06 18:59 ` [PATCH v2 1/2] drm/vc4: Fix negative X/Y positioning on SAND planes Eric Anholt
2018-12-06 19:29 ` Boris Brezillon [this message]
2018-12-07 8:19 ` Boris Brezillon
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=20181206202919.43fce719@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.