[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260205103207.4020959-1-isaac.scott@ideasonboard.com>
Date: Thu, 5 Feb 2026 10:32:05 +0000
From: Isaac Scott <isaac.scott@...asonboard.com>
To: linux-media@...r.kernel.org
Cc: dafna@...tmail.com,
laurent.pinchart@...asonboard.com,
mchehab@...nel.org,
heiko@...ech.de,
linux-rockchip@...ts.infradead.org,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
Isaac Scott <isaac.scott@...asonboard.com>
Subject: [PATCH v2 0/2] media: rkisp1: Add YUV bypass support for rkisp1
Hi all,
"Smart" cameras that do all image processing on the camera module itself
may not have the ability to output image data in RAW formats. These
cameras would require the use of the ISI, which is sometimes not
included in the hardware.
In hotplug systems, it is also impossible to switch between the ISP and
ISI at runtime, meaning if a media pipeline was set up between the
sensor and the rkisp1 ISP capture device, it would not be possible to
switch from a sensor supporting RAW formats to one outputting only YUV.
Thankfully, the ISP can be configured to allow the incoming YUV stream
to "bypass" the ISP blocks, allowing these sensors to be used. It
bypasses all ISP blocks and passes through the resizer, with the input
image data being presented at the output of the ISP to be captured.
In bypass mode, stats buffers are not provided by the ISP.
This series adds support for "YUV bypass", allowing sensors which only
output YUV streams to be used through the rkisp1.
Tested on: v6.18
Compile-tested on: media/next
---
Changelog since v1:
- Dropped patches 1, 3, 4 and 5.
- Removed the in_bypass flag from patch 2, as it is not needed due to
the removal of the other patches.
Isaac Scott (2):
media: rkisp1-isp: Set correct data mode for YUV bypass
media: rkisp1: Treat 8 bus width and 16 bus width formats the same
drivers/media/platform/rockchip/rkisp1/rkisp1-isp.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
--
2.43.0
Powered by blists - more mailing lists