From: <Eugen.Hristev@microchip.com>
To: <luis.oliveira@synopsys.com>, <linux-media@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <joao.pinto@synopsys.com>, <festevam@gmail.com>,
<mchehab@kernel.org>, <robh+dt@kernel.org>,
<mark.rutland@arm.com>, <hans.verkuil@cisco.com>,
<laurent.pinchart+renesas@ideasonboard.com>, <arnd@arndb.de>,
<geert+renesas@glider.be>, <narmstrong@baylibre.com>,
<p.zabel@pengutronix.de>, <keiichiw@chromium.org>,
<kstewart@linuxfoundation.org>, <todor.tomov@linaro.org>,
<devicetree@vger.kernel.org>
Subject: Re: [V3, 3/4] Documentation: dt-bindings: media: Document bindings for DW MIPI CSI-2 Host
Date: Fri, 11 Jan 2019 15:29:03 +0000 [thread overview]
Message-ID: <a967f37a-07cb-4b0b-1777-f354427445ea@microchip.com> (raw)
In-Reply-To: <1539953556-35762-4-git-send-email-lolivei@synopsys.com>
On 19.10.2018 15:52, Luis Oliveira wrote:
> Add bindings for Synopsys DesignWare MIPI CSI-2 host.
>
> Signed-off-by: Luis Oliveira <lolivei@synopsys.com>
> ---
> Changelog
> v2-V3
> - removed IPI settings
>
> .../devicetree/bindings/media/snps,dw-csi-plat.txt | 52 ++++++++++++++++++++++
> 1 file changed, 52 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/media/snps,dw-csi-plat.txt
>
> diff --git a/Documentation/devicetree/bindings/media/snps,dw-csi-plat.txt b/Documentation/devicetree/bindings/media/snps,dw-csi-plat.txt
> new file mode 100644
> index 0000000..be3da05
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/media/snps,dw-csi-plat.txt
> @@ -0,0 +1,52 @@
> +Synopsys DesignWare CSI-2 Host controller
> +
> +Description
> +-----------
> +
> +This HW block is used to receive image coming from an MIPI CSI-2 compatible
> +camera.
> +
> +Required properties:
> +- compatible: shall be "snps,dw-csi-plat"
> +- reg : physical base address and size of the device memory mapped
> + registers;
> +- interrupts : CSI-2 Host interrupt
> +- snps,output-type : Core output to be used (IPI-> 0 or IDI->1 or BOTH->2)
> + These values choose which of the Core outputs will be used,
> + it can be Image Data Interface or Image Pixel Interface.
> +- phys : List of one PHY specifier (as defined in
> + Documentation/devicetree/bindings/phy/phy-bindings.txt).
> + This PHY is a MIPI DPHY working in RX mode.
> +- resets : Reference to a reset controller (optional)
> +
> +The per-board settings:
> + - port sub-node describing a single endpoint connected to the camera as
> + described in video-interfaces.txt[1].
> +
> +Example:
> +
> + csi2_1: csi2@3000 {
> + compatible = "snps,dw-csi-plat";
> + #address-cells = <1>;
> + #size-cells = <0>;
> + reg = < 0x03000 0x7FF>;
> + interrupts = <2>;
> + output-type = <2>;
> + resets = <&dw_rst 1>;
> + phys = <&mipi_dphy_rx1 0>;
> + phy-names = "csi2-dphy";
> +
> + /* CSI-2 per-board settings */
> + port@1 {
> + reg = <1>;
> + csi1_ep1: endpoint {
> + remote-endpoint = <&camera_1>;
> + data-lanes = <1 2>;
> + };
> + };
> + port@2 {
> + csi1_ep2: endpoint {
> + remote-endpoint = <&vif1_ep>;
Hi again Luis,
Regarding the output endpoint, in your example port@2, if we use the
property snps,output-type=2 for example, so IDI output, which bus-type
you have in mind for this link? IDI is not documented in the
video-interfaces.txt binding.
Since the MIPI CSI-2 DPHY is actually between camera sensor and
csi2host, after this we can use either IDI or IPI if my understanding is
correct, and connect to a different pad/hw block which can further
handle these packets/pixels.
I am interested on how to specify the connection type between this
output pad and the next one (until a /dev/video can be registered by the
last driver for the last hw block).
Thanks,
Eugen
> + };
> + };
> + };
> --
> 2.7.4
>
>
next prev parent reply other threads:[~2019-01-11 15:29 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 12:52 [V3, 0/4] platform: dwc: Add of DesignWare MIPI CSI-2 Host Luis Oliveira
2018-10-19 12:52 ` [V3, 1/4] Documentation: dt-bindings: phy: Document the Synopsys MIPI DPHY Rx bindings Luis Oliveira
2018-10-24 17:36 ` Rob Herring
2018-11-13 8:58 ` Luis Oliveira
2018-11-13 9:30 ` Luis de Oliveira
2018-11-14 20:08 ` Laurent Pinchart
2018-10-19 12:52 ` [V3, 2/4] media: platform: dwc: Add DW MIPI DPHY Rx platform Luis Oliveira
2019-01-07 11:58 ` Sakari Ailus
2019-01-08 9:17 ` Luis de Oliveira
2018-10-19 12:52 ` [V3, 3/4] Documentation: dt-bindings: media: Document bindings for DW MIPI CSI-2 Host Luis Oliveira
2018-10-24 17:40 ` Rob Herring
2018-11-13 10:00 ` Luis de Oliveira
2018-11-14 20:16 ` Laurent Pinchart
2018-10-24 17:41 ` Rob Herring
2018-11-13 10:00 ` Luis de Oliveira
2019-01-11 15:29 ` Eugen.Hristev [this message]
2018-10-19 12:52 ` [V3, 4/4] media: platform: dwc: Add MIPI CSI-2 controller driver Luis Oliveira
2018-11-14 20:22 ` Laurent Pinchart
2019-01-10 17:00 ` Luis de Oliveira
2018-12-10 12:39 ` Eugen.Hristev
2019-01-10 16:11 ` Luis de Oliveira
2019-01-09 13:07 ` Eugen.Hristev
2019-01-10 16:18 ` Luis de Oliveira
2019-01-11 7:25 ` Eugen.Hristev
2019-01-11 8:11 ` Luis de Oliveira
2019-01-11 9:49 ` Eugen.Hristev
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=a967f37a-07cb-4b0b-1777-f354427445ea@microchip.com \
--to=eugen.hristev@microchip.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=joao.pinto@synopsys.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=luis.oliveira@synopsys.com \
--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;
as well as URLs for NNTP newsgroup(s).