On Thu, Jul 8, 2010 at 2:33 PM, William von Achen <wvonachen@...> wrote:
> OK, I've finally gotten some more time to work on this ...
> I created a board-overo-camera.c file based on board-omap3evm-camera.c,
> changing very little other than removing the mux-related stuff and
> altering the definition of the decoder's reset pin so that it maps to
> the GPIO we tied it to. Also changed the i2c slave address of the
> decoder to 0x5d to match our board.
> However, I still don't see /dev/video0 populated on boot. I hooked a
> logic analyzer up to the i2c pins and the only traffic I see during boot
> is going to slave address 0x51, which seems to be an EEPROM on the Tobi
> board. After inserting a bunch of printk statements into the functions
> in board-overo-camera.c, I could see that the functions
> tvp5146_set_prv_data and tvp5146_power_set are never called, the latter
> of which looks like it does most of the setup.
> Am I correct in assuming that these functions are supposed to be called
> automatically by v4l2? Or do I need to do something in the init function
> to kick off the process? Currently, the init function only calls
> omap3evmdc_mdc_config and i2c_register_board_info, both successfully.
I don't have your board file (and can't seem to find
board-omap3evm-camera.c, but it's probably just because my view is
My suspicion is related to drivers and devices.
Normally, the board will register a bunch of platform_devices, and a
driver somewhere will register a platform_driver.
When a driver and device with matching names are both loaded, then the
probe function will be called.
So things to check:
1 - Does the driver name match the device name?
2 - Was the driver actually loaded? (i.e. typically via modprobe). If
you cat /proc/devices you should see your driver listed. If it's not
listed, then you need to figure out why not.
Shuswap, BC, Canada