I forwarded this question along to one of the developers who has the most camera knowledge.

adam

I talked with the developer and he gave me some suggestions. First, we haven't ever tried this, so we cannot be certain it will work. We have only ever used 1 camera on a board as a proof of concept.

static struct isp_subdev_i2c_board_info omap3logic_mt9p031_subdevs[] is a NULL terminated list, so you'll need to clone the contents of (see stuff below) for each camera.

{
.board_info = &omap3logic_mt9p031_board_info,
.i2c_adapter_id = 2,
},


You'll most likely need to clone (see below) for the second camera which would be referenced by what you just did above.

static struct i2c_board_info omap3logic_mt9p031_board_info = {
I2C_BOARD_INFO("mt9p031", 0x48),
.platform_data = &omap3logic_mt9p031_platform_data,
};

Lastly, you'll need to reference the new cameras in "static struct isp_v4l2_subdevs_group omap3logic_camera_subdevs[]"

This is a NULL terminated list of cameras.

Make a copy of
{
.subdevs = omap3logic_mt9p031_subdevs,
.interface = ISP_INTERFACE_PARALLEL,
.bus = {
.parallel = {
.data_lane_shift = ISPCTRL_SHIFT_0 >> ISPCTRL_SHIFT_SHIFT, //3.3+ISP_LANE_SHIFT_0,
.clk_pol = 1, // PIXCLK inverted
.hs_pol = 0, // HSYNC not inverted
.vs_pol = 0, // VSYNC not inverted
.bridge = ISPCTRL_PAR_BRIDGE_DISABLE>> ISPCTRL_PAR_BRIDGE_SHIFT //3.3+ISP_BRIDGE_DISABLE,
//3.3+ .bt656 = 0,
},
},
},

for the second camera and place it in the list before the final NULL. Having two cameras in this list should correspond in the same order as the cameras in the previous list you did in omap3logic_mt9p031_subdevs.

Does that help?


Since we don't have either your cameras or your development board, it's all considered theoretical, but if you're intersted in getting some development assistance (or accelerate your development), we do have development services available, and I can have an account manager discuss with you options.

Hopefully that helps.

adam