public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Luis Oliveira <Luis.Oliveira@synopsys.com>
Cc: linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
	Joao.Pinto@synopsys.com, festevam@gmail.com,
	Luis Oliveira <luis.oliveira@synopsys.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Hans Verkuil <hans.verkuil@cisco.com>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>,
	Arnd Bergmann <arnd@arndb.de>, Jacob Chen <jacob-chen@iotwrt.com>,
	Neil Armstrong <narmstrong@baylibre.com>,
	Keiichi Watanabe <keiichiw@chromium.org>,
	Kate Stewart <kstewart@linuxfoundation.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Todor Tomov <todor.tomov@linaro.org>,
	devicetree@vger.kernel.org
Subject: Re: [V2, 2/5] Documentation: dt-bindings: Document the Synopsys MIPI DPHY Rx bindings
Date: Thu, 20 Sep 2018 16:11:14 +0300	[thread overview]
Message-ID: <1754496.WQhu2lOnZY@avalon> (raw)
In-Reply-To: <20180920111648.27000-3-lolivei@synopsys.com>

Hi Louis,

Thank you for the patch.

On Thursday, 20 September 2018 14:16:40 EEST Luis Oliveira wrote:
> Add device-tree bindings documentation for SNPS DesignWare MIPI D-PHY in
> RX mode.
> 
> Signed-off-by: Luis Oliveira <lolivei@synopsys.com>
> ---
> Changelog
> v2:
> - no changes
> 
>  .../devicetree/bindings/phy/snps,dphy-rx.txt       | 36 +++++++++++++++++++
>  1 file changed, 36 insertions(+)
>  create mode 100644 Documentation/devicetree/bindings/phy/snps,dphy-rx.txt
> 
> diff --git a/Documentation/devicetree/bindings/phy/snps,dphy-rx.txt
> b/Documentation/devicetree/bindings/phy/snps,dphy-rx.txt new file mode
> 100644
> index 0000000..9079f4a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/snps,dphy-rx.txt
> @@ -0,0 +1,36 @@
> +Synopsys DesignWare MIPI Rx D-PHY block details
> +
> +Description
> +-----------
> +
> +The Synopsys MIPI D-PHY controller supports MIPI-DPHY in receiver mode.
> +Please refer to phy-bindings.txt for more information.
> +
> +Required properties:
> +- compatible		: Shall be "snps,dphy-rx".
> +- #phy-cells		: Must be 1.
> +- snps,dphy-frequency	: Output frequency of the D-PHY.

If that's the frequency of the clock on the output side of the RX PHY, doesn't 
it depend on the frequency on the CSI-2 (or other) bus ? Can't it vary ? Why 
do you need to have it in DT ?

> +- snps,dphy-te-len	: Size of the communication interface (8 bits->8 or
> 12bits->12).

We have similar properties in various bindings, such as bus-width in video-
interfaces.txt. Couldn't we use a more standard name ?

> +- reg			: Physical base address and size of the device memory mapped
> +		 	  registers;

The example below shows three ranges. Could you document the ranges that are 
expected ?

> +Optional properties:
> +- snps,compat-mode	: Compatibility mode control

What is this ?

> +The per-board settings:
> +- gpios 		: Synopsys testchip used as reference uses this to change 
setup
> +		  	  configurations.

Here too, what is this for ?

> +Example:
> +
> +	mipi_dphy_rx1: dphy@3040 {
> +		compatible = "snps,dphy-rx";
> +		#phy-cells = <1>;
> +		snps,dphy-frequency = <300000>;
> +		snps,dphy-te-len = <12>;
> +		snps,compat-mode = <1>;
> +		reg = < 0x03040 0x20
> +			0x08000 0x100
> +			0x09000 0x100>;

The base addresses are pretty low, what kind of bus does this sit on ?

> +	};
> +

-- 
Regards,

Laurent Pinchart

  reply	other threads:[~2018-09-20 18:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-20 11:16 [V2, 0/5] platform: dwc: Add of DesignWare MIPI CSI-2 Host Luis Oliveira
2018-09-20 11:16 ` [V2, 1/5] media: platform: Add a DesignWare folder to have Synopsys drivers Luis Oliveira
2018-09-20 12:26   ` Laurent Pinchart
2018-09-20 12:30     ` Luis Oliveira
2018-09-20 11:16 ` [V2, 2/5] Documentation: dt-bindings: Document the Synopsys MIPI DPHY Rx bindings Luis Oliveira
2018-09-20 13:11   ` Laurent Pinchart [this message]
2018-09-20 14:26     ` Luis Oliveira
2018-10-12 16:45   ` Rob Herring
2018-10-12 16:46     ` Rob Herring
2018-10-15 16:21     ` Luis Oliveira
2018-09-20 11:16 ` [V2, 3/5] media: platform: dwc: Add DW MIPI DPHY Rx platform Luis Oliveira
2018-09-20 13:20   ` Laurent Pinchart
2018-09-21 15:25     ` Luis Oliveira
2018-09-20 11:16 ` [V2, 4/5] Documentation: dt-bindings: Document bindings for DW MIPI CSI-2 Host Luis Oliveira
2018-09-20 13:24   ` Laurent Pinchart
2018-09-20 15:44     ` Luis Oliveira
2018-09-20 11:16 ` [V2, 5/5] media: platform: dwc: Add MIPI CSI-2 controller driver Luis Oliveira
2018-09-21 14:37 ` [V2, 0/5] platform: dwc: Add of DesignWare MIPI CSI-2 Host Maxime Ripard
2018-09-21 15:27   ` Luis Oliveira

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=1754496.WQhu2lOnZY@avalon \
    --to=laurent.pinchart@ideasonboard.com \
    --cc=Joao.Pinto@synopsys.com \
    --cc=Luis.Oliveira@synopsys.com \
    --cc=arnd@arndb.de \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=hans.verkuil@cisco.com \
    --cc=jacob-chen@iotwrt.com \
    --cc=keiichiw@chromium.org \
    --cc=kstewart@linuxfoundation.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=mchehab@kernel.org \
    --cc=narmstrong@baylibre.com \
    --cc=p.zabel@pengutronix.de \
    --cc=robh+dt@kernel.org \
    --cc=todor.tomov@linaro.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