Kernel configuration for camera module

Kernel configuration for camera module

[Johannes Lahti]

Hi!

I'm using AP3300 board for my development tasks and I recently got a
camera module for it. I don't have any other info about the module
than it has Renesas and R0P04MDLE0011RL written on it and the serial
number.

It seems that I need a newer kernel to get the module working
(currently running 2.6.27), so I downloaded 2.6.31 sources. Now I
would like to know what kernel configuration options I should be
looking for?

Thanks for any replies!

Cheers,
Johannes

Re: Kernel configuration for camera module

[Magnus Damm]

Hi Johannes,

On Wed, Sep 16, 2009 at 10:48 PM, Johannes Lahti <johannes@nomasi.com> wrote:
> Hi!
>
> I'm using AP3300 board for my development tasks and I recently got a
> camera module for it. I don't have any other info about the module
> than it has Renesas and R0P04MDLE0011RL written on it and the serial
> number.

Not sure about the board name (AP3300) and the camera module name. I
guess you are using a sh7723 based ap325rxa board?

For camera capture support you need to enable the CEU driver:
CONFIG_VIDEO_SH_MOBILE_CEU=y

The two sensors that I've seen for ap325rxa are ov772x and ncm03j.
CONFIG_SOC_CAMERA_OV772X=y
CONFIG_SOC_CAMERA_PLATFORM=y

You can enable all the options above and the code should autodetect
sensor model for you.

If you just want to play with the V4L2 interface then I recommend you
to try the vivi driver:
CONFIG_VIDEO_VIVI=y

Cheers,

/ magnus

Re: Kernel configuration for camera module

[Johannes Lahti]

Hi Magnus!

Sorry for the delay, there was more urgent things to do in our project
and I couldn't get back to this issue until today.

2009/9/24 Magnus Damm <magnus.damm@gmail.com>:

> Not sure about the board name (AP3300) and the camera module name. I
> guess you are using a sh7723 based ap325rxa board?

Yeah, that's it. AP3300 is written in the back of the board.

> For camera capture support you need to enable the CEU driver:
> CONFIG_VIDEO_SH_MOBILE_CEU=y
>
> The two sensors that I've seen for ap325rxa are ov772x and ncm03j.
> CONFIG_SOC_CAMERA_OV772X=y
> CONFIG_SOC_CAMERA_PLATFORM=y
>
> You can enable all the options above and the code should autodetect
> sensor model for you.
>
> If you just want to play with the V4L2 interface then I recommend you
> to try the vivi driver:
> CONFIG_VIDEO_VIVI=y

I copied the default kernel configuration for ap325rxa board and all
these were set, except for the CONFIG_VIDEO_VIVI. I was able to
compile the kernel and it seems to recognize the camera module, but I
cannot find the device under /dev.

I get these messages with dmesg:
Linux video capture interface: v2.00
vivi-000: V4L2 device registered as /dev/video0
Video Technology Magazine Virtual Video Capture Board ver 0.6.0 successfully lo.
camera 0-0: Probing 0-0
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 0
ov772x 0-0021: ov7725 Product ID 77:21 Manufacturer ID 7f:a2
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 0
camera 0-1: Probing 0-1
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 1
sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 1

But the /dev/video0 is not there. Do you know how to fix this?

Cheers!
-Johannes

Re: Kernel configuration for camera module

[Magnus Damm]

Hi Johannes,

On Mon, Nov 16, 2009 at 6:29 PM, Johannes Lahti <johannes@nomasi.com> wrote:
> I copied the default kernel configuration for ap325rxa board and all
> these were set, except for the CONFIG_VIDEO_VIVI. I was able to
> compile the kernel and it seems to recognize the camera module, but I
> cannot find the device under /dev.
>
> I get these messages with dmesg:
> Linux video capture interface: v2.00
> vivi-000: V4L2 device registered as /dev/video0
> Video Technology Magazine Virtual Video Capture Board ver 0.6.0 successfully lo.
> camera 0-0: Probing 0-0
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 0
> ov772x 0-0021: ov7725 Product ID 77:21 Manufacturer ID 7f:a2
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 0
> camera 0-1: Probing 0-1
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver attached to camera 1
> sh_mobile_ceu sh_mobile_ceu.0: SuperH Mobile CEU driver detached from camera 1
>
> But the /dev/video0 is not there. Do you know how to fix this?

It all depends on your user space setup. I suggest that you double
check that udev or mdev are running and/or manually create the v4l2
device nodes. For static systems I have some old scripts that seem to
do "mknod /dev/video0 c 81 0", but I'm not sure if it will work with
your kernel.

/ magnus