Linux Media Controller development
 help / color / mirror / Atom feed
From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Linux Media Mailing List <linux-media@vger.kernel.org>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
	Sylwester Nawrocki <s.nawrocki@samsung.com>,
	Sylwester Nawrocki <sylvester.nawrocki@gmail.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Magnus Damm <magnus.damm@gmail.com>,
	linux-sh@vger.kernel.org
Subject: [PATCH 0/2] media: V4L2: clock and asynchronous registration
Date: Sat, 20 Oct 2012 00:20:16 +0200 (CEST)	[thread overview]
Message-ID: <Pine.LNX.4.64.1210192358520.28993@axis700.grange> (raw)

Hi all

During a recent discussion of a V4L2 DT RFC it has become apparent, that 
we first need two more preliminary steps, before implementing DT: we need 
a (temporary) V4L2 clock implementation and asynchronous subdevice 
registration. As follow ups to this mail I'm posting two patches, 
implementing those. I have actually been able to get that to work with an 
soc-camera system (sh7372), but respective soc-camera and bridge patches 
are still raw, need a lot of clean up, and I don't know when I'll be able 
to do that. So, I decided to first dump these two patches to the list, and 
then see when I find time for the rest.

Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/

             reply	other threads:[~2012-10-19 22:20 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-19 22:20 Guennadi Liakhovetski [this message]
2012-10-19 22:20 ` [PATCH 1/2] media: V4L2: add temporary clock helpers Guennadi Liakhovetski
2012-10-21 18:52   ` Sylwester Nawrocki
2012-10-22  9:14     ` Guennadi Liakhovetski
2012-10-22 10:13       ` Sylwester Nawrocki
2012-10-26  2:05     ` Laurent Pinchart
2012-10-22 12:55   ` Laurent Pinchart
2012-10-22 12:59   ` Laurent Pinchart
2012-10-19 22:20 ` [PATCH 2/2] media: V4L2: support asynchronous subdevice registration Guennadi Liakhovetski
2012-10-22 10:18   ` Hans Verkuil
2012-10-22 11:08     ` Guennadi Liakhovetski
2012-10-22 11:54       ` Hans Verkuil
2012-10-22 12:50         ` Guennadi Liakhovetski
2012-10-22 13:36           ` Hans Verkuil
2012-10-22 14:48             ` Guennadi Liakhovetski
2012-10-22 15:22               ` Hans Verkuil
2012-11-01 14:42                 ` Laurent Pinchart
2012-11-01 15:01                   ` Guennadi Liakhovetski
2012-11-01 15:22                     ` Laurent Pinchart
2012-11-01 15:37                       ` Guennadi Liakhovetski
2012-11-01 16:15                     ` Hans Verkuil
2012-11-01 16:41                       ` Guennadi Liakhovetski
2012-11-01 19:33                       ` Sylwester Nawrocki
2012-10-24 12:00               ` Sylwester Nawrocki
2012-11-01 15:13             ` Laurent Pinchart
2012-11-01 16:15               ` Guennadi Liakhovetski
2012-10-24 13:54   ` Guennadi Liakhovetski
     [not found]     ` <508D4F79.2000204@gmail.com>
     [not found]       ` <Pine.LNX.4.64.1210290841200.17869@axis700.grange>
2012-10-31 23:09         ` Sylwester Nawrocki
2012-10-31 23:25           ` Sylwester Nawrocki

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=Pine.LNX.4.64.1210192358520.28993@axis700.grange \
    --to=g.liakhovetski@gmx.de \
    --cc=hverkuil@xs4all.nl \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=s.nawrocki@samsung.com \
    --cc=sylvester.nawrocki@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox