Linux Media Controller development
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Hans de Goede <hansg@kernel.org>
Cc: Sakari Ailus <sakari.ailus@linux.intel.com>,
	Mathis Foerst <mathis.foerst@mt.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH v3 09/15] media: mt9m114: Add and use mt9m114_ifp_get_border() helper function
Date: Wed, 2 Jul 2025 03:17:45 +0300	[thread overview]
Message-ID: <20250702001745.GD17819@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20250629205626.68341-10-hansg@kernel.org>

Hi Hans,

On Sun, Jun 29, 2025 at 10:56:19PM +0200, Hans de Goede wrote:
> Normally the IFP removes a 4 pixel border all around its sink format
> size for demosaicing. But in RAW10 mode it does not do this.
> 
> Add a new mt9m114_ifp_get_border() helper function to get the border size
> (4 or 0) and use this where applicable instead of hardcoding a border
> of 4 pixels everywhere.
> 
> Signed-off-by: Hans de Goede <hansg@kernel.org>
> ---
> Changes in v3:
> - New patch in v3 of this patch-set
> ---
>  drivers/media/i2c/mt9m114.c | 54 ++++++++++++++++++++++++++-----------
>  1 file changed, 38 insertions(+), 16 deletions(-)
> 
> diff --git a/drivers/media/i2c/mt9m114.c b/drivers/media/i2c/mt9m114.c
> index d4aad77b095b..020caae95a3d 100644
> --- a/drivers/media/i2c/mt9m114.c
> +++ b/drivers/media/i2c/mt9m114.c
> @@ -843,6 +843,18 @@ static int mt9m114_configure_pa(struct mt9m114 *sensor,
>  	return ret;
>  }
>  
> +/*
> + * For src pad fmts other then RAW10 the IFP removes a 4 pixel border from its

"source pad formats"

> + * sink pad format size for demosaicing.
> + */
> +static int mt9m114_ifp_get_border(struct v4l2_subdev_state *state)
> +{
> +	const struct v4l2_mbus_framefmt *format =
> +		v4l2_subdev_state_get_format(state, 1);
> +
> +	return format->code == MEDIA_BUS_FMT_SGRBG10_1X10 ? 0 : 4;
> +}
> +
>  static int mt9m114_configure_ifp(struct mt9m114 *sensor,
>  				 struct v4l2_subdev_state *state)
>  {
> @@ -850,6 +862,7 @@ static int mt9m114_configure_ifp(struct mt9m114 *sensor,
>  	const struct v4l2_mbus_framefmt *format;
>  	const struct v4l2_rect *crop;
>  	const struct v4l2_rect *compose;
> +	unsigned int border;
>  	u64 output_format;
>  	int ret = 0;
>  
> @@ -864,15 +877,18 @@ static int mt9m114_configure_ifp(struct mt9m114 *sensor,
>  		return ret;
>  
>  	/*
> +	 * For src pad fmts other then RAW10 adjust cropping coordinates for

Ditto.

>  	 * Color pipeline (IFP) cropping and scaling. Subtract 4 from the left
>  	 * and top coordinates to compensate for the lines and columns removed
>  	 * by demosaicing that are taken into account in the crop rectangle but
>  	 * not in the hardware.

But while at it this can be improved, as it took me a moment to remember
what was going on.

	/*
	 * Color pipeline (IFP) cropping and scaling. The crop window registers
	 * apply cropping after demosaicing, which itself consumes 4 pixels on
	 * each side of the image. The crop rectangle exposed to userspace
	 * includes that demosaicing border, subtract it from the left and top
	 * coordinates to configure the crop window.
	 */

>  	 */
> +	border = mt9m114_ifp_get_border(state);
> +
>  	cci_write(sensor->regmap, MT9M114_CAM_CROP_WINDOW_XOFFSET,
> -		  crop->left - 4, &ret);
> +		  crop->left - border, &ret);
>  	cci_write(sensor->regmap, MT9M114_CAM_CROP_WINDOW_YOFFSET,
> -		  crop->top - 4, &ret);
> +		  crop->top - border, &ret);
>  	cci_write(sensor->regmap, MT9M114_CAM_CROP_WINDOW_WIDTH,
>  		  crop->width, &ret);
>  	cci_write(sensor->regmap, MT9M114_CAM_CROP_WINDOW_HEIGHT,
> @@ -1845,6 +1861,7 @@ static int mt9m114_ifp_get_selection(struct v4l2_subdev *sd,
>  {
>  	const struct v4l2_mbus_framefmt *format;
>  	const struct v4l2_rect *crop;
> +	unsigned int border;
>  	int ret = 0;
>  
>  	/* Crop and compose are only supported on the sink pad. */
> @@ -1859,15 +1876,17 @@ static int mt9m114_ifp_get_selection(struct v4l2_subdev *sd,
>  	case V4L2_SEL_TGT_CROP_DEFAULT:
>  	case V4L2_SEL_TGT_CROP_BOUNDS:
>  		/*
> -		 * The crop default and bounds are equal to the sink
> -		 * format size minus 4 pixels on each side for demosaicing.
> +		 * Crop defaults and bounds are equal to the sink format size.
> +		 * For src pad fmts other then RAW10 this gets reduced by 4

"For source pad formats".

> +		 * pixels on each side for demosaicing.
>  		 */
>  		format = v4l2_subdev_state_get_format(state, 0);
> +		border = mt9m114_ifp_get_border(state);
>  
> -		sel->r.left = 4;
> -		sel->r.top = 4;
> -		sel->r.width = format->width - 8;
> -		sel->r.height = format->height - 8;
> +		sel->r.left = border;
> +		sel->r.top = border;
> +		sel->r.width = format->width - 2 * border;
> +		sel->r.height = format->height - 2 * border;
>  		break;
>  
>  	case V4L2_SEL_TGT_COMPOSE:
> @@ -1902,6 +1921,7 @@ static int mt9m114_ifp_set_selection(struct v4l2_subdev *sd,
>  	struct v4l2_mbus_framefmt *format;
>  	struct v4l2_rect *crop;
>  	struct v4l2_rect *compose;
> +	unsigned int border;
>  
>  	if (sel->target != V4L2_SEL_TGT_CROP &&
>  	    sel->target != V4L2_SEL_TGT_COMPOSE)
> @@ -1917,21 +1937,23 @@ static int mt9m114_ifp_set_selection(struct v4l2_subdev *sd,
>  
>  	if (sel->target == V4L2_SEL_TGT_CROP) {
>  		/*
> -		 * Clamp the crop rectangle. Demosaicing removes 4 pixels on
> -		 * each side of the image.
> +		 * Clamp the crop rectangle. For src pad fmts other then RAW10

Same here.

Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>

> +		 * demosaicing removes 4 pixels on each side of the image.
>  		 */
> -		crop->left = clamp_t(unsigned int, ALIGN(sel->r.left, 2), 4,
> -				     format->width - 4 -
> +		border = mt9m114_ifp_get_border(state);
> +
> +		crop->left = clamp_t(unsigned int, ALIGN(sel->r.left, 2), border,
> +				     format->width - border -
>  				     MT9M114_SCALER_CROPPED_INPUT_WIDTH);
> -		crop->top = clamp_t(unsigned int, ALIGN(sel->r.top, 2), 4,
> -				    format->height - 4 -
> +		crop->top = clamp_t(unsigned int, ALIGN(sel->r.top, 2), border,
> +				    format->height - border -
>  				    MT9M114_SCALER_CROPPED_INPUT_HEIGHT);
>  		crop->width = clamp_t(unsigned int, ALIGN(sel->r.width, 2),
>  				      MT9M114_SCALER_CROPPED_INPUT_WIDTH,
> -				      format->width - 4 - crop->left);
> +				      format->width - border - crop->left);
>  		crop->height = clamp_t(unsigned int, ALIGN(sel->r.height, 2),
>  				       MT9M114_SCALER_CROPPED_INPUT_HEIGHT,
> -				       format->height - 4 - crop->top);
> +				       format->height - border - crop->top);
>  
>  		sel->r = *crop;
>  

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2025-07-02  0:18 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-29 20:56 [PATCH v3 00/15] media: mt9m114: Changes to make it work with atomisp devices Hans de Goede
2025-06-29 20:56 ` [PATCH v3 01/15] media: aptina-pll: Debug log p1 min and max values Hans de Goede
2025-06-29 20:56 ` [PATCH v3 02/15] media: mt9m114: Add support for clock-frequency property Hans de Goede
2025-06-29 20:56 ` [PATCH v3 03/15] media: mt9m114: Use aptina-PLL helper to get PLL values Hans de Goede
2025-06-29 20:56 ` [PATCH v3 04/15] media: mt9m114: Lower minimum vblank value Hans de Goede
2025-06-29 20:56 ` [PATCH v3 05/15] media: mt9m114: Fix default hblank and vblank values Hans de Goede
2025-06-29 20:56 ` [PATCH v3 06/15] media: mt9m114: Tweak default hblank and vblank for more accurate fps Hans de Goede
2025-06-29 20:56 ` [PATCH v3 07/15] media: mt9m114: Avoid a reset low spike during probe() Hans de Goede
2025-06-29 20:56 ` [PATCH v3 08/15] media: mt9m114: Put sensor in reset on power down Hans de Goede
2025-06-29 20:56 ` [PATCH v3 09/15] media: mt9m114: Add and use mt9m114_ifp_get_border() helper function Hans de Goede
2025-07-02  0:17   ` Laurent Pinchart [this message]
2025-06-29 20:56 ` [PATCH v3 10/15] media: mt9m114: Adjust IFP selections and src format when src pixelfmt changes to/from RAW10 Hans de Goede
2025-07-02  0:32   ` Laurent Pinchart
2025-12-23 13:33     ` Hans de Goede
2025-06-29 20:56 ` [PATCH v3 11/15] media: mt9m114: Update src pad sel and format when sink pad format changes Hans de Goede
2025-07-02  0:36   ` Laurent Pinchart
2025-06-29 20:56 ` [PATCH v3 12/15] media: mt9m114: Don't allow changing the IFP crop/compose selections when bypassing the scaler Hans de Goede
2025-07-02  0:42   ` Laurent Pinchart
2025-06-29 20:56 ` [PATCH v3 13/15] media: mt9m114: Drop start-, stop-streaming sequence from initialize Hans de Goede
2025-07-02  1:08   ` Laurent Pinchart
2025-12-23 13:37     ` Hans de Goede
2025-12-23 16:50       ` Laurent Pinchart
2025-12-23 16:57         ` Hans de Goede
2025-06-29 20:56 ` [PATCH v3 14/15] media: mt9m114: Return -EPROBE_DEFER if no endpoint is found Hans de Goede
2025-07-02  0:53   ` Laurent Pinchart
2025-12-24 12:12     ` Hans de Goede
2025-12-27 14:54       ` Laurent Pinchart
2025-06-29 20:56 ` [PATCH v3 15/15] media: mt9m114: Add ACPI enumeration support Hans de Goede
     [not found] ` <6861b00f.050a0220.379e4a.5185@mx.google.com>
2025-06-30  7:34   ` [v3,00/15] media: mt9m114: Changes to make it work with atomisp devices Hans de Goede
2025-06-30 22:28 ` [PATCH v3 00/15] " Laurent Pinchart
2025-07-01 13:21   ` Hans de Goede

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=20250702001745.GD17819@pendragon.ideasonboard.com \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=hansg@kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mathis.foerst@mt.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