From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: javier Martin <javier.martin@vista-silicon.com>
Cc: linux-media@vger.kernel.org, hverkuil@xs4all.nl,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Sakari Ailus <sakari.ailus@maxwell.research.nokia.com>,
Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH 1/2] media: tvp5150 Fix default input selection.
Date: Thu, 15 Dec 2011 14:04:08 -0200 [thread overview]
Message-ID: <4EEA1A78.9000504@infradead.org> (raw)
In-Reply-To: <CACKLOr1N0i0tmA7f3WT+nZ6Tn45naRz0CtR6mHyKJ9P5_Lgr+w@mail.gmail.com>
On 15-12-2011 10:33, javier Martin wrote:
> On 15 December 2011 13:01, javier Martin
> <javier.martin@vista-silicon.com> wrote:
>>> The mx2_camera needs some code to forward calls to S_INPUT/S_ROUTING to
>>> tvp5150, in order to set the pipelines there.
>>
>> This sounds like a sensible solution I will work on that soon.
>>
>
> Hi Mauro,
> regarding this subject it seems soc-camera assumes the attached sensor
> has only one input: input 0. This means I am not able to forward
> S_INPUT/S_ROUTING as you suggested:
> http://lxr.linux.no/#linux+v3.1.5/drivers/media/video/soc_camera.c#L213
Then, you need to submit a patch for soc_camera, in order to allow it
to work with devices that provide more than one input.
> This trick is clearly a loss of functionality because it restricts
> sensors to output 0, but it should work since the subsystem can assume
> a sensor whose inputs have not been configured has input 0 as the one
> selected.
>
> However, this trick in the tvp5150 which selects input 1 (instead of
> 0) as the default input is breaking that assumption. The solution
> could be either apply my patch to set input 0 (COMPOSITE0) as default
> or swap input numbers so that COMPOSITE1 input is input 0.
>
> Personally I find my approach more convenient since it matches with
> the default behavior expected in the datasheet.
Both of your described ways are just hacks. tvp5150 has more than one
input. So, the bridge should be supporting the selection between
them.
Regards,
Mauro
>
> Regards.
prev parent reply other threads:[~2011-12-15 16:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 9:39 [PATCH 1/2] media: tvp5150 Fix default input selection Javier Martin
2011-12-15 9:39 ` [PATCH 2/2] media: tvp5150: Add mbus_fmt callbacks Javier Martin
2011-12-15 10:00 ` Mauro Carvalho Chehab
2011-12-15 10:12 ` javier Martin
2011-12-15 10:12 ` [PATCH 1/2] media: tvp5150 Fix default input selection Mauro Carvalho Chehab
2011-12-15 10:24 ` javier Martin
2011-12-15 11:51 ` Mauro Carvalho Chehab
2011-12-15 12:01 ` javier Martin
2011-12-15 12:33 ` javier Martin
2011-12-15 16:04 ` Mauro Carvalho Chehab [this message]
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=4EEA1A78.9000504@infradead.org \
--to=mchehab@infradead.org \
--cc=g.liakhovetski@gmx.de \
--cc=hverkuil@xs4all.nl \
--cc=javier.martin@vista-silicon.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.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