linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Takanari Hayama <taki@igel.co.jp>
Cc: linux-media@vger.kernel.org, linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 2/2] v4l: vsp1: Always enable virtual RPF when BRU is in use
Date: Thu, 27 Nov 2014 20:03:41 +0000	[thread overview]
Message-ID: <6244918.ULpQcsacKi@avalon> (raw)
In-Reply-To: <1417051502-30169-3-git-send-email-taki@igel.co.jp>

Hi Hayama-san,

Thank you for the patch.

On Thursday 27 November 2014 10:25:02 Takanari Hayama wrote:
> Regardless of a number of inputs, we should always enable virtual RPF
> when BRU is used. This allows the case when there's only one input to
> BRU, and a size of the input is smaller than a size of an output of BRU.
> 
> Signed-off-by: Takanari Hayama <taki@igel.co.jp>

Acked-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

I've applied the patch to my tree. I'll wait for your reply regarding my 
comments to the first patch and will then send a pull request for both.

> ---
>  drivers/media/platform/vsp1/vsp1_wpf.c | 11 ++++++-----
>  1 file changed, 6 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/media/platform/vsp1/vsp1_wpf.c
> b/drivers/media/platform/vsp1/vsp1_wpf.c index 6e05776..cb17c4d 100644
> --- a/drivers/media/platform/vsp1/vsp1_wpf.c
> +++ b/drivers/media/platform/vsp1/vsp1_wpf.c
> @@ -92,19 +92,20 @@ static int wpf_s_stream(struct v4l2_subdev *subdev, int
> enable) return 0;
>  	}
> 
> -	/* Sources. If the pipeline has a single input configure it as the
> -	 * master layer. Otherwise configure all inputs as sub-layers and
> -	 * select the virtual RPF as the master layer.
> +	/* Sources. If the pipeline has a single input and BRU is not used,
> +	 * configure it as the master layer. Otherwise configure all
> +	 * inputs as sub-layers and select the virtual RPF as the master
> +	 * layer.
>  	 */
>  	for (i = 0; i < pipe->num_inputs; ++i) {
>  		struct vsp1_rwpf *input = pipe->inputs[i];
> 
> -		srcrpf |= pipe->num_inputs = 1
> +		srcrpf |= (!pipe->bru && pipe->num_inputs = 1)
>  			? VI6_WPF_SRCRPF_RPF_ACT_MST(input->entity.index)
> 
>  			: VI6_WPF_SRCRPF_RPF_ACT_SUB(input->entity.index);
> 
>  	}
> 
> -	if (pipe->num_inputs > 1)
> +	if (pipe->bru || pipe->num_inputs > 1)
>  		srcrpf |= VI6_WPF_SRCRPF_VIRACT_MST;
> 
>  	vsp1_wpf_write(wpf, VI6_WPF_SRCRPF, srcrpf);

-- 
Regards,

Laurent Pinchart


  reply	other threads:[~2014-11-27 20:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-27  1:25 [PATCH v2 0/2] v4l: vsp1: crop and a single input issues Takanari Hayama
2014-11-27  1:25 ` [PATCH v2 1/2] v4l: vsp1: Reset VSP1 RPF source address Takanari Hayama
2014-11-27 19:11   ` Laurent Pinchart
2014-11-27 23:35     ` Takanari Hayama
2014-11-27  1:25 ` [PATCH v2 2/2] v4l: vsp1: Always enable virtual RPF when BRU is in use Takanari Hayama
2014-11-27 20:03   ` Laurent Pinchart [this message]
2014-11-27 23:37     ` Takanari Hayama

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=6244918.ULpQcsacKi@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=taki@igel.co.jp \
    /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).