From: <dongchun.zhu@mediatek.com>
To: <mchehab@kernel.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <sakari.ailus@linux.intel.com>,
<drinkcat@chromium.org>, <tfiga@chromium.org>,
<matthias.bgg@gmail.com>, <bingbu.cao@intel.com>
Cc: <srv_heupstream@mediatek.com>,
<linux-mediatek@lists.infradead.org>,
<linux-arm-kernel@lists.infradead.org>, <sj.huang@mediatek.com>,
<linux-media@vger.kernel.org>, <devicetree@vger.kernel.org>,
<louis.kuo@mediatek.com>, <shengnan.wang@mediatek.com>,
<dongchun.zhu@mediatek.com>
Subject: [V3, 0/2] media: Add support for OV02A10 sensor
Date: Mon, 19 Aug 2019 11:43:29 +0800 [thread overview]
Message-ID: <20190819034331.13098-1-dongchun.zhu@mediatek.com> (raw)
From: Dongchun Zhu <dongchun.zhu@mediatek.com>
Hello,
This patch adds driver and bindings for Omnivision's OV02A10 2 megapixel CMOS 1/5" sensor,
which has a single MIPI lane interface and output format of 10-bit Raw.
The driver is implemented wth V4L2 framework.
1. Async registered as a V4L2 I2C sub-device.
2. A media entity that can provide several source pads and sink pads to link with other device like Seninf, ISP one after another
to create a default overall camera topology, image frame or meta-data from sensor can flow through particular path to output
preview or capture image or 3A info.
Changes of v3 are mainly addressing comments from Rob, Sakari, Bingbu.
- Fix coding style errors in dt-bindings
- Use macro flag to describle basic line 1224 when updating v-blanking
- Remove unnecessary debug log in driver
Mainly changes of v2 are addressing the comments from Nicolas, Bingbu, Sakari, Rob,
including,
- Put dt binding before driver in series
- Add MAINTAINERS entries
- Squash the MAINTAINERS entry and Kconfig to driver patch
- Add rotation support for driver
- Fix other reviewed issues in v1
Dongchun Zhu (2):
media: dt-bindings: media: i2c: Add bindings for OV02A10
media: i2c: Add Omnivision OV02A10 camera sensor driver
.../devicetree/bindings/media/i2c/ov02a10.txt | 54 ++
MAINTAINERS | 8 +
drivers/media/i2c/Kconfig | 11 +
drivers/media/i2c/Makefile | 1 +
drivers/media/i2c/ov02a10.c | 1018 ++++++++++++++++++++
5 files changed, 1092 insertions(+)
create mode 100644 Documentation/devicetree/bindings/media/i2c/ov02a10.txt
create mode 100644 drivers/media/i2c/ov02a10.c
--
2.9.2
next reply other threads:[~2019-08-19 3:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-19 3:43 dongchun.zhu [this message]
2019-08-19 3:43 ` [V3, 1/2] media: dt-bindings: media: i2c: Add bindings for OV02A10 dongchun.zhu
2019-08-27 16:48 ` Rob Herring
2019-08-19 3:43 ` [V3, 2/2] media: i2c: Add Omnivision OV02A10 camera sensor driver dongchun.zhu
2019-08-19 8:30 ` Sakari Ailus
2019-09-05 9:41 ` Dongchun Zhu
2019-09-05 10:45 ` Sakari Ailus
2019-09-05 10:53 ` Tomasz Figa
2019-09-05 16:05 ` Sakari Ailus
2019-09-05 22:58 ` Nicolas Boichat
2019-09-06 1:33 ` Dongchun Zhu
2019-09-07 3:51 ` Tomasz Figa
2019-08-21 10:30 ` Tomasz Figa
2019-08-21 11:05 ` Sakari Ailus
2019-08-26 6:54 ` Tomasz Figa
2019-09-05 15:54 ` Dongchun Zhu
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=20190819034331.13098-1-dongchun.zhu@mediatek.com \
--to=dongchun.zhu@mediatek.com \
--cc=bingbu.cao@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=louis.kuo@mediatek.com \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=shengnan.wang@mediatek.com \
--cc=sj.huang@mediatek.com \
--cc=srv_heupstream@mediatek.com \
--cc=tfiga@chromium.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).