linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: EMAC device-tree binding (#2)
Date: Sun, 04 Feb 2007 15:41:48 +1100	[thread overview]
Message-ID: <1170564108.2620.21.camel@localhost.localdomain> (raw)
In-Reply-To: <70A55501-3409-460B-8EBA-B880F3EA9A5F@kernel.crashing.org>

On Fri, 2007-02-02 at 07:50 +0100, Segher Boessenkool wrote:
> >  - phy-mode          : 1 cell, Mode of operations of the PHY  
> > interface:
> >                          #define PHY_MODE_NA    0
> >                          #define PHY_MODE_MII   1
> >                          #define PHY_MODE_RMII  2
> >                          #define PHY_MODE_SMII  3
> >                          #define PHY_MODE_RGMII 4
> >                          #define PHY_MODE_TBI   5
> >                          #define PHY_MODE_GMII  6
> >                          #define PHY_MODE_RTBI  7
> >                          #define PHY_MODE_SGMII 8
> >                        For axon, it is PHY_MODE_RGMII
> 
> Just use a string here...  phy-mode = "rgmii" etc.

Good point. I'll change that.

> > * In the McMAL node
> >
> >  - name               : "mcmal"
> >  - device_type        : "mcmal-dma"
> 
> "dma-controller" instead?

Yeah, good idea.

> >  - device_type        : "emac-zmii"
> 
> Similar.

rgmii and zmii are "weird"... they aren't DMA controllers. They are EMAC
specific link interfaces, I'm not sure how to call them.

Ben.

  reply	other threads:[~2007-02-04  4:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30  0:58 EMAC device-tree binding (#2) Benjamin Herrenschmidt
2007-02-02  1:12 ` David Gibson
2007-02-04  4:40   ` Benjamin Herrenschmidt
2007-02-02  6:50 ` Segher Boessenkool
2007-02-04  4:41   ` Benjamin Herrenschmidt [this message]
2007-02-05  6:00 ` EMAC device-tree binding #3 (& driver) Benjamin Herrenschmidt

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=1170564108.2620.21.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=segher@kernel.crashing.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).