In the end it turns out it does make sense for the sensor (accessible
under /camera-i2c) and the camera (/camera) to be separate.
But Mitch identified the optimal DT layout where the sensor is defined
in the DT at /camera-i2c/image-sensor, which causes i2c-gpio to probe
the ov7670 driver directly.
On Wed, Aug 29, 2012 at 1:59 PM, Daniel Drake d...@laptop.org wrote:
In the end it turns out it does make sense for the sensor (accessible
under /camera-i2c) and the camera (/camera) to be separate.
But Mitch identified the optimal DT layout where the sensor is defined
in the DT at
On Wed, Aug 29, 2012 at 2:22 PM, Martin Langhoff
martin.langh...@gmail.com wrote:
We'll be probably qualifying siv120d for XO-4 production as well. How
do we handle this situation?
So far, OFW didn't need to know which one was installed; the
mmp-camera driver was loading both ov7670 and
Hi,
Here is the first pass at camera support from the device tree.
Firmware patch:
http://dev.laptop.org/~dsd/20120823/fw-camera.patch
Kernel patch:
http://dev.laptop.org/~dsd/20120823/kernel-camera.patch
My next step is to explore putting the camera node as a child of the
camera-i2c node,
