From: Andrew Lunn <andrew@lunn.ch>
To: Dave Richards <drichards@impinj.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: DSA
Date: Mon, 30 Apr 2018 14:50:30 +0200 [thread overview]
Message-ID: <20180430125030.GB10066@lunn.ch> (raw)
In-Reply-To: <MWHPR06MB3503CE521D6993C7786A3E93DC8D0@MWHPR06MB3503.namprd06.prod.outlook.com>
On Fri, Apr 27, 2018 at 06:10:55PM +0000, Dave Richards wrote:
> Hello,
>
> I am building a prototype for a new product based on a Lanner, Inc. embedded PC. It is an Intel Celeron-based system with two host I210 GbE chips connected to 2 MV88E6172 chips (one NIC to one switch). Everything appears to show up hardware-wise. My question is, what is the next step? How does DSA know which NICs are intended to be masters? Is this supposed to be auto-detected or is this knowledge supposed to be communicated explicitly. Reading through the DSA driver code I see that there is a check of the OF property list for the device for a "label"/"cpu" property/value pair that needs to be present. Who sets this and when?
Hi Dave
Since you are on Intel, you don't have simple access to Device
tree. So you need to use platform data instead. Or possibly start
hacking on ACPI support for DSA. For the moment, i would suggest
platform data.
I'm also working on a similar setup, intel CPU connected to an
MV88E6532. I have some work in progress code i can share with you,
which i want to submit for inclusion to mainline in the next few
weeks. This adds platform data support to the mv88e6xxx driver, and
will give you an idea how you link the MAC to the switch.
What MDIO bus do you connect the switches to? The i210 MDIO bus? If
so, this is going to cause you a problem. The igb driver ignores the
Linux MDIO and PHY code, and does it all itself. DSA assumes the
switch can be accessed using Linux standard MDIO interfaces. So you
have going to have to hack on the igb driver to make it use standard
MDIO.
Andrew
next prev parent reply other threads:[~2018-04-30 12:50 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 ` Andrew Lunn [this message]
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 ` DSA George McCollister
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=20180430125030.GB10066@lunn.ch \
--to=andrew@lunn.ch \
--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.