From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
Hans Verkuil <hverkuil@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans Verkuil <hans.verkuil@cisco.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Maxime Ripard <mripard@redhat.com>
Subject: Re: [PATCH v6 2/2] media: bcm2835-unicam: Fix RGB format / mbus code association
Date: Thu, 5 Mar 2026 13:17:20 +0100 [thread overview]
Message-ID: <20260305121720.GB203047@killaraus.ideasonboard.com> (raw)
In-Reply-To: <20260217-csi-bgr-rgb-v6-2-064607effe42@redhat.com>
Hi Maxime,
Thank you for the patch.
On Tue, Feb 17, 2026 at 09:38:58AM +0100, Maxime Ripard wrote:
> From: Maxime Ripard <mripard@redhat.com>
>
> The Unicam driver is a MIPI-CSI2 Receiver, that can capture RGB 4:4:4,
> YCbCr 4:2:2, and raw formats.
>
> RGB 4:4:4 is converted to the MIPI-CSI2 RGB888 video format, and
> associated to the MEDIA_BUS_FMT_RGB888_1X24 media bus code.
>
> However, V4L2_PIX_FMT_RGB24 is defined as having its color components in
> the R, G and B order, from left to right. MIPI-CSI2 however defines the
> RGB888 format with blue first, and that's what MEDIA_BUS_FMT_RGB888_1X24
> defines too.
>
> This essentially means that the R and B will be swapped compared to what
> V4L2_PIX_FMT_RGB24 defines. The same situation occurs with
> V4L2_PIX_FMT_BGR24 being associated to MEDIA_BUS_FMT_BGR888_1X24.
>
> In order to fix the swapped components, we need to change the
> association of V4L2_PIX_FMT_BGR24 to MEDIA_BUS_FMT_RGB888_1X24, and of
> V4L2_PIX_FMT_RGB24 to MEDIA_BUS_FMT_BGR888_1X24.
>
> Since the media bus code is exposed to userspace, and validated by
> unicam's link_validate implementation, we need to explicitly accept (and
> warn) the old association still to preserve backward compatibility.
>
> Signed-off-by: Maxime Ripard <mripard@redhat.com>
> ---
> drivers/media/platform/broadcom/bcm2835-unicam.c | 43 +++++++++++++++++++-----
> 1 file changed, 34 insertions(+), 9 deletions(-)
>
> diff --git a/drivers/media/platform/broadcom/bcm2835-unicam.c b/drivers/media/platform/broadcom/bcm2835-unicam.c
> index f10064107d543caf867249d0566a0f42d6d8c4c6..648d81b741e258cc24075d5f95903ee748280695 100644
> --- a/drivers/media/platform/broadcom/bcm2835-unicam.c
> +++ b/drivers/media/platform/broadcom/bcm2835-unicam.c
> @@ -340,16 +340,16 @@ static const struct unicam_format_info unicam_image_formats[] = {
> .code = MEDIA_BUS_FMT_RGB565_1X16,
> .depth = 16,
> .csi_dt = MIPI_CSI2_DT_RGB565,
> }, {
> .fourcc = V4L2_PIX_FMT_RGB24, /* rgb */
> - .code = MEDIA_BUS_FMT_RGB888_1X24,
> + .code = MEDIA_BUS_FMT_BGR888_1X24,
> .depth = 24,
> .csi_dt = MIPI_CSI2_DT_RGB888,
> }, {
> .fourcc = V4L2_PIX_FMT_BGR24, /* bgr */
> - .code = MEDIA_BUS_FMT_BGR888_1X24,
> + .code = MEDIA_BUS_FMT_RGB888_1X24,
> .depth = 24,
> .csi_dt = MIPI_CSI2_DT_RGB888,
> }, {
> /* Bayer Formats */
> .fourcc = V4L2_PIX_FMT_SBGGR8,
> @@ -2146,26 +2146,51 @@ static int unicam_video_link_validate(struct media_link *link)
>
> if (is_image_node(node)) {
> const struct v4l2_pix_format *fmt = &node->fmt.fmt.pix;
> const struct unicam_format_info *fmtinfo;
>
> - fmtinfo = unicam_find_format_by_fourcc(fmt->pixelformat,
> - UNICAM_SD_PAD_SOURCE_IMAGE);
> + fmtinfo = unicam_find_format_by_code(format->code,
> + UNICAM_SD_PAD_SOURCE_IMAGE);
> if (WARN_ON(!fmtinfo)) {
> ret = -EPIPE;
> goto out;
> }
>
> - if (fmtinfo->code != format->code ||
> - fmt->height != format->height ||
> + /*
> + * Unicam initially associated BGR24 to BGR888_1X24 and
> + * RGB24 to RGB888_1X24.
> + *
> + * In order to allow the applications using the old
> + * behaviour to run, let's accept the old combination,
> + * but warn about it.
> + */
You could reflow this to 80 columns.
> + if (fmtinfo->fourcc != fmt->pixelformat) {
> + if ((fmt->pixelformat == V4L2_PIX_FMT_BGR24 &&
> + format->code == MEDIA_BUS_FMT_BGR888_1X24) ||
> + (fmt->pixelformat == V4L2_PIX_FMT_RGB24 &&
> + format->code == MEDIA_BUS_FMT_RGB888_1X24)) {
> + dev_warn_once(node->dev->dev,
> + "Incorrect pixel format %p4cc for 0x%04x. Fix your application to use %p4cc.\n",
> + &fmt->pixelformat, format->code, &fmtinfo->fourcc);
> + } else {
> + dev_dbg(node->dev->dev,
> + "image: format mismatch: 0x%04x <=> %p4cc\n",
> + format->code, &fmt->pixelformat);
> + ret = -EPIPE;
> + goto out;
> + }
> + }
> +
> +
Double blank line.
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> + if (fmt->height != format->height ||
> fmt->width != format->width ||
> fmt->field != format->field) {
> dev_dbg(node->dev->dev,
> - "image: (%u x %u) 0x%08x %s != (%u x %u) 0x%08x %s\n",
> - fmt->width, fmt->height, fmtinfo->code,
> + "image: (%u x %u) %s != (%u x %u) %s\n",
> + fmt->width, fmt->height,
> v4l2_field_names[fmt->field],
> - format->width, format->height, format->code,
> + format->width, format->height,
> v4l2_field_names[format->field]);
> ret = -EPIPE;
> }
> } else {
> const struct v4l2_meta_format *fmt = &node->fmt.fmt.meta;
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2026-03-05 12:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 8:38 [PATCH v6 0/2] media: Fix CSI2 RGB vs BGR pixel order Maxime Ripard
2026-02-17 8:38 ` [PATCH v6 1/2] media: uapi: Clarify MBUS color component order for serial buses Maxime Ripard
2026-03-05 12:14 ` Laurent Pinchart
2026-02-17 8:38 ` [PATCH v6 2/2] media: bcm2835-unicam: Fix RGB format / mbus code association Maxime Ripard
2026-03-05 12:17 ` Laurent Pinchart [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=20260305121720.GB203047@killaraus.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=hans.verkuil@cisco.com \
--cc=hverkuil@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=mripard@redhat.com \
--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 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®