From: Philipp Zabel <p.zabel@pengutronix.de>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, kernel@pengutronix.de,
patchwork-lst@pengutronix.de
Subject: Re: [PATCH 1/3] [media] coda: use correct offset for mvcol buffer
Date: Wed, 05 Apr 2017 15:49:53 +0200 [thread overview]
Message-ID: <1491400193.2381.96.camel@pengutronix.de> (raw)
In-Reply-To: <20170405130955.30513-1-l.stach@pengutronix.de>
On Wed, 2017-04-05 at 15:09 +0200, Lucas Stach wrote:
> The mvcol buffer needs to be placed behind the chroma plane(s), so
> use the real offset including any required rounding.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
Reviewed-by: Philipp Zabel <p.zabel@pengutronix.de>
regards
Philipp
> ---
> drivers/media/platform/coda/coda-bit.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/media/platform/coda/coda-bit.c b/drivers/media/platform/coda/coda-bit.c
> index 466a44e4549e..36062fc494e3 100644
> --- a/drivers/media/platform/coda/coda-bit.c
> +++ b/drivers/media/platform/coda/coda-bit.c
> @@ -387,14 +387,16 @@ static int coda_alloc_framebuffers(struct coda_ctx *ctx,
>
> /* Register frame buffers in the parameter buffer */
> for (i = 0; i < ctx->num_internal_frames; i++) {
> - u32 y, cb, cr;
> + u32 y, cb, cr, mvcol;
>
> /* Start addresses of Y, Cb, Cr planes */
> y = ctx->internal_frames[i].paddr;
> cb = y + ysize;
> cr = y + ysize + ysize/4;
> + mvcol = y + ysize + ysize/4 + ysize/4;
> if (ctx->tiled_map_type == GDI_TILED_FRAME_MB_RASTER_MAP) {
> cb = round_up(cb, 4096);
> + mvcol = cb + ysize/2;
> cr = 0;
> /* Packed 20-bit MSB of base addresses */
> /* YYYYYCCC, CCyyyyyc, cccc.... */
> @@ -408,9 +410,7 @@ static int coda_alloc_framebuffers(struct coda_ctx *ctx,
> /* mvcol buffer for h.264 */
> if (ctx->codec->src_fourcc == V4L2_PIX_FMT_H264 &&
> dev->devtype->product != CODA_DX6)
> - coda_parabuf_write(ctx, 96 + i,
> - ctx->internal_frames[i].paddr +
> - ysize + ysize/4 + ysize/4);
> + coda_parabuf_write(ctx, 96 + i, mvcol);
> }
>
> /* mvcol buffer for mpeg4 */
prev parent reply other threads:[~2017-04-05 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 13:09 [PATCH 1/3] [media] coda: use correct offset for mvcol buffer Lucas Stach
2017-04-05 13:09 ` [PATCH 2/3] [media] coda: first step at error recovery Lucas Stach
2017-04-05 13:49 ` Philipp Zabel
2017-06-07 7:21 ` Hans Verkuil
2017-04-05 13:09 ` [PATCH 3/3] [media] coda/imx-vdoa: always wait for job completion Lucas Stach
2017-04-05 14:13 ` Philipp Zabel
2017-04-05 13:49 ` Philipp Zabel [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=1491400193.2381.96.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=patchwork-lst@pengutronix.de \
/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).