From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
Cc: linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH 3/4] v4l: vsp1: Calculate partition sizes at stream start.
Date: Mon, 13 Feb 2017 23:21:58 +0200 [thread overview]
Message-ID: <3804080.QOE9vPlxB7@avalon> (raw)
In-Reply-To: <1478283570-19688-4-git-send-email-kieran.bingham+renesas@ideasonboard.com>
Hi Kieran,
Thank you for the patch.
On Friday 04 Nov 2016 18:19:29 Kieran Bingham wrote:
> Previously the active window and partition sizes for each partition is
s/is/were/
> calculated for each partition every frame. This data is constant and
> only needs to be calculated once at the start of the stream.
>
> Extend the vsp1_pipe object to store the maximum number of partitions
> possible and pre-calculate the partition sizes into this table.
>
> Signed-off-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> ---
> drivers/media/platform/vsp1/vsp1_pipe.h | 6 ++++++
> drivers/media/platform/vsp1/vsp1_video.c | 8 ++++++--
> 2 files changed, 12 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/platform/vsp1/vsp1_pipe.h
> b/drivers/media/platform/vsp1/vsp1_pipe.h index f181949824c9..3af96c4ea244
> 100644
> --- a/drivers/media/platform/vsp1/vsp1_pipe.h
> +++ b/drivers/media/platform/vsp1/vsp1_pipe.h
> @@ -20,6 +20,9 @@
>
> #include <media/media-entity.h>
>
> +/* Max Video Width / Min Partition Size = 8190/128 */
> +#define VSP1_PIPE_MAX_PARTITIONS 64
> +
> struct vsp1_dl_list;
> struct vsp1_rwpf;
>
> @@ -81,7 +84,9 @@ enum vsp1_pipeline_state {
> * @dl: display list associated with the pipeline
> * @div_size: The maximum allowed partition size for the pipeline
> * @partitions: The number of partitions used to process one frame
> + * @partition: The current partition for configuration to process
> * @current_partition: The partition number currently being configured
> + * @part_table: The pre-calculated partitions used by the pipeline
> */
> struct vsp1_pipeline {
> struct media_pipeline pipe;
> @@ -116,6 +121,7 @@ struct vsp1_pipeline {
> unsigned int partitions;
> struct v4l2_rect partition;
> unsigned int current_partition;
> + struct v4l2_rect part_table[VSP1_PIPE_MAX_PARTITIONS];
That's an extra 1kB or kmalloc'ed data. I'd prefer allocating it dynamically
as needed.
> };
>
> void vsp1_pipeline_reset(struct vsp1_pipeline *pipe);
> diff --git a/drivers/media/platform/vsp1/vsp1_video.c
> b/drivers/media/platform/vsp1/vsp1_video.c index 6d43c02bbc56..c4a8c30df108
> 100644
> --- a/drivers/media/platform/vsp1/vsp1_video.c
> +++ b/drivers/media/platform/vsp1/vsp1_video.c
> @@ -255,6 +255,7 @@ static void vsp1_video_pipeline_setup_partitions(struct
> vsp1_pipeline *pipe) const struct v4l2_mbus_framefmt *format;
> struct vsp1_entity *entity;
> unsigned int div_size;
> + int i;
i can never be negative, you can make it an unsigned int.
Apart from that,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> /*
> * Partitions are computed on the size before rotation, use the format
> @@ -269,6 +270,7 @@ static void vsp1_video_pipeline_setup_partitions(struct
> vsp1_pipeline *pipe) if (vsp1->info->gen == 2) {
> pipe->div_size = div_size;
> pipe->partitions = 1;
> + pipe->part_table[0] = vsp1_video_partition(pipe, div_size, 0);
> return;
> }
>
> @@ -284,6 +286,9 @@ static void vsp1_video_pipeline_setup_partitions(struct
> vsp1_pipeline *pipe)
>
> pipe->div_size = div_size;
> pipe->partitions = DIV_ROUND_UP(format->width, div_size);
> +
> + for (i = 0; i < pipe->partitions; i++)
> + pipe->part_table[i] = vsp1_video_partition(pipe, div_size, i);
> }
>
> /* ------------------------------------------------------------------------
> @@ -355,8 +360,7 @@ static void vsp1_video_pipeline_run_partition(struct
> vsp1_pipeline *pipe, {
> struct vsp1_entity *entity;
>
> - pipe->partition = vsp1_video_partition(pipe, pipe->div_size,
> - pipe->current_partition);
> + pipe->partition = pipe->part_table[pipe->current_partition];
>
> list_for_each_entry(entity, &pipe->entities, list_pipe) {
> if (entity->ops->configure)
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2017-02-13 21:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-04 18:19 [PATCH 0/4] vsp1 partition algorithm improvements Kieran Bingham
2016-11-04 18:19 ` [PATCH 1/4] v4l: vsp1: Implement partition algorithm restrictions Kieran Bingham
2017-02-13 19:17 ` Laurent Pinchart
2017-02-14 1:15 ` Kuninori Morimoto
2017-03-01 2:26 ` Kuninori Morimoto
2017-03-06 6:17 ` Kuninori Morimoto
2017-03-06 15:16 ` Laurent Pinchart
2017-03-06 17:07 ` Kieran Bingham
2017-05-09 15:45 ` Kieran Bingham
2016-11-04 18:19 ` [PATCH 2/4] v4l: vsp1: Move vsp1_video_pipeline_setup_partitions() function Kieran Bingham
2017-02-13 19:23 ` Laurent Pinchart
2016-11-04 18:19 ` [PATCH 3/4] v4l: vsp1: Calculate partition sizes at stream start Kieran Bingham
2017-02-13 21:21 ` Laurent Pinchart [this message]
2017-05-08 18:31 ` Kieran Bingham
2016-11-04 18:19 ` [PATCH 4/4] v4l: vsp1: Remove redundant context variables Kieran Bingham
2017-02-13 21:21 ` Laurent Pinchart
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=3804080.QOE9vPlxB7@avalon \
--to=laurent.pinchart@ideasonboard.com \
--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