Hi Laurent,
thank you for the feedback!
On Thu, 29 Aug 2024 at 15:19, Laurent Pinchart
<laurent.pinchart@xxxxxxxxxxxxxxxx> wrote:
> Hi Benjamin,
>
> Thank you for the patch.
>
> On Wed, Aug 28, 2024 at 08:13:07PM +0200, Benjamin Bara wrote:
> > Currently, the V4L2 subdevice is also created when the device is not
> > available/connected. In this case, dmesg shows the following:
> >
> > [ 10.419510] imx290 7-001a: Error writing reg 0x301c: -6
> > [ 10.428981] imx290 7-001a: Error writing reg 0x3020: -6
> > [ 10.442712] imx290 7-001a: Error writing reg 0x3018: -6
> > [ 10.454018] imx290 7-001a: Error writing reg 0x3020: -6
> >
> > which seems to come from imx290_ctrl_update() after the subdev init is
> > finished.
>
> I think this should also be fixed. There should be no need to write
> those registers at probe time. Would moving the
> pm_runtime_mark_last_busy() and pm_runtime_put_autosuspend() calls to
> just before imx290_subdev_init() help ?
I guess if I decrease the autosuspend delay (now 1s), it would work -
but it feels like a hack to me. I would prefer to not call
imx290_ctrl_update() at all during probe(). I guess the reason why it is
done is to have sane ctrl values for link_freq, hblank and vblank.
However, as they depend on the mode (which isn't known at that time), it
(at least to me) doesn't make sense to just "assume" the first mode
here.
I would prefer to introduce a FREQ_INDEX_OFF with 0 here and use this as
default, and use the ranges from the datasheet for {v,h}blank already
when creating the controls. When the mode is decided, the blanks will be
adapted to be in range.
I can add an example in the next round, need to implement and test
first.
> > However, as the errors are ignored, the subdev is initialized
> > but simply does not work. From userspace perspective, there is no
> > visible difference between a working and not-working subdevice (except
> > when trying it out or watching for the error message).
> >
> > This commit adds a simple availability check before starting with the
> > subdev initialization to error out instead.
> >
> > Signed-off-by: Benjamin Bara <benjamin.bara@xxxxxxxxxxx>
> > ---
> > Changes since v1:
> > - define operating/standby mode and use it
> > - read out the standby mode during probe and ensure it is standby
> > ---
> > drivers/media/i2c/imx290.c | 17 +++++++++++++++--
> > 1 file changed, 15 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/i2c/imx290.c b/drivers/media/i2c/imx290.c
> > index 4150e6e4b9a6..2a869576600c 100644
> > --- a/drivers/media/i2c/imx290.c
> > +++ b/drivers/media/i2c/imx290.c
> > @@ -29,6 +29,8 @@
> > #include <media/v4l2-subdev.h>
> >
> > #define IMX290_STANDBY CCI_REG8(0x3000)
> > +#define IMX290_STANDBY_OPERATING (0 << 0)
> > +#define IMX290_STANDBY_STANDBY (1 << 0)
>
> The datasheet documents the STANDBY field as a single bit, but doesn't
> mention an OPERATING value. I would match that, drop
> IMX290_STANDBY_OPERATING and write
The imx290 datasheet from Arrow has it on page 35, but I can switch to
your version if preferred :)
> #define IMX290_STANDBY_STANDBY BIT(0)
>
> > #define IMX290_REGHOLD CCI_REG8(0x3001)
> > #define IMX290_XMSTA CCI_REG8(0x3002)
> > #define IMX290_ADBIT CCI_REG8(0x3005)
> > @@ -1016,7 +1018,7 @@ static int imx290_start_streaming(struct imx290 *imx290,
> > return ret;
> > }
> >
> > - cci_write(imx290->regmap, IMX290_STANDBY, 0x00, &ret);
> > + cci_write(imx291->regmap, IMX290_STANDBY, IMX290_STANDBY_OPERATING, &ret);
>
> This hunk would then be dropped.
>
> >
> > msleep(30);
> >
> > @@ -1029,7 +1031,7 @@ static int imx290_stop_streaming(struct imx290 *imx290)
> > {
> > int ret = 0;
> >
> > - cci_write(imx290->regmap, IMX290_STANDBY, 0x01, &ret);
> > + cci_write(imx290->regmap, IMX290_STANDBY, IMX290_STANDBY_STANDBY, &ret);
>
> And this looks fine.
>
> The change isn't mentioned in the commit message though. I wouldn't ask
> for a v3 just to split this, but as you need to address other issues, it
> would be nice to have a separate patch in v3.
Yup, can do that :)
> >
> > msleep(30);
> >
> > @@ -1520,6 +1522,7 @@ static int imx290_probe(struct i2c_client *client)
> > {
> > struct device *dev = &client->dev;
> > struct imx290 *imx290;
> > + u64 val;
> > int ret;
> >
> > imx290 = devm_kzalloc(dev, sizeof(*imx290), GFP_KERNEL);
> > @@ -1580,6 +1583,16 @@ static int imx290_probe(struct i2c_client *client)
> > pm_runtime_set_autosuspend_delay(dev, 1000);
> > pm_runtime_use_autosuspend(dev);
> >
> > + /* Make sure the sensor is available before V4L2 subdev init. */
> > + ret = cci_read(imx290->regmap, IMX290_STANDBY, &val, NULL);
>
> I still wish we had an ID register, but so be it.
When we implement a SW reset (to be sure that there was a reset in case
a dummy regulator is used), we can probably come up with a mix of
different default values of registers to go through, but not sure if
this is really worth it...
> > + if (ret)
>
> Maybe add
>
> ret = dev_err_probe(dev, -ENODEV, "Failed to detect sensor\n");
>
> or something similar ? Up to you.
Probably a good idea. I didn't print something here because cci_read()
already does.
> > + goto err_pm;
> > + if (val != IMX290_STANDBY_STANDBY) {
>
> I think this check could be dropped though. If the sensor isn't present
> or doesn't respond to I2C reads for any other reason, cci_read() will
> fail.
I added it because Sakari and Alex suggested to read back a value and
compare it to an expectation. Would keep it therefore?
> > + dev_err(dev, "Sensor is not in standby mode\n");
> > + ret = -ENODEV;
> > + goto err_pm;
> > + }
> > +
>
> My last concern is about accessing hardware at probe time. There are
> known cases where this is problematic. They can be split in two
> categories, systems that exhibit unwanted side effects when powering the
> sensor up, and systems where the sensor can't be accessed at probe time.
>
> The two issues I can think of in the first category is devices that have
> a camera privacy light that could cause worries among users if it
> flashes at boot time, and devices that agressively optimize boot time.
>
> In the second category, I know that some people use camera serdes
> (FPD-Link, GMSL, ...) that are controlled by userspace. As they should
> instead use kernel drivers for those components, upstream may not care
> too much about this use case. Another issue I was told about was a
> device booting in temperatures that were too low for the camera to
> operate, which then needed half an hour to heat the device enclosure
> before the sensor and serdes could be accessed. That's a bit extreme,
> but it sounds like a valid use case to me.
>
> What do we do with those cases ? Detecting devices at probe time does
> have value, so I think it should be a policy decision. We may want to
> convey some of that information through DT properties (I'm not sure what
> would be acceptable there though). In any case, that's quite a bit of
> yak shaving, so I'm inclined to accept this series (or rather its next
> version), given that quite a few other camera sensor drivers detect the
> device at probe time. I would however like feedback on the problem to
> try and find a good solution.
One of the rather "simpler" solutions that come to my mind (without
adding something like a generic "disallow-regulator-during-probe" or
similar DT property) is to check the current state of the used
regulator(s) and keep it during the cam probe. If it is already active:
fine, we can communicate and find out; if not: live with schroedinger's
cam. Probably we should decide at one point in time if dead or alive.
If you think this sounds fine, I can modify the series to do that.
> > /* Initialize the V4L2 subdev. */
> > ret = imx290_subdev_init(imx290);
> > if (ret)
> >
--
Kind regards
Benjamin
