From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sakari Ailus <sakari.ailus@iki.fi>
Cc: LMML <linux-media@vger.kernel.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [RFC] Representing hardware connections via MC
Date: Wed, 2 Mar 2016 13:04:09 -0300 [thread overview]
Message-ID: <20160302130409.60df670f@recife.lan> (raw)
In-Reply-To: <20160302124029.0e6cee85@recife.lan>
Em Wed, 2 Mar 2016 12:40:29 -0300
Mauro Carvalho Chehab <mchehab@osg.samsung.com> escreveu:
> After all the discussions, I guess "CONN" for connection is the best way
> to represent it.
Better to put it on a patch.
Please review.
Regards,
Mauro
[media] Better define MEDIA_ENT_F_CONN_* entities
Putting concepts in a paper is hard, specially since different people
may interpret it in a different way.
Make clear about the meaning of the MEDIA_ENT_F_CONN_* entities
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
diff --git a/Documentation/DocBook/media/v4l/media-types.xml b/Documentation/DocBook/media/v4l/media-types.xml
index 5e3f20fdcf17..b036e6103949 100644
--- a/Documentation/DocBook/media/v4l/media-types.xml
+++ b/Documentation/DocBook/media/v4l/media-types.xml
@@ -46,15 +46,26 @@
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_RF</constant></entry>
- <entry>Connector for a Radio Frequency (RF) signal.</entry>
+ <entry>Entity representing the logical connection associated with a
+ single Radio Frequency (RF) signal connector. It
+ corresponds to the logical input or output associated
+ with the RF signal.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_SVIDEO</constant></entry>
- <entry>Connector for a S-Video signal.</entry>
+ <entry>Entity representing the logical connection assowiated
+ with a sigle S-Video connector. Such entity should have
+ two pads, one for the luminance signal(Y) and one
+ for the chrominance signal (C). It corresponds to the
+ logical input or output associated with S-Video Y and C
+ signals.</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CONN_COMPOSITE</constant></entry>
- <entry>Connector for a RGB composite signal.</entry>
+ <entry>Entity representing the logical connection for a composite
+ signal. It corresponds to the logical input or output
+ associated with the a single signal that carries both
+ chrominance and luminance information (Y+C).</entry>
</row>
<row>
<entry><constant>MEDIA_ENT_F_CAM_SENSOR</constant></entry>
next prev parent reply other threads:[~2016-03-02 16:04 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 12:13 [RFC] Representing hardware connections via MC Mauro Carvalho Chehab
2016-02-26 13:13 ` Javier Martinez Canillas
2016-02-26 13:48 ` Mauro Carvalho Chehab
2016-03-02 11:10 ` Laurent Pinchart
2016-02-26 13:23 ` Hans Verkuil
2016-02-26 13:47 ` Javier Martinez Canillas
2016-02-26 14:05 ` Mauro Carvalho Chehab
2016-02-26 14:00 ` Mauro Carvalho Chehab
2016-02-26 14:07 ` Hans Verkuil
2016-02-26 14:27 ` Mauro Carvalho Chehab
2016-03-02 10:34 ` Laurent Pinchart
2016-03-02 11:13 ` Mauro Carvalho Chehab
2016-03-02 11:16 ` Laurent Pinchart
2016-03-02 11:28 ` Hans Verkuil
2016-03-02 12:08 ` Mauro Carvalho Chehab
2016-03-02 18:33 ` Hans Verkuil
2016-03-02 19:31 ` Mauro Carvalho Chehab
2016-03-02 23:18 ` Laurent Pinchart
2016-03-05 14:53 ` Mauro Carvalho Chehab
2016-03-02 12:32 ` Mauro Carvalho Chehab
2016-03-02 23:23 ` Laurent Pinchart
2016-03-02 14:16 ` Sakari Ailus
2016-03-02 15:40 ` Mauro Carvalho Chehab
2016-03-02 16:04 ` Mauro Carvalho Chehab [this message]
2016-03-02 16:24 ` Javier Martinez Canillas
2016-03-02 17:32 ` Shuah Khan
2016-03-02 18:30 ` Hans Verkuil
2016-03-02 22:58 ` Laurent Pinchart
2016-03-03 7:54 ` Hans Verkuil
2016-03-03 10:10 ` Laurent Pinchart
2016-03-05 15:00 ` Mauro Carvalho Chehab
2016-03-03 12:48 ` Mauro Carvalho Chehab
2016-03-05 14:18 ` Mauro Carvalho Chehab
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=20160302130409.60df670f@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=hverkuil@xs4all.nl \
--cc=javier@osg.samsung.com \
--cc=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