From: Todor Tomov <todor.tomov@linaro.org>
To: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
devicetree@vger.kernel.org, mchehab@osg.samsung.com,
hverkuil@xs4all.nl, geert@linux-m68k.org, matrandg@cisco.com,
linux-media@vger.kernel.org
Cc: laurent.pinchart@ideasonboard.com, Todor Tomov <todor.tomov@linaro.org>
Subject: [PATCH v2 0/2] OV5645 camera sensor driver
Date: Wed, 18 May 2016 14:50:06 +0300 [thread overview]
Message-ID: <1463572208-8826-1-git-send-email-todor.tomov@linaro.org> (raw)
This is second version of the OV5645 camera sensor driver patchset.
Changes from version 1 include:
- patch split to dt binding doc patch and driver patch;
- changes in power on/off logic - s_power is now not called on
open/close;
- using assigned-clock-rates in dt for setting camera external
clock rate;
- correct api for gpio handling;
- return values checks;
- style fixes.
Todor Tomov (2):
[media] media: i2c/ov5645: add the device tree binding document
media: Add a driver for the ov5645 camera sensor.
.../devicetree/bindings/media/i2c/ov5645.txt | 56 +
drivers/media/i2c/Kconfig | 11 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov5645.c | 1425 ++++++++++++++++++++
4 files changed, 1493 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5645.txt
create mode 100644 drivers/media/i2c/ov5645.c
--
1.9.1
next reply other threads:[~2016-05-18 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-18 11:50 Todor Tomov [this message]
2016-05-18 11:50 ` [PATCH v2 1/2] [media] media: i2c/ov5645: add the device tree binding document Todor Tomov
2016-05-18 23:16 ` Rob Herring
2016-05-19 8:14 ` Todor Tomov
2016-05-20 0:16 ` Rob Herring
2016-05-20 8:20 ` Todor Tomov
2016-05-18 11:50 ` [PATCH v2 2/2] media: Add a driver for the ov5645 camera sensor Todor Tomov
2016-05-20 15:20 ` Stanimir Varbanov
2016-05-27 11:59 ` Todor Tomov
2016-05-23 10:36 ` Hans Verkuil
2016-05-26 8:55 ` Todor Tomov
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=1463572208-8826-1-git-send-email-todor.tomov@linaro.org \
--to=todor.tomov@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=geert@linux-m68k.org \
--cc=hverkuil@xs4all.nl \
--cc=ijc+devicetree@hellion.org.uk \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=matrandg@cisco.com \
--cc=mchehab@osg.samsung.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
/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).