From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Eric Anholt <eric@anholt.net>
Cc: David Airlie <airlied@linux.ie>,
stable@vger.kernel.org, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/vc4: Fix scaling of uni-planar formats
Date: Wed, 9 May 2018 09:43:24 +0200 [thread overview]
Message-ID: <20180509094324.2139ce11@bbrezillon> (raw)
In-Reply-To: <20180507181102.47ea0060@bbrezillon>
On Mon, 7 May 2018 18:11:02 +0200
Boris Brezillon <boris.brezillon@bootlin.com> wrote:
> On Mon, 07 May 2018 08:56:14 -0700
> Eric Anholt <eric@anholt.net> wrote:
>
> > Boris Brezillon <boris.brezillon@bootlin.com> writes:
> >
> > > When using uni-planar formats (like RGB), the scaling parameters are
> > > stored in plane 0, not plane 1.
> > >
> > > Fixes: fc04023fafec ("drm/vc4: Add support for YUV planes.")
> > > Cc: stable@vger.kernel.org
> > > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> >
> > Reviewed-by: Eric Anholt <eric@anholt.net>
> >
> > Looking at the other branch, did I get the scl0/scl1 backwards? HVS
> > docs say for non-444 YCBCR: "In these cases Channel 0 performs Y/Alpha
> > scaling and Channel 1 performs CB/CR scaling and should be configured as
> > appropriate."
>
> Didn't test, but I think rescaling of multi-planar format is correct.
I just tested, and I confirm the other branch is correct.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-05-09 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 12:13 [PATCH] drm/vc4: Fix scaling of uni-planar formats Boris Brezillon
2018-05-07 15:56 ` Eric Anholt
2018-05-07 16:11 ` Boris Brezillon
2018-05-09 7:43 ` Boris Brezillon [this message]
2018-05-09 7:50 ` 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=20180509094324.2139ce11@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=eric@anholt.net \
--cc=stable@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).