From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Tommaso Merciai <tomm.merciai@gmail.com>
Cc: linuxfancy@googlegroups.com, martin.hecht@avnet.eu,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] media: i2c: alvium: removal of fr field
Date: Wed, 20 Dec 2023 11:13:09 +0200 [thread overview]
Message-ID: <20231220091309.GG29638@pendragon.ideasonboard.com> (raw)
In-Reply-To: <20231220085609.2595732-3-tomm.merciai@gmail.com>
Hi Tommaso,
Thank you for the patch.
Use the imperative in the subject line:
media: i2c: alvium: Remove the fr field of the alvium_dev structure
On Wed, Dec 20, 2023 at 09:56:07AM +0100, Tommaso Merciai wrote:
> The fr (frame rate) field of the alvium_dev structure is
> only used to pass result from alvium_set_frame_interval() to
> alvium_set_frame_rate() that writes this info into the hw reg.
> Replace them with function parameter.
Replace it with a function parameter.
>
> Signed-off-by: Tommaso Merciai <tomm.merciai@gmail.com>
> ---
> drivers/media/i2c/alvium-csi2.c | 24 ++++++++++++------------
> drivers/media/i2c/alvium-csi2.h | 1 -
> 2 files changed, 12 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/media/i2c/alvium-csi2.c b/drivers/media/i2c/alvium-csi2.c
> index 0dcd69bf9f92..a9ff6cc97cff 100644
> --- a/drivers/media/i2c/alvium-csi2.c
> +++ b/drivers/media/i2c/alvium-csi2.c
> @@ -1185,19 +1185,19 @@ static int alvium_get_frame_interval(struct alvium_dev *alvium,
> return ret;
> }
>
> -static int alvium_set_frame_rate(struct alvium_dev *alvium)
> +static int alvium_set_frame_rate(struct alvium_dev *alvium, u64 fr)
> {
> struct device *dev = &alvium->i2c_client->dev;
> int ret;
>
> ret = alvium_write_hshake(alvium, REG_BCRM_ACQUISITION_FRAME_RATE_RW,
> - alvium->fr);
> + fr);
> if (ret) {
> dev_err(dev, "Fail to set frame rate lanes reg\n");
> return ret;
> }
>
> - dev_dbg(dev, "set frame rate: %llu us\n", alvium->fr);
> + dev_dbg(dev, "set frame rate: %llu us\n", fr);
>
> return 0;
> }
> @@ -1661,10 +1661,11 @@ static int alvium_g_frame_interval(struct v4l2_subdev *sd,
> }
>
> static int alvium_set_frame_interval(struct alvium_dev *alvium,
> - struct v4l2_subdev_frame_interval *fi)
> + struct v4l2_subdev_frame_interval *fi,
> + u64 *req_fr)
> {
> struct device *dev = &alvium->i2c_client->dev;
> - u64 req_fr, dft_fr, min_fr, max_fr;
> + u64 dft_fr, min_fr, max_fr;
> int ret;
>
> if (fi->interval.denominator == 0)
> @@ -1681,13 +1682,12 @@ 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;
Shouldn't we clamp the value to [min, max] instead of using the default
if it's out of range ? Something like
*req_fr = clamp(*req_fr, min_fr, max_fr)
This makes me realize that the current code is wrong, req_fr can't be >=
max and <= min at the same time. You probably meant || instead of &&.
This should be fixed in a separate patch.
>
> - alvium->fr = req_fr;
> alvium->frame_interval.numerator = fi->interval.numerator;
> alvium->frame_interval.denominator = fi->interval.denominator;
>
> @@ -1699,6 +1699,7 @@ static int alvium_s_frame_interval(struct v4l2_subdev *sd,
> struct v4l2_subdev_frame_interval *fi)
> {
> struct alvium_dev *alvium = sd_to_alvium(sd);
> + u64 req_fr = ALVIUM_DEFAULT_FR_HZ;
Do you need to initialize the variable ? It doesn't seem to be required.
With these small issues fixed,
Reviewed-by: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
> int ret;
>
> /*
> @@ -1711,9 +1712,9 @@ static int alvium_s_frame_interval(struct v4l2_subdev *sd,
> if (alvium->streaming)
> return -EBUSY;
>
> - ret = alvium_set_frame_interval(alvium, fi);
> + ret = alvium_set_frame_interval(alvium, fi, &req_fr);
> if (!ret)
> - ret = alvium_set_frame_rate(alvium);
> + ret = alvium_set_frame_rate(alvium, req_fr);
>
> return ret;
> }
> @@ -2273,7 +2274,6 @@ static int alvium_subdev_init(struct alvium_dev *alvium)
> /* Setup initial frame interval*/
> alvium->frame_interval.numerator = 1;
> alvium->frame_interval.denominator = ALVIUM_DEFAULT_FR_HZ;
> - alvium->fr = ALVIUM_DEFAULT_FR_HZ;
>
> /* Setup the initial mode */
> alvium->mode.fmt = alvium_csi2_default_fmt;
> diff --git a/drivers/media/i2c/alvium-csi2.h b/drivers/media/i2c/alvium-csi2.h
> index 17f0bbbd1839..80066ac25047 100644
> --- a/drivers/media/i2c/alvium-csi2.h
> +++ b/drivers/media/i2c/alvium-csi2.h
> @@ -443,7 +443,6 @@ struct alvium_dev {
>
> struct alvium_mode mode;
> struct v4l2_fract frame_interval;
> - u64 fr;
>
> u8 h_sup_csi_lanes;
> u64 link_freq;
--
Regards,
Laurent Pinchart
next prev parent reply other threads:[~2023-12-20 9:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 8:56 [PATCH v2 0/4] media: i2c: alvium: store frame interval in subdev Tommaso Merciai
2023-12-20 8:56 ` [PATCH v2 1/4] media: i2c: alvium: removal of dft_fr, min_fr and max_fr Tommaso Merciai
2023-12-20 9:08 ` Laurent Pinchart
2023-12-20 8:56 ` [PATCH v2 2/4] media: i2c: alvium: removal of fr field Tommaso Merciai
2023-12-20 9:13 ` Laurent Pinchart [this message]
2023-12-20 10:02 ` Tommaso Merciai
2023-12-20 10:06 ` Laurent Pinchart
2023-12-20 11:19 ` Tommaso Merciai
2023-12-20 11:29 ` Laurent Pinchart
2023-12-20 12:03 ` Tommaso Merciai
2023-12-20 12:19 ` Laurent Pinchart
2023-12-20 12:42 ` Tommaso Merciai
2023-12-20 8:56 ` [PATCH v2 3/4] media: i2c: alvium: inline set_frame_interval into s_frame_interval Tommaso Merciai
2023-12-20 9:14 ` Laurent Pinchart
2023-12-20 10:04 ` Tommaso Merciai
2023-12-20 8:56 ` [PATCH v2 4/4] media: i2c: alvium: store frame interval in subdev state Tommaso Merciai
2023-12-20 9:17 ` Laurent Pinchart
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=20231220091309.GG29638@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=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