Add support for OV5647 sensor
Subsystems (4)
cover Add support for OV5647 sensor
Hello,
This RFC patch adds support for the Omnivision OV5647 sensor.
At the moment it only supports 640x480 in Raw 8.
Ramiro Oliveira (2):
Add OV5647 device tree documentation
Add support for Omnivision OV5647
.../devicetree/bindings/media/i2c/ov5647.txt | 29 + MAINTAINERS | 7 + drivers/media/i2c/Kconfig | 11 + drivers/media/i2c/Makefile | 1 + drivers/media/i2c/ov5647.c | 891 +++++++++++++++++++++ 5 files changed, 939 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt create mode 100644 drivers/media/i2c/ov5647.c
Signature · 1 line
2.8.1
RFC 1/2 Add OV5647 device tree documentation
Signed-off-by roliveir <[email protected]>
--- .../devicetree/bindings/media/i2c/ov5647.txt | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt
Documentation/devicetree/bindings/media/i2c/ov5647.txt new file +29 -0
@@ -0,0 +1,29 @@ +Omnivision OV5657 raw image sensor +--------------------------------- + +OV5657 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces +and CCI (I2C compatible) control bus. + +Required properties: + +- compatible : "ov5647"; +- reg : I2C slave address of the sensor; +- clocks : should contain list of phandle and clock specifier pairs + according to common clock bindings for the clocks described + in the clock-names property; +- clock-names : should contain "extclk" entry for the sensor's EXTCLK clock; + +Optional properties: + +- clock-frequency : the frequency at which the "extclk" clock should be + configured to operate, in Hz; if this property is not + specified default 27 MHz value will be used. + +The common video interfaces bindings (see video-interfaces.txt) should be +used to specify link to the image data receiver. The OV5657 device +node should contain one 'port' child node with an 'endpoint' subnode. + +Following properties are valid for the endpoint node: + +- data-lanes : (optional) specifies MIPI CSI-2 data lanes as covered in + video-interfaces.txt. The sensor supports only two data lanes.
Signature · 1 line
2.8.1
Rob Herring
maintainerRe: [RFC 1/2] Add OV5647 device tree documentation
Documentation/devicetree/bindings/media/i2c/ov5647.txt line 1
Quoted 13 lines · roliveir
Signed-off-by roliveir <[email protected]>--- .../devicetree/bindings/media/i2c/ov5647.txt | 29 ++++++++++++++++++++++ 1 file changed, 29 insertions(+) create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txtDocumentation/devicetree/bindings/media/i2c/ov5647.txt new file +1
-0@@ -0,0 +1,29 @@ +Omnivision OV5657 raw image sensor
5657?
Documentation/devicetree/bindings/media/i2c/ov5647.txt line 13
Quoted 12 lines
Documentation/devicetree/bindings/media/i2c/ov5647.txt new file +12
-0+--------------------------------- + +OV5657 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces +and CCI (I2C compatible) control bus. + +Required properties: + +- compatible : "ov5647"; +- reg : I2C slave address of the sensor; +- clocks : should contain list of phandle and clock specifier pairs + according to common clock bindings for the clocks described + in the clock-names property;
Need to state how many clocks and the order.
Quoted 20 lines
Documentation/devicetree/bindings/media/i2c/ov5647.txt new file +16
-0+- clock-names : should contain "extclk" entry for the sensor's EXTCLK clock; + +Optional properties: + +- clock-frequency : the frequency at which the "extclk" clock should be + configured to operate, in Hz; if this property is not + specified default 27 MHz value will be used. + +The common video interfaces bindings (see video-interfaces.txt) should be +used to specify link to the image data receiver. The OV5657 device +node should contain one 'port' child node with an 'endpoint' subnode. + +Following properties are valid for the endpoint node: + +- data-lanes : (optional) specifies MIPI CSI-2 data lanes as covered in + video-interfaces.txt. The sensor supports only two data lanes.Signature · 1 line
2.8.1
RFC 2/2 Add support for Omnivision OV5647
In reply to roliveirSigned-off-by roliveir <[email protected]>
--- MAINTAINERS | 7 + drivers/media/i2c/Kconfig | 11 + drivers/media/i2c/Makefile | 1 + drivers/media/i2c/ov5647.c | 891 +++++++++++++++++++++++++++++++++++++++++++++ 4 files changed, 910 insertions(+) create mode 100644 drivers/media/i2c/ov5647.c
MAINTAINERS +7 -0
@@ -8106,6 +8106,13 @@ M: Harald Welte <[email protected]> S: Maintained F: drivers/char/pcmcia/cm4040_cs.* +OMNIVISION OV5647 SENSOR DRIVER +M: Ramiro Oliveira <[email protected]> +L: [email protected] +T: git git://linuxtv.org/media_tree.git +S: Maintained +F: drivers/media/i2c/ov5647.c + OMNIVISION OV7670 SENSOR DRIVER M: Jonathan Corbet <[email protected]> L: [email protected]
drivers/media/i2c/Kconfig +11 -0
@@ -500,6 +500,17 @@ config VIDEO_OV2659 To compile this driver as a module, choose M here: the module will be called ov2659. +config VIDEO_OV5647 + tristate "OmniVision OV5647 sensor support" + depends on I2C && VIDEO_V4L2 + depends on MEDIA_CAMERA_SUPPORT + ---help--- + This is a Video4Linux2 sensor-level driver for the OmniVision + OV5647 camera. + + To compile this driver as a module, choose M here: the + module will be called ov5647. + config VIDEO_OV7640 tristate "OmniVision OV7640 sensor support" depends on I2C && VIDEO_V4L2
drivers/media/i2c/Makefile +1 -0
@@ -80,3 +80,4 @@ obj-$(CONFIG_VIDEO_IR_I2C) += ir-kbd-i2c.o obj-$(CONFIG_VIDEO_ML86V7667) += ml86v7667.o obj-$(CONFIG_VIDEO_OV2659) += ov2659.o obj-$(CONFIG_VIDEO_TC358743) += tc358743.o +obj-$(CONFIG_VIDEO_OV5647) += ov5647.o
drivers/media/i2c/ov5647.c new file +891 -0
891 lines not on this page · raw message
Signature · 1 line
2.8.1