From: Martin Kepplinger <martin.kepplinger@puri.sm>
To: "rogerio.silva@nxp.com" <rogerio.silva@nxp.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
"slongerbeam@gmail.com" <slongerbeam@gmail.com>,
Fabio Estevam <festevam@gmail.com>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Cc: "linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
linux-media@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
"kernel@puri.sm" <kernel@puri.sm>,
Pengutronix Kernel Team <kernel@pengutronix.de>
Subject: question: CSI on imx8mq with (any) CSI2 camera / experience with mx6s_capture?
Date: Thu, 10 Dec 2020 09:17:48 +0100 [thread overview]
Message-ID: <9e09ca8b-d1bc-eaa9-d296-c4ee98882c06@puri.sm> (raw)
hi,
TL;DR: did you use the NXP "mx6s_capture" csi bridge driver with other
cameras?
I try to use a CSI2 camera (hi846 I'm writing a driver for) on imx8mq:
Using NXP's CSI bridge driver
https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/mxc/capture/mx6s_capture.c?h=imx_5.4.0_8dxlphantom_er
as well as the CSI driver itself:
https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/imx8/mxc-mipi-csi2_yav.c?h=imx_5.4.0_8dxlphantom_er
works fine when using the ov5640 camera with this driver:
https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/mxc/capture/ov5640_mipi_v2.c?h=imx_5.4.0_8dxlphantom_er
(I realize there is a CSI bridge driver in staging, but that need more
work to be actually used. Of course after this the goal is to fix and
use it; and mainline a CSI phy driver too.)
Now I use said NXP's CSI drivers on mainline without problems with the
ov5640. For the hi846 (as an example), I want to use a different
pixelformat and CSI media bus format. Describing, say,
MEDIA_BUS_FMT_SBGGR10_1X10 in the driver lets mx6s_capture find it; but
as soon as I try to add a different pixelformat than V4L2_PIX_FMT_UYVY in:
https://source.codeaurora.org/external/imx/linux-imx/tree/drivers/media/platform/mxc/capture/mx6s_capture.c?h=imx_5.4.0_8dxlphantom_er#n244
streaming won't start anymore: "not negotiated, -4" and the
"mx6s_vidioc_enum_framesizes" ioctl is not called anymore. Why so?
I didn't find much when comparing strace from "gst-launch-1.0 v4l2src !
video/x-raw,width=1280,height=720 ! videoconvert ! xvimagesink" (which
is how I test).
When I simply use V4L2_PIX_FMT_UYVY I *do* get interrupts (in mx6s) but
only "FIELD0_INT" (and drawing at this point suggests that buffer 1 is
not yet full and "distorted" in a wrong format, which could explain why
DMA is never completed in order to create a full frame).
Now this is details, but the hi846 camera uses a 10bit CSI format and
therefore I need to set PIXEL_BIT in cr1 too, but when I do that for
example, I don't get "FIELD0_INT" anymore (only SFF_OR_INT and of course
the "base address switching Change Err").
Do you have experience with using this driver with other cameras and can
point me in a direction that might help me?
If you want to look at the work-in-progress driver:
https://source.puri.sm/martin.kepplinger/linux-next/-/blob/hi846/drivers/media/i2c/hi846.c
thanks a lot,
martin
next reply other threads:[~2020-12-10 8:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-10 8:17 Martin Kepplinger [this message]
2020-12-10 9:23 ` question: CSI on imx8mq with (any) CSI2 camera / experience with mx6s_capture? Laurent Pinchart
2020-12-10 12:17 ` Laurent Pinchart
2020-12-10 13:12 ` Martin Kepplinger
2020-12-10 16:04 ` Laurent Pinchart
2020-12-22 14:06 ` Martin Kepplinger
2020-12-22 15:35 ` Laurent Pinchart
2020-12-22 15:55 ` Martin Kepplinger
2021-02-23 9:04 ` Martin Kepplinger
2021-02-23 11:32 ` Laurent Pinchart
2020-12-22 17:15 ` Fabio Estevam
2020-12-22 18:16 ` 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=9e09ca8b-d1bc-eaa9-d296-c4ee98882c06@puri.sm \
--to=martin.kepplinger@puri.sm \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rogerio.silva@nxp.com \
--cc=slongerbeam@gmail.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