From: Steve Longerbeam <slongerbeam@gmail.com>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] media: imx: prpencvf: enable double write reduction
Date: Sat, 22 Jul 2017 15:04:57 -0700 [thread overview]
Message-ID: <a3299b77-917a-f946-d9fc-33efcf3f2721@gmail.com> (raw)
In-Reply-To: <1500758501-5394-1-git-send-email-steve_longerbeam@mentor.com>
Hi Philipp,
This is the same as your patch to CSI, applied to ic-prpencvf.
I'm not really sure what this cpmem bit is doing. The U/V planes
in memory are already subsampled by 2 in both width and height.
This must be referring to what the IDMAC is transferring on the bus,
but why would it place duplicate U/V samples on the bus in the first
place?
Anyway, thanks for the heads-up on this.
Steve
On 07/22/2017 02:21 PM, Steve Longerbeam wrote:
> For the write channels with 4:2:0 subsampled YUV formats, avoid chroma
> overdraw by only writing chroma for even lines. Reduces necessary write
> memory bandwidth by at least 25% (more with rotation enabled).
>
> Signed-off-by: Steve Longerbeam<steve_longerbeam@mentor.com>
> ---
> drivers/staging/media/imx/imx-ic-prpencvf.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/staging/media/imx/imx-ic-prpencvf.c b/drivers/staging/media/imx/imx-ic-prpencvf.c
> index ed363fe..42c5045 100644
> --- a/drivers/staging/media/imx/imx-ic-prpencvf.c
> +++ b/drivers/staging/media/imx/imx-ic-prpencvf.c
> @@ -374,6 +374,17 @@ static int prp_setup_channel(struct prp_priv *priv,
> image.phys0 = addr0;
> image.phys1 = addr1;
>
> + if (channel == priv->out_ch || channel == priv->rot_out_ch) {
> + switch (image.pix.pixelformat) {
> + case V4L2_PIX_FMT_YUV420:
> + case V4L2_PIX_FMT_YVU420:
> + case V4L2_PIX_FMT_NV12:
> + /* Skip writing U and V components to odd rows */
> + ipu_cpmem_skip_odd_chroma_rows(channel);
> + break;
> + }
> + }
> +
> ret = ipu_cpmem_set_image(channel, &image);
> if (ret)
> return ret;
next prev parent reply other threads:[~2017-07-22 22:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-22 21:21 Steve Longerbeam
2017-07-22 22:04 ` Steve Longerbeam [this message]
2017-07-24 7:21 ` Philipp Zabel
2017-07-24 7:21 ` Philipp Zabel
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=a3299b77-917a-f946-d9fc-33efcf3f2721@gmail.com \
--to=slongerbeam@gmail.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@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
all inboxes | Powered by JetHome®