| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAPY8ntDF8W+xRBXbe=LYpg21LL7-svhCySTSJHRNiDzQs4Xw5Q@mail.gmail.com>
Date: Thu, 7 Nov 2024 12:43:52 +0000
From: Dave Stevenson <dave.stevenson@...pberrypi.com>
To: Sakari Ailus <sakari.ailus@...ux.intel.com>
Cc: Jai Luthra <jai.luthra@...asonboard.com>, Mauro Carvalho Chehab <mchehab@...nel.org>,
linux-media@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 2/3] media: i2c: imx219: make HBLANK r/w to allow longer exposures
Hi Sakari
On Fri, 1 Nov 2024 at 08:48, Sakari Ailus <sakari.ailus@...ux.intel.com> wrote:
>
> Hi Jai,
>
> On Tue, Oct 29, 2024 at 02:27:36PM +0530, Jai Luthra wrote:
> > From: Dave Stevenson <dave.stevenson@...pberrypi.com>
> >
> > The HBLANK control was read-only, and always configured such
> > that the sensor HTS register was 3448. This limited the maximum
> > exposure time that could be achieved to around 1.26 secs.
> >
> > Make HBLANK read/write so that the line time can be extended,
> > and thereby allow longer exposures (and slower frame rates).
> > Retain the overall HTS setting when changing modes rather than
> > resetting it to a default.
>
> It looks like this changes horizontal blanking at least in some cases. Does
> this also work as expected in binned modes, for instance?
>
> Many sensors have image quality related issues on untested albeit
> functional line length values.
>
> So my question is: how has this been validated?
Validated by Sony, or others?
I've tested a range of values in all modes and not observed any image
quality issues.
>From previous discussions with Sony, they always provide their big
spreadsheet of register values for the specific mode and frame rate
requested. I don't think they even officially state that changing
VTS/FRM_LENGTH_LINES to change the framerate is permitted.
There are some Sony datasheets (eg imx258) that state "set to X. Any
other value please confirm with Sony", but that isn't the case for the
imx219 datasheet. I take that as it is permitted within the defined
ranges.
Dave
> >
> > Signed-off-by: Dave Stevenson <dave.stevenson@...pberrypi.com>
> > Signed-off-by: Jai Luthra <jai.luthra@...asonboard.com>
> > ---
> > drivers/media/i2c/imx219.c | 35 +++++++++++++++++++++++------------
> > 1 file changed, 23 insertions(+), 12 deletions(-)
> >
> > diff --git a/drivers/media/i2c/imx219.c b/drivers/media/i2c/imx219.c
> > index f98aad74fe584a18e2fe7126f92bf294762a54e3..de9230d4ad81f085640be254db9391ae7ad20773 100644
> > --- a/drivers/media/i2c/imx219.c
> > +++ b/drivers/media/i2c/imx219.c
> > @@ -76,8 +76,10 @@
> >
> > #define IMX219_VBLANK_MIN 32
> >
> > -/* HBLANK control - read only */
> > -#define IMX219_PPL_DEFAULT 3448
> > +/* HBLANK control range */
> > +#define IMX219_PPL_MIN 3448
> > +#define IMX219_PPL_MAX 0x7ff0
> > +#define IMX219_REG_HTS CCI_REG16(0x0162)
> >
> > #define IMX219_REG_LINE_LENGTH_A CCI_REG16(0x0162)
> > #define IMX219_REG_X_ADD_STA_A CCI_REG16(0x0164)
> > @@ -422,6 +424,10 @@ static int imx219_set_ctrl(struct v4l2_ctrl *ctrl)
> > cci_write(imx219->regmap, IMX219_REG_VTS,
> > format->height + ctrl->val, &ret);
> > break;
> > + case V4L2_CID_HBLANK:
> > + cci_write(imx219->regmap, IMX219_REG_HTS,
> > + format->width + ctrl->val, &ret);
> > + break;
> > case V4L2_CID_TEST_PATTERN_RED:
> > cci_write(imx219->regmap, IMX219_REG_TESTP_RED,
> > ctrl->val, &ret);
> > @@ -496,12 +502,11 @@ static int imx219_init_controls(struct imx219 *imx219)
> > V4L2_CID_VBLANK, IMX219_VBLANK_MIN,
> > IMX219_VTS_MAX - mode->height, 1,
> > mode->vts_def - mode->height);
> > - hblank = IMX219_PPL_DEFAULT - mode->width;
> > + hblank = IMX219_PPL_MIN - mode->width;
> > imx219->hblank = v4l2_ctrl_new_std(ctrl_hdlr, &imx219_ctrl_ops,
> > - V4L2_CID_HBLANK, hblank, hblank,
> > + V4L2_CID_HBLANK, hblank,
> > + IMX219_PPL_MIN - mode->width,
> > 1, hblank);
> > - if (imx219->hblank)
> > - imx219->hblank->flags |= V4L2_CTRL_FLAG_READ_ONLY;
> > exposure_max = mode->vts_def - 4;
> > exposure_def = (exposure_max < IMX219_EXPOSURE_DEFAULT) ?
> > exposure_max : IMX219_EXPOSURE_DEFAULT;
> > @@ -842,6 +847,7 @@ static int imx219_set_pad_format(struct v4l2_subdev *sd,
> > crop->top = (IMX219_NATIVE_HEIGHT - crop->height) / 2;
> >
> > if (fmt->which == V4L2_SUBDEV_FORMAT_ACTIVE) {
> > + u32 prev_hts = format->width + imx219->hblank->val;
> > int exposure_max;
> > int exposure_def;
> > int hblank;
> > @@ -861,13 +867,18 @@ static int imx219_set_pad_format(struct v4l2_subdev *sd,
> > exposure_max, imx219->exposure->step,
> > exposure_def);
> > /*
> > - * Currently PPL is fixed to IMX219_PPL_DEFAULT, so hblank
> > - * depends on mode->width only, and is not changeble in any
> > - * way other than changing the mode.
> > + * Retain PPL setting from previous mode so that the
> > + * line time does not change on a mode change.
> > + * Limits have to be recomputed as the controls define
> > + * the blanking only, so PPL values need to have the
> > + * mode width subtracted.
> > */
> > - hblank = IMX219_PPL_DEFAULT - mode->width;
> > - __v4l2_ctrl_modify_range(imx219->hblank, hblank, hblank, 1,
> > - hblank);
> > + hblank = prev_hts - mode->width;
> > + __v4l2_ctrl_modify_range(imx219->hblank,
> > + IMX219_PPL_MIN - mode->width,
> > + IMX219_PPL_MAX - mode->width,
> > + 1, IMX219_PPL_MIN - mode->width);
> > + __v4l2_ctrl_s_ctrl(imx219->hblank, hblank);
> > }
> >
> > return 0;
> >
>
> --
> Kind regards,
>
> Sakari Ailus
Powered by blists - more mailing lists