From: "Niklas Söderlund" <niklas.soderlund@ragnatech.se>
To: Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
Cc: Mauro Carvalho Chehab <mchehab@kernel.org>,
Sakari Ailus <sakari.ailus@linux.intel.com>,
linux-media@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Subject: Re: [PATCH 3/3] media: rcar-vin: Fix RAW10
Date: Mon, 31 Mar 2025 23:11:22 +0200 [thread overview]
Message-ID: <20250331211122.GA1240431@ragnatech.se> (raw)
In-Reply-To: <20250324-rcar-fix-raw-v1-3-ae56c1c7a2f6@ideasonboard.com>
Hi Tomi,
Thanks for your work.
On 2025-03-24 13:48:54 +0200, Tomi Valkeinen wrote:
> Fix the following to get RAW10 formats working:
>
> In rvin_formats, the bpp is set to 4 for RAW10. As VIN unpacks RAW10 to
> 16-bit containers, the bpp should be 2.
>
> Don't set VNDMR_YC_THR to the VNDMR register. The YC_THR is "YC Data
> Through Mode", used for YUV formats and should not be set for RAW10.
>
> Fix the check related to the RGB666 format and CSI-2 mode. The
> VNMC_INF_RGB666 define is the same as used for RAW10 on Gen4, and RAW10
> is allowed on CSI-2 (whereas RGB666 is not allowed on Gen3 on CSI-2).
> This feels a bit hacky, though, and the formats should really have been
> verified already earlier.
I agree, it feels hacky. I would rather just remove the while switch
then try to "fix" it by extending it more. When testing this series I
needed a similar fix for VNMC_INF_RAW8 check below to get it to work on
Gen4.
>
> Fixes: 1b7e7240eaf3 ("media: rcar-vin: Add support for RAW10")
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>
> ---
> drivers/media/platform/renesas/rcar-vin/rcar-dma.c | 9 +++++++--
> drivers/media/platform/renesas/rcar-vin/rcar-v4l2.c | 8 ++++----
> 2 files changed, 11 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/media/platform/renesas/rcar-vin/rcar-dma.c b/drivers/media/platform/renesas/rcar-vin/rcar-dma.c
> index 53046614f7a1..f8394be8a922 100644
> --- a/drivers/media/platform/renesas/rcar-vin/rcar-dma.c
> +++ b/drivers/media/platform/renesas/rcar-vin/rcar-dma.c
> @@ -811,12 +811,17 @@ static int rvin_setup(struct rvin_dev *vin)
> case VNMC_INF_YUV8_BT656:
> case VNMC_INF_YUV10_BT656:
> case VNMC_INF_YUV16:
> - case VNMC_INF_RGB666:
> if (vin->is_csi) {
> vin_err(vin, "Invalid setting in MIPI CSI2\n");
> return -EINVAL;
> }
> break;
> + case VNMC_INF_RGB666:
> + if (vin->info->model == RCAR_GEN3 && vin->is_csi) {
> + vin_err(vin, "Invalid setting in MIPI CSI2\n");
> + return -EINVAL;
> + }
> + break;
> case VNMC_INF_RAW8:
> if (!vin->is_csi) {
> vin_err(vin, "Invalid setting in Digital Pins\n");
> @@ -913,7 +918,7 @@ static int rvin_setup(struct rvin_dev *vin)
> case V4L2_PIX_FMT_SGBRG10:
> case V4L2_PIX_FMT_SGRBG10:
> case V4L2_PIX_FMT_SRGGB10:
> - dmr = VNDMR_RMODE_RAW10 | VNDMR_YC_THR;
> + dmr = VNDMR_RMODE_RAW10;
> break;
> default:
> vin_err(vin, "Invalid pixelformat (0x%x)\n",
> diff --git a/drivers/media/platform/renesas/rcar-vin/rcar-v4l2.c b/drivers/media/platform/renesas/rcar-vin/rcar-v4l2.c
> index 756fdfdbce61..65da8d513b52 100644
> --- a/drivers/media/platform/renesas/rcar-vin/rcar-v4l2.c
> +++ b/drivers/media/platform/renesas/rcar-vin/rcar-v4l2.c
> @@ -88,19 +88,19 @@ static const struct rvin_video_format rvin_formats[] = {
> },
> {
> .fourcc = V4L2_PIX_FMT_SBGGR10,
> - .bpp = 4,
> + .bpp = 2,
> },
> {
> .fourcc = V4L2_PIX_FMT_SGBRG10,
> - .bpp = 4,
> + .bpp = 2,
> },
> {
> .fourcc = V4L2_PIX_FMT_SGRBG10,
> - .bpp = 4,
> + .bpp = 2,
> },
> {
> .fourcc = V4L2_PIX_FMT_SRGGB10,
> - .bpp = 4,
> + .bpp = 2,
> },
> };
>
>
> --
> 2.43.0
>
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2025-03-31 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-24 11:48 [PATCH 0/3] media: rcar: Fix RAW formats Tomi Valkeinen
2025-03-24 11:48 ` [PATCH 1/3] media: rcar-vin: Add RCAR_GEN4 model value Tomi Valkeinen
2025-03-31 21:13 ` Niklas Söderlund
2025-03-24 11:48 ` [PATCH 2/3] media: rcar-vin: Fix RAW8 Tomi Valkeinen
2025-03-31 21:16 ` Niklas Söderlund
2025-03-24 11:48 ` [PATCH 3/3] media: rcar-vin: Fix RAW10 Tomi Valkeinen
2025-03-31 21:11 ` Niklas Söderlund [this message]
2025-04-03 8:15 ` Tomi Valkeinen
2025-04-03 8:57 ` Niklas Söderlund
2025-04-03 9:12 ` Tomi Valkeinen
2025-04-03 9:36 ` Niklas Söderlund
2025-04-03 8:18 ` Tomi Valkeinen
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=20250331211122.GA1240431@ragnatech.se \
--to=niklas.soderlund@ragnatech.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomi.valkeinen+renesas@ideasonboard.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