All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rui Miguel Silva <rui.silva@linaro.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Rui Miguel Silva <rui.silva@linaro.org>,
	mchehab@kernel.org, Steve Longerbeam <slongerbeam@gmail.com>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Rob Herring <robh+dt@kernel.org>,
	linux-media@vger.kernel.org, devel@driverdev.osuosl.org,
	Shawn Guo <shawnguo@kernel.org>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ryan Harkin <ryan.harkin@linaro.org>,
	linux-clk@vger.kernel.org
Subject: Re: [PATCH v6 07/13] media: dt-bindings: add bindings for i.MX7 media driver
Date: Thu, 02 Aug 2018 17:48:06 +0100	[thread overview]
Message-ID: <m38t5ou33t.fsf@linaro.org> (raw)
In-Reply-To: <20180802130027.yltizjaagt7q3vqu@paasikivi.fi.intel.com>

Hi Sakari,
Thanks for the review.

I will take this in account when preparing the v7, all your 
comments
bellow look reasonable to me.

---
Cheers,
	Rui

On Thu 02 Aug 2018 at 14:00, Sakari Ailus wrote:
> Hi Rui,
>
> On Tue, May 22, 2018 at 03:52:39PM +0100, Rui Miguel Silva 
> wrote:
>> Add bindings documentation for i.MX7 media drivers.
>> The imx7 MIPI CSI2 and imx7 CMOS Sensor Interface.
>> 
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>>  .../devicetree/bindings/media/imx7-csi.txt    | 44 ++++++++++
>>  .../bindings/media/imx7-mipi-csi2.txt         | 82 
>>  +++++++++++++++++++
>>  2 files changed, 126 insertions(+)
>>  create mode 100644 
>>  Documentation/devicetree/bindings/media/imx7-csi.txt
>>  create mode 100644 
>>  Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> 
>> diff --git 
>> a/Documentation/devicetree/bindings/media/imx7-csi.txt 
>> b/Documentation/devicetree/bindings/media/imx7-csi.txt
>> new file mode 100644
>> index 000000000000..aab4f5d72390
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/imx7-csi.txt
>> @@ -0,0 +1,44 @@
>> +Freescale i.MX7 CMOS Sensor Interface
>> +=====================================
>> +
>> +csi node
>> +--------
>> +
>> +This is device node for the CMOS Sensor Interface (CSI) which 
>> enables the chip
>> +to connect directly to external CMOS image sensors.
>> +
>> +Required properties:
>> +
>> +- compatible    : "fsl,imx7-csi";
>> +- reg           : base address and length of the register set 
>> for the device;
>> +- interrupts    : should contain CSI interrupt;
>> +- clocks        : list of clock specifiers, see
>> + 
>> Documentation/devicetree/bindings/clock/clock-bindings.txt for 
>> details;
>> +- clock-names   : must contain "axi", "mclk" and "dcic" 
>> entries, matching
>> +                 entries in the clock property;
>> +
>> +The device node should contain one 'port' child node with one 
>> child 'endpoint'
>
> "should" or "shall"?
>
>> +node, according to the bindings defined in 
>> Documentation/devicetree/bindings/
>> +media/video-interfaces.txt. In the following example a remote 
>> endpoint is a
>
> I wouldn't split the path as it breaks copy-paste; up to you.
>
>> +video multiplexer.
>> +
>> +example:
>> +
>> +                csi: csi@30710000 {
>> +                        #address-cells = <1>;
>> +                        #size-cells = <0>;
>> +
>> +                        compatible = "fsl,imx7-csi";
>> +                        reg = <0x30710000 0x10000>;
>> +                        interrupts = <GIC_SPI 7 
>> IRQ_TYPE_LEVEL_HIGH>;
>> +                        clocks = <&clks IMX7D_CLK_DUMMY>,
>> +                                        <&clks 
>> IMX7D_CSI_MCLK_ROOT_CLK>,
>> +                                        <&clks 
>> IMX7D_CLK_DUMMY>;
>> +                        clock-names = "axi", "mclk", "dcic";
>> +
>> +                        port {
>> +                                csi_from_csi_mux: endpoint {
>> +                                        remote-endpoint = 
>> <&csi_mux_to_csi>;
>> +                                };
>> +                        };
>> +                };
>> diff --git 
>> a/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt 
>> b/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> new file mode 100644
>> index 000000000000..7c5f20863724
>> --- /dev/null
>> +++ 
>> b/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> @@ -0,0 +1,82 @@
>> +Freescale i.MX7 Mipi CSI2
>> +=========================
>> +
>> +mipi_csi2 node
>> +--------------
>> +
>> +This is the device node for the MIPI CSI-2 receiver core in 
>> i.MX7 SoC. It is
>> +compatible with previous version of Samsung D-phy.
>> +
>> +Required properties:
>> +
>> +- compatible    : "fsl,imx7-mipi-csi2";
>> +- reg           : base address and length of the register set 
>> for the device;
>> +- interrupts    : should contain MIPI CSIS interrupt;
>> +- clocks        : list of clock specifiers, see
>> + 
>> Documentation/devicetree/bindings/clock/clock-bindings.txt for 
>> details;
>> +- clock-names   : must contain "pclk", "wrap" and "phy" 
>> entries, matching
>> +                  entries in the clock property;
>> +- power-domains : a phandle to the power domain, see
>> + 
>> Documentation/devicetree/bindings/power/power_domain.txt for 
>> details.
>> +- reset-names   : should include following entry "mrst";
>> +- resets        : a list of phandle, should contain reset 
>> entry of
>> +                  reset-names;
>> +- phy-supply    : from the generic phy bindings, a phandle to 
>> a regulator that
>> +	          provides power to MIPI CSIS core;
>> +
>> +Optional properties:
>> +
>> +- clock-frequency : The IP's main (system bus) clock frequency 
>> in Hz, default
>> +		    value when this property is not specified is 
>> 166 MHz;
>> +- fsl,csis-hs-settle : differential receiver (HS-RX) settle 
>> time;
>> +
>> +port node
>> +---------
>> +
>> +- reg		  : (required) can take the values 0 or 1, 
>> where 0 is the
>> +                     related sink port and port 1 should be 
>> the source one;
>
> Should and is -> shall?
>
> I think you should also elaborate whether or not the port (as 
> well as the
> endpoint) nodes themselves are mandatory.
>
>> +
>> +endpoint node
>> +-------------
>> +
>> +- data-lanes    : (required) an array specifying active 
>> physical MIPI-CSI2
>> +		    data input lanes and their mapping to logical 
>> lanes; the
>> +		    array's content is unused, only its length is 
>> meaningful;
>
> If this is for port 0 only, please document that. Which values 
> (length) are
> allowed?
>
>> +
>> +example:
>> +
>> +        mipi_csi: mipi-csi@30750000 {
>> +                #address-cells = <1>;
>> +                #size-cells = <0>;
>> +
>> +                compatible = "fsl,imx7-mipi-csi2";
>> +                reg = <0x30750000 0x10000>;
>> +                interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
>> +                clocks = <&clks IMX7D_IPG_ROOT_CLK>,
>> +                                <&clks 
>> IMX7D_MIPI_CSI_ROOT_CLK>,
>> +                                <&clks 
>> IMX7D_MIPI_DPHY_ROOT_CLK>;
>> +                clock-names = "pclk", "wrap", "phy";
>> +                clock-frequency = <166000000>;
>> +                power-domains = <&pgc_mipi_phy>;
>> +                phy-supply = <&reg_1p0d>;
>> +                resets = <&src IMX7_RESET_MIPI_PHY_MRST>;
>> +                reset-names = "mrst";
>> +                fsl,csis-hs-settle = <3>;
>> +
>> +                port@0 {
>> +                        reg = <0>;
>> +
>> +                        mipi_from_sensor: endpoint {
>> +                                remote-endpoint = 
>> <&ov2680_to_mipi>;
>> +                                data-lanes = <1>;
>> +                        };
>> +                };
>> +
>> +                port@1 {
>> +                        reg = <1>;
>> +
>> +                        mipi_vc0_to_csi_mux: endpoint {
>> +                                remote-endpoint = 
>> <&csi_mux_from_mipi_vc0>;
>> +                        };
>> +                };
>> +        };


WARNING: multiple messages have this Message-ID (diff)
From: Rui Miguel Silva <rui.silva@linaro.org>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Ryan Harkin <ryan.harkin@linaro.org>,
	Rob Herring <robh+dt@kernel.org>,
	Rui Miguel Silva <rui.silva@linaro.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Steve Longerbeam <slongerbeam@gmail.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	mchehab@kernel.org, Shawn Guo <shawnguo@kernel.org>,
	linux-clk@vger.kernel.org, linux-media@vger.kernel.org
Subject: Re: [PATCH v6 07/13] media: dt-bindings: add bindings for i.MX7 media driver
Date: Thu, 02 Aug 2018 17:48:06 +0100	[thread overview]
Message-ID: <m38t5ou33t.fsf@linaro.org> (raw)
In-Reply-To: <20180802130027.yltizjaagt7q3vqu@paasikivi.fi.intel.com>

Hi Sakari,
Thanks for the review.

I will take this in account when preparing the v7, all your 
comments
bellow look reasonable to me.

---
Cheers,
	Rui

On Thu 02 Aug 2018 at 14:00, Sakari Ailus wrote:
> Hi Rui,
>
> On Tue, May 22, 2018 at 03:52:39PM +0100, Rui Miguel Silva 
> wrote:
>> Add bindings documentation for i.MX7 media drivers.
>> The imx7 MIPI CSI2 and imx7 CMOS Sensor Interface.
>> 
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>>  .../devicetree/bindings/media/imx7-csi.txt    | 44 ++++++++++
>>  .../bindings/media/imx7-mipi-csi2.txt         | 82 
>>  +++++++++++++++++++
>>  2 files changed, 126 insertions(+)
>>  create mode 100644 
>>  Documentation/devicetree/bindings/media/imx7-csi.txt
>>  create mode 100644 
>>  Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> 
>> diff --git 
>> a/Documentation/devicetree/bindings/media/imx7-csi.txt 
>> b/Documentation/devicetree/bindings/media/imx7-csi.txt
>> new file mode 100644
>> index 000000000000..aab4f5d72390
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/media/imx7-csi.txt
>> @@ -0,0 +1,44 @@
>> +Freescale i.MX7 CMOS Sensor Interface
>> +=====================================
>> +
>> +csi node
>> +--------
>> +
>> +This is device node for the CMOS Sensor Interface (CSI) which 
>> enables the chip
>> +to connect directly to external CMOS image sensors.
>> +
>> +Required properties:
>> +
>> +- compatible    : "fsl,imx7-csi";
>> +- reg           : base address and length of the register set 
>> for the device;
>> +- interrupts    : should contain CSI interrupt;
>> +- clocks        : list of clock specifiers, see
>> + 
>> Documentation/devicetree/bindings/clock/clock-bindings.txt for 
>> details;
>> +- clock-names   : must contain "axi", "mclk" and "dcic" 
>> entries, matching
>> +                 entries in the clock property;
>> +
>> +The device node should contain one 'port' child node with one 
>> child 'endpoint'
>
> "should" or "shall"?
>
>> +node, according to the bindings defined in 
>> Documentation/devicetree/bindings/
>> +media/video-interfaces.txt. In the following example a remote 
>> endpoint is a
>
> I wouldn't split the path as it breaks copy-paste; up to you.
>
>> +video multiplexer.
>> +
>> +example:
>> +
>> +                csi: csi@30710000 {
>> +                        #address-cells = <1>;
>> +                        #size-cells = <0>;
>> +
>> +                        compatible = "fsl,imx7-csi";
>> +                        reg = <0x30710000 0x10000>;
>> +                        interrupts = <GIC_SPI 7 
>> IRQ_TYPE_LEVEL_HIGH>;
>> +                        clocks = <&clks IMX7D_CLK_DUMMY>,
>> +                                        <&clks 
>> IMX7D_CSI_MCLK_ROOT_CLK>,
>> +                                        <&clks 
>> IMX7D_CLK_DUMMY>;
>> +                        clock-names = "axi", "mclk", "dcic";
>> +
>> +                        port {
>> +                                csi_from_csi_mux: endpoint {
>> +                                        remote-endpoint = 
>> <&csi_mux_to_csi>;
>> +                                };
>> +                        };
>> +                };
>> diff --git 
>> a/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt 
>> b/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> new file mode 100644
>> index 000000000000..7c5f20863724
>> --- /dev/null
>> +++ 
>> b/Documentation/devicetree/bindings/media/imx7-mipi-csi2.txt
>> @@ -0,0 +1,82 @@
>> +Freescale i.MX7 Mipi CSI2
>> +=========================
>> +
>> +mipi_csi2 node
>> +--------------
>> +
>> +This is the device node for the MIPI CSI-2 receiver core in 
>> i.MX7 SoC. It is
>> +compatible with previous version of Samsung D-phy.
>> +
>> +Required properties:
>> +
>> +- compatible    : "fsl,imx7-mipi-csi2";
>> +- reg           : base address and length of the register set 
>> for the device;
>> +- interrupts    : should contain MIPI CSIS interrupt;
>> +- clocks        : list of clock specifiers, see
>> + 
>> Documentation/devicetree/bindings/clock/clock-bindings.txt for 
>> details;
>> +- clock-names   : must contain "pclk", "wrap" and "phy" 
>> entries, matching
>> +                  entries in the clock property;
>> +- power-domains : a phandle to the power domain, see
>> + 
>> Documentation/devicetree/bindings/power/power_domain.txt for 
>> details.
>> +- reset-names   : should include following entry "mrst";
>> +- resets        : a list of phandle, should contain reset 
>> entry of
>> +                  reset-names;
>> +- phy-supply    : from the generic phy bindings, a phandle to 
>> a regulator that
>> +	          provides power to MIPI CSIS core;
>> +
>> +Optional properties:
>> +
>> +- clock-frequency : The IP's main (system bus) clock frequency 
>> in Hz, default
>> +		    value when this property is not specified is 
>> 166 MHz;
>> +- fsl,csis-hs-settle : differential receiver (HS-RX) settle 
>> time;
>> +
>> +port node
>> +---------
>> +
>> +- reg		  : (required) can take the values 0 or 1, 
>> where 0 is the
>> +                     related sink port and port 1 should be 
>> the source one;
>
> Should and is -> shall?
>
> I think you should also elaborate whether or not the port (as 
> well as the
> endpoint) nodes themselves are mandatory.
>
>> +
>> +endpoint node
>> +-------------
>> +
>> +- data-lanes    : (required) an array specifying active 
>> physical MIPI-CSI2
>> +		    data input lanes and their mapping to logical 
>> lanes; the
>> +		    array's content is unused, only its length is 
>> meaningful;
>
> If this is for port 0 only, please document that. Which values 
> (length) are
> allowed?
>
>> +
>> +example:
>> +
>> +        mipi_csi: mipi-csi@30750000 {
>> +                #address-cells = <1>;
>> +                #size-cells = <0>;
>> +
>> +                compatible = "fsl,imx7-mipi-csi2";
>> +                reg = <0x30750000 0x10000>;
>> +                interrupts = <GIC_SPI 25 IRQ_TYPE_LEVEL_HIGH>;
>> +                clocks = <&clks IMX7D_IPG_ROOT_CLK>,
>> +                                <&clks 
>> IMX7D_MIPI_CSI_ROOT_CLK>,
>> +                                <&clks 
>> IMX7D_MIPI_DPHY_ROOT_CLK>;
>> +                clock-names = "pclk", "wrap", "phy";
>> +                clock-frequency = <166000000>;
>> +                power-domains = <&pgc_mipi_phy>;
>> +                phy-supply = <&reg_1p0d>;
>> +                resets = <&src IMX7_RESET_MIPI_PHY_MRST>;
>> +                reset-names = "mrst";
>> +                fsl,csis-hs-settle = <3>;
>> +
>> +                port@0 {
>> +                        reg = <0>;
>> +
>> +                        mipi_from_sensor: endpoint {
>> +                                remote-endpoint = 
>> <&ov2680_to_mipi>;
>> +                                data-lanes = <1>;
>> +                        };
>> +                };
>> +
>> +                port@1 {
>> +                        reg = <1>;
>> +
>> +                        mipi_vc0_to_csi_mux: endpoint {
>> +                                remote-endpoint = 
>> <&csi_mux_from_mipi_vc0>;
>> +                        };
>> +                };
>> +        };

  reply	other threads:[~2018-08-02 18:40 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-22 14:52 [PATCH v6 00/13] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2018-05-22 14:52 ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 01/13] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 02/13] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 03/13] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 04/13] clk: imx7d: fix mipi dphy div parent Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-06-01 19:41   ` Stephen Boyd
2018-06-01 19:41     ` Stephen Boyd
2018-06-01 19:41     ` Stephen Boyd
2018-05-22 14:52 ` [PATCH v6 05/13] clk: imx7d: reset parent for mipi csi root Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-06-01 19:41   ` Stephen Boyd
2018-06-01 19:41     ` Stephen Boyd
2018-06-01 19:41     ` Stephen Boyd
2018-05-22 14:52 ` [PATCH v6 06/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 07/13] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 16:10   ` Rob Herring
2018-05-22 16:10     ` Rob Herring
2018-08-02 13:00   ` Sakari Ailus
2018-08-02 13:00     ` Sakari Ailus
2018-08-02 16:48     ` Rui Miguel Silva [this message]
2018-08-02 16:48       ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 08/13] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 09/13] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 10/13] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 11/13] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 12/13] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-05-22 14:52 ` [PATCH v6 13/13] media: staging/imx: add i.MX7 entries to TODO file Rui Miguel Silva
2018-05-22 14:52   ` Rui Miguel Silva
2018-08-02 12:37 ` [PATCH v6 00/13] media: staging/imx7: add i.MX7 media driver Hans Verkuil
2018-08-02 12:37   ` Hans Verkuil
2018-08-02 16:45   ` Rui Miguel Silva
2018-08-02 16:45     ` Rui Miguel Silva
2018-08-03 11:00     ` Hans Verkuil
2018-08-03 11:00       ` Hans Verkuil

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=m38t5ou33t.fsf@linaro.org \
    --to=rui.silva@linaro.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=ryan.harkin@linaro.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=shawnguo@kernel.org \
    --cc=slongerbeam@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.