From: Scott Wood <scottwood@freescale.com>
To: <igal.liberman@freescale.com>, <devicetree@vger.kernel.org>,
<linuxppc-dev@lists.ozlabs.org>
Cc: <madalin.bucur@freescale.com>, <shaohui.xie@freescale.com>
Subject: Re: [PATCH] powerpc/fsl: Update fman dt binding with pcs-phy and tbi-phy
Date: Tue, 22 Dec 2015 15:42:58 -0600 [thread overview]
Message-ID: <1450820578.18314.94.camel@freescale.com> (raw)
In-Reply-To: <1450757888-14216-1-git-send-email-igal.liberman@freescale.com>
On Tue, 2015-12-22 at 06:18 +0200, igal.liberman@freescale.com wrote:
> From: Igal Liberman <igal.liberman@freescale.com>
>
> Signed-off-by: Igal Liberman <igal.liberman@freescale.com>
> ---
> .../devicetree/bindings/powerpc/fsl/fman.txt | 39
> ++++++++++++++++++++
> 1 file changed, 39 insertions(+)
Some description in the log would be nice, especially why it can't use phy
-handle
>
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> index 1fc5328..7a6d7c3 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> @@ -315,6 +315,16 @@ PROPERTIES
> Value type: <phandle>
> Definition: A phandle for 1EEE1588 timer.
>
> +- pcsphy-handle
> + Usage required for "fsl,fman-memac" MACs
> + Value type: <phandle>
> + Definition: A phandle for pcsphy.
> +
> +- tbi-handle
> + Usage required for "fsl,fman-dtsec" MACs
> + Value type: <phandle>
> + Definition: A phandle for tbiphy.
> +
> EXAMPLE
>
> fman1_tx28: port@a8000 {
> @@ -340,6 +350,7 @@ ethernet@e0000 {
> reg = <0xe0000 0x1000>;
> fsl,fman-ports = <&fman1_rx8 &fman1_tx28>;
> ptp-timer = <&ptp-timer>;
> + tbi-handle = <&tbi0>;
> };
>
> ===========================================================================
> =
> @@ -415,6 +426,13 @@ PROPERTIES
> The settings and programming routines for internal/external
> MDIO are different. Must be included for internal MDIO.
>
> +For internal PHY device on internal mdio bus, a PHY node should be created.
> +See the definition of the PHY node in booting-without-of.txt for an
> +example of how to define a PHY (Internal PHY has no interrupt line).
> +- For "fsl,fman-mdio" compatible internal mdio bus, the PHY is TBI PHY.
> +- For "fsl,fman-memac-mdio" compatible internal mdio bus, the PHY is PCS
> PHY,
> + PCS PHY addr must be '0'.
> +
> EXAMPLE
>
> Example for FMan v2 external MDIO:
> @@ -425,12 +443,28 @@ mdio@f1000 {
> interrupts = <101 2 0 0>;
> };
>
> +Example for FMan v2 internal MDIO:
> +
> +mdio@e3120 {
> + compatible = "fsl,fman-mdio";
> + reg = <0xe3120 0xee0>;
> + fsl,fman-internal-mdio;
> +
> + tbi1: tbi-phy@8 {
> + reg = <0x8>;
> + device_type = "tbi-phy";
> + };
> +};
> +
> Example for FMan v3 internal MDIO:
>
> mdio@f1000 {
> compatible = "fsl,fman-memac-mdio";
> reg = <0xf1000 0x1000>;
> fsl,fman-internal-mdio;
> +
> + pcsphy6: ethernet-phy@0 {
> + reg = <0x0>;
> };
missing }
-Scott
prev parent reply other threads:[~2015-12-22 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-22 4:18 [PATCH] powerpc/fsl: Update fman dt binding with pcs-phy and tbi-phy igal.liberman
2015-12-22 15:56 ` Joakim Tjernlund
2015-12-22 16:10 ` Liberman Igal
2015-12-22 21:42 ` Scott Wood [this message]
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=1450820578.18314.94.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=igal.liberman@freescale.com \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=shaohui.xie@freescale.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).