From: Rui Miguel Silva <rui.silva@linaro.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: devel@driverdev.osuosl.org, devicetree@vger.kernel.org,
sakari.ailus@linux.intel.com,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Hans Verkuil <hverkuil@xs4all.nl>,
Philipp Zabel <p.zabel@pengutronix.de>,
Steve Longerbeam <slongerbeam@gmail.com>,
linux-media@vger.kernel.org
Subject: Re: [PATCH v14 08/13] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections
Date: Tue, 12 Mar 2019 14:05:24 +0000 [thread overview]
Message-ID: <m3y35kdw7v.fsf@linaro.org> (raw)
In-Reply-To: <20190310214102.GA7578@pendragon.ideasonboard.com>
Hi Laurent,
On Sun 10 Mar 2019 at 21:41, Laurent Pinchart wrote:
> Hi Rui,
>
> Thank you for the patch.
Where have you been for the latest 14 versions? :)
This is already merged, but... follow up patches can address your
issues bellow.
>
> On Wed, Feb 06, 2019 at 03:13:23PM +0000, Rui Miguel Silva
> wrote:
>> This patch adds the device tree nodes for csi, video
>> multiplexer and
>> mipi-csi besides the graph connecting the necessary endpoints
>> to make
>> the media capture entities to work in imx7 Warp board.
>>
>> Signed-off-by: Rui Miguel Silva <rui.silva@linaro.org>
>> ---
>> arch/arm/boot/dts/imx7s-warp.dts | 51
>> ++++++++++++++++++++++++++++++++
>> arch/arm/boot/dts/imx7s.dtsi | 27 +++++++++++++++++
>
> I would have split this in two patches to make backporting
> easier, but
> it's not a big deal.
>
> Please see below for a few additional comments.
>
>> 2 files changed, 78 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/imx7s-warp.dts
>> b/arch/arm/boot/dts/imx7s-warp.dts
>> index 23431faecaf4..358bcae7ebaf 100644
>> --- a/arch/arm/boot/dts/imx7s-warp.dts
>> +++ b/arch/arm/boot/dts/imx7s-warp.dts
>> @@ -277,6 +277,57 @@
>> status = "okay";
>> };
>>
>> +&gpr {
>> + csi_mux {
>> + compatible = "video-mux";
>> + mux-controls = <&mux 0>;
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + port@1 {
>> + reg = <1>;
>> +
>> + csi_mux_from_mipi_vc0: endpoint {
>> + remote-endpoint =
>> <&mipi_vc0_to_csi_mux>;
>> + };
>> + };
>> +
>> + port@2 {
>> + reg = <2>;
>> +
>> + csi_mux_to_csi: endpoint {
>> + remote-endpoint =
>> <&csi_from_csi_mux>;
>> + };
>> + };
>> + };
>> +};
>> +
>> +&csi {
>> + status = "okay";
>> +
>> + port {
>> + csi_from_csi_mux: endpoint {
>> + remote-endpoint = <&csi_mux_to_csi>;
>> + };
>> + };
>> +};
>
> Shouldn't these two nodes, as well as port@1 of the mipi_csi
> node, be
> moved to imx7d.dtsi ?
Yeah, I guess you are right here.
>
>> +
>> +&mipi_csi {
>> + clock-frequency = <166000000>;
>> + status = "okay";
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> + fsl,csis-hs-settle = <3>;
>
> Shouldn't this be an endpoint property ? Different sensors
> connected
> through different endpoints could have different timing
> requirements.
Hum... I see you point, even tho the phy hs-settle is a common
control.
>
>> +
>> + port@1 {
>> + reg = <1>;
>> +
>> + mipi_vc0_to_csi_mux: endpoint {
>> + remote-endpoint =
>> <&csi_mux_from_mipi_vc0>;
>> + };
>> + };
>> +};
>> +
>> &wdog1 {
>> pinctrl-names = "default";
>> pinctrl-0 = <&pinctrl_wdog>;
>> diff --git a/arch/arm/boot/dts/imx7s.dtsi
>> b/arch/arm/boot/dts/imx7s.dtsi
>> index 792efcd2caa1..01962f85cab6 100644
>> --- a/arch/arm/boot/dts/imx7s.dtsi
>> +++ b/arch/arm/boot/dts/imx7s.dtsi
>> @@ -8,6 +8,7 @@
>> #include <dt-bindings/gpio/gpio.h>
>> #include <dt-bindings/input/input.h>
>> #include <dt-bindings/interrupt-controller/arm-gic.h>
>> +#include <dt-bindings/reset/imx7-reset.h>
>> #include "imx7d-pinfunc.h"
>>
>> / {
>> @@ -709,6 +710,17 @@
>> status = "disabled";
>> };
>>
>> + csi: csi@30710000 {
>> + 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";
>> + status = "disabled";
>> + };
>> +
>> lcdif: lcdif@30730000 {
>> compatible = "fsl,imx7d-lcdif",
>> "fsl,imx28-lcdif";
>> reg = <0x30730000 0x10000>;
>> @@ -718,6 +730,21 @@
>> clock-names = "pix", "axi";
>> status = "disabled";
>> };
>> +
>> + mipi_csi: mipi-csi@30750000 {
>> + 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";
>> + power-domains = <&pgc_mipi_phy>;
>> + phy-supply = <®_1p0d>;
>> + resets = <&src
>> IMX7_RESET_MIPI_PHY_MRST>;
>> + reset-names = "mrst";
>> + status = "disabled";
>
> How about already declaring port@0 here too (but obviously
> without any
> endoint) ?
empty port, do not know if they make much sense.
---
Cheers,
Rui
next prev parent reply other threads:[~2019-03-12 14:05 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 15:13 [PATCH v14 00/13] media: staging/imx7: add i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 01/13] media: staging/imx: refactor imx media device probe Rui Miguel Silva
2019-02-06 15:36 ` Hans Verkuil
2019-02-06 15:13 ` [PATCH v14 02/13] media: staging/imx: rearrange group id to take in account IPU Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 03/13] media: dt-bindings: add bindings for i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 04/13] media: staging/imx7: add imx7 CSI subdev driver Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 05/13] media: staging/imx7: add MIPI CSI-2 receiver subdev for i.MX7 Rui Miguel Silva
2019-02-20 8:56 ` Hans Verkuil
2019-02-20 11:26 ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 06/13] ARM: dts: imx7s: add mipi phy power domain Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 07/13] ARM: dts: imx7s: add multiplexer controls Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 08/13] ARM: dts: imx7: Add video mux, csi and mipi_csi and connections Rui Miguel Silva
2019-03-10 21:41 ` Laurent Pinchart
2019-03-12 14:05 ` Rui Miguel Silva [this message]
2019-03-12 14:10 ` Laurent Pinchart
2019-03-12 15:35 ` Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 09/13] ARM: dts: imx7s-warp: add ov2680 sensor node Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 10/13] media: imx7.rst: add documentation for i.MX7 media driver Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 11/13] media: staging/imx: add i.MX7 entries to TODO file Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 12/13] media: video-mux: add bayer formats Rui Miguel Silva
2019-02-06 15:13 ` [PATCH v14 13/13] media: MAINTAINERS: add entry for Freescale i.MX7 media driver Rui Miguel Silva
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=m3y35kdw7v.fsf@linaro.org \
--to=rui.silva@linaro.org \
--cc=devel@driverdev.osuosl.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil@xs4all.nl \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=sakari.ailus@linux.intel.com \
--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 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).