From: Scott Wood <scottwood@freescale.com>
To: <shh.xie@gmail.com>
Cc: devicetree@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Shaohui Xie <Shaohui.Xie@freescale.com>,
Emilian.Medve@freescale.com
Subject: Re: [PATCH] DT: add MDIO node for FMan node
Date: Mon, 10 Nov 2014 18:23:04 -0600 [thread overview]
Message-ID: <1415665384.15957.16.camel@freescale.com> (raw)
In-Reply-To: <1415102196-9238-1-git-send-email-shh.xie@gmail.com>
On Tue, 2014-11-04 at 19:56 +0800, shh.xie@gmail.com wrote:
> From: Shaohui Xie <Shaohui.Xie@freescale.com>
>
> This binding is for FMan MDIO, it covers FMan v2 & FMan v3.
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie@freescale.com>
> ---
> based on http://patchwork.ozlabs.org/patch/390351/
> for 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux.git
Are there any other FMan pieces that are missing from the above patch?
> .../devicetree/bindings/powerpc/fsl/fman.txt | 69 ++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> index da8e5f2..83c2f14 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> @@ -7,6 +7,7 @@ CONTENTS
> - FMan MURAM Node
> - FMan dTSEC/XGEC/mEMAC Node
> - FMan IEEE 1588 Node
> + - FMan MDIO Node
> - Example
>
> =============================================================================
> @@ -352,6 +353,67 @@ ptp-timer@fe000 {
> };
>
> =============================================================================
> +FMan MDIO Node
> +
> +DESCRIPTION
> +
> +The MDIO is a bus to which the PHY devices are connected.
> +
> +PROPERTIES
> +
> +- compatible
> + Usage: required
> + Value type: <stringlist>
> + Definition: A standard property.
> + Must include "fsl,fman-mdio" for 1 Gb/s MDIO from FMan v2.
> + Must include "fsl,fman-xmdio" for 10 Gb/s MDIO from FMan v2.
> + Must include "fsl,fman-memac-mdio" for 1/10 Gb/s MDIO from
> + FMan v3.
> +
> +- reg
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: A standard property.
> +
> +- bus-frequency
> + Usage: optional
> + Value type: <u32>
> + Definition: Default MDIO bus clock speed.
Use clocks/clock-names
> +- interrupts
> + Usage: optional
> + Value type: <prop-encoded-array>
> + Definition: MDIO controller event interrupts.
One interrupt or multiple?
> +
> +- type
> + Usage: required for FMan v3
> + Value type: <stringlist>
> + Definition: A standard property.
What standard is "type" defined in?
> + FMan v3 has internal MDIO for internal PCS(Physical Coding
> + Sublayer) PHYs and external MDIO for external PHYs.
> + The settings and programming routines for internal/external
> + MDIO are different. Must include "internal" for internal MDIO,
> + must include "external" for external MDIO.
I assume fman v2 is always internal? How about a boolean
"fsl,fman-internal-phy" property instead?
> +
> +EXAMPLE
> +
> +Example for FMan v2:
> +
> +mdio@f1000 {
> + compatible = "fsl,fman-xmdio";
> + reg = <0xf1000 0x1000>;
> +};
> +
> +Example for FMan v3:
> +
> +mdio@fd000 {
> + compatible = "fsl,fman-memac-mdio";
> + reg = <0xfd000 0x1000>;
> + bus-frequency = <2500000>;
> + type = "external";
> +};
> +
> +=============================================================================
> Example
>
> fman@400000 {
> @@ -526,4 +588,11 @@ fman@400000 {
> compatible = "fsl,fman-ptp-timer";
> reg = <0xfe000 0x1000>;
> };
> +
> + mdio@fd000 {
> + compatible = "fsl,fman-memac-mdio";
> + reg = <0xfd000 0x1000>;
> + bus-frequency = <2500000>;
> + type = "external";
> + };
> };
The rest of the example is fman v2; don't mix an fman v3 node in with
that.
-Scott
WARNING: multiple messages have this Message-ID (diff)
From: Scott Wood <scottwood-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
To: shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
Cc: linuxppc-dev-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Emilian.Medve-KZfg59tc24xl57MIdRCFDg@public.gmane.org,
Shaohui Xie <Shaohui.Xie-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
Subject: Re: [PATCH] DT: add MDIO node for FMan node
Date: Mon, 10 Nov 2014 18:23:04 -0600 [thread overview]
Message-ID: <1415665384.15957.16.camel@freescale.com> (raw)
In-Reply-To: <1415102196-9238-1-git-send-email-shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
On Tue, 2014-11-04 at 19:56 +0800, shh.xie-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org wrote:
> From: Shaohui Xie <Shaohui.Xie-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
>
> This binding is for FMan MDIO, it covers FMan v2 & FMan v3.
>
> Signed-off-by: Shaohui Xie <Shaohui.Xie-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
> ---
> based on http://patchwork.ozlabs.org/patch/390351/
> for 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux.git
Are there any other FMan pieces that are missing from the above patch?
> .../devicetree/bindings/powerpc/fsl/fman.txt | 69 ++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> index da8e5f2..83c2f14 100644
> --- a/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> +++ b/Documentation/devicetree/bindings/powerpc/fsl/fman.txt
> @@ -7,6 +7,7 @@ CONTENTS
> - FMan MURAM Node
> - FMan dTSEC/XGEC/mEMAC Node
> - FMan IEEE 1588 Node
> + - FMan MDIO Node
> - Example
>
> =============================================================================
> @@ -352,6 +353,67 @@ ptp-timer@fe000 {
> };
>
> =============================================================================
> +FMan MDIO Node
> +
> +DESCRIPTION
> +
> +The MDIO is a bus to which the PHY devices are connected.
> +
> +PROPERTIES
> +
> +- compatible
> + Usage: required
> + Value type: <stringlist>
> + Definition: A standard property.
> + Must include "fsl,fman-mdio" for 1 Gb/s MDIO from FMan v2.
> + Must include "fsl,fman-xmdio" for 10 Gb/s MDIO from FMan v2.
> + Must include "fsl,fman-memac-mdio" for 1/10 Gb/s MDIO from
> + FMan v3.
> +
> +- reg
> + Usage: required
> + Value type: <prop-encoded-array>
> + Definition: A standard property.
> +
> +- bus-frequency
> + Usage: optional
> + Value type: <u32>
> + Definition: Default MDIO bus clock speed.
Use clocks/clock-names
> +- interrupts
> + Usage: optional
> + Value type: <prop-encoded-array>
> + Definition: MDIO controller event interrupts.
One interrupt or multiple?
> +
> +- type
> + Usage: required for FMan v3
> + Value type: <stringlist>
> + Definition: A standard property.
What standard is "type" defined in?
> + FMan v3 has internal MDIO for internal PCS(Physical Coding
> + Sublayer) PHYs and external MDIO for external PHYs.
> + The settings and programming routines for internal/external
> + MDIO are different. Must include "internal" for internal MDIO,
> + must include "external" for external MDIO.
I assume fman v2 is always internal? How about a boolean
"fsl,fman-internal-phy" property instead?
> +
> +EXAMPLE
> +
> +Example for FMan v2:
> +
> +mdio@f1000 {
> + compatible = "fsl,fman-xmdio";
> + reg = <0xf1000 0x1000>;
> +};
> +
> +Example for FMan v3:
> +
> +mdio@fd000 {
> + compatible = "fsl,fman-memac-mdio";
> + reg = <0xfd000 0x1000>;
> + bus-frequency = <2500000>;
> + type = "external";
> +};
> +
> +=============================================================================
> Example
>
> fman@400000 {
> @@ -526,4 +588,11 @@ fman@400000 {
> compatible = "fsl,fman-ptp-timer";
> reg = <0xfe000 0x1000>;
> };
> +
> + mdio@fd000 {
> + compatible = "fsl,fman-memac-mdio";
> + reg = <0xfd000 0x1000>;
> + bus-frequency = <2500000>;
> + type = "external";
> + };
> };
The rest of the example is fman v2; don't mix an fman v3 node in with
that.
-Scott
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-11 0:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 11:56 [PATCH] DT: add MDIO node for FMan node shh.xie
2014-11-04 11:56 ` shh.xie-Re5JQEeQqe8AvxtiuMwx3w
2014-11-10 10:19 ` Shaohui Xie
2014-11-10 10:19 ` Shaohui Xie
2014-11-11 0:23 ` Scott Wood [this message]
2014-11-11 0:23 ` Scott Wood
2014-11-11 10:32 ` Shaohui Xie
2014-11-11 10:32 ` Shaohui Xie
2014-11-11 17:37 ` Scott Wood
2014-11-11 17:37 ` Scott Wood
2014-11-11 22:27 ` Joakim Tjernlund
2014-11-11 22:27 ` Joakim Tjernlund
2014-11-12 13:40 ` Shaohui Xie
2014-11-12 13:40 ` Shaohui Xie
2014-11-13 6:16 ` Scott Wood
2014-11-13 6:16 ` Scott Wood
2014-11-13 7:11 ` Shaohui Xie
2014-11-13 7:11 ` Shaohui Xie
2014-11-13 7:15 ` Scott Wood
2014-11-13 7:15 ` Scott Wood
2014-11-13 8:02 ` Shaohui Xie
2014-11-13 8:02 ` Shaohui Xie
2014-11-13 8:04 ` Scott Wood
2014-11-13 8:04 ` Scott Wood
2014-11-13 8:27 ` Shaohui Xie
2014-11-13 8:27 ` Shaohui Xie
2014-11-13 8:29 ` Scott Wood
2014-11-13 8:29 ` Scott Wood
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=1415665384.15957.16.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Emilian.Medve@freescale.com \
--cc=Shaohui.Xie@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=shh.xie@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 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.