From: <dongchun.zhu@mediatek.com>
To: mchehab@kernel.org, andriy.shevchenko@linux.intel.com,
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: devicetree@vger.kernel.org, srv_heupstream@mediatek.com,
shengnan.wang@mediatek.com, sj.huang@mediatek.com,
linux-mediatek@lists.infradead.org, dongchun.zhu@mediatek.com,
louis.kuo@mediatek.com, linux-arm-kernel@lists.infradead.org,
linux-media@vger.kernel.org
Subject: [V4, 0/2] media: i2c: Add support for OV02A10 sensor
Date: Sat, 7 Sep 2019 17:27:26 +0800 [thread overview]
Message-ID: <20190907092728.23897-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 v4 mainly address the comments from Sakari, Rob, Tomasz.
- Remove data-lanes property in DT
- Add link frequencies in DT to match the expect value that driver requires
- Omit open callback as int_cfg is implemented
- Use i2c_smbus_write_byte_data/i2c_smbus_read_byte_data instead of customed APIs
- Use do_div to calculate pixel rate
- Use usleep_range directly for shoter sleep case
- Re-adjust sensor power up/off sequence
- Re-set pd/rst GPIO inverter property according to the datasheet
- Refine set_exposure/set_gain/set_vblanking/set_test_pattern functions
- Fix other reviewed issues in v3
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 | 1062 ++++++++++++++++++++
5 files changed, 1136 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-09-07 9:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 9:27 dongchun.zhu [this message]
2019-09-07 9:27 ` [V4, 1/2] media: dt-bindings: media: i2c: Add bindings for OV02A10 dongchun.zhu
2019-09-09 6:46 ` Sakari Ailus
2019-09-09 9:45 ` Andy Shevchenko
2019-09-09 9:57 ` Sakari Ailus
2019-09-09 10:11 ` Andy Shevchenko
2019-09-07 9:27 ` [V4, 2/2] media: i2c: Add Omnivision OV02A10 camera sensor driver dongchun.zhu
2019-09-08 2:00 ` kbuild test robot
2019-09-08 2:31 ` kbuild test robot
2019-09-08 2:31 ` [PATCH] media: i2c: fix semicolon.cocci warnings kbuild test robot
2019-09-09 6:55 ` [V4, 2/2] media: i2c: Add Omnivision OV02A10 camera sensor driver Sakari Ailus
2019-11-04 3:30 ` 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=20190907092728.23897-1-dongchun.zhu@mediatek.com \
--to=dongchun.zhu@mediatek.com \
--cc=andriy.shevchenko@linux.intel.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