All of lore.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Linux Media Mailing List <linux-media@vger.kernel.org>
Subject: Re: V4L-DVB Summit Day 3
Date: Tue, 29 Sep 2009 00:16:43 +0200	[thread overview]
Message-ID: <200909290016.43635.laurent.pinchart@ideasonboard.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0909261419220.4273@axis700.grange>

Hi Guennadi,

On Saturday 26 September 2009 14:25:07 Guennadi Liakhovetski wrote:
> On Fri, 25 Sep 2009, Hans Verkuil wrote:
> > - implement sensor v4l2_subdev support (Laurent). We are still missing
> > some v4l2_subdev sensor ops for setting up the bus config and data
> > format. Laurent will look into implementing those. An RFC for the bus
> > config already exists and will function as the basis of this.

I volunteered to port the sensor drivers we use with the OMAP3 to v4l2_subdev, 
implementing the missing operations/helpers/whatever on the way, but it 
somehow escaped my mind at the time that it included the bus config and data 
format operations :-)

> Good, obviously, I'm veryinterested in both these APIs, and I hope Laurent
> will have a look at my earlier imagebus proposal and use that API as a
> basis for the data format API. My RFC, probably, didn't cover all possible
> cases, but it should be a reasonable starting point with easy enough
> extensibility. I did get a couple of positive feedbacks regarding that
> API, and I have converted the whole soc-camera stack to it and am working
> on some new drivers with that API. So far I didn't have a single case
> where I would have to amend or extend it.

Your RFC will be used as a starting point (actually more than a starting 
point, as there has been lots of discussions around it already). My plan is to 
reuse what's available in RFCs as-is, port the drivers, see how everything 
shatters to pieces (hopefully it won't :-)), and post RFCs to fix the problems 
if required. You will of course be included in the discussion.

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2009-09-28 22:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26  6:22 V4L-DVB Summit Day 3 Hans Verkuil
2009-09-26 12:25 ` Guennadi Liakhovetski
2009-09-28 22:16   ` Laurent Pinchart [this message]
2009-09-27 11:51 ` Dongsoo, Nathaniel Kim
2009-10-02 17:56 ` [Bulk] " CityK
2009-10-02 20:40   ` Markus Rechberger

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=200909290016.43635.laurent.pinchart@ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=linux-media@vger.kernel.org \
    /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.