Re: [PATCH 3/3] V4L2: Add a v4l2-subdev (soc-camera) driver for OmniVision OV2640 sensor

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Guennadi Liakhovetski
Date: Wednesday, December 1, 2010 - 4:32 pm

Well, I have no secrets, but I'm not sure everyone on the CC list is 
really interested in this thread(s)... So, please consider dropping some 
of them when replying, they might be grateful;)

In general looks good, just a couple of easy to fix remarks below, and, 
please, fix line wrapping with the next version.

On Sun, 28 Nov 2010, Alberto Panizzo wrote:


might as well keep them alphabetically and numerically ordered


ditto


Wrapped lines throughout the patch


Second comment wrong?


please, add spaces


nitpicking really, but wouldn't "enum ov2640_width" be descriptive enough?


ditto


Nice, have I mentioned, how I don't find such register lists particularly 
developer-friendly?:) But this is one of the cases where I don't think 
requesting you to open code this one would be a wise way to spend your 
time, even if it is done in emacs with something around 50 key-strokes;) 
Hm, these repeated writes to unnamed registers 0x91, 0x93, 0x97, 0xa7 look 
like some writing to internal memory, perhaps?


IMHO this would look prettier one-per-line, similarly below


Have you also tested rgb565?


Well, you trust and don't check, that register numbers are within range, 
so, you might just as well trust the value.


ditto


If I understand this correctly, your sensor has just 10 data lines, and 
has no configuration to switch to any other bus width. Then I wouldn#t 
advertise 8 and 10 bits here. Please, have a look how this is done, e.g., 
in mt9m001.c. There we're trying to reflect the configuration more 
correctly: the sensor can do 10 bits only. But the platform can override 
this, if only some data lines are actually connected on the board.


Is this type-cast really needed?


+	for (i = 0; i <= def; i++) {

would do too


hmm, what exactly does this reset do? It probably doesn't reset register 
values, right? it only resets frame capture or what?


Please, also implement at least a .cropcap, maybe also .g_crop - both 
trivial for your case of a constant sensor window.


Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH 1/3] soc_camera: Add the ability to bind regula ..., Guennadi Liakhovetski, (Sun Nov 28, 12:05 pm)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Tue Nov 30, 7:31 am)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Wed Dec 1, 11:54 am)
Re: [PATCH 3/3] V4L2: Add a v4l2-subdev (soc-camera) drive ..., Guennadi Liakhovetski, (Wed Dec 1, 4:32 pm)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Sat Dec 18, 9:24 am)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Thu Dec 30, 12:38 pm)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Mon Jan 3, 9:24 am)
Re: [PATCH 2/3] mx3_camera: Support correctly the YUV222 a ..., Guennadi Liakhovetski, (Mon Jan 3, 12:37 pm)