From: Florian Fainelli <f.fainelli@gmail.com>
To: Dave Richards <drichards@impinj.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
andrew@lunn.ch, vivien.didelot@savoirfairelinux.com
Subject: Re: DSA
Date: Fri, 27 Apr 2018 11:32:24 -0700 [thread overview]
Message-ID: <aca4371f-e32b-4de3-77b7-2c14ba4d5cce@gmail.com> (raw)
In-Reply-To: <MWHPR06MB3503CE521D6993C7786A3E93DC8D0@MWHPR06MB3503.namprd06.prod.outlook.com>
Hello,
On 04/27/2018 11:10 AM, 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?
On system where Device Tree can be used, we expect you to declare all
relevant peripherals in Device Tree and those would include the Ethernet
controller (i210) and the Ethernet switches. An example of this can be
found here:
On x86, there is not an universal use of Device Tree, so we can use
something along these lines to register an Ethernet switch through DSA:
https://github.com/lunn/linux/commit/34055b931848545b6ba11ee50b88e89aeb02c9a5
There might be a way for you to use a conjuction of DMI Match entries to
match your specific board design and based on that run the DSA switch
registration code, indicating the port mapping and the Ethernet
controller to be used as a "master device.
--
Florian
next prev parent reply other threads:[~2018-04-27 18:32 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 ` Florian Fainelli [this message]
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 ` 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=aca4371f-e32b-4de3-77b7-2c14ba4d5cce@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=drichards@impinj.com \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@savoirfairelinux.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.