Hello Guennadi,
> > Also,
> > I would like to know, if I need to bind to
> > sh_mobile_ceu_camera.c
> > too, and how, because the camera is connected to CEU.
>
> Yes, you do. Look at the board-ap4evb and board-mackerel files at
> everything, containing the "ceu" string in it. The former configures a
> serially connected camera sensor over the MIPI CSI-2 bus, the latter over
> the parallel interface.
Thank you, I will definitely look into those files about ceu.
> > +static struct platform_device rj65na20_camera = {
> > + .name = "soc-camera-pdrv-2M",
>
> This name has to match with what's advertised in
> drivers/media/video/soc_camera.c, namely "soc-camera-pdrv"
I will fix it.
> > static struct i2c_board_info i2c0_devices[] = {
> > {
> > I2C_BOARD_INFO("ag5evm_ts", 0x20),
> > .irq = pint2irq(12), /* PINTC3 */
> > },
> > + /* 2M camera */
> > + {
> > + I2C_BOARD_INFO("rj65na20", 0x40),
> > + },
>
> No, you do not have to include this here, the sensor must not be registered
> automatically during the board initialisation.
Thank you for your review. It is already midnight in Tokyo,
so I will try it first in the morning tomorrow.
With kind regards,
FYI:
> the ARM board, Renesas, through I2C.
> arch/arm/mach-shmobile/board-ag5evm.c
This file is temporal situation just for me to start with.
Akira
--
Akira Tsukamoto
--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
