From: <Eugen.Hristev@microchip.com> To: <Luis.Oliveira@synopsys.com>, <mchehab@kernel.org>, <davem@davemloft.net>, <gregkh@linuxfoundation.org>, <Jonathan.Cameron@huawei.com>, <robh@kernel.org>, <Nicolas.Ferre@microchip.com>, <paulmck@linux.ibm.com>, <mark.rutland@arm.com>, <kishon@ti.com>, <devicetree@vger.kernel.org>, <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org> Cc: <Joao.Pinto@synopsys.com> Subject: Re: [v4 1/6] dt-bindings: media: Document bindings for DW MIPI CSI-2 Host Date: Wed, 10 Jul 2019 06:53:02 +0000 [thread overview] Message-ID: <415416c4-c6d8-f81e-82cb-126e4702801b@microchip.com> (raw) In-Reply-To: <MN2PR12MB3710465D7065DAF1F2D45C45CBF10@MN2PR12MB3710.namprd12.prod.outlook.com> On 09.07.2019 20:08, Luis de Oliveira wrote: > > Hi Eugen, > > > From: Eugen.Hristev@microchip.com <Eugen.Hristev@microchip.com> > Date: Tue, Jul 09, 2019 at 15:33:50 > >> >> >> On 11.06.2019 22:20, Luis Oliveira wrote: >>> From: Luis Oliveira <lolivei@synopsys.com> >>> >>> Add bindings for Synopsys DesignWare MIPI CSI-2 host. >>> >>> Signed-off-by: Luis Oliveira <lolivei@synopsys.com> >>> --- >>> Changelog >>> v3-v4 >>> - remove "plat" from the block name @rob @laurent >>> - remove "phy-names" when single-entry @rob >>> - remove "snps,output-type" -> went to the driver config @laurent >>> >>> .../devicetree/bindings/media/snps,dw-csi.txt | 41 ++++++++++++++++++++++ >>> 1 file changed, 41 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> >>> diff --git a/Documentation/devicetree/bindings/media/snps,dw-csi.txt b/Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> new file mode 100644 >>> index 0000000..613b7f9 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> @@ -0,0 +1,41 @@ >>> +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" >>> +- reg : physical base address and size of the device memory >>> + mapped registers; >>> +- interrupts : DW CSI-2 Host interrupts >>> +- 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: csi2@3000 { >>> + compatible = "snps,dw-csi"; >>> + #address-cells = <1>; >>> + #size-cells = <0>; >>> + reg = < 0x03000 0x7FF>; >>> + phys = <&mipi_dphy_rx>; >>> + resets = <&dw_rst 1>; >>> + interrupts = <2>; >>> + >>> + port@0 { >>> + reg = <0>; >>> + csi_ep1: endpoint { >>> + remote-endpoint = <&camera_1>; >>> + data-lanes = <1 2>; >>> + }; >> >> Hello Luis, >> >> Which is the output port (endpoint) : how to connect the output of >> csi2host to another node ? >> I mean, the second port of this block, or, how is the data taken from >> csi2host ? >> > > I understand your question, I think you guessed this is not the complete > pipeline (I have a top driver that interacts with this one). > I was not planning to submit it, do you think I should? Yes please, you can have the patch with subject DO NOT MERGE if you do not want that patch to be included in the kernel and just for reference. but it would help me in understanding your setup Thanks ! > > The behavior is very similar with this one > ./drivers/media/platform/exynos4-is/media-dev.c > > >> Thanks, >> >> Eugen >> >>> + }; >>> + }; >>> > > Thanks, > Luis >
WARNING: multiple messages have this Message-ID (diff)
From: <Eugen.Hristev@microchip.com> To: Luis.Oliveira@synopsys.com, mchehab@kernel.org, davem@davemloft.net, gregkh@linuxfoundation.org, Jonathan.Cameron@huawei.com, robh@kernel.org, Nicolas.Ferre@microchip.com, paulmck@linux.ibm.com, mark.rutland@arm.com, kishon@ti.com, devicetree@vger.kernel.org, linux-media@vger.kernel.org, linux-kernel@vger.kernel.org Cc: Joao.Pinto@synopsys.com Subject: Re: [v4 1/6] dt-bindings: media: Document bindings for DW MIPI CSI-2 Host Date: Wed, 10 Jul 2019 06:53:02 +0000 [thread overview] Message-ID: <415416c4-c6d8-f81e-82cb-126e4702801b@microchip.com> (raw) In-Reply-To: <MN2PR12MB3710465D7065DAF1F2D45C45CBF10@MN2PR12MB3710.namprd12.prod.outlook.com> On 09.07.2019 20:08, Luis de Oliveira wrote: > > Hi Eugen, > > > From: Eugen.Hristev@microchip.com <Eugen.Hristev@microchip.com> > Date: Tue, Jul 09, 2019 at 15:33:50 > >> >> >> On 11.06.2019 22:20, Luis Oliveira wrote: >>> From: Luis Oliveira <lolivei@synopsys.com> >>> >>> Add bindings for Synopsys DesignWare MIPI CSI-2 host. >>> >>> Signed-off-by: Luis Oliveira <lolivei@synopsys.com> >>> --- >>> Changelog >>> v3-v4 >>> - remove "plat" from the block name @rob @laurent >>> - remove "phy-names" when single-entry @rob >>> - remove "snps,output-type" -> went to the driver config @laurent >>> >>> .../devicetree/bindings/media/snps,dw-csi.txt | 41 ++++++++++++++++++++++ >>> 1 file changed, 41 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> >>> diff --git a/Documentation/devicetree/bindings/media/snps,dw-csi.txt b/Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> new file mode 100644 >>> index 0000000..613b7f9 >>> --- /dev/null >>> +++ b/Documentation/devicetree/bindings/media/snps,dw-csi.txt >>> @@ -0,0 +1,41 @@ >>> +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" >>> +- reg : physical base address and size of the device memory >>> + mapped registers; >>> +- interrupts : DW CSI-2 Host interrupts >>> +- 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: csi2@3000 { >>> + compatible = "snps,dw-csi"; >>> + #address-cells = <1>; >>> + #size-cells = <0>; >>> + reg = < 0x03000 0x7FF>; >>> + phys = <&mipi_dphy_rx>; >>> + resets = <&dw_rst 1>; >>> + interrupts = <2>; >>> + >>> + port@0 { >>> + reg = <0>; >>> + csi_ep1: endpoint { >>> + remote-endpoint = <&camera_1>; >>> + data-lanes = <1 2>; >>> + }; >> >> Hello Luis, >> >> Which is the output port (endpoint) : how to connect the output of >> csi2host to another node ? >> I mean, the second port of this block, or, how is the data taken from >> csi2host ? >> > > I understand your question, I think you guessed this is not the complete > pipeline (I have a top driver that interacts with this one). > I was not planning to submit it, do you think I should? Yes please, you can have the patch with subject DO NOT MERGE if you do not want that patch to be included in the kernel and just for reference. but it would help me in understanding your setup Thanks ! > > The behavior is very similar with this one > ./drivers/media/platform/exynos4-is/media-dev.c > > >> Thanks, >> >> Eugen >> >>> + }; >>> + }; >>> > > Thanks, > Luis >
next prev parent reply other threads:[~2019-07-10 6:53 UTC|newest] Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-06-11 19:20 [v4 0/6] platform: dwc: Adding DesignWare MIPI CSI-2 Host and D-PHY Luis Oliveira 2019-06-11 19:20 ` [v4 1/6] dt-bindings: media: Document bindings for DW MIPI CSI-2 Host Luis Oliveira 2019-06-28 14:13 ` Sakari Ailus 2019-07-08 15:21 ` Luis de Oliveira 2019-07-09 18:25 ` Sakari Ailus 2019-07-10 10:20 ` Luis de Oliveira 2019-07-25 20:02 ` Sakari Ailus 2019-07-26 9:50 ` Luis de Oliveira 2019-07-26 11:13 ` Eugen.Hristev 2019-07-26 11:13 ` Eugen.Hristev 2019-07-09 14:33 ` Eugen.Hristev 2019-07-09 14:33 ` Eugen.Hristev 2019-07-09 17:08 ` Luis de Oliveira 2019-07-10 6:53 ` Eugen.Hristev [this message] 2019-07-10 6:53 ` Eugen.Hristev 2019-07-10 10:23 ` Luis de Oliveira 2019-06-11 19:20 ` [v4 2/6] media: platform: dwc: Add MIPI CSI-2 controller driver Luis Oliveira 2019-07-10 8:59 ` Eugen.Hristev 2019-07-10 8:59 ` Eugen.Hristev 2019-07-10 14:21 ` Luis de Oliveira 2019-08-09 14:10 ` Sakari Ailus 2019-08-10 13:09 ` Andy Shevchenko 2019-08-12 9:45 ` Luis de Oliveira 2019-08-12 16:50 ` Andy Shevchenko 2019-06-11 19:20 ` [v4 3/6] media: platform: dwc: Add MIPI CSI-2 platform data Luis Oliveira 2019-08-09 14:39 ` Sakari Ailus 2019-06-11 19:20 ` [v4 4/6] dt-bindings: phy: Document the Synopsys MIPI DPHY Rx bindings Luis Oliveira 2019-07-09 14:20 ` Rob Herring 2019-07-09 16:28 ` Luis de Oliveira 2019-07-10 13:50 ` Rob Herring 2019-08-09 14:42 ` Sakari Ailus 2019-08-09 14:45 ` Sakari Ailus 2019-08-09 14:47 ` Sakari Ailus 2019-06-11 19:20 ` [v4 5/6] media: platform: dwc: Add DW MIPI DPHY Rx driver Luis Oliveira 2019-06-11 19:20 ` [v4 6/6] media: platform: dwc: Add platform data support to D-Phy 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=415416c4-c6d8-f81e-82cb-126e4702801b@microchip.com \ --to=eugen.hristev@microchip.com \ --cc=Joao.Pinto@synopsys.com \ --cc=Jonathan.Cameron@huawei.com \ --cc=Luis.Oliveira@synopsys.com \ --cc=Nicolas.Ferre@microchip.com \ --cc=davem@davemloft.net \ --cc=devicetree@vger.kernel.org \ --cc=gregkh@linuxfoundation.org \ --cc=kishon@ti.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-media@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=mchehab@kernel.org \ --cc=paulmck@linux.ibm.com \ --cc=robh@kernel.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: linkBe 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.