From: Hans Verkuil <hverkuil@xs4all.nl>
To: Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
media-workshop@linuxtv.org, linux-media@vger.kernel.org
Subject: Re: [RFC] Media graph flow for an hybrid device as discussed at the media workshop
Date: Mon, 10 Aug 2015 14:43:50 +0200 [thread overview]
Message-ID: <55C89C86.2070707@xs4all.nl> (raw)
In-Reply-To: <20150808083330.7daf111f@recife.lan>
Hi Mauro,
On 08/08/2015 01:33 PM, Mauro Carvalho Chehab wrote:
> During the discussions at the Media Workshop, we came with some dot files that
> would describe a hybrid PC-consumer TV stick with radio, analog video, analog
> TV and digital TV on it.
>
> I consolidated all the dot files we've worked there, and added the
> connectors for RF, S-Video and Composite.
>
> The dot file and the corresponding picture is at:
> http://linuxtv.org/downloads/presentations/mc_ws_2015/dvb-pipeline-v2.dot
> http://linuxtv.org/downloads/presentations/mc_ws_2015/dvb-pipeline-v2.png
>
> As my plan is to start working on some real driver to produce such graph,
> please validate if the entities, interfaces, data links and interface links
> are correct, and if the namespace nomenclature is ok, or if I miss something.
This looks OK to me, except for one small detail: I wouldn't use the name
"Source entities" for connectors. Instead use "Connector entities" since
such entities correspond to actual real connectors on a backplane. A proper
source entity would be a sensor or test pattern generator. Which actually
can occur with the em28xx since it's used in webcams as well.
And a really, really small detail: in the legend the 'interface link' is an
arrow, but it should be a line, since there is no direction. The graph itself
is fine.
As you mentioned on irc, the v4l-subdevX nodes won't be created for this device
since all the configuration happens via the standard interfaces.
But if they were to be created, then they would appear where they are in this
example.
Regards,
Hans
next prev parent reply other threads:[~2015-08-10 12:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 11:33 [RFC] Media graph flow for an hybrid device as discussed at the media workshop Mauro Carvalho Chehab
2015-08-10 12:43 ` Hans Verkuil [this message]
2015-08-10 13:05 ` [media-workshop] " Mauro Carvalho Chehab
2015-08-10 13:19 ` Mauro Carvalho Chehab
2015-08-10 13:44 ` Hans Verkuil
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=55C89C86.2070707@xs4all.nl \
--to=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@osg.samsung.com \
--cc=media-workshop@linuxtv.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