From: Benoit Parrot <bparrot@ti.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
Prabhakar Lad <prabhakar.csengg@gmail.com>,
Rob Herring <robh+dt@kernel.org>, <linux-media@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [Patch v3 6/8] media: i2c: ov2659: Add powerdown/reset gpio handling
Date: Wed, 25 Sep 2019 09:37:41 -0500 [thread overview]
Message-ID: <20190925143741.25qn2wuyiwapsehr@ti.com> (raw)
In-Reply-To: <20190925095154.GL9467@paasikivi.fi.intel.com>
Sakari Ailus <sakari.ailus@linux.intel.com> wrote on Wed [2019-Sep-25 12:51:54 +0300]:
> Hi Benoit,
>
> On Tue, Sep 24, 2019 at 11:44:12AM -0500, Benoit Parrot wrote:
> > On some board it is possible that the sensor 'powerdown' and or 'reset'
> > pin might be controlled by gpio instead of being tied.
> >
> > To implement we add pm_runtime support which will handle the power
> > up/down sequence when it is available otherwise the sensor will be
> > powered on at module insertion/probe and powered off at module removal.
> >
> > Now originally the driver assumed that the sensor would always stay
> > powered and keep its register setting. We cannot assume this anymore, so
> > every time we "power up" we need to re-program the initial registers
> > configuration first. This was previously done only at probe time.
> >
> > Signed-off-by: Benoit Parrot <bparrot@ti.com>
>
> Thanks for the update.
>
> I missed the control interface is accessible also when the device is not
> streaming, and the driver doesn't appear to power on the sensor for that,
> leading to a failing I²C write.
>
> Could you address that as well, either here or as a separate patch? E.g.
> the smiapp driver does this.
Yes, I missed that also.
I'll add a check in .s_ctrl().
Benoit
>
> --
> Kind regards,
>
> Sakari Ailus
> sakari.ailus@linux.intel.com
next prev parent reply other threads:[~2019-09-25 14:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 16:44 [Patch v3 0/8] media: i2c: ov2659: maintenance series Benoit Parrot
2019-09-24 16:44 ` [Patch v3 1/8] media: i2c: ov2659: Fix for image wrap-around in lower resolution Benoit Parrot
2019-09-24 16:44 ` [Patch v3 2/8] media: i2c: ov2659: Fix sensor detection to actually fail when device is not present Benoit Parrot
2019-09-24 16:44 ` [Patch v3 3/8] media: i2c: ov2659: Cleanup include file list Benoit Parrot
2019-09-24 16:44 ` [Patch v3 4/8] media: i2c: ov2659: fix s_stream return value Benoit Parrot
2019-09-24 16:44 ` [Patch v3 5/8] media: dt-bindings: ov2659: add powerdown/reset-gpios optional property Benoit Parrot
2019-09-27 18:40 ` Rob Herring
2019-09-24 16:44 ` [Patch v3 6/8] media: i2c: ov2659: Add powerdown/reset gpio handling Benoit Parrot
2019-09-25 9:51 ` Sakari Ailus
2019-09-25 14:37 ` Benoit Parrot [this message]
2019-09-24 16:44 ` [Patch v3 7/8] media: i2c: ov2659: Fix missing 720p register config Benoit Parrot
2019-09-24 16:44 ` [Patch v3 8/8] 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=20190925143741.25qn2wuyiwapsehr@ti.com \
--to=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 \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.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