From: Razvan Stefanescu <razvan.stefanescu@nxp.com>
To: gregkh@linuxfoundation.org
Cc: devel@driverdev.osuosl.org, arnd@arndb.de,
netdev@vger.kernel.org, alexandru.marginean@nxp.com,
linux-kernel@vger.kernel.org, agraf@suse.de, stuyoder@gmail.com,
ioana.ciornei@nxp.com, laurentiu.tudor@nxp.com
Subject: [PATCH v6 6/6] staging: fsl-dpaa2/ethsw: Add TODO
Date: Wed, 14 Mar 2018 10:55:58 -0500 [thread overview]
Message-ID: <20180314155558.6898-7-razvan.stefanescu@nxp.com> (raw)
In-Reply-To: <20180314155558.6898-1-razvan.stefanescu@nxp.com>
Add a TODO file describing what needs to be added/changed before the driver
can be moved out of staging.
Signed-off-by: Razvan Stefanescu <razvan.stefanescu@nxp.com>
---
Changelog:
v2:
- no changes
v3:
- no changes
v4:
- remove fsl-mc bus driver dependency as it is out of staging
v5:
- no changes
v6:
- add port partitioning requirement
drivers/staging/fsl-dpaa2/ethsw/TODO | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 drivers/staging/fsl-dpaa2/ethsw/TODO
diff --git a/drivers/staging/fsl-dpaa2/ethsw/TODO b/drivers/staging/fsl-dpaa2/ethsw/TODO
new file mode 100644
index 0000000..24b5e95
--- /dev/null
+++ b/drivers/staging/fsl-dpaa2/ethsw/TODO
@@ -0,0 +1,14 @@
+* Add I/O capabilities on switch port netdevices. This will allow control
+traffic to reach the CPU.
+* Add ACL to redirect control traffic to CPU.
+* Add support for displaying learned FDB entries
+* Add support for multiple FDBs and switch port partitioning
+* MC firmware uprev; the DPAA2 objects used by the Ethernet Switch driver
+need to be kept in sync with binary interface changes in MC
+* refine README file
+* cleanup
+
+NOTE: At least first three of the above are required before getting the
+DPAA2 Ethernet Switch driver out of staging. Another requirement is that
+dpio driver is moved to drivers/soc (this is required for I/O).
+
--
1.9.1
_______________________________________________
devel mailing list
devel@linuxdriverproject.org
http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
next prev parent reply other threads:[~2018-03-14 15:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 15:55 [PATCH v6 0/6] staging: Introduce DPAA2 Ethernet Switch driver Razvan Stefanescu
2018-03-14 15:55 ` [PATCH v6 1/6] staging: fsl-dpaa2/ethsw: Add APIs for DPSW object Razvan Stefanescu
2018-03-14 15:55 ` [PATCH v6 2/6] staging: fsl-dpaa2/ethsw: Add Freescale DPAA2 Ethernet Switch driver Razvan Stefanescu
2018-03-14 15:55 ` [PATCH v6 3/6] staging: fsl-dpaa2/ethsw: Add ethtool support Razvan Stefanescu
2018-03-14 15:55 ` [PATCH v6 4/6] staging: fsl-dpaa2/ethsw: Add maintainer for Ethernet Switch driver Razvan Stefanescu
2018-03-14 15:55 ` [PATCH v6 5/6] staging: fsl-dpaa2/ethsw: Add README Razvan Stefanescu
2018-03-14 15:55 ` Razvan Stefanescu [this message]
2018-03-14 23:44 ` [PATCH v6 0/6] staging: Introduce DPAA2 Ethernet Switch driver Andrew Lunn
2018-03-15 10:56 ` Dan Carpenter
2018-03-16 0:15 ` Andrew Lunn
2018-03-16 10:59 ` Laurentiu Tudor
2018-03-16 11:36 ` Razvan Stefanescu
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=20180314155558.6898-7-razvan.stefanescu@nxp.com \
--to=razvan.stefanescu@nxp.com \
--cc=agraf@suse.de \
--cc=alexandru.marginean@nxp.com \
--cc=arnd@arndb.de \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=ioana.ciornei@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=stuyoder@gmail.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;
as well as URLs for NNTP newsgroup(s).