All of lore.kernel.org
 help / color / mirror / Atom feed
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	netdev@vger.kernel.org, Antoine Tenart <atenart@kernel.org>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	Vivien Didelot <vivien.didelot@gmail.com>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	"David S. Miller" <davem@davemloft.net>,
	linux-arm-kernel@lists.infradead.org,
	Heiner Kallweit <hkallweit1@gmail.com>
Subject: Re: net: phy: Dealing with 88e1543 dual-port mode
Date: Thu, 19 Nov 2020 16:45:44 +0100	[thread overview]
Message-ID: <20201119164544.69b87307@bootlin.com> (raw)
In-Reply-To: <20201119151641.GJ1853236@lunn.ch>

Hi Andrew,

On Thu, 19 Nov 2020 16:16:41 +0100
Andrew Lunn <andrew@lunn.ch> wrote:

>Hi Maxime
>
>> The way this works is that the PHY is internally configured by chaining
>> 2 internal PHYs back to back. One PHY deals with the Host interface and
>> is configured as an SGMII to QSGMII converter (the QSGMII is only used
>> from within the PHY), and the other PHY acts as the Media-side PHY,
>> configured in QSGMII to auto-media (RJ45 or Fiber (SFP)) :
>> 
>>                 +- 88e1543 -----------------------+
>> +-----+         | +--------+          +--------+  |  /-- Copper (RJ45)
>> |     |--SGMII----| Port 0 |--QSGMII--| Port 1 |----<
>> |     |         | +--------+          +--------+  |  \--- Fiber
>> | MAC |         |                                 |
>> |     |         | +--------+          +--------+  |  /-- Copper (RJ45)
>> |     |--SGMII----| Port 2 |--QSGMII--| Port 3 |----<
>> +-----+         | +--------+          +--------+  |  \-- Fiber
>>                 +---------------------------------+  
>
>Does this mean you need a dual port MAC as well?
>
>Do we need to configure the MUX in the MAC?

No, it's my schematic that is misleading in that case :) The 2
ports are independent of each other. There isn't any configuration on
the MAC part for that setup.

Thanks,

Maxime



-- 
Maxime Chevallier, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: Maxime Chevallier <maxime.chevallier@bootlin.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Vivien Didelot <vivien.didelot@gmail.com>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	Russell King - ARM Linux <linux@armlinux.org.uk>,
	"David S. Miller" <davem@davemloft.net>,
	Antoine Tenart <atenart@kernel.org>,
	Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	netdev@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: net: phy: Dealing with 88e1543 dual-port mode
Date: Thu, 19 Nov 2020 16:45:44 +0100	[thread overview]
Message-ID: <20201119164544.69b87307@bootlin.com> (raw)
In-Reply-To: <20201119151641.GJ1853236@lunn.ch>

Hi Andrew,

On Thu, 19 Nov 2020 16:16:41 +0100
Andrew Lunn <andrew@lunn.ch> wrote:

>Hi Maxime
>
>> The way this works is that the PHY is internally configured by chaining
>> 2 internal PHYs back to back. One PHY deals with the Host interface and
>> is configured as an SGMII to QSGMII converter (the QSGMII is only used
>> from within the PHY), and the other PHY acts as the Media-side PHY,
>> configured in QSGMII to auto-media (RJ45 or Fiber (SFP)) :
>> 
>>                 +- 88e1543 -----------------------+
>> +-----+         | +--------+          +--------+  |  /-- Copper (RJ45)
>> |     |--SGMII----| Port 0 |--QSGMII--| Port 1 |----<
>> |     |         | +--------+          +--------+  |  \--- Fiber
>> | MAC |         |                                 |
>> |     |         | +--------+          +--------+  |  /-- Copper (RJ45)
>> |     |--SGMII----| Port 2 |--QSGMII--| Port 3 |----<
>> +-----+         | +--------+          +--------+  |  \-- Fiber
>>                 +---------------------------------+  
>
>Does this mean you need a dual port MAC as well?
>
>Do we need to configure the MUX in the MAC?

No, it's my schematic that is misleading in that case :) The 2
ports are independent of each other. There isn't any configuration on
the MAC part for that setup.

Thanks,

Maxime



-- 
Maxime Chevallier, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com

  reply	other threads:[~2020-11-19 15:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 14:22 net: phy: Dealing with 88e1543 dual-port mode Maxime Chevallier
2020-11-19 14:22 ` Maxime Chevallier
2020-11-19 14:55 ` Russell King - ARM Linux admin
2020-11-19 14:55   ` Russell King - ARM Linux admin
2020-11-19 15:19   ` Russell King - ARM Linux admin
2020-11-19 15:19     ` Russell King - ARM Linux admin
2020-11-19 15:24   ` Maxime Chevallier
2020-11-19 15:24     ` Maxime Chevallier
2020-11-19 22:43     ` Tobias Waldekranz
2020-11-19 22:43       ` Tobias Waldekranz
2020-11-19 23:16       ` Russell King - ARM Linux admin
2020-11-19 23:16         ` Russell King - ARM Linux admin
2020-11-20  0:11         ` Tobias Waldekranz
2020-11-20  0:11           ` Tobias Waldekranz
2020-11-20  0:40           ` Russell King - ARM Linux admin
2020-11-20  0:40             ` Russell King - ARM Linux admin
2020-11-20  9:12             ` Tobias Waldekranz
2020-11-20  9:12               ` Tobias Waldekranz
2020-11-20  9:36           ` Maxime Chevallier
2020-11-20  9:36             ` Maxime Chevallier
2020-11-20 10:25             ` Russell King - ARM Linux admin
2020-11-20 10:25               ` Russell King - ARM Linux admin
2020-11-20 10:59               ` Tobias Waldekranz
2020-11-20 10:59                 ` Tobias Waldekranz
2020-11-20 13:55               ` Andrew Lunn
2020-11-20 13:55                 ` Andrew Lunn
2020-11-20 14:18                 ` Maxime Chevallier
2020-11-20 14:18                   ` Maxime Chevallier
2020-11-20  0:00       ` Andrew Lunn
2020-11-20  0:00         ` Andrew Lunn
2020-11-20  9:05         ` Tobias Waldekranz
2020-11-20  9:05           ` Tobias Waldekranz
2020-11-19 15:16 ` Andrew Lunn
2020-11-19 15:16   ` Andrew Lunn
2020-11-19 15:45   ` Maxime Chevallier [this message]
2020-11-19 15:45     ` Maxime Chevallier

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=20201119164544.69b87307@bootlin.com \
    --to=maxime.chevallier@bootlin.com \
    --cc=andrew@lunn.ch \
    --cc=atenart@kernel.org \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=vivien.didelot@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.