From: Jacopo Mondi <jacopo.mondi@ideasonboard.com>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
Steve Longerbeam <slongerbeam@gmail.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 05/11] media: i2c: ov5640: Remove unsupported bayer orders
Date: Thu, 14 May 2026 10:10:48 +0200 [thread overview]
Message-ID: <agWDRd0oOBsNfyy_@zed> (raw)
In-Reply-To: <20260501-ov5640_cleanup-v1-5-0869a7802a33@ideasonboard.com>
Hi Kieran
On Fri, May 01, 2026 at 04:39:07PM +0100, Kieran Bingham wrote:
> The OV5640 only outputs SBGGR8. Remove the incorrectly advertised
> alternatives which allow a misconfigured pipeline to be established.
Do you have any idea why the datasheet mentions all the RGGB
permutations as valid outputs ?
>
> Signed-off-by: Kieran Bingham <kieran.bingham@ideasonboard.com>
> ---
> drivers/media/i2c/ov5640.c | 21 ---------------------
> 1 file changed, 21 deletions(-)
>
> diff --git a/drivers/media/i2c/ov5640.c b/drivers/media/i2c/ov5640.c
> index 244c341d0e77..e1e253730206 100644
> --- a/drivers/media/i2c/ov5640.c
> +++ b/drivers/media/i2c/ov5640.c
> @@ -309,27 +309,6 @@ static const struct ov5640_pixfmt ov5640_csi2_formats[] = {
> .bpp = 8,
> .ctrl00 = 0x00,
> .mux = OV5640_FMT_MUX_RAW_DPC,
> - }, {
> - /* Raw bayer, GBGB... / RGRG... */
> - .code = MEDIA_BUS_FMT_SGBRG8_1X8,
> - .colorspace = V4L2_COLORSPACE_SRGB,
> - .bpp = 8,
> - .ctrl00 = 0x01,
> - .mux = OV5640_FMT_MUX_RAW_DPC,
> - }, {
> - /* Raw bayer, GRGR... / BGBG... */
> - .code = MEDIA_BUS_FMT_SGRBG8_1X8,
> - .colorspace = V4L2_COLORSPACE_SRGB,
> - .bpp = 8,
> - .ctrl00 = 0x02,
> - .mux = OV5640_FMT_MUX_RAW_DPC,
> - }, {
> - /* Raw bayer, RGRG... / GBGB... */
> - .code = MEDIA_BUS_FMT_SRGGB8_1X8,
> - .colorspace = V4L2_COLORSPACE_SRGB,
> - .bpp = 8,
> - .ctrl00 = 0x03,
> - .mux = OV5640_FMT_MUX_RAW_DPC,
> },
Seems like you've missed the same entries in the ov5640_dvp_formats[]
table.
> { /* sentinel */ }
> };
>
> --
> 2.52.0
>
>
next prev parent reply other threads:[~2026-05-14 8:10 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-01 15:39 [PATCH 00/11] media: i2c: ov5640: Refactor ISP configuration Kieran Bingham
2026-05-01 15:39 ` [PATCH 01/11] media: i2c: ov5640: Set default WB gains Kieran Bingham
2026-05-14 7:44 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 02/11] media: i2c: ov5640: Set exposure minimum and defaults Kieran Bingham
2026-05-14 7:58 ` Jacopo Mondi
2026-05-14 8:01 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 03/11] media: i2c: ov5640: Fix minimum gain to 1.0x Kieran Bingham
2026-05-14 8:05 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 04/11] media: i2c: ov5640: fix error path in ov5640_set_mode Kieran Bingham
2026-05-14 8:08 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 05/11] media: i2c: ov5640: Remove unsupported bayer orders Kieran Bingham
2026-05-14 8:10 ` Jacopo Mondi [this message]
2026-05-14 8:43 ` Kieran Bingham
2026-05-14 9:22 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 06/11] media: i2c: ov5640: split out the LSC registers Kieran Bingham
2026-05-14 8:23 ` Jacopo Mondi
2026-05-14 8:44 ` Kieran Bingham
2026-05-01 15:39 ` [PATCH 07/11] media: i2c: ov5640: Split out AWB registers Kieran Bingham
2026-05-01 15:39 ` [PATCH 08/11] media: i2c: ov5640: Document AWB control registers Kieran Bingham
2026-05-14 8:33 ` Jacopo Mondi
2026-05-14 8:34 ` Jacopo Mondi
2026-05-14 8:48 ` Kieran Bingham
2026-05-01 15:39 ` [PATCH 09/11] media: i2c: ov5640: Add ISP Control registers Kieran Bingham
2026-05-14 8:36 ` Jacopo Mondi
2026-05-01 15:39 ` [PATCH 10/11] media: i2c: ov5640: Disable ISP for raw output Kieran Bingham
2026-05-14 8:39 ` Jacopo Mondi
2026-05-14 8:50 ` Kieran Bingham
2026-05-01 15:39 ` [PATCH 11/11] media: i2c: ov5640: Split out format mux registers Kieran Bingham
2026-05-14 8:41 ` Jacopo Mondi
2026-05-14 8:51 ` Kieran Bingham
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=agWDRd0oOBsNfyy_@zed \
--to=jacopo.mondi@ideasonboard.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=slongerbeam@gmail.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