Netdev Archive on lore.kernel.org
 help / color / Atom feed
* Q: fixed link
@ 2019-09-08  7:30 Ranran
  2019-09-08  9:05 ` Andrew Lunn
  0 siblings, 1 reply; 3+ messages in thread
From: Ranran @ 2019-09-08  7:30 UTC (permalink / raw)
  To: netdev

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 ?

Thanks,
ranran

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Q: fixed link
  2019-09-08  7:30 Q: fixed link Ranran
@ 2019-09-08  9:05 ` Andrew Lunn
  2019-09-11  7:25   ` Ranran
  0 siblings, 1 reply; 3+ messages in thread
From: Andrew Lunn @ 2019-09-08  9:05 UTC (permalink / raw)
  To: Ranran; +Cc: netdev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Q: fixed link
  2019-09-08  9:05 ` Andrew Lunn
@ 2019-09-11  7:25   ` Ranran
  0 siblings, 0 replies; 3+ messages in thread
From: Ranran @ 2019-09-11  7:25 UTC (permalink / raw)
  To: Andrew Lunn; +Cc: netdev

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

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, back to index

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-08  7:30 Q: fixed link Ranran
2019-09-08  9:05 ` Andrew Lunn
2019-09-11  7:25   ` Ranran

Netdev Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/netdev/0 netdev/git/0.git
	git clone --mirror https://lore.kernel.org/netdev/1 netdev/git/1.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 netdev netdev/ https://lore.kernel.org/netdev \
		netdev@vger.kernel.org netdev@archiver.kernel.org
	public-inbox-index netdev


Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.netdev


AGPL code for this site: git clone https://public-inbox.org/ public-inbox