From: Sakari Ailus <sakari.ailus@linux.intel.com>
To: Benoit Parrot <bparrot@ti.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [Patch v2 5/7] media: i2c: ov2659: Add powerdown/reset gpio handling
Date: Mon, 23 Sep 2019 09:17:32 +0300 [thread overview]
Message-ID: <20190923061731.GZ5781@paasikivi.fi.intel.com> (raw)
In-Reply-To: <20190920165529.it7urirm6epg4woq@ti.com>
Hi Benoit,
On Fri, Sep 20, 2019 at 11:55:29AM -0500, Benoit Parrot wrote:
...
> > > @@ -1400,6 +1440,18 @@ static int ov2659_probe(struct i2c_client *client)
> > > ov2659->xvclk_frequency > 27000000)
> > > return -EINVAL;
> > >
> > > + /* Optional gpio don't fail if not present */
> > > + ov2659->pwdn_gpio = devm_gpiod_get_optional(&client->dev, "powerdown",
> > > + GPIOD_OUT_LOW);
> > > + if (IS_ERR(ov2659->pwdn_gpio))
> > > + return PTR_ERR(ov2659->pwdn_gpio);
> > > +
> > > + /* Optional gpio don't fail if not present */
> > > + ov2659->resetb_gpio = devm_gpiod_get_optional(&client->dev, "reset",
> > > + GPIOD_OUT_HIGH);
> > > + if (IS_ERR(ov2659->resetb_gpio))
> > > + return PTR_ERR(ov2659->resetb_gpio);
> > > +
> > > v4l2_ctrl_handler_init(&ov2659->ctrls, 2);
> > > ov2659->link_frequency =
> > > v4l2_ctrl_new_std(&ov2659->ctrls, &ov2659_ctrl_ops,
> > > @@ -1445,6 +1497,9 @@ static int ov2659_probe(struct i2c_client *client)
> > > ov2659->frame_size = &ov2659_framesizes[2];
> > > ov2659->format_ctrl_regs = ov2659_formats[0].format_ctrl_regs;
> > >
> > > + pm_runtime_enable(&client->dev);
> > > + pm_runtime_get_sync(&client->dev);
> >
> > This makes the driver depend on runtime PM.
>
> Obviously.
> Why? Is that bad?
Well, if it is, then it should be listed in driver's dependencies in
Kconfig.
>
> >
> > See e.g. the smiapp driver for an example how to make it work without. It
> > wasn't trivial. :I You won't need autosuspend.
>
> I took a look at that driver, but I don't get your reference to being able
> to work without runtime pm!
The driver didn't need runtime PM, so it'd be nice to continue work
without.
What smiapp does is that it powers the sensor on first *without* runtime
PM, and then proceeds to set up runtime PM if it's available. The sensor
will only be powered off when the device is unbound with runtime PM
disabled.
Regarding the smiapp driver, you can replace pm_runtime_get_noresume() and
all the autoidle lines with pm_runtime_idle() call after
pm_runtime_enable() in the ov2659 driver.
> That driver looks pretty similar to ov7740.c which I used as a reference
> for this.
I guess in practice many sensor drivers don't work without it on DT-based
systems I'm afraid. :-( They should be fixed.
--
Kind regards,
Sakari Ailus
sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2019-09-23 6:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 20:39 [Patch v2 0/7] media: i2c: ov2659: maintenance series Benoit Parrot
2019-09-19 20:39 ` [Patch v2 1/7] media: i2c: ov2659: Fix for image wrap-around in lower resolution Benoit Parrot
2019-09-19 20:39 ` [Patch v2 2/7] media: i2c: ov2659: Fix sensor detection to actually fail when device is not present Benoit Parrot
2019-09-19 20:39 ` [Patch v2 3/7] media: i2c: ov2659: Cleanup include file list Benoit Parrot
2019-09-19 20:39 ` [Patch v2 4/7] media: dt-bindings: ov2659: add powerdown/reset-gpios optional property Benoit Parrot
2019-09-19 20:39 ` [Patch v2 5/7] media: i2c: ov2659: Add powerdown/reset gpio handling Benoit Parrot
2019-09-20 10:17 ` Sakari Ailus
2019-09-20 16:55 ` Benoit Parrot
2019-09-23 6:17 ` Sakari Ailus [this message]
2019-09-23 17:05 ` Benoit Parrot
2019-09-23 17:07 ` Sakari Ailus
2019-09-19 20:39 ` [Patch v2 6/7] media: i2c: ov2659: Fix missing 720p register config Benoit Parrot
2019-09-19 20:39 ` [Patch v2 7/7] media: i2c: ov2659: Switch to SPDX Licensing Benoit Parrot
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=20190923061731.GZ5781@paasikivi.fi.intel.com \
--to=sakari.ailus@linux.intel.com \
--cc=bparrot@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=prabhakar.csengg@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
all inboxes | Powered by JetHome®