netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ranran <ranshalit@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: netdev@vger.kernel.org
Subject: Re: Q: fixed link
Date: Wed, 11 Sep 2019 10:25:13 +0300	[thread overview]
Message-ID: <CAJ2oMhJKPxDEm=Zhwyfc4CVCd9Esd5PLT76WEUPY_sSyRN3GgA@mail.gmail.com> (raw)
In-Reply-To: <20190908090551.GC28580@lunn.ch>

On Sun, Sep 8, 2019 at 12:05 PM Andrew Lunn <andrew@lunn.ch> wrote:
>
> On Sun, Sep 08, 2019 at 10:30:51AM +0300, Ranran wrote:
> > Hello,
> >
> > In documentation of fixed-link it is said:"
> > Some Ethernet MACs have a "fixed link", and are not connected to a
> > normal MDIO-managed PHY device. For those situations, a Device Tree
> > binding allows to describe a "fixed link".
> > "
> > Does it mean, that on using unmanaged switch ("no cpu" mode), it is
> > better be used with fixed-link ?
>
> Hi Ranran
>
> Is there a MAC to MAC connection, or PHY to PHY connection?
>
> If the interface MAC is directly connected to the switch MAC, fixed
> link is what you should use. The fixed link will then tell the
> interface MAC what speed it should use.
>
> If you have back to back PHYs, you need a PHY driver for the PHY
> connected to the interface MAC, to configure its speed, duplex
> etc. The dumb switch should be controlling its PHY, and auto-neg will
> probably work.
>
>          Andrew


Hi,

We are using RGMII mode with the switch, which probably means
mac-to-mac (as far as I understand).

Does it mean we can choose between these 2 options:
1. configure dsa switch in device tree
2. configure fixed link in device tree


Thanks,
ranran

      reply	other threads:[~2019-09-11  7:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-08  7:30 Q: fixed link Ranran
2019-09-08  9:05 ` Andrew Lunn
2019-09-11  7:25   ` Ranran [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='CAJ2oMhJKPxDEm=Zhwyfc4CVCd9Esd5PLT76WEUPY_sSyRN3GgA@mail.gmail.com' \
    --to=ranshalit@gmail.com \
    --cc=andrew@lunn.ch \
    --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).