From: Rob Herring <robh@kernel.org>
To: "Guido Günther" <agx@sigxcpu.org>
Cc: "Kishon Vijay Abraham I" <kishon@ti.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Fabio Estevam" <festevam@gmail.com>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Thierry Reding" <treding@nvidia.com>,
"Andreas Färber" <afaerber@suse.de>,
"Martin Blumenstingl" <martin.blumenstingl@googlemail.com>,
"Heiko Stuebner" <heiko@sntech.de>,
"Johan Hovold" <johan@kernel.org>,
"Lucas Stach" <l.stach@pengutronix.de>,
"Abel Vesa" <abel.vesa@nxp.com>, "Li Jun" <jun.li@nxp.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
"Robert Chiras" <robert.chiras@nxp.com>
Subject: Re: [PATCH RESEND v7 2/3] dt-bindings: phy: Add documentation for mixel dphy
Date: Thu, 28 Mar 2019 11:57:29 -0500 [thread overview]
Message-ID: <20190328165729.GA32345@bogus> (raw)
In-Reply-To: <3319783f60fedd7f0029dd60a51c76a75003fe05.1553674604.git.agx@sigxcpu.org>
On Wed, Mar 27, 2019 at 09:20:00AM +0100, Guido Günther wrote:
> Add support for the MIXEL DPHY IP as found in the NXP's i.MX8MQ.
>
> Signed-off-by: Guido Günther <agx@sigxcpu.org>
> Reviewed-by: Sam Ravnborg <sam@ravnborg.org>
> ---
> .../bindings/phy/mixel,mipi-dsi-phy.txt | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.txt
>
> diff --git a/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.txt b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.txt
> new file mode 100644
> index 000000000000..d3646580412a
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/phy/mixel,mipi-dsi-phy.txt
> @@ -0,0 +1,29 @@
> +Mixel DSI PHY for i.MX8
> +
> +The Mixel MIPI-DSI PHY IP block is e.g. found on i.MX8 platforms (along the
> +MIPI-DSI IP from Northwest Logic). It represents the physical layer for the
> +electrical signals for DSI.
> +
> +Required properties:
> +- compatible: Must be:
> + - "mixel,imx8mq-mipi-dphy"
If you had a fallback for mixel, then it would make sense, but as this
is imx8mq specifc 'fsl' should be the vendor prefix.
> +- clocks: Must contain an entry for each entry in clock-names.
> +- clock-names: Must contain the following entries:
> + - "phy_ref": phandle and specifier referring to the DPHY ref clock
> +- reg: the register range of the PHY controller
> +- #phy-cells: number of cells in PHY, as defined in
> + Documentation/devicetree/bindings/phy/phy-bindings.txt
> + this must be <0>
> +
> +Optional properties:
> +- power-domains: phandle to power domain
> +
> +Example:
> + mipi_dphy: mipi_dphy@30A0030 {
mipi-dphy@... or just dphy@...
> + compatible = "mixel,imx8mq-mipi-dphy";
> + clocks = <&clk IMX8MQ_CLK_DSI_PHY_REF>;
> + clock-names = "phy_ref";
> + reg = <0x30A00300 0x100>;
> + power-domains = <&pd_mipi0>;
> + #phy-cells = <0>;
> + };
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-03-28 16:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-27 8:19 [PATCH RESEND v7 0/3] Mixel DPHY support for i.MX8 Guido Günther
2019-03-27 8:19 ` [PATCH RESEND v7 1/3] dt-bindings: Add vendor prefix for Mixel Inc Guido Günther
2019-03-28 17:04 ` Andreas Färber
2019-04-01 10:24 ` Guido Günther
2019-03-27 8:20 ` [PATCH RESEND v7 2/3] dt-bindings: phy: Add documentation for mixel dphy Guido Günther
2019-03-28 16:57 ` Rob Herring [this message]
2019-04-01 10:23 ` Guido Günther
2019-03-27 8:20 ` [PATCH RESEND v7 3/3] phy: Add driver for mixel dphy found on imx8 Guido Günther
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=20190328165729.GA32345@bogus \
--to=robh@kernel.org \
--cc=abel.vesa@nxp.com \
--cc=afaerber@suse.de \
--cc=agx@sigxcpu.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=heiko@sntech.de \
--cc=johan@kernel.org \
--cc=jun.li@nxp.com \
--cc=kernel@pengutronix.de \
--cc=kishon@ti.com \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martin.blumenstingl@googlemail.com \
--cc=robert.chiras@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=treding@nvidia.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).