From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH v1.1 3/5] media: Pads that are not connected by even a disabled link are fine
Date: Tue, 03 Sep 2013 20:07:43 +0200 [thread overview]
Message-ID: <1806796.1hWpdenVOE@avalon> (raw)
In-Reply-To: <1377966487-22565-1-git-send-email-sakari.ailus@iki.fi>
Hi Sakari,
Thank you for the patch.
On Saturday 31 August 2013 19:28:06 Sakari Ailus wrote:
> Do not require a connected link to a pad if a pad has no links connected to
> it.
>
> Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
> ---
> Hi Laurent,
>
> This goes on top of patch 2/4. I can combine the two in the end but I think
> this is cleaner as a separate change.
Merging the patches separately could result in a bisection breakage, so I'd
rather combine the patches if that's OK. What about the following commit
message ?
"media: Check for active links on pads with MEDIA_PAD_FL_MUST_CONNECT flag
Do not allow streaming if a pad with MEDIA_PAD_FL_MUST_CONNECT flag is
connected by links that are all inactive.
This patch makes it possible to avoid drivers having to check for the most
common case of link state validation: a sink pad that must be connected."
> drivers/media/media-entity.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/media/media-entity.c b/drivers/media/media-entity.c
> index a99396b..2ad291f 100644
> --- a/drivers/media/media-entity.c
> +++ b/drivers/media/media-entity.c
> @@ -236,6 +236,7 @@ __must_check int media_entity_pipeline_start(struct
> media_entity *entity,
>
> while ((entity = media_entity_graph_walk_next(&graph))) {
> DECLARE_BITMAP(active, entity->num_pads);
> + DECLARE_BITMAP(has_no_links, entity->num_pads);
> unsigned int i;
>
> entity->stream_count++;
> @@ -250,6 +251,7 @@ __must_check int media_entity_pipeline_start(struct
> media_entity *entity, continue;
>
> bitmap_zero(active, entity->num_pads);
> + bitmap_fill(has_no_links, entity->num_pads);
>
> for (i = 0; i < entity->num_links; i++) {
> struct media_link *link = &entity->links[i];
> @@ -257,6 +259,11 @@ __must_check int media_entity_pipeline_start(struct
> media_entity *entity, ? link->sink : link->source;
>
> /*
> + * Mark that a pad is connected by a link.
> + */
> + bitmap_clear(has_no_links, pad->index, 1);
> +
> + /*
> * Pads that either do not need to connect or
> * are connected through an enabled link are
> * fine.
> @@ -278,6 +285,9 @@ __must_check int media_entity_pipeline_start(struct
> media_entity *entity, goto error;
> }
>
> + /* Either no links or validated links are fine. */
> + bitmap_or(active, active, has_no_links, entity->num_pads);
> +
> if (!bitmap_full(active, entity->num_pads)) {
> ret = -EPIPE;
> goto error;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-09-03 18:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 17:55 [RFC 0/4] Add MEDIA_PAD_FL_MUST_CONNECT pad flag, check it Sakari Ailus
2013-07-19 17:55 ` [RFC 1/4] media: Add pad flag MEDIA_PAD_FL_MUST_CONNECT Sakari Ailus
2013-07-19 17:55 ` [RFC 2/4] media: Check for active links on pads with MEDIA_PAD_FL_MUST_CONNECT flag Sakari Ailus
2013-08-08 23:34 ` Laurent Pinchart
2013-08-10 12:16 ` Sakari Ailus
2013-08-21 3:22 ` Laurent Pinchart
2013-08-21 10:32 ` Sakari Ailus
2013-08-31 16:28 ` [PATCH v1.1 3/5] media: Pads that are not connected by even a disabled link are fine Sakari Ailus
2013-09-03 18:07 ` Laurent Pinchart [this message]
2013-09-03 23:56 ` Sakari Ailus
2013-09-04 0:09 ` [RFC v1.2 2/4] media: Check for active links on pads with MEDIA_PAD_FL_MUST_CONNECT flag Sakari Ailus
2013-09-06 16:30 ` Laurent Pinchart
2013-09-06 17:10 ` Sakari Ailus
2013-09-18 8:37 ` Sakari Ailus
2013-07-19 17:55 ` [RFC 3/4] omap3isp: Mark which pads must connect Sakari Ailus
2013-07-19 17:55 ` [RFC 4/4] omap3isp: Add resizer data rate configuration to resizer_link_validate Sakari Ailus
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=1806796.1hWpdenVOE@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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).