public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Valentin Longchamp <valentin.longchamp@epfl.ch>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: "Linux Media Mailing List" <linux-media@vger.kernel.org>,
	"Mauro Carvalho Chehab" <mchehab@infradead.org>,
	"Magnus Damm" <damm@opensource.se>,
	"Kuninori Morimoto" <morimoto.kuninori@renesas.com>,
	"Antonio Ospite" <ospite@studenti.unina.it>,
	"Németh Márton" <nm127@freemail.hu>
Subject: Re: soc-camera: patches for 2.6.34
Date: Tue, 09 Feb 2010 20:07:49 +0100	[thread overview]
Message-ID: <4B71B285.7020208@epfl.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.1002091705500.4585@axis700.grange>

Guennadi Liakhovetski wrote:
> Hi all
> 
> Nothing exciting for soc-camera this time for a change, just a couple of 
> small improvements. These patches are already in my local tree, waiting to 
> be pushed up:
> 
> Antonio Ospite (1):
>       pxa_camera: remove init() callback
> 
> Guennadi Liakhovetski (3):
>       soc-camera: update mt9v022 to take into account board signal routing
>       tw9910: use TABs for indentation
>       soc-camera: adjust coding style to match V4L preferences
> 
> Kuninori Morimoto (1):
>       soc-camera: ov772x: Modify buswidth control
> 
> Magnus Damm (1):
>       soc-camera: return -ENODEV is sensor is missing
> 
> Others on the radar:
> 
> Kuninori Morimoto:
> 	MT9T031: write xskip and yskip at each set_params call
> 	* status: being discussed in PM context in:

Well, the above one is from me, and I have posted the updated version 
for pm context this morning: 
http://thread.gmane.org/gmane.linux.drivers.video-input-infrastructure/15897

(You certainly had noticed, but wanted to make sure).


> 
> Guennadi Liakhovetski:
> 	soc-camera: add runtime pm support for subdevices
> 	* under discussion
> 
> Németh Márton:
> 	soc_camera: match signedness of soc_camera_limit_side()                 
> 	* status: an updated patch has been proposed by me, waiting for 
> 	  confirmation
> 
> Guennadi Liakhovetski:
> 	document new pixel formats
> 	* status: I still have to figure out how to combine git / hg for 
> 	  this one and actually do it...
> 
> Kuninori Morimoto:
> 	[1/3] soc-camera: mt9t112: modify exiting conditions from standby mode
> 	[2/3] soc-camera: mt9t112: modify delay time after initialize
> 	[3/3] soc-camera: mt9t112: The flag which control camera-init is
> 	* status: at least patches 2 and 3 are still being discussed, 
> 	  waiting for results
> 
> 
> Any patches, that I've forgotten?
> 

Val

-- 
Valentin Longchamp, PhD Student, EPFL-STI-LSRO1
valentin.longchamp@epfl.ch, Phone: +41216937827
http://people.epfl.ch/valentin.longchamp
MEB3494, Station 9, CH-1015 Lausanne

  parent reply	other threads:[~2010-02-09 19:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09 16:35 soc-camera: patches for 2.6.34 Guennadi Liakhovetski
2010-02-09 16:54 ` Guennadi Liakhovetski
2010-02-09 19:07 ` Valentin Longchamp [this message]
2010-02-09 21:07   ` Guennadi Liakhovetski

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=4B71B285.7020208@epfl.ch \
    --to=valentin.longchamp@epfl.ch \
    --cc=damm@opensource.se \
    --cc=g.liakhovetski@gmx.de \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=morimoto.kuninori@renesas.com \
    --cc=nm127@freemail.hu \
    --cc=ospite@studenti.unina.it \
    /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