[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180402134441.GB10520@lunn.ch>
Date: Mon, 2 Apr 2018 15:44:41 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Ioana Ciornei <ioana.ciornei@....com>
Cc: Arnd Bergmann <arnd@...db.de>, gregkh <gregkh@...uxfoundation.org>,
Laurentiu Tudor <laurentiu.tudor@....com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Stuart Yoder <stuyoder@...il.com>,
Ruxandra Ioana Ciocoi Radulescu <ruxandra.radulescu@....com>,
Razvan Stefanescu <razvan.stefanescu@....com>,
Roy Pledge <roy.pledge@....com>,
Networking <netdev@...r.kernel.org>
Subject: Re: [PATCH v3 2/4] bus: fsl-mc: add restool userspace support
Hi Ioana
> The commands listed above are for creating/destroying DPAA2 objects
> in Management Complex and not for runtime configuration where
> standard userspace tools are used.
Please can you explain why this is not just plumbing inside a
switchdev driver?
The hardware has a number of physical ports. So on probe, i would
expect it to create a DPMAC, DPNI, and DPIO for each port, and a linux
netdev. From then on, standard tools are all that are needed. The
switchdev driver can create a l2 switch object when the user uses the
ip link add name br0 type bridge. It can then connect the switch
object to the DPNI when the user adds an interface to the switch, etc.
Andrew
Powered by blists - more mailing lists