From: Wenyou Yang <wenyou.yang@microchip.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@microchip.com>,
devicetree@vger.kernel.org, Sakari Ailus <sakari.ailus@iki.fi>,
Jonathan Corbet <corbet@lwn.net>,
Hans Verkuil <hverkuil@xs4all.nl>,
linux-arm-kernel@lists.infradead.org,
Linux Media Mailing List <linux-media@vger.kernel.org>,
Wenyou Yang <wenyou.yang@microchip.com>
Subject: [PATCH v6 0/2] media: ov7740: Add a V4L2 sensor-level driver
Date: Mon, 4 Dec 2017 14:58:56 +0800 [thread overview]
Message-ID: <20171204065858.3138-1-wenyou.yang@microchip.com> (raw)
Add a Video4Linux2 sensor-level driver for the OmniVision OV7740
VGA camera image sensor.
Changes in v6:
- Remove unnecessary #include <linux/init>.
- Remove unnecessary comments and extra newline.
- Add const for some structures.
- Add the check of the return value from regmap_write().
- Simplify the calling of __v4l2_ctrl_handler_setup().
- Add the default format initialization function.
- Integrate the set_power() and enable/disable the clock into
one function.
Changes in v5:
- Squash the driver and MAINTAINERS entry patches to one.
- Precede the driver patch with the bindings patch.
Changes in v4:
- Assign 'val' a initial value to avoid warning: 'val' may be
used uninitialized.
- Rename REG_REG15 to avoid warning: "REG_REG15" redefined.
Changes in v3:
- Explicitly document the "remote-endpoint" property.
- Put the MAINTAINERS change to a separate patch.
Changes in v2:
- Split off the bindings into a separate patch.
- Add a new entry to the MAINTAINERS file.
Wenyou Yang (2):
media: ov7740: Document device tree bindings
media: i2c: Add the ov7740 image sensor driver
.../devicetree/bindings/media/i2c/ov7740.txt | 47 +
MAINTAINERS | 8 +
drivers/media/i2c/Kconfig | 8 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov7740.c | 1226 ++++++++++++++++++++
5 files changed, 1290 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov7740.txt
create mode 100644 drivers/media/i2c/ov7740.c
--
2.15.0
next reply other threads:[~2017-12-04 6:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 6:58 Wenyou Yang [this message]
[not found] ` <20171204065858.3138-1-wenyou.yang-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2017-12-04 6:58 ` [PATCH v6 1/2] media: ov7740: Document device tree bindings Wenyou Yang
[not found] ` <20171204065858.3138-2-wenyou.yang-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2017-12-04 20:24 ` Rob Herring
2017-12-05 0:48 ` Yang, Wenyou
2017-12-04 6:58 ` [PATCH v6 2/2] media: i2c: Add the ov7740 image sensor driver Wenyou Yang
[not found] ` <20171204065858.3138-3-wenyou.yang-UWL1GkI3JZL3oGB3hsPCZA@public.gmane.org>
2017-12-05 10:45 ` Sakari Ailus
[not found] ` <20171205104549.aoturlmm3s6net37-S+BSfZ9RZZmRSg0ZkenSGLdO1Tsj/99ntUK59QYPAWc@public.gmane.org>
2017-12-06 5:38 ` Yang, Wenyou
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=20171204065858.3138-1-wenyou.yang@microchip.com \
--to=wenyou.yang@microchip.com \
--cc=corbet@lwn.net \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@s-opensource.com \
--cc=nicolas.ferre@microchip.com \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@iki.fi \
/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).