From: Andrew Lunn <andrew@lunn.ch>
To: Ioana Ciornei <ioana.ciornei@nxp.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
Ioana Ciocoi Radulescu <ruxandra.radulescu@nxp.com>
Subject: Re: [PATCH] dpaa2-ethsw: move the DPAA2 Ethernet Switch driver out of staging
Date: Mon, 12 Aug 2019 16:03:11 +0200 [thread overview]
Message-ID: <20190812140311.GM14290@lunn.ch> (raw)
In-Reply-To: <VI1PR0402MB2800292DCA9CC91085E5033FE0D00@VI1PR0402MB2800.eurprd04.prod.outlook.com>
> >> Yes, we only support a single bridge.
> >
> > That is a pretty severe restriction for a device of this class. Some
> > of the very simple switches DSA support have a similar restriction,
> > but in general, most do support multiple bridges.
> >
>
> Let me make a distinction here: we do no support multiple bridges on the
> same DPSW object but we do support multiple DPSW objects, each with its
> bridge.
>
>
> > Are there any plans to fix this?
> >
>
> We had some internal discussions on this, the hardware could support
> this kind of further partitioning the switch object but, at the moment,
> the firmware doesn't.
I assume the firmware allows you to create switch objects on the fly?
I think this was discussed a long time ago, but why not create a new
switch object when you need it? That seems like the whole point of
this dynamic hardware design of dpaa2.
Andrew
next prev parent reply other threads:[~2019-08-12 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-09 15:56 [PATCH] dpaa2-ethsw: move the DPAA2 Ethernet Switch driver out of staging Ioana Ciornei
2019-08-09 19:04 ` Andrew Lunn
2019-08-10 21:45 ` Ioana Ciornei
2019-08-11 1:03 ` Joe Perches
2019-08-11 3:22 ` Andrew Lunn
2019-08-11 21:20 ` Ioana Ciornei
2019-08-12 14:03 ` Andrew Lunn [this message]
2019-08-12 13:57 ` Andrew Lunn
2019-08-13 7:21 ` Ioana Ciornei
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=20190812140311.GM14290@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=ruxandra.radulescu@nxp.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