From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: linux-media@vger.kernel.org
Subject: Re: [RFC 2/4] media: Check for active links on pads with MEDIA_PAD_FL_MUST_CONNECT flag
Date: Wed, 21 Aug 2013 05:22:45 +0200 [thread overview]
Message-ID: <1611138.kmhZXgyzhc@avalon> (raw)
In-Reply-To: <20130810121629.GF16719@valkosipuli.retiisi.org.uk>
Hi Sakari,
On Saturday 10 August 2013 15:16:29 Sakari Ailus wrote:
> On Fri, Aug 09, 2013 at 01:34:46AM +0200, Laurent Pinchart wrote:
> > On Friday 19 July 2013 20:55:07 Sakari Ailus wrote:
> > > Do not allow streaming if a pad with MEDIA_PAD_FL_MUST_CONNECT flag is
> > > not connected by an active link.
> > >
> > > 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.
> > >
> > > Signed-off-by: Sakari Ailus <sakari.ailus@iki.fi>
> > > ---
> > >
> > > drivers/media/media-entity.c | 34 +++++++++++++++++++++++++++-------
> > > 1 file changed, 27 insertions(+), 7 deletions(-)
> > >
> > > diff --git a/drivers/media/media-entity.c b/drivers/media/media-entity.c
> > > index cb30ffb..4e58f8a 100644
> > > --- a/drivers/media/media-entity.c
> > > +++ b/drivers/media/media-entity.c
> > > @@ -20,6 +20,7 @@
> > > * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307
> > > USA */
> > >
> > > +#include <linux/bitmap.h>
> > > #include <linux/module.h>
> > > #include <linux/slab.h>
> > > #include <media/media-entity.h>
> > > @@ -227,6 +228,7 @@ __must_check int media_entity_pipeline_start(struct
> > > media_entity *entity,
> > > media_entity_graph_walk_start(&graph, entity);
> > >
> > > while ((entity = media_entity_graph_walk_next(&graph))) {
> > > + DECLARE_BITMAP(active, entity->num_pads);
> > > unsigned int i;
> > >
> > > entity->stream_count++;
> > >
> > > @@ -240,21 +242,39 @@ __must_check int
> > > media_entity_pipeline_start(struct media_entity *entity,
> > > if (!entity->ops || !entity->ops->link_validate)
> > > continue;
> > >
> > > + bitmap_zero(active, entity->num_pads);
> > > +
> > > for (i = 0; i < entity->num_links; i++) {
> > > struct media_link *link = &entity->links[i];
> > > -
> > > - /* Is this pad part of an enabled link? */
> > > - if (!(link->flags & MEDIA_LNK_FL_ENABLED))
> > > - continue;
> > > -
> > > - /* Are we the sink or not? */
> > > - if (link->sink->entity != entity)
> > > + struct media_pad *pad = link->sink->entity == entity
> > > + ? link->sink : link->source;
> > > +
> > > + /*
> > > + * Pads that either do not need to connect or
> > > + * are connected through an enabled link are
> > > + * fine.
> > > + */
> > > + if (!(pad->flags & MEDIA_PAD_FL_MUST_CONNECT)
> > > + || link->flags & MEDIA_LNK_FL_ENABLED)
> > > + bitmap_set(active, pad->index, 1);
> > > +
> > > + /*
> > > + * Link validation will only take place for
> > > + * sink ends of the link that are enabled.
> > > + */
> > > + if (link->sink != pad
> > > + || !(link->flags & MEDIA_LNK_FL_ENABLED))
> > > continue;
> > >
> > > ret = entity->ops->link_validate(link);
> > > if (ret < 0 && ret != -ENOIOCTLCMD)
> > > goto error;
> > > }
> > > +
> > > + if (!bitmap_full(active, entity->num_pads)) {
> > > + ret = -EPIPE;
> > > + goto error;
> > > + }
> >
> > I'm afraid that won't work if one of the pads has no links. In that case
> > the bitmap won't be full. I think you will have to iterate separately on
> > the links to validate them, and on the pads to check the flags.
>
> Good point.
>
> I could as well add another bitmap or perhaps rather keep the information in
> struct media_pad, separately from flags since this is something the user can
> find through other means --- that way we don't add practically any runtime
> overhead.
>
> What do you think?
Given the number of pads we expect on an entity, is it really worth the micro-
optimization ? I think I would just loop over the links and pads separately,
especially given that you need to validate pads even if the entity has no
link_validate operation, which is checked before the for loop over the links.
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2013-08-21 3:21 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 [this message]
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
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=1611138.kmhZXgyzhc@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).