From: Kieran Bingham <kieran.bingham@ideasonboard.com>
To: Tim Harvey <tharvey@gateworks.com>
Cc: Adam Ford <aford173@gmail.com>,
linux-media <linux-media@vger.kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Linux ARM Mailing List <linux-arm-kernel@lists.infradead.org>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Xavier Roumegue <xavier.roumegue@oss.nxp.com>,
Fabio Estevam <festevam@gmail.com>,
Schrempf Frieder <frieder.schrempf@kontron.de>
Subject: Re: imx8mp mipi csi camera overlay: Unable to retrieve endpoint for port@1
Date: Wed, 12 Jul 2023 10:27:23 +0100 [thread overview]
Message-ID: <168915404389.540247.12034155743376705581@Monstersaurus> (raw)
In-Reply-To: <CAJ+vNU111GKHpu4pkTUpgXCxV2iOQ-kQ4OL7mHgBRJ+3SX18PA@mail.gmail.com>
Quoting Tim Harvey (2023-07-12 00:45:10)
> On Tue, Jul 11, 2023 at 3:49 PM Kieran Bingham
> <kieran.bingham@ideasonboard.com> wrote:
> >
> > Hi Tim,
> >
<snip>
> > >
> > > Hi Adam,
> > >
> > > Thanks, this helped point me in the right direction and proves the
> > > video capture device works with v4l2.
> > >
> > > For the imx219 which can capture 640x480 raw 8bit bayer:
> > > # configure media entities for 8-bit raw bayer 640x480
> > > media-ctl -v -V "'imx219 3-0010':0 [fmt:SRGGB8/640x480 field:none]"
> > > media-ctl -v -V "'crossbar':0 [fmt:SRGGB8/640x480 field:none]"
> > > media-ctl -v -V "'mxc_isi.0':0 [fmt:SRGGB8/640x480 field:none]"
> > > # configure for RGGB (8-bit bayer) 640x480
> > > v4l2-ctl --device /dev/video0
> > > --set-fmt-video=width=640,height=480,pixelformat=RGGB --verbose
> > > # capture a frame
> > > v4l2-ctl --device /dev/video0 --stream-mmap --stream-to=frame.raw
> > > --stream-count=1
> > > convert -size 640x480 -depth 8 gray:frame.raw frame.png # convert to png
> > > # stream to display
> > > gst-launch-1.0 v4l2src ! \
> > > video/x-bayer,format=rggb,width=640,height=480,framerate=10/1 ! \
> > > bayer2rgb ! fbdevsink
> > >
> >
> > I would expect if that's all working then libcamera with the ISI
> > pipeline handler would be able to handle all of the media-ctl
> > configuration for you.
> >
> > You should be able to use this directly (without needing calls to media-ctl):
> >
> > gst-launch-1.0 libcamerasrc ! \
> > video/x-bayer,format=rggb,width=640,height=480 ! \
> > bayer2rgb ! fbdevsink
> >
> > in the same way.
> >
> > If it does work, I'd be interested to hear that, and if it doesn't -
> > then lets fix it!
> >
> > Note I removed the framerate=10/1 as that's the part I would suspect
> > might cause issues in the libcamerasrc. It's likely worth trying both
> > with and without it.
>
> Hi Kieran,
>
> I've never looked into libcamera before but I love the idea of not
> needing to deal with media-ctl pipelines. I don't see a libcamerasrc
Indeed, that's one of the key points of libcamera - to handle all this
complexity of routing, configuration, and format propogation for every
platform on behalf of each application. (As well as manage any connected
ISP).
There's a few out of tree patches I believe, but it doesn't take much to
get libcamera running the ISP on the i.MX8MP as well so then you can
have hardware accelerated debayering and image processing too.
> in gstreamer 1.20.3 which I'm using. A quick look at the libcamera
> docs [1] seems to indicate building from source isn't necessary when
> libcamera is installed but I've installed libcamera-tools/libcamera0
> and there is still no libcamerasrc shown in gstreamer?
libcamerasrc is currently built as part of the libcamera project, not
gstreamer. I don't know what package libcamera-tools/libcamera0 refers
to - but look to see if your distribution package the gstreamer
component of libcamera separately. Once that's installed it should be
available.
Feel free to find us in the IRC/Matrix channels too if you get stuck for
a realtime support channel to get things running.
--
Kieran
>
> best regards,
>
> Tim
> [1] https://libcamera.org/getting-started.html
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-12 9:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-08 0:27 imx8mp mipi csi camera overlay: Unable to retrieve endpoint for port@1 Tim Harvey
2023-07-08 1:10 ` Adam Ford
2023-07-11 0:58 ` Tim Harvey
2023-07-11 1:08 ` Adam Ford
2023-07-11 22:16 ` Tim Harvey
2023-07-11 22:49 ` Kieran Bingham
2023-07-11 23:45 ` Tim Harvey
2023-07-12 9:27 ` Kieran Bingham [this message]
2023-07-12 17:34 ` 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=168915404389.540247.12034155743376705581@Monstersaurus \
--to=kieran.bingham@ideasonboard.com \
--cc=aford173@gmail.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=jacopo.mondi@ideasonboard.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=shawnguo@kernel.org \
--cc=tharvey@gateworks.com \
--cc=xavier.roumegue@oss.nxp.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