From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Eugen.Hristev@microchip.com
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
sakari.ailus@iki.fi
Subject: Re: [PATCH] media: i2c: mt9v032: fix enum mbus codes and frame sizes
Date: Thu, 21 Nov 2019 10:20:27 +0200 [thread overview]
Message-ID: <20191121082027.GJ4958@pendragon.ideasonboard.com> (raw)
In-Reply-To: <1574322901-7097-1-git-send-email-eugen.hristev@microchip.com>
Hi Eugen,
Thank you for the patch.
On Thu, Nov 21, 2019 at 07:55:24AM +0000, Eugen.Hristev@microchip.com wrote:
> From: Eugen Hristev <eugen.hristev@microchip.com>
>
> This driver supports both the mt9v032 (color) and the mt9v022 (mono) sensors.
> Depending on which sensor is used, the format from the sensor is different.
> The format.code inside the dev struct holds this information.
> The enum mbus and enum frame sizes need to take into account both type of
> sensors, not just the color one.
> To solve this, use the format.code in these functions instead of the
> hardcoded bayer color format (which is only used for mt9v032).
>
> Suggested-by: Wenyou Yang <wenyou.yang@microchip.com>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> ---
> drivers/media/i2c/mt9v032.c | 10 ++++++++--
> 1 file changed, 8 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/media/i2c/mt9v032.c b/drivers/media/i2c/mt9v032.c
> index 4b9b98c..5bd3ae82 100644
> --- a/drivers/media/i2c/mt9v032.c
> +++ b/drivers/media/i2c/mt9v032.c
> @@ -428,10 +428,12 @@ static int mt9v032_enum_mbus_code(struct v4l2_subdev *subdev,
> struct v4l2_subdev_pad_config *cfg,
> struct v4l2_subdev_mbus_code_enum *code)
> {
> + struct mt9v032 *mt9v032 = to_mt9v032(subdev);
> +
> if (code->index > 0)
> return -EINVAL;
>
> - code->code = MEDIA_BUS_FMT_SGRBG10_1X10;
> + code->code = mt9v032->format.code;
> return 0;
> }
>
> @@ -439,7 +441,11 @@ static int mt9v032_enum_frame_size(struct v4l2_subdev *subdev,
> struct v4l2_subdev_pad_config *cfg,
> struct v4l2_subdev_frame_size_enum *fse)
> {
> - if (fse->index >= 3 || fse->code != MEDIA_BUS_FMT_SGRBG10_1X10)
> + struct mt9v032 *mt9v032 = to_mt9v032(subdev);
> +
> + if (fse->index >= 3)
> + return -EINVAL;
> + if (mt9v032->format.code != fse->code)
> return -EINVAL;
>
> fse->min_width = MT9V032_WINDOW_WIDTH_DEF / (1 << fse->index);
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2019-11-21 8:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-21 7:55 [PATCH] media: i2c: mt9v032: fix enum mbus codes and frame sizes Eugen.Hristev
2019-11-21 8:20 ` 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=20191121082027.GJ4958@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=Eugen.Hristev@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=sakari.ailus@iki.fi \
/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