From: Sergey Lebedev <lsa.uz@pm.me>
To: German Pablo Lindo <germanpapulindez@gmail.com>
Cc: "André Gilerson" <andre.gilerson@gmail.com>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Hans de Goede" <hansg@kernel.org>,
"Dan Scally" <dan.scally@ideasonboard.com>,
linux-media@vger.kernel.org
Subject: Re: Reply cause of the image error in Gnome Snapshot [PATCH v3 0/3] media: Add support for the Sony IMX681
Date: Sun, 13 Sep 2026 19:05:25 +0000 [thread overview]
Message-ID: <20260913190520.31357-1-lsa.uz@pm.me> (raw)
In-Reply-To: <20260913181806.8626-1-germanpapulindez@gmail.com>
Short, because the detail belongs on another list.
The colour errors and the lines German reported are not in the sensor
drivers. His control shows it: the same pipeline renders correctly when the
software ISP is forced onto the CPU.
LIBCAMERA_SOFTISP_MODE=cpu qcam --stream "width=1920,height=1080"
Same kernel, same driver, same sensor, same resolution. Only the debayer
implementation changes.
It is a GPU debayer problem in libcamera, and it turns on the input stride
being larger than the width. I measured that side here. The IPU7 ISYS video
node rounds width up to a multiple of 32 pixels - fourteen widths, no
exceptions - and German's IMX681 figure reproduces exactly: width 3844 gives
a stride of 7744 bytes, which is 3872 pixels.
That padding is the ISYS node's. A sensor subdev has no bytesperline to set.
It is also ordinary V4L2: a driver may pad, and a consumer must use the
bytesperline it is handed.
So nothing in this thread asks for a change to the IMX681 series. I am
sending German the rest separately - the upstream patch this matches, what
the v0.7.2 source actually does, and where I would look next - so that it can
go to libcamera-devel, where it belongs and where I do not want to drag this
thread.
Sergey
prev parent reply other threads:[~2026-09-13 19:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-09 20:37 [PATCH v3 0/3] media: Add support for the Sony IMX681 Sergey Lebedev
2026-09-09 20:37 ` [PATCH v3 1/3] dt-bindings: media: Add " Sergey Lebedev
2026-09-11 7:36 ` Krzysztof Kozlowski
2026-09-09 20:37 ` [PATCH v3 2/3] media: i2c: Add Sony IMX681 sensor driver Sergey Lebedev
2026-09-09 20:52 ` sashiko-bot
2026-09-09 21:14 ` Sergey Lebedev
2026-09-11 7:38 ` Krzysztof Kozlowski
2026-09-11 9:24 ` Sergey Lebedev
2026-09-09 20:37 ` [PATCH v3 3/3] media: ipu-bridge: Add Sony IMX681 Sergey Lebedev
2026-09-09 20:46 ` sashiko-bot
2026-09-10 10:36 ` Test for [PATCH v3 0/3] media: Add support for the " German
2026-09-10 11:22 ` Sergey Lebedev
2026-09-10 11:48 ` Test on another machine and userspace for [PATCH v3 0/3] media: Add support for the Sony IMX681 Thanks for clarifying the origin of the errors I am more than happy to provide the tag Tested-by: German <germanpapulindez@gmail.com> German
2026-09-10 11:53 ` Test on another machine and userspace for [PATCH v3 0/3] media: Add support for the Sony IMX681 German
2026-09-11 7:35 ` Krzysztof Kozlowski
2026-09-11 8:18 ` Sergey Lebedev
2026-09-11 8:50 ` Full name to validate the " German
2026-09-12 16:16 ` cause of the image error in Gnome Snapshot " German
2026-09-13 8:24 ` Sergey Lebedev
2026-09-13 18:18 ` Reply " German Pablo Lindo
2026-09-13 19:05 ` Sergey Lebedev [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=20260913190520.31357-1-lsa.uz@pm.me \
--to=lsa.uz@pm.me \
--cc=andre.gilerson@gmail.com \
--cc=dan.scally@ideasonboard.com \
--cc=germanpapulindez@gmail.com \
--cc=hansg@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.