From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Javier Martinez Canillas <javier@osg.samsung.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>, <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Shuah Khan <shuahkh@osg.samsung.com>
Subject: Re: [RFC PATCH 1/3] [media] v4l2-mc.h: Add a S-Video C input PAD to demod enum
Date: Mon, 21 Mar 2016 18:20:47 -0300 [thread overview]
Message-ID: <20160321182047.3f52e119@recife.lan> (raw)
In-Reply-To: <56F04969.6070908@osg.samsung.com>
Em Mon, 21 Mar 2016 16:20:09 -0300
Javier Martinez Canillas <javier@osg.samsung.com> escreveu:
> > BTW, if the tvp5150 needs to know which composite connector is connected
> > to which hardware pin, then you still may need to be explicit w.r.t. the
> > number of pads. I just thought of that.
> >
>
> The tvp5150 doesn't care about that, as Mauro said is just a mux so you can
> have logic in the .link_setup that does the mux depending on the remote
> entity (that's in fact how I implemented and is currently in mainline).
>
> Now, the user needs to know which entity is mapped to which input pin.
> All its know from the HW documentation is that for example the left
> RCA connector is AIP1A and the one inf the right is connected to AIP1B.
>
> So there could be a convention that the composite connected to AIP1A pin
> (the default) is Composite0 and the connected to AIP1B is Composite1.
We should avoid a convention here... instead, we should support
properties via the properties API to export enough info for userspace
to know what physical connectors correspond to each "connection" entity.
As we've discussed previously, such properties can be:
- connector's name
- color
- position
etc...
Regards,
Mauro
next prev parent reply other threads:[~2016-03-21 21:20 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-09 19:09 [RFC PATCH 0/3] [media] tvp515p: Proposal for MC input connector support Javier Martinez Canillas
2016-03-09 19:09 ` [RFC PATCH 1/3] [media] v4l2-mc.h: Add a S-Video C input PAD to demod enum Javier Martinez Canillas
2016-03-18 15:45 ` Hans Verkuil
2016-03-18 17:33 ` Hans Verkuil
2016-03-21 14:40 ` Mauro Carvalho Chehab
2016-03-21 15:05 ` Hans Verkuil
2016-03-21 16:01 ` Hans Verkuil
2016-03-21 17:50 ` Mauro Carvalho Chehab
2016-03-21 18:08 ` Hans Verkuil
2016-03-21 18:23 ` Mauro Carvalho Chehab
2016-03-21 18:48 ` Hans Verkuil
2016-03-21 18:24 ` Javier Martinez Canillas
2016-03-21 18:34 ` Mauro Carvalho Chehab
2016-03-21 18:38 ` Javier Martinez Canillas
2016-03-21 18:51 ` Hans Verkuil
2016-03-21 19:06 ` Hans Verkuil
2016-03-21 19:20 ` Javier Martinez Canillas
2016-03-21 19:30 ` Hans Verkuil
2016-03-21 19:48 ` Javier Martinez Canillas
2016-03-21 21:15 ` Mauro Carvalho Chehab
2016-03-22 0:22 ` Javier Martinez Canillas
2016-03-21 21:20 ` Mauro Carvalho Chehab [this message]
2016-03-22 0:16 ` Javier Martinez Canillas
2016-03-09 19:09 ` [RFC PATCH 2/3] [media] tvp5150: Add input connectors DT bindings Javier Martinez Canillas
2016-03-09 19:09 ` [RFC PATCH 3/3] [media] tvp5150: Replace connector support according to DT binding Javier Martinez Canillas
2016-03-18 15:01 ` [RFC PATCH 0/3] [media] tvp515p: Proposal for MC input connector support Javier Martinez Canillas
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=20160321182047.3f52e119@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@xs4all.nl \
--cc=javier@osg.samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shuahkh@osg.samsung.com \
/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).