From: Scott Wood <scottwood@freescale.com>
To: Xie Shaohui-B21989 <Shaohui.Xie@freescale.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
Medve Emilian-EMMEDVE1 <Emilian.Medve@freescale.com>
Subject: Re: [PATCH] [v3] power/fsl: add MDIO dt binding for FMan
Date: Tue, 6 Jan 2015 18:28:40 -0600 [thread overview]
Message-ID: <1420590520.4961.38.camel@freescale.com> (raw)
In-Reply-To: <DM2PR0301MB08640979E5088618D1395CFAE2580@DM2PR0301MB0864.namprd03.prod.outlook.com>
On Mon, 2015-01-05 at 05:21 -0600, Xie Shaohui-B21989 wrote:
> Hello Scott,
>
> Is this v3 OK?
>
> Best Regards,
> Shaohui Xie
> > -----Original Message-----
> > From: shh.xie@gmail.com [mailto:shh.xie@gmail.com]
> > Sent: Tuesday, December 23, 2014 3:58 PM
> > To: linuxppc-dev@lists.ozlabs.org; devicetree@vger.kernel.org; Wood Scott-B07421
> > Cc: Medve Emilian-EMMEDVE1; Xie Shaohui-B21989
> > Subject: [PATCH] [v3] power/fsl: add MDIO dt binding for FMan
> >
> > 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>
> > ---
> > changes in v3:
> > rephrase the 'Definition' of property 'bus-frequency', don't include the
> > property in example.
> >
> > changes in v2:
> > addressed comments from Scott in V1.
> >
> > .../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 edeea16..737aa4c 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
> >
> > =============================================================================
> > @@ -357,6 +358,69 @@ 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: Specifies the external MDIO bus clock speed to
> > + be used, if different from the standard 2.5 MHz.
> > + This may be due to the standard speed being unsupported (e.g.
> > + due to a hardware problem), or to advertise that all relevant
> > + components in the system support a faster speed.
> > +
> > +- interrupts
> > + Usage: optional
> > + Value type: <prop-encoded-array>
> > + Definition: Event interrupt of external MDIO controller.
> > + 1 Gb/s MDIO and 10 Gb/s MDIO has one interrupt respectively.
I'm confused by "respectively" here. Does fsl,fman-memac-mdio have two
interrupts (one for 1 Gb/s and one for 10 Gb/s)? If there's only (at
most) one interrupt per MDIO controller then just delete this line.
What interrupt is used for internal MDIO? Does "optional" mean it's
used if and only if external MDIO is used, or is it optional even with
external MDIO? I see it's not present in the example -- do we not have
a real example that has the interrupt?
-Scott
next prev parent reply other threads:[~2015-01-07 0:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-23 7:57 [PATCH] [v3] power/fsl: add MDIO dt binding for FMan shh.xie
2015-01-05 11:21 ` Shaohui Xie
2015-01-07 0:28 ` Scott Wood [this message]
2015-01-07 5:29 ` Shaohui Xie
2015-01-07 18:05 ` Scott Wood
2015-01-07 19:44 ` Emil Medve
2015-01-08 1:12 ` Scott Wood
2015-01-08 3:58 ` Shaohui Xie
2015-01-08 9:31 ` Emil Medve
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=1420590520.4961.38.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 \
/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).