From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: Kieran Bingham <kbingham@kernel.org>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [RFC 1/3] Revert "[media] v4l: vsp1: Supply frames to the DU continuously"
Date: Thu, 03 Nov 2016 01:57:43 +0200 [thread overview]
Message-ID: <61591109.Gs03RqNDyH@avalon> (raw)
In-Reply-To: <1477576885-21978-2-git-send-email-kieran.bingham+renesas@ideasonboard.com>
Hi Kieran,
Thank you for the patch.
On Thursday 27 Oct 2016 15:01:23 Kieran Bingham wrote:
> This reverts commit 3299ba5c0b213be5d911752d40251c1abc1004f7.
>
> The DU output mode does not rely on frames being supplied on the WPF as
> its pipeline is supplied from DRM. For the upcoming WPF writeback
> functionality, we will choose to enable writeback mode if there is an
> output buffer, or disable it (leaving the existing display pipeline
> unharmed) otherwise.
>
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
and applied to my tree.
> ---
> drivers/media/platform/vsp1/vsp1_video.c | 11 -----------
> 1 file changed, 11 deletions(-)
>
> diff --git a/drivers/media/platform/vsp1/vsp1_video.c
> b/drivers/media/platform/vsp1/vsp1_video.c index 94b428596c4f..f10401065cd3
> 100644
> --- a/drivers/media/platform/vsp1/vsp1_video.c
> +++ b/drivers/media/platform/vsp1/vsp1_video.c
> @@ -296,11 +296,6 @@ static struct v4l2_rect vsp1_video_partition(struct
> vsp1_pipeline *pipe, * This function completes the current buffer by
> filling its sequence number, * time stamp and payload size, and hands it
> back to the videobuf core. *
> - * When operating in DU output mode (deep pipeline to the DU through the
> LIF), - * the VSP1 needs to constantly supply frames to the display. In
> that case, if - * no other buffer is queued, reuse the one that has just
> been processed instead - * of handing it back to the videobuf core.
> - *
> * Return the next queued buffer or NULL if the queue is empty.
> */
> static struct vsp1_vb2_buffer *
> @@ -322,12 +317,6 @@ vsp1_video_complete_buffer(struct vsp1_video *video)
> done = list_first_entry(&video->irqqueue,
> struct vsp1_vb2_buffer, queue);
>
> - /* In DU output mode reuse the buffer if the list is singular. */
> - if (pipe->lif && list_is_singular(&video->irqqueue)) {
> - spin_unlock_irqrestore(&video->irqlock, flags);
> - return done;
> - }
> -
> list_del(&done->queue);
>
> if (!list_empty(&video->irqqueue))
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2016-11-02 23:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-27 14:01 [RFC 0/3] vsp1 writeback prototype Kieran Bingham
2016-10-27 14:01 ` [RFC 1/3] Revert "[media] v4l: vsp1: Supply frames to the DU continuously" Kieran Bingham
2016-11-02 23:57 ` Laurent Pinchart [this message]
2016-10-27 14:01 ` [RFC 2/3] v4l: vsp1: allow entities to have multiple source pads Kieran Bingham
2016-11-02 23:59 ` Laurent Pinchart
2016-11-03 10:51 ` Kieran Bingham
2016-10-27 14:01 ` [RFC 3/3] v4l: vsp1: Provide a writeback video device Kieran Bingham
2016-11-01 12:19 ` Kieran Bingham
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=61591109.Gs03RqNDyH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=kbingham@kernel.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@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).