From: Ioana Radulescu <ruxandra.radulescu@nxp.com>
To: <gregkh@linuxfoundation.org>
Cc: <devel@driverdev.osuosl.org>, <linux-kernel@vger.kernel.org>,
<agraf@suse.de>, <arnd@arndb.de>,
<linux-arm-kernel@lists.infradead.org>,
<alexandru.marginean@nxp.com>, <bogdan.hamciuc@nxp.com>,
<stuyoder@gmail.com>, <laurentiu.tudor@nxp.com>,
<ruxandra.radulescu@nxp.com>, <roy.pledge@nxp.com>,
<haiying.wang@nxp.com>
Subject: [PATCH v2 8/9] staging: fsl-dpaa2/eth: Add TODO file
Date: Wed, 12 Apr 2017 11:25:37 -0500 [thread overview]
Message-ID: <20170412162538.25302-9-ruxandra.radulescu@nxp.com> (raw)
In-Reply-To: <20170412162538.25302-1-ruxandra.radulescu@nxp.com>
Add a list of TODO items for the Ethernet driver
Signed-off-by: Ioana Radulescu <ruxandra.radulescu@nxp.com>
---
v2: Add note
drivers/staging/fsl-dpaa2/ethernet/TODO | 14 ++++++++++++++
1 file changed, 14 insertions(+)
create mode 100644 drivers/staging/fsl-dpaa2/ethernet/TODO
diff --git a/drivers/staging/fsl-dpaa2/ethernet/TODO b/drivers/staging/fsl-dpaa2/ethernet/TODO
new file mode 100644
index 000000000000..110e66d44b42
--- /dev/null
+++ b/drivers/staging/fsl-dpaa2/ethernet/TODO
@@ -0,0 +1,14 @@
+* Add a DPAA2 MAC kernel driver in order to allow PHY management; currently
+ the DPMAC objects and their link to DPNIs are handled by MC internally
+ and all PHYs are seen as fixed-link
+* add more debug support: decide how to expose detailed debug statistics,
+ add ingress error queue support
+* MC firmware uprev; the DPAA2 objects used by the Ethernet driver need to
+ be kept in sync with binary interface changes in MC
+* refine README file
+* cleanup
+
+NOTE: None of the above is must-have before getting the DPAA2 Ethernet driver
+out of staging. The main requirement for that is to have the drivers it
+depends on, fsl-mc bus and DPIO driver, moved to drivers/bus and drivers/soc
+respectively.
--
2.11.0
next prev parent reply other threads:[~2017-04-12 16:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 16:25 [PATCH v2 0/9] staging: Introduce the DPAA2 Ethernet driver Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 1/9] bus: fsl-mc: add DPCON object APIs Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 2/9] staging: fsl-dpaa2/eth: Add Ethernet driver overview document Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 3/9] staging: fsl-dpaa2/eth: Add APIs for DPNI objects Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 4/9] staging: fsl-dpaa2/eth: Add Freescale DPAA2 Ethernet driver Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 5/9] staging: fsl-dpaa2/eth: Add ethtool support Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 6/9] staging: fsl-dpaa2/eth: Add driver specific stats Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 7/9] staging: fsl-dpaa2/eth: Add trace points Ioana Radulescu
2017-04-12 16:25 ` Ioana Radulescu [this message]
2017-04-19 3:44 ` [PATCH v2 8/9] staging: fsl-dpaa2/eth: Add TODO file Stuart Yoder
2017-04-20 8:31 ` Ruxandra Ioana Radulescu
2017-04-12 16:25 ` [PATCH v2 9/9] staging: fsl-dpaa2/eth: Add maintainer for Ethernet driver Ioana Radulescu
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=20170412162538.25302-9-ruxandra.radulescu@nxp.com \
--to=ruxandra.radulescu@nxp.com \
--cc=agraf@suse.de \
--cc=alexandru.marginean@nxp.com \
--cc=arnd@arndb.de \
--cc=bogdan.hamciuc@nxp.com \
--cc=devel@driverdev.osuosl.org \
--cc=gregkh@linuxfoundation.org \
--cc=haiying.wang@nxp.com \
--cc=laurentiu.tudor@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roy.pledge@nxp.com \
--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).