From: Michael Jones <michael.jones@matrix-vision.de>
To: laurent.pinchart@ideasonboard.com
Cc: "sakari.ailus@maxwell.research.nokia.com"
<sakari.ailus@maxwell.research.nokia.com>,
linux-media@vger.kernel.org
Subject: CCP2 on OMAP35x
Date: Mon, 16 Aug 2010 17:38:43 +0200 [thread overview]
Message-ID: <4C695B83.90405@matrix-vision.de> (raw)
Hi Laurent,
I'm working on a sensor driver with a parallel interface to the ISP. In my OMAP35x TRM (spruf98h.pdf), I only find 2 occurrences of "CCP2", with no discussion or description, whereas in the ISP sources on omap3camera/devel I see that it is a building block of the ISP. From the sources, I'm guessing that it is involved in interfacing a serial sensor data stream to the CCDC, and would be uninvolved in parallel data from a sensor.
Is the CCP2 indeed documented somewhere for the OMAP35x? Or is this perhaps only available in the OMAP34x?
In omap34xxcam_video_init(), the media_entity links are activated. In this if/else there,
if (vdev->vdev_sensor->entity.links[0].sink->entity ==
&isp->isp_csi2a.subdev.entity) {...} else {...}
the assumption is made that a sensor is either connected
A. (sensor->)CSI2A->CCDC or
B. sensor->CCP2->CCDC
but if I'm correct that the CCP2 is related to serial data, there is an option (C) missing for parallel data: sensor->CCDC. In fact, this is the link that is created in omap34xxcam_probe() if 'case ISP_INTERFACE_PARALLEL'. Is this correct, that I would need to add an 'else if' to get parallel data working?
sincerely,
Michael
MATRIX VISION GmbH, Talstrasse 16, DE-71570 Oppenweiler
Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschaeftsfuehrer: Gerhard Thullner, Werner Armingeon, Uwe Furtner, Hans-Joachim Reich
next reply other threads:[~2010-08-16 15:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-16 15:38 Michael Jones [this message]
2010-08-16 19:25 ` CCP2 on OMAP35x Laurent Pinchart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C695B83.90405@matrix-vision.de \
--to=michael.jones@matrix-vision.de \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@maxwell.research.nokia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox