From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Rui Miguel Silva <rmfrfs@gmail.com>,
Martin Kepplinger <martink@posteo.de>,
Purism Kernel Team <kernel@puri.sm>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
linux-media@vger.kernel.org, imx@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
Alice Yuan <alice.yuan@nxp.com>
Subject: Re: [PATCH 1/5] media: nxp: isi: add support for UYVY8_2X8 and YUYV8_2X8 bus codes
Date: Tue, 1 Jul 2025 02:03:06 +0300 [thread overview]
Message-ID: <20250630230306.GF15184@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20250630-imx8qxp_pcam-v1-1-eccd38d99201@nxp.com>
On Mon, Jun 30, 2025 at 06:28:17PM -0400, Frank Li wrote:
> From: Alice Yuan <alice.yuan@nxp.com>
>
> Add support for media bus codes UYVY8_2X8 and YUYV8_2X8 in the ISI pipe.
> These formats are commonly used by sensors like ov5640, which typically
> uses MEDIA_BUS_FMT_YUYV8_2X8.
>
> Signed-off-by: Alice Yuan <alice.yuan@nxp.com>
> Signed-off-by: Frank Li <Frank.Li@nxp.com>
> ---
> drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c b/drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c
> index d76eb58deb096..1a4bf1ac02641 100644
> --- a/drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c
> +++ b/drivers/media/platform/nxp/imx8-isi/imx8-isi-pipe.c
> @@ -39,6 +39,16 @@ static const struct mxc_isi_bus_format_info mxc_isi_bus_formats[] = {
> .output = MEDIA_BUS_FMT_YUV8_1X24,
> .pads = BIT(MXC_ISI_PIPE_PAD_SINK),
> .encoding = MXC_ISI_ENC_YUV,
> + }, {
> + .mbus_code = MEDIA_BUS_FMT_UYVY8_2X8,
> + .output = MEDIA_BUS_FMT_YUV8_1X24,
> + .pads = BIT(MXC_ISI_PIPE_PAD_SINK),
> + .encoding = MXC_ISI_ENC_YUV,
> + }, {
> + .mbus_code = MEDIA_BUS_FMT_YUYV8_2X8,
> + .output = MEDIA_BUS_FMT_YUV8_1X24,
> + .pads = BIT(MXC_ISI_PIPE_PAD_SINK),
> + .encoding = MXC_ISI_ENC_YUV,
This doesn't seem quite right. The format here corresponds to the pixel
link interface between the ISI and its source. There's no difference in
this patch in in register values between MEDIA_BUS_FMT_UYVY8_2X8 and
MEDIA_BUS_FMT_UYVY8_1X16. I don't think the ISI would be able to
automatically differentiate between receiving UYVY on a 16-bit bus with
one clock per pixel, and receiving it on a 8-bit bus with two clocks per
pixel. I believe you should translate MEDIA_BUS_FMT_UYVY8_2X8 to
MEDIA_BUS_FMT_UYVY8_1X16 in the source subdev driver.
> }, {
> .mbus_code = MEDIA_BUS_FMT_YUV8_1X24,
> .output = MEDIA_BUS_FMT_YUV8_1X24,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2025-06-30 23:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 22:28 [PATCH 0/5] media: imx8qxp: add parallel camera support Frank Li
2025-06-30 22:28 ` [PATCH 1/5] media: nxp: isi: add support for UYVY8_2X8 and YUYV8_2X8 bus codes Frank Li
2025-06-30 23:03 ` Laurent Pinchart [this message]
2025-06-30 22:28 ` [PATCH 2/5] dt-bindings: media: add i.MX parallel csi support Frank Li
2025-06-30 22:53 ` Laurent Pinchart
2025-07-01 14:55 ` Frank Li
2025-07-01 15:26 ` Frank Li
2025-07-01 20:40 ` Laurent Pinchart
2025-07-01 19:32 ` Laurent Pinchart
2025-06-30 22:28 ` [PATCH 3/5] media: nxp: add V4L2 subdev driver for parallel CSI Frank Li
2025-07-02 6:43 ` Krzysztof Kozlowski
2025-07-02 18:05 ` Frank Li
2025-06-30 22:28 ` [PATCH 4/5] arm64: dts: imx8: add parallel CSI node Frank Li
2025-06-30 22:28 ` [PATCH 5/5] arm64: dts: imx8qxp-mek: add parallel ov5640 camera support Frank Li
2025-06-30 23:06 ` Laurent Pinchart
2025-07-01 15:08 ` Frank Li
2025-07-01 20:52 ` 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=20250630230306.GF15184@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Frank.Li@nxp.com \
--cc=alice.yuan@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=kernel@puri.sm \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=martink@posteo.de \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rmfrfs@gmail.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
/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