netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Russell King <rmk+kernel@armlinux.org.uk>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Heiner Kallweit <hkallweit1@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org, Vivien Didelot <vivien.didelot@gmail.com>
Subject: Re: [PATCH net-next 4/8] net: dsa: mv88e6xxx: extend phylink to Serdes PHYs
Date: Sat, 14 Mar 2020 19:47:50 +0100	[thread overview]
Message-ID: <20200314184750.GH5388@lunn.ch> (raw)
In-Reply-To: <E1jD3pX-0006Db-Hi@rmk-PC.armlinux.org.uk>

> @@ -683,9 +754,14 @@ static void mv88e6xxx_mac_link_up(struct dsa_switch *ds, int port,
>  		/* FIXME: for an automedia port, should we force the link
>  		 * down here - what if the link comes up due to "other" media
>  		 * while we're bringing the port up, how is the exclusivity
> -		 * handled in the Marvell hardware? E.g. port 4 on 88E6532
> +		 * handled in the Marvell hardware? E.g. port 2 on 88E6390
>  		 * shared between internal PHY and Serdes.
>  		 */

automedia makes things interesting. You have to read the cmode to know
if the internal PHY or the SERDES has 'won'. I thimk my preference
would of been to keep it simple and look at phy-mode in DT. If it is
1000BaseX, turn on the SERDES and turn off the internal PHY. But i
know of at lease one person who wants auto media.

> +static int mv88e6xxx_serdes_pcs_get_state(struct mv88e6xxx_chip *chip,
> +					  u16 status, u16 lpa,
> +					  struct phylink_link_state *state)
> +{

At some point in the future, we might want to rename this. If i
remember correct, the 1000BaseX and SGMII PCS uses different registers
to the 10G PCS. We will need to look at the cmode to determine which
PCS is in operation.

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

  reply	other threads:[~2020-03-15  1:54 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-14 10:14 [PATCH REPOST net-next 0/8] net: dsa: improve serdes integration Russell King - ARM Linux admin
2020-03-14 10:15 ` [PATCH net-next 1/8] net: dsa: warn if phylink_mac_link_state returns error Russell King
2020-03-14 18:34   ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 2/8] net: dsa: mv88e6xxx: use BMCR definitions for serdes control register Russell King
2020-03-14 18:35   ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 3/8] net: dsa: mv88e6xxx: configure interface settings in mac_config Russell King
2020-03-14 18:38   ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 4/8] net: dsa: mv88e6xxx: extend phylink to Serdes PHYs Russell King
2020-03-14 18:47   ` Andrew Lunn [this message]
2020-03-14 10:15 ` [PATCH net-next 5/8] net: dsa: mv88e6xxx: fix Serdes link changes Russell King
2020-03-14 18:48   ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 6/8] net: dsa: mv88e6xxx: combine port_set_speed and port_set_duplex Russell King
2020-03-14 18:49   ` Andrew Lunn
2020-03-14 10:15 ` [PATCH net-next 7/8] net: dsa: mv88e6xxx: remove port_link_state functions Russell King
2020-03-14 21:29   ` Andrew Lunn
2020-03-14 10:16 ` [PATCH net-next 8/8] net: dsa: mv88e6xxx: use PHY_DETECT in mac_link_up/mac_link_down Russell King
2020-03-14 21:31   ` Andrew Lunn
2020-03-14 18:33 ` [PATCH REPOST net-next 0/8] net: dsa: improve serdes integration Andrew Lunn
2020-03-16  0:11 ` David Miller

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=20200314184750.GH5388@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=rmk+kernel@armlinux.org.uk \
    --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 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).