All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
	javier Martin <javier.martin@vista-silicon.com>,
	Scott Jiang <scott.jiang.linux@gmail.com>,
	Linux Media Mailing List <linux-media@vger.kernel.org>,
	saaguirre@ti.com
Subject: Re: [PATCH] V4L: soc-camera: provide support for S_INPUT.
Date: Mon, 19 Dec 2011 14:28:18 -0200	[thread overview]
Message-ID: <4EEF6622.6050904@infradead.org> (raw)
In-Reply-To: <201112191252.24101.laurent.pinchart@ideasonboard.com>

On 19-12-2011 09:52, Laurent Pinchart wrote:
> Hi,
> 
> On Monday 19 December 2011 12:43:28 Guennadi Liakhovetski wrote:
>> On Mon, 19 Dec 2011, javier Martin wrote:
>>> On 19 December 2011 11:58, Guennadi Liakhovetski wrote:
>>>> On Mon, 19 Dec 2011, javier Martin wrote:
>>>>> On 19 December 2011 11:41, Guennadi Liakhovetski wrote:
>>>>>> On Mon, 19 Dec 2011, Laurent Pinchart wrote:
>>>>>>> On Monday 19 December 2011 11:13:58 Guennadi Liakhovetski wrote:
>>>>>>>> On Mon, 19 Dec 2011, Laurent Pinchart wrote:
>>>>>>>>> On Monday 19 December 2011 09:09:34 Guennadi Liakhovetski wrote:
> 
> [snip]
> 
>>>>>>>>>> Good, this would mean, we need additional subdevice
>>>>>>>>>> operations along the lines of enum_input and enum_output,
>>>>>>>>>> and maybe also g_input and g_output?
>>>>>>>>>
>>>>>>>>> What about implementing pad support in the subdevice ? Input
>>>>>>>>> enumeration could then be performed without a subdev
>>>>>>>>> operation.
>>>>>>>>
>>>>>>>> soc-camera doesn't support pad operations yet.
>>>>>>>
>>>>>>> soc-camera doesn't support enum_input yet either, so you need to
>>>>>>> implement something anyway ;-)
>>>>>>>
>>>>>>> You wouldn't need to call a pad operation here, you would just need
>>>>>>> to iterate through the pads provided by the subdev.
>>>>>>
>>>>>> tvp5150 doesn't implement it either yet. So, I would say, it is a
>>>>>> better solution ATM to fix this functionality independent of the
>>>>>> pad-level API.
>>>>>
>>>>> I agree,
>>>>> I cannot contribute to implement pad-level API stuff since I can't
>>>>> test it with tvp5150.
>>>>>
>>>>> Would you accept a patch implementing only S_INPUT?
>>>>
>>>> Sorry, maybe I'm missing something, but how would it work? I mean, how
>>>> can we accept from the user any S_INPUT request with index != 0, if we
>>>> always return only 0 in reply to ENUM_INPUT? Ok, G_INPUT we could
>>>> implement internally in soc-camera: return 0 by default, then remember
>>>> last set input number per soc-camera device / subdev. But
>>>> ENUM_INPUT?...
>>>
>>> It clearly is not a complete solution but at least it allows setting
>>> input 0 in broken drivers such as tvp5150 which have input 1 enabled
>>> by default, while soc-camera assumes input 0 is enabled.
>>
>> I would really prefer an addition of an .enum_input() video subdev
>> operation.
> 
> I agree that input enumeration is needed, but I really think this should be 
> handled through pads, no with a new subdev operation. I don't like the idea of 
> introducing a new operation that will already be deprecated from the very 
> beginning.

The enum_input/g_input/s_input operations/callbacks are not deprecated at all.
They're widely used on all analog TV devices, and there's absolutely no reason
at all to deprecate them.

Regards,
Mauro

  parent reply	other threads:[~2011-12-19 16:28 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16  8:00 [PATCH] V4L: soc-camera: provide support for S_INPUT Javier Martin
2011-12-16  8:34 ` Scott Jiang
2011-12-16  9:19   ` javier Martin
2011-12-16  8:47 ` Guennadi Liakhovetski
2011-12-16  9:09   ` Scott Jiang
2011-12-16  9:16     ` Guennadi Liakhovetski
2011-12-16  9:36       ` Scott Jiang
2011-12-16  9:47         ` javier Martin
2011-12-16  9:50         ` Guennadi Liakhovetski
2011-12-19  0:51           ` Laurent Pinchart
2011-12-19  7:44             ` javier Martin
2011-12-19 10:06               ` Laurent Pinchart
2011-12-19  8:09             ` Guennadi Liakhovetski
2011-12-19 10:05               ` Laurent Pinchart
2011-12-19 10:13                 ` Guennadi Liakhovetski
2011-12-19 10:20                   ` Laurent Pinchart
2011-12-19 10:41                     ` Guennadi Liakhovetski
2011-12-19 10:45                       ` javier Martin
2011-12-19 10:58                         ` Guennadi Liakhovetski
2011-12-19 11:25                           ` javier Martin
2011-12-19 11:43                             ` Guennadi Liakhovetski
2011-12-19 11:52                               ` Laurent Pinchart
2011-12-19 12:01                                 ` Guennadi Liakhovetski
2011-12-19 12:11                                   ` javier Martin
2011-12-19 16:28                                 ` Mauro Carvalho Chehab [this message]
2011-12-19 16:30                                   ` Laurent Pinchart
2011-12-19 16:30                             ` Mauro Carvalho Chehab
2012-01-03 14:50                               ` javier Martin
2012-01-03 15:05                                 ` Guennadi Liakhovetski
2012-01-04 16:03                                   ` javier Martin
2012-01-04 16:35                                     ` Guennadi Liakhovetski
2012-01-04 17:01                                       ` Laurent Pinchart
2012-01-04 17:13                                         ` Guennadi Liakhovetski
2012-01-04 20:47                                           ` Laurent Pinchart
2012-01-04 21:26                                             ` Guennadi Liakhovetski
2012-01-05 10:23                                               ` Guennadi Liakhovetski
2011-12-16  9:21   ` javier Martin

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=4EEF6622.6050904@infradead.org \
    --to=mchehab@infradead.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=javier.martin@vista-silicon.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=scott.jiang.linux@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.