Hello Sakari.
Since I was working on my target board with OMAP3 camera interface, It
seems to take a little much time for boot up.
I found that it was about v4l2 int device register routine. (while
probing camera interface)
It turns on int devices and checks their version information through
I2C command.
It usually seems to be proper, but in some cases it should be an
overhead in booting time.
Let me give an example.
Lately I was working on CE131 ISP from NEC.
The ARM processor inside of this ISP needs booting time itself at
least 600ms (depending on firmware version I guess..not fancy at all
:( )
So if we check firmware version or something while v4l2 int device
registering, it should take "at least" 600ms to attach this device as
an int device.
I'm trying to figure out what else could alter version checking for
int device detection, but unfortunately nothing pops up yet :(
Of course I can make it not to check version information for CE131 and
just return true while v4l2 int device registering, but doesn't seem
to be a neat way.
How about taking the similar way with i2c_board_info ?
Please let me know your opinion.
Cheers,
Nate
--
========================================================
DongSoo(Nathaniel), Kim
Engineer
Mobile S/W Platform Lab. S/W centre
Telecommunication R&D Centre
Samsung Electronics CO., LTD.
e-mail : dongsoo.kim@xxxxxxxxx
dongsoo45.kim@xxxxxxxxxxx
========================================================
--
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
