This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Linux/TVP5150AM1: Kernel Panic when TVP5150 is registered as V4L2 sub device

Part Number: TVP5150AM1
Other Parts Discussed in Thread: TVP5150

Tool/software: Linux

1. I'm trying to make a camera based embedded system.

2. Development and target platform are both linux operating systems.

3. we are using Microchip SAMA5D27SOM based evaluation kit for this development.

4. We would like to interface PAL camera to processor, For this we are using TVP5150AM1 video decoder for digitizing the analog PAL video and applying to processor.

5. We have interfaced TVP5150AM1 to evaluation kit via I2C interface for configuration/communication and Image sensor controller interface for the 8-bit Parallel video.

6. Driver for TVP5150AM1 available in the mainline linux is used.

7. When device is booted with this setup, Kernel is able to detect the  TVP5150AM1 IC. But when it tries to register as V4L2 sub device kernel panic is happening and system is crashing.

8. Options we have tried.

    a) Driver as a loadable kernel module

    b) Driver as a builtin kernel module

    c) Device tree remote end point with out any sync signals(BT.656 Embedded sync)

    d) Device tree remote end point with sync signals

   All options are resulting kernel panic.

9. I have tried to debug the cause of this by commenting out line by line in the driver code of TVP5150 and found that v4l2_async_register (Which registers the device) is resulting this issue.

10. In the same environment we have connected ov7670 camera module (same I2C for control & 8-bit bus for parallel video with sync signals) and found working perfectly fine. Driver for ov7670 is taken from the same mainline kernel.

11 But we could not figure out what could be issue for this.

12. Kernel log file & device tree is attached for you reference.

Can any one help me in resolving this issue

0207.LOG.zip