From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: linuxfancy@googlegroups.com, sakari.ailus@linux.intel.com,
Martin Hecht <martin.hecht@avnet.eu>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] media: i2c: alvium: inline set_frame_interval into s_frame_interval
Date: Mon, 18 Dec 2023 04:55:07 +0200 [thread overview]
Message-ID: <20231218025507.GI5290@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20231215082452.1720481-3-tomm.merciai@gmail.com>
Hi Tommaso,
Thank you for the patch.
On Fri, Dec 15, 2023 at 09:24:51AM +0100, Tommaso Merciai wrote:
> Inline alvium_s_frame_interval function into alvium_s_frame_interval.
I think you mean "alvium_set_frame_interval() function into
alvium_s_frame_interval.()"
> This to clean the driver code.
You can describe the reason more precisely:
The alvium_set_frame_interval() is called once only, by
alvium_s_frame_interval(). The latter is a thin wrapper around the
former. Inline the function in its caller to make the code more
readable.
The rest looks good to me.
> Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> ---
> drivers/media/i2c/alvium-csi2.c | 56 ++++++++++++---------------------
> 1 file changed, 20 insertions(+), 36 deletions(-)
>
> diff --git a/drivers/media/i2c/alvium-csi2.c b/drivers/media/i2c/alvium-csi2.c
> index c4b7851045a1..fde456357be1 100644
> --- a/drivers/media/i2c/alvium-csi2.c
> +++ b/drivers/media/i2c/alvium-csi2.c
> @@ -1662,16 +1662,25 @@ static int alvium_g_frame_interval(struct v4l2_subdev *sd,
> return 0;
> }
>
> -static int alvium_set_frame_interval(struct alvium_dev *alvium,
> - struct v4l2_subdev *sd,
> - struct v4l2_subdev_state *sd_state,
> - struct v4l2_subdev_frame_interval *fi,
> - u64 *req_fr)
> +static int alvium_s_frame_interval(struct v4l2_subdev *sd,
> + struct v4l2_subdev_state *sd_state,
> + struct v4l2_subdev_frame_interval *fi)
> {
> + struct alvium_dev *alvium = sd_to_alvium(sd);
> struct device *dev = &alvium->i2c_client->dev;
> - u64 dft_fr, min_fr, max_fr;
> + u64 req_fr, dft_fr, min_fr, max_fr;
> int ret;
>
> + /*
> + * FIXME: Implement support for V4L2_SUBDEV_FORMAT_TRY, using the V4L2
> + * subdev active state API.
> + */
> + if (fi->which != V4L2_SUBDEV_FORMAT_ACTIVE)
> + return -EINVAL;
> +
> + if (alvium->streaming)
> + return -EBUSY;
> +
> if (fi->interval.denominator == 0)
> return -EINVAL;
>
> @@ -1686,42 +1695,17 @@ static int alvium_set_frame_interval(struct alvium_dev *alvium,
> dev_dbg(dev, "fi->interval.denominator = %d\n",
> fi->interval.denominator);
>
> - *req_fr = (u64)((fi->interval.denominator * USEC_PER_SEC) /
> + req_fr = (u64)((fi->interval.denominator * USEC_PER_SEC) /
> fi->interval.numerator);
>
> - if (*req_fr >= max_fr && *req_fr <= min_fr)
> - *req_fr = dft_fr;
> + if (req_fr >= max_fr && req_fr <= min_fr)
> + req_fr = dft_fr;
>
> - alvium->fr = *req_fr;
> + alvium->fr = req_fr;
> alvium->frame_interval.numerator = fi->interval.numerator;
> alvium->frame_interval.denominator = fi->interval.denominator;
>
> - return 0;
> -}
> -
> -static int alvium_s_frame_interval(struct v4l2_subdev *sd,
> - struct v4l2_subdev_state *sd_state,
> - struct v4l2_subdev_frame_interval *fi)
> -{
> - struct alvium_dev *alvium = sd_to_alvium(sd);
> - u64 req_fr;
> - int ret;
> -
> - /*
> - * FIXME: Implement support for V4L2_SUBDEV_FORMAT_TRY, using the V4L2
> - * subdev active state API.
> - */
> - if (fi->which != V4L2_SUBDEV_FORMAT_ACTIVE)
> - return -EINVAL;
> -
> - if (alvium->streaming)
> - return -EBUSY;
> -
> - ret = alvium_set_frame_interval(alvium, sd, sd_state, fi, &req_fr);
> - if (!ret)
> - ret = alvium_set_frame_rate(alvium, req_fr);
> -
> - return ret;
> + return alvium_set_frame_rate(alvium, req_fr);
> }
>
> static int alvium_enum_mbus_code(struct v4l2_subdev *sd,
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-12-18 2:55 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-15 8:24 [PATCH 0/3] media: i2c: alvium: store frame interval in subdev state Tommaso Merciai
2023-12-15 8:24 ` [PATCH 1/3] media: i2c: alvium: removal of dft_fr, min_fr and max_fr Tommaso Merciai
2023-12-18 2:50 ` Laurent Pinchart
2023-12-18 2:54 ` Laurent Pinchart
2023-12-18 10:26 ` Tommaso Merciai
2023-12-15 8:24 ` [PATCH 2/3] media: i2c: alvium: inline set_frame_interval into s_frame_interval Tommaso Merciai
2023-12-18 2:55 ` Laurent Pinchart [this message]
2023-12-18 10:28 ` Tommaso Merciai
2023-12-15 8:24 ` [PATCH 3/3] media: i2c: alvium: store frame interval in subdev state Tommaso Merciai
2023-12-18 2:59 ` Laurent Pinchart
2023-12-18 10:30 ` Tommaso Merciai
2023-12-18 11:03 ` Laurent Pinchart
2023-12-18 11:19 ` Tommaso Merciai
2023-12-18 11:36 ` Laurent Pinchart
2023-12-18 11:39 ` Tommaso Merciai
2023-12-18 11:44 ` Laurent Pinchart
2023-12-18 11:58 ` Tommaso Merciai
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=20231218025507.GI5290@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linuxfancy@googlegroups.com \
--cc=martin.hecht@avnet.eu \
--cc=mchehab@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tomm.merciai@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