Re: [PATCH v3 1/2] Add OV5647 device tree documentation
On 10/18/2016 2:14 PM, Rob Herring wrote: > On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: >> Signed-off-by: Ramiro Oliveira>> --- >> .../devicetree/bindings/media/i2c/ov5647.txt | 19 >> +++ >> 1 file changed, 19 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt >> >> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> b/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> new file mode 100644 >> index 000..4c91b3b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> @@ -0,0 +1,19 @@ >> +Omnivision OV5647 raw image sensor >> +- >> + >> +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces >> +and CCI (I2C compatible) control bus. >> + >> +Required properties: >> + >> +- compatible: "ovti,ov5647"; >> +- reg : I2C slave address of the sensor; >> + >> +The common video interfaces bindings (see video-interfaces.txt) should be >> +used to specify link to the image data receiver. The OV5647 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. > What's the default if not present? Since the sensor only supports 2 data lanes, this information will not be used, even if it is available in the DT. So the default will be 2. > >> -- >> 2.9.3 >> >>
Re: [PATCH v3 1/2] Add OV5647 device tree documentation
On 10/18/2016 2:14 PM, Rob Herring wrote: > On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: >> Signed-off-by: Ramiro Oliveira >> --- >> .../devicetree/bindings/media/i2c/ov5647.txt | 19 >> +++ >> 1 file changed, 19 insertions(+) >> create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt >> >> diff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> b/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> new file mode 100644 >> index 000..4c91b3b >> --- /dev/null >> +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt >> @@ -0,0 +1,19 @@ >> +Omnivision OV5647 raw image sensor >> +- >> + >> +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces >> +and CCI (I2C compatible) control bus. >> + >> +Required properties: >> + >> +- compatible: "ovti,ov5647"; >> +- reg : I2C slave address of the sensor; >> + >> +The common video interfaces bindings (see video-interfaces.txt) should be >> +used to specify link to the image data receiver. The OV5647 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. > What's the default if not present? Since the sensor only supports 2 data lanes, this information will not be used, even if it is available in the DT. So the default will be 2. > >> -- >> 2.9.3 >> >>
Re: [PATCH v3 1/2] Add OV5647 device tree documentation
On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: > Signed-off-by: Ramiro Oliveira> --- > .../devicetree/bindings/media/i2c/ov5647.txt | 19 > +++ > 1 file changed, 19 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt > > diff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt > b/Documentation/devicetree/bindings/media/i2c/ov5647.txt > new file mode 100644 > index 000..4c91b3b > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt > @@ -0,0 +1,19 @@ > +Omnivision OV5647 raw image sensor > +- > + > +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces > +and CCI (I2C compatible) control bus. > + > +Required properties: > + > +- compatible : "ovti,ov5647"; > +- reg: I2C slave address of the sensor; > + > +The common video interfaces bindings (see video-interfaces.txt) should be > +used to specify link to the image data receiver. The OV5647 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. What's the default if not present? > -- > 2.9.3 > >
Re: [PATCH v3 1/2] Add OV5647 device tree documentation
On Wed, Oct 12, 2016 at 05:02:21PM +0100, Ramiro Oliveira wrote: > Signed-off-by: Ramiro Oliveira > --- > .../devicetree/bindings/media/i2c/ov5647.txt | 19 > +++ > 1 file changed, 19 insertions(+) > create mode 100644 Documentation/devicetree/bindings/media/i2c/ov5647.txt > > diff --git a/Documentation/devicetree/bindings/media/i2c/ov5647.txt > b/Documentation/devicetree/bindings/media/i2c/ov5647.txt > new file mode 100644 > index 000..4c91b3b > --- /dev/null > +++ b/Documentation/devicetree/bindings/media/i2c/ov5647.txt > @@ -0,0 +1,19 @@ > +Omnivision OV5647 raw image sensor > +- > + > +OV5647 is a raw image sensor with MIPI CSI-2 and CCP2 image data interfaces > +and CCI (I2C compatible) control bus. > + > +Required properties: > + > +- compatible : "ovti,ov5647"; > +- reg: I2C slave address of the sensor; > + > +The common video interfaces bindings (see video-interfaces.txt) should be > +used to specify link to the image data receiver. The OV5647 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. What's the default if not present? > -- > 2.9.3 > >