public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Sakari Ailus <sakari.ailus@nokia.com>
To: "DongSoo(Nathaniel) Kim" <dongsoo.kim@gmail.com>
Cc: "Toivonen Tuukka.O (Nokia-D/Oulu)" <tuukka.o.toivonen@nokia.com>,
	"Aguirre Rodriguez, Sergio Alberto" <saaguirre@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Nagalla, Hari" <hnagalla@ti.com>
Subject: Re: [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver
Date: Tue, 03 Mar 2009 09:25:31 +0200	[thread overview]
Message-ID: <49ACDB6B.4000102@nokia.com> (raw)
In-Reply-To: <5e9665e10903021848u328e0cd4m5186344be15b817@mail.gmail.com>

DongSoo(Nathaniel) Kim wrote:
> Hi Tuukka,
> 
> I understand that it is a huge thing to support VIDIOC_S_INPUT.

It might not be that much, in case it's supported by just one slave.

> But without that, we don't have any proper "V4L2" api to get
> information about how many devices are attached to camera interface,
> and names of input devices...and so on. Because VIDIOC_ENUMINPUT and
> VIDIOC_G_INPUT needs VIDIOC_S_INPUT for prior. Of course we can refer
> to sysfs, but using only single set of APIs like V4L2 looks more
> decent.
> 
> What do you think about this?
> If you think that it is a big burden, can I make a patch for this?

I'm just wondering the purpose --- as Tuukka explained, the ISP block 
doesn't make a camera, but a sensor essentially does. So for every 
sensor there's a video device, even if they are implemented by using 
just one ISP. How does this sound like?

But for video decoders at least it's definitely meaningful to support 
VIDIOC_S_INPUT.

-- 
Sakari Ailus
sakari.ailus@maxwell.research.nokia.com

  parent reply	other threads:[~2009-03-03  7:26 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Aclb0Ghhhph2tRyARSuubB27tGfovg==>
2008-12-11 20:38 ` [REVIEW PATCH 11/14] OMAP34XXCAM: Add driver Aguirre Rodriguez, Sergio Alberto
2009-02-23  8:08   ` DongSoo(Nathaniel) Kim
2009-02-23  8:50     ` Tuukka.O Toivonen
2009-03-03  2:48       ` DongSoo(Nathaniel) Kim
2009-03-03  3:53         ` Hiremath, Vaibhav
2009-03-03  5:13           ` DongSoo(Nathaniel) Kim
2009-03-03  7:36             ` Hans Verkuil
2009-03-04  0:42               ` DongSoo(Nathaniel) Kim
2009-03-04  7:39                 ` Hans Verkuil
2009-03-04  7:49                   ` Tuukka.O Toivonen
2009-03-04 19:22                   ` Sakari Ailus
2009-03-04 21:05                     ` Hans Verkuil
2009-03-04 21:46                       ` Aguirre Rodriguez, Sergio Alberto
2009-03-04 22:44                         ` Hans Verkuil
2009-03-04 23:30                           ` Aguirre Rodriguez, Sergio Alberto
2009-03-05  7:39                             ` Hans Verkuil
2009-03-05 20:11                           ` Sakari Ailus
2009-03-05 21:24                             ` Hans Verkuil
2009-03-10 12:14                               ` Sakari Ailus
2009-03-04 23:42                         ` Trent Piepho
2009-03-05  2:25                           ` hermann pitton
2009-03-03  7:38             ` Sakari Ailus
2009-03-03  7:25         ` Sakari Ailus [this message]
2009-03-03  7:40           ` DongSoo(Nathaniel) Kim
2009-02-23  8:26   ` DongSoo(Nathaniel) Kim
     [not found] <Acl1IyQQvIDQejCAQ5O/QnkHIBmt3w==>
2009-01-13  2:03 ` Aguirre Rodriguez, Sergio Alberto
2009-01-13  7:24   ` Hans Verkuil
2009-02-06  2:26   ` DongSoo Kim
2009-02-11  4:00   ` DongSoo Kim
2009-02-12  7:09     ` Sakari Ailus
2009-02-12  7:52       ` DongSoo Kim
2009-02-13  9:31         ` Arun KS
2009-02-13 10:04           ` DongSoo(Nathaniel) Kim
2009-02-13 10:02         ` Sakari Ailus
2009-02-13 10:11           ` DongSoo(Nathaniel) Kim
2009-03-04  8:12 Hans Verkuil
  -- strict thread matches above, loose matches on Subject: below --
2009-03-10 13:34 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=49ACDB6B.4000102@nokia.com \
    --to=sakari.ailus@nokia.com \
    --cc=dongsoo.kim@gmail.com \
    --cc=hnagalla@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=saaguirre@ti.com \
    --cc=sakari.ailus@maxwell.research.nokia.com \
    --cc=tuukka.o.toivonen@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