From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Richard Leitner <richard.leitner@linux.dev>
Cc: Dave Stevenson <dave.stevenson@raspberrypi.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org, Hans Verkuil <hverkuil@kernel.org>
Subject: Re: [PATCH v8 7/8] media: i2c: ov9282: implement try_ctrl for strobe_duration
Date: Mon, 10 Nov 2025 09:55:18 +0200 [thread overview]
Message-ID: <aRGaZptpBRq_iga-@kekkonen.localdomain> (raw)
In-Reply-To: <20251104-ov9282-flash-strobe-v8-7-b91dfef1c65a@linux.dev>
Hi Richard,
On Tue, Nov 04, 2025 at 03:30:58PM +0100, Richard Leitner wrote:
> As the granularity of the hardware supported values is lower than the
> control value, implement a try_ctrl() function for
> V4L2_CID_FLASH_DURATION. This function calculates the nearest possible
> µs strobe duration for the given value and returns it back to the
> caller.
>
> Signed-off-by: Richard Leitner <richard.leitner@linux.dev>
> ---
> drivers/media/i2c/ov9282.c | 55 +++++++++++++++++++++++++++++++++++++++++++---
> 1 file changed, 52 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/media/i2c/ov9282.c b/drivers/media/i2c/ov9282.c
> index 26296dc1d1b95..7aa74feb3ee44 100644
> --- a/drivers/media/i2c/ov9282.c
> +++ b/drivers/media/i2c/ov9282.c
> @@ -128,6 +128,8 @@
> #define OV9282_REG_MIN 0x00
> #define OV9282_REG_MAX 0xfffff
>
> +#define OV9282_STROBE_SPAN_FACTOR 192
> +
> static const char * const ov9282_supply_names[] = {
> "avdd", /* Analog power */
> "dovdd", /* Digital I/O power */
> @@ -691,9 +693,8 @@ static int ov9282_set_ctrl_flash_strobe_oe(struct ov9282 *ov9282, bool enable)
> return ov9282_write_reg(ov9282, OV9282_REG_OUTPUT_ENABLE6, 1, current_val);
> }
>
> -static int ov9282_set_ctrl_flash_duration(struct ov9282 *ov9282, u32 value)
> +static u32 ov9282_us_to_flash_duration(struct ov9282 *ov9282, u32 value)
> {
> - int ret;
> /*
> * Calculate "strobe_frame_span" increments from a given value (µs).
> * This is quite tricky as "The step width of shift and span is
> @@ -703,7 +704,28 @@ static int ov9282_set_ctrl_flash_duration(struct ov9282 *ov9282, u32 value)
> * The formula below is interpolated from different modes/framerates
> * and should work quite well for most settings.
> */
> - u32 val = value * 192 / (ov9282->cur_mode->width + ov9282->hblank_ctrl->val);
> + u32 frame_width = ov9282->cur_mode->width + ov9282->hblank_ctrl->val;
> +
> + return value * OV9282_STROBE_SPAN_FACTOR / frame_width;
> +}
> +
> +static u32 ov9282_flash_duration_to_us(struct ov9282 *ov9282, u32 value)
> +{
> + /*
> + * As the calculation in ov9282_us_to_flash_duration uses an integer
> + * divison calculate in ns here to get more precision. Then check if
> + * we need to compensate that divison by incrementing the µs result.
> + */
> + u32 frame_width = ov9282->cur_mode->width + ov9282->hblank_ctrl->val;
> + u64 ns = value * 1000 * frame_width / OV9282_STROBE_SPAN_FACTOR;
> +
> + return DIV_ROUND_UP(ns, 1000);
Can ns even exceed U32_MAX? It doesn't seem to be useful to multiply and
then divide by 1000.
I guess this warrants v9, please fix the other issue for that, too.
> +}
> +
> +static int ov9282_set_ctrl_flash_duration(struct ov9282 *ov9282, u32 value)
> +{
> + int ret;
> + u32 val = ov9282_us_to_flash_duration(ov9282, value);
>
> ret = ov9282_write_reg(ov9282, OV9282_REG_STROBE_FRAME_SPAN, 1,
> (val >> 24) & 0xff);
> @@ -798,9 +820,36 @@ static int ov9282_set_ctrl(struct v4l2_ctrl *ctrl)
> return ret;
> }
>
> +static int ov9282_try_ctrl(struct v4l2_ctrl *ctrl)
> +{
> + struct ov9282 *ov9282 =
> + container_of_const(ctrl->handler, struct ov9282, ctrl_handler);
> +
> + if (ctrl->id == V4L2_CID_FLASH_DURATION) {
> + u32 us = ctrl->val;
> + u32 fd = ov9282_us_to_flash_duration(ov9282, us);
> +
> + /* get nearest strobe_duration value */
> + u32 us0 = ov9282_flash_duration_to_us(ov9282, fd);
> + u32 us1 = ov9282_flash_duration_to_us(ov9282, fd + 1);
> +
> + if (abs(us1 - us) < abs(us - us0))
> + ctrl->val = us1;
> + else
> + ctrl->val = us0;
> +
> + if (us != ctrl->val)
> + dev_dbg(ov9282->dev, "using next valid strobe_duration %u instead of %u\n",
> + ctrl->val, us);
> + }
> +
> + return 0;
> +}
> +
> /* V4l2 subdevice control ops*/
> static const struct v4l2_ctrl_ops ov9282_ctrl_ops = {
> .s_ctrl = ov9282_set_ctrl,
> + .try_ctrl = ov9282_try_ctrl,
> };
>
> /**
>
--
Regards,
Sakari Ailus
next prev parent reply other threads:[~2025-11-10 7:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-04 14:30 [PATCH v8 0/8] Add strobe duration and strobe output enable v4l2 ctrl Richard Leitner
2025-11-04 14:30 ` [PATCH v8 1/8] media: v4l: ctrls: add a control for flash/strobe duration Richard Leitner
2025-11-04 14:30 ` [PATCH v8 2/8] media: v4l: ctrls: add a control for enabling strobe output Richard Leitner
2025-11-04 14:30 ` [PATCH v8 3/8] Documentation: uAPI: media: add V4L2_CID_FLASH_{DURATION,STROBE_OE} Richard Leitner
2025-11-04 14:30 ` [PATCH v8 4/8] media: i2c: ov9282: add output enable register definitions Richard Leitner
2025-11-04 14:30 ` [PATCH v8 5/8] media: i2c: ov9282: add strobe output enable v4l2 control Richard Leitner
2025-11-04 14:30 ` [PATCH v8 6/8] media: i2c: ov9282: add strobe_duration " Richard Leitner
2025-11-04 14:30 ` [PATCH v8 7/8] media: i2c: ov9282: implement try_ctrl for strobe_duration Richard Leitner
2025-11-07 21:05 ` kernel test robot
2025-11-10 7:55 ` Sakari Ailus [this message]
2025-11-12 8:01 ` Richard Leitner
2025-11-04 14:30 ` [PATCH v8 8/8] media: i2c: ov9282: dynamic flash_duration maximum Richard Leitner
2025-11-10 7:56 ` Sakari Ailus
2025-11-12 8:10 ` Richard Leitner
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=aRGaZptpBRq_iga-@kekkonen.localdomain \
--to=sakari.ailus@linux.intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=hverkuil@kernel.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=pavel@kernel.org \
--cc=richard.leitner@linux.dev \
/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