From: Benoit Parrot <bparrot@ti.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Prabhakar Lad <prabhakar.csengg@gmail.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, Benoit Parrot <bparrot@ti.com>
Subject: [Patch v2 0/7] media: i2c: ov2659: maintenance series
Date: Thu, 19 Sep 2019 15:39:48 -0500 [thread overview]
Message-ID: <20190919203955.15125-1-bparrot@ti.com> (raw)
This patch series is a collection of patches we have been carrying for a
while.
It includes a few sensor register fixes which would cause visual
artifacts at lower resolution and also at 720p.
Also on some board the 'powerdown' and /or 'reset' pins are not tied so
we need to add support for optional gpios to handle these.
Since these camera are removable on some board we also need the driver
to actually fail when there is no hardware present so the driver is
actually removed.
Finally, we update the licensing statement to use SPDX licensing.
Changes since v1:
- Addressed review comment from Prabhakar
- Added support for reset-gpios
- Rework the power setting to use pm_runtime instead of s_power
as based on discussion with Sakari it would be the prefered method
- Added a patch to reduce the number explicit include files to the
minimum necessary instead of the previous kitchen sink approach
Benoit Parrot (7):
media: i2c: ov2659: Fix for image wrap-around in lower resolution
media: i2c: ov2659: Fix sensor detection to actually fail when device
is not present
media: i2c: ov2659: Cleanup include file list
media: dt-bindings: ov2659: add powerdown/reset-gpios optional
property
media: i2c: ov2659: Add powerdown/reset gpio handling
media: i2c: ov2659: Fix missing 720p register config
media: i2c: ov2659: Switch to SPDX Licensing
.../devicetree/bindings/media/i2c/ov2659.txt | 9 ++
drivers/media/i2c/Kconfig | 2 +-
drivers/media/i2c/ov2659.c | 129 +++++++++++++-----
3 files changed, 107 insertions(+), 33 deletions(-)
--
2.17.1
next reply other threads:[~2019-09-19 20:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-19 20:39 Benoit Parrot [this message]
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
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=20190919203955.15125-1-bparrot@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=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;
as well as URLs for NNTP newsgroup(s).