From: Andrew Lunn <andrew@lunn.ch>
To: Daniel Mack <daniel@zonque.org>
Cc: Russell King - ARM Linux admin <linux@armlinux.org.uk>,
netdev@vger.kernel.org, vivien.didelot@gmail.com,
f.fainelli@gmail.com
Subject: Re: [PATCH] net: dsa: mv88e6xxx: Allow MAC configuration for ports with internal PHY
Date: Mon, 22 Jun 2020 21:29:27 +0200 [thread overview]
Message-ID: <20200622192927.GH405672@lunn.ch> (raw)
In-Reply-To: <bb89fbef-bde7-2a7f-9089-bbe86323dd63@zonque.org>
> To recap, my setup features a Cadence GEM that is connected to a 88E1510
> PHY which is then connected to port 4 of the switch (which has an
> internal PHY) through a transformer-less link. I know this is not
> optimal as the speed is limited to 100M by that, but that was the only
> way as all other ports where used up.
This is the important bit you failed to mention. Given the number of
patches on netdev, you should assume anything older than three days
has been forgotten.
Back to Back PHYs for the CPU port has never really been supported.
It does however work if the PHYs are 1G and there are a few boards out
there like this, with their owns having crossed fingers this never
breaks. Because it is not really supported.
I guess you need to work out why PPU is not working for you. I would
not be too surprised if it is because it is the CPU port, it is not
supposed to have a PHY, so it is not enabled.
Andrew
next prev parent reply other threads:[~2020-06-22 19:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 18:34 [PATCH] net: dsa: mv88e6xxx: Allow MAC configuration for ports with internal PHY Daniel Mack
2020-06-22 18:41 ` Andrew Lunn
2020-06-22 18:44 ` Daniel Mack
2020-06-22 18:52 ` Andrew Lunn
2020-06-22 18:58 ` Russell King - ARM Linux admin
2020-06-22 19:16 ` Daniel Mack
2020-06-22 19:29 ` Andrew Lunn [this message]
2020-06-22 19:43 ` Russell King - ARM Linux admin
2020-06-22 19:50 ` Daniel Mack
2020-06-22 18:52 ` Russell King - ARM Linux admin
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=20200622192927.GH405672@lunn.ch \
--to=andrew@lunn.ch \
--cc=daniel@zonque.org \
--cc=f.fainelli@gmail.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--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).