Hello Adam, On Wed, Jan 6, 2016 at 3:33 PM, Adam Ford <aford173@xxxxxxxxx> wrote: > I am trying to setup the device tree to enable a parallel camera > interface as found on the LPD Dev Kit. > > The instructions I am using for the basis are: > https://alaganraj.wordpress.com/2015/08/08/beagleboard-xm-camera-li-5m03-mt9p031-support-with-device-tree/ > > It I get the same results when I compile it into the kernel or as a > module, but the errors are the same. > > When I modprobe it, I get: > > # modprobe omap3-isp > omap3isp 480bc000.isp: parsing endpoint > /ocp/isp@480bc000/ports/port@0/endpoint, interface 0 > omap3isp 480bc000.isp: Revision 15.0 found > iommu: Adding device 480bc000.isp to group 0 > omap-iommu 480bd400.mmu: 480bd400.mmu: version 1.1 > omap3isp 480bc000.isp: hist: using DMA channel dma0chan6 > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > CCP2 was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > CSI2a was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > CCDC was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > preview was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > resizer was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > AEWB was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > AF was not initialized! > omap3isp 480bc000.isp: Entity type for entity OMAP3 ISP > histogram was not initialized! > # > > I then modprobe the mt9p031 driver, and it won't initialize, but it > is detected. > > # modprobe mt9p031 > [ 127.390808] 1-0048 supply vdd not found, using dummy regulator > [ 127.398101] 1-0048 supply vaa not found, using dummy regulator > [ 127.404907] omap3isp 480bc000.isp: isp_xclk_set_rate: cam_xclka set > to 21600000 Hz (div 8) > [ 127.432861] mt9p031 1-0048: MT9P031 detected at address 0x48 > [ 127.438873] omap3isp 480bc000.isp: Entity type for entity mt9p031 > 1-0048 was not initialized! > # Those "Entity type for entity $foo was not initialized" messages are not errors but just warning messages due the entity function being MEDIA_ENT_F_*_UNKNOWN Now, those messages were added very recently (it is just in the media tree right now and not in mainline) but the post you mentioned refers to a pre-built images for 4.2.0-rc3. I assume that you cherry-picked in the tree that you are building, all the needed patches that are in whatever tree used to build those 4.2.0-rc3 binaries? > > I can post my device tree if necessary, but it's basically like what's > in the link above. Does anyone have any ideas on what I am doing > wrong? > The mt9p031 and omap3isp drivers seems to be probed correctly (or at least I don't see that failed in your logs). What does media-ctl -p shows? Best regards, Javier -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
