From: Scott Wood <scottwood@freescale.com>
To: Sergej Stepanov <Sergej.Stepanov@ids.de>
Cc: linuxppc-dev@ozlabs.org, jgarzik@pobox.com, netdev@vger.kernel.org
Subject: Re: [PATCH] using mii-bitbang on different processor ports - update the booting-without-of.txt-file
Date: Fri, 09 Nov 2007 10:03:23 -0600 [thread overview]
Message-ID: <473484CB.1010604@freescale.com> (raw)
In-Reply-To: <1194608283.8755.10.camel@p60635-ste.ids.de>
Sergej Stepanov wrote:
>> We also need to change the reference to port C in fsl,mdio-pin and
>> fsl,mdc-pin.
> Do you mean this:
> Currently defined compatibles:
> fsl,pq1-fec-mdio (reg is same as first resource of FEC device)
> -> fsl,cpm2-mdio-bitbang (reg is port C registers)
>
> Properties for fsl,cpm2-mdio-bitbang:
> -> fsl,mdio-pin : pin of port C controlling mdio data
> -> fsl,mdc-pin : pin of port C controlling mdio clock
Yes.
> Right. But i thought it would be related to the example,
> and than the reader gets the short comment about I/O ports.
No, the example is the example, and the spec is the spec. :-)
> Or the other variant would be:
> --------------------
> iv) MDIO
>
> Currently defined compatibles:
> fsl,pq1-fec-mdio (reg is same as first resource of FEC device)
> fsl,cpm2-mdio-bitbang (reg is the I/O port register block(s))
>
> Properties for fsl,cpm2-mdio-bitbang:
> The first reg resource is the I/O port register block on which MDIO
> resides. The second reg resource is the I/O port register block on
> which MDC resides. If there is only one reg resource, it is used for
> both MDIO and MDC.
> fsl,mdio-pin : pin of chosen port for controlling mdio data
> fsl,mdc-pin : pin of chosen port for controlling mdio clock
Looks good. We can eliminate the parenthetical for
fsl,cpm2-mdio-bitbang because reg is now explained below.
-Scott
prev parent reply other threads:[~2007-11-09 16:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-06 8:51 [PATCH] using mii-bitbang on different processor ports - update the booting-without-of.txt-file Sergej Stepanov
2007-11-06 18:46 ` Scott Wood
2007-11-07 13:40 ` Sergej Stepanov
2007-11-08 20:20 ` Scott Wood
2007-11-09 11:38 ` Sergej Stepanov
2007-11-09 16:03 ` 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=473484CB.1010604@freescale.com \
--to=scottwood@freescale.com \
--cc=Sergej.Stepanov@ids.de \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.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).