From: Ruslan Koreev <koreev.r@gmail.com>
To: Qiling Zhu <kmatzkaczor244@gmail.com>
Cc: Ruslan Koreev <koreev.r@gmail.com>,
sakari.ailus@linux.intel.com, benjamin.mugnier@foss.st.com,
sylvain.petinot@foss.st.com, dan.scally@ideasonboard.com,
mchehab@kernel.org, hansg@kernel.org,
ilpo.jarvinen@linux.intel.com, gregkh@linuxfoundation.org,
linux-media@vger.kernel.org, platform-driver-x86@vger.kernel.org,
linux-staging@lists.linux.dev, linux-kernel@vger.kernel.org,
pm@petermarshall.ca
Subject: Re: [PATCH 4/4] media: staging/ipu7: Add monochrome pixel formats
Date: Thu, 1 Oct 2026 17:47:47 +0300 [thread overview]
Message-ID: <20261001144747.1167917-1-koreev.r@gmail.com> (raw)
In-Reply-To: <aru5-aq_sPUDy8dq@ThinkPad>
Hi Qiling,
On Tue, Sep 29, 2026 at 09:25:39PM +0800, Qiling Zhu wrote:
> Since you reported successful plain-V4L2 Y10/Y10P streaming on
> next-20260924, could you share the exact media-ctl/v4l2-ctl commands
> and any setup performed before STREAMON?
I tested on next-20260924 with intel-ipu6 bound to 8086:b05d and v1
patches 1-3, with the vd55g1 changes reworked for v2. Before the plain
V4L2 test, I ran the following with libcamera 0.7.2:
cam -l
timeout 30 cam -c '\_SB_.LNK1' -C5 -s width=804,height=704
That captured five frames at 804x704 R8. Afterwards, media-ctl -p
showed Y8_1X8/804x704 on sensor pad 0 and CSI2 pads 0 and 1. The sensor
link was enabled and immutable, and this capture link was enabled:
"Intel IPU6 CSI2 2":1 -> "Intel IPU6 ISYS Capture 16":0
I did not enable any links manually. I have not repeated this sequence
from a fresh boot using only media-ctl and v4l2-ctl, so the prior
libcamera setup is relevant to reproducing my test.
For each format, I ran these commands first:
sudo media-ctl -V '"vd55g1 1-0010":0 [fmt:Y10_1X10/804x704]'
sudo media-ctl -V '"Intel IPU6 CSI2 2":0 [fmt:Y10_1X10/804x704]'
sudo media-ctl -V '"Intel IPU6 CSI2 2":1 [fmt:Y10_1X10/804x704]'
Then, for Y10 (with the trailing space in the FourCC):
sudo v4l2-ctl -d /dev/video16 --set-fmt-video \
'width=804,height=704,pixelformat=Y10 '
sudo v4l2-ctl -d /dev/video16 --get-fmt-video
sudo timeout 20 v4l2-ctl -d /dev/video16 --stream-mmap=4 \
--stream-count=5 --stream-to=/tmp/ir-Y10.raw
I repeated the three media-ctl commands, then used:
sudo v4l2-ctl -d /dev/video16 --set-fmt-video \
'width=804,height=704,pixelformat=Y10P'
sudo v4l2-ctl -d /dev/video16 --get-fmt-video
sudo timeout 20 v4l2-ctl -d /dev/video16 --stream-mmap=4 \
--stream-count=5 --stream-to=/tmp/ir-Y10P.raw
Both Y10 and Y10P captured five frames successfully and the images
looked correct.
I have not tested next-20260928, so I cannot yet explain the EPIPE.
Could you capture media-ctl -p immediately before STREAMON and any
IPU or vd55g1 messages from dmesg after it fails?
Ruslan
prev parent reply other threads:[~2026-10-01 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-24 17:18 [PATCH 0/4] Lenovo ThinkPad X1 Carbon Gen 14 IR camera: ST VD55G1 on Intel IPU7 Ruslan Koreev
2026-09-24 17:18 ` [PATCH 1/4] platform/x86: int3472: Map the VD55G1 power enable GPIO to "vana" Ruslan Koreev
2026-09-28 8:39 ` Benjamin Mugnier
2026-09-24 17:18 ` [PATCH 2/4] media: ipu-bridge: Add the ST VD55G1 (TBE20A1) Ruslan Koreev
2026-09-28 8:39 ` Benjamin Mugnier
2026-09-24 17:18 ` [PATCH 3/4] media: i2c: vd55g1: Add ACPI support for the Lenovo TBE20A1 HID Ruslan Koreev
2026-09-25 8:50 ` Sakari Ailus
2026-09-24 17:18 ` [PATCH 4/4] media: staging/ipu7: Add monochrome pixel formats Ruslan Koreev
2026-09-25 8:51 ` Sakari Ailus
2026-09-29 9:22 ` Ruslan Koreev
2026-09-29 13:25 ` Qiling Zhu
2026-10-01 14:47 ` Ruslan Koreev [this message]
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=20261001144747.1167917-1-koreev.r@gmail.com \
--to=koreev.r@gmail.com \
--cc=benjamin.mugnier@foss.st.com \
--cc=dan.scally@ideasonboard.com \
--cc=gregkh@linuxfoundation.org \
--cc=hansg@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kmatzkaczor244@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=pm@petermarshall.ca \
--cc=sakari.ailus@linux.intel.com \
--cc=sylvain.petinot@foss.st.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
all inboxes | Powered by JetHome®