From: Sergej Stepanov <Sergej.Stepanov@ids.de>
To: Scott Wood <scottwood@freescale.com>
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: Wed, 07 Nov 2007 14:40:44 +0100 [thread overview]
Message-ID: <1194442844.3571.14.camel@p60635-ste.ids.de> (raw)
In-Reply-To: <20071106184649.GA5283@loki.buserror.net>
Am Dienstag, den 06.11.2007, 12:46 -0600 schrieb Scott Wood:
> >
> > + The "reg"-property may have also depending on board design
> > + the following form:
> > + reg = <10d40 14 10d60 14>;
> > + In that case the pin for mdio data controlling is on the port C,
> > + and the pin for mdio clock controlling is on the port D.
>
> It'd be better to explicitly say that the first resource is mdio, and the
> second resource is mdc, rather than require the reader to know/look up which
> corresponds to 10d40 and which to 10d60.
>
> -Scott
Ok. What would you say about something like that:
--
If both mdio and mdc controlling pins are on the same processor port,
one resource should be used.
Otherwise, two resources are used: the 1-st - mdio, the 2-nd - mdc.
--
Please, correct me, if it sounds bad.
Thanks and regards
Sergej.
next prev parent reply other threads:[~2007-11-07 13:40 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 [this message]
2007-11-08 20:20 ` Scott Wood
2007-11-09 11:38 ` Sergej Stepanov
2007-11-09 16:03 ` 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=1194442844.3571.14.camel@p60635-ste.ids.de \
--to=sergej.stepanov@ids.de \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=scottwood@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).