All of lore.kernel.org
 help / color / mirror / Atom feed
From: George McCollister <george.mccollister@gmail.com>
To: "Wyse, Chris" <cwyse@canoga.com>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"drichards@impinj.com" <drichards@impinj.com>
Subject: Re: DSA
Date: Wed, 31 Mar 2021 08:56:28 -0500	[thread overview]
Message-ID: <CAFSKS=OvPO=0bYm6o2L=2BH8eQDKtzPw+qA2Phx2sk59BGRnRA@mail.gmail.com> (raw)
In-Reply-To: <497bb0d287474ba1dbaded0c5068569203a8691a.camel@canoga.com>

[snip]

I'm using an i210 w/ mdio to connect to cascaded mv88e6390 switches on
an Intel platform. I have patches based on patches sent in 2014 that
allow use of mdio and configuration with device-tree. I'd like to get
them upstreamed but there are some unresolved problems. For one I have
no way of testing external mdio connected phys since my board only
connects to a switch. Second it's not clear what the "correct" mode
configured in the EEPROM should be SGMII, 1000BASE_KX or SERDES. Based
on 2014 mailing list discussion I'm using SGMII in the EEPROM
configuration but it ends up having to change the link mode to
E1000_CTRL_EXT_LINK_MODE_PCIE_SERDES when a phy is not detected or it
won't link with the mv88e6390. I think there may be push back from
upstream in changing the behavior of various modes even if external
mdio is enabled in the EEPROM due to fear that vendors may have
enabled it for no reason (needs more investigation). I've also had to
add a hack to the mv88e6xxx driver to stop calling
phylink_helper_basex_speed, otherwise it always tries to use
2500base-x which doesn't work with the i210. I posted to the ML about
this but no one bothered to reply.

My Intel Atom platform happens to be using u-boot rather than UEFI so
I'm able to apply DT overlays based on detected PCI subsystem VID/ID
before the linux kernel is started.

I'm on #linuxswitch on Freenode if there is anything you want to
discuss off the list. If any of you have interest in getting these
patches upstream it would be great to work with someone on it.

You can find what I have here:
https://github.com/gmccollister/linux/tree/net-i210-mv88e6390

Regards,
George McCollister

      reply	other threads:[~2021-03-31 13:57 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 18:10 DSA Dave Richards
2018-04-27 18:32 ` DSA Florian Fainelli
2018-04-30 12:50 ` DSA Andrew Lunn
2021-03-09 16:24   ` DSA Wyse, Chris
2021-03-09 16:46     ` DSA Andrew Lunn
2021-03-09 21:55       ` DSA Wyse, Chris
2021-03-09 22:53         ` DSA Andrew Lunn
2021-03-10  5:46           ` DSA Wyse, Chris
2021-03-10 13:42             ` DSA Andrew Lunn
2021-03-10 15:37               ` DSA Wyse, Chris
2021-03-31 13:56                 ` George McCollister [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='CAFSKS=OvPO=0bYm6o2L=2BH8eQDKtzPw+qA2Phx2sk59BGRnRA@mail.gmail.com' \
    --to=george.mccollister@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=cwyse@canoga.com \
    --cc=drichards@impinj.com \
    --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 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.