1* Decide if multiple root fsl-mc buses will be supported per Linux instance,
2  and if so add support for this.
3
4* Add at least one device driver for a DPAA2 object (child device of the
5  fsl-mc bus).  Most likely candidate for this is adding DPAA2 Ethernet
6  driver support, which depends on drivers for several objects: DPNI,
7  DPIO, DPMAC.  Other pre-requisites include:
8
9     * interrupt support. for meaningful driver support we need
10       interrupts, and thus need message interrupt support by the bus
11       driver.
12          -Note: this has dependencies on generic MSI support work
13           in process upstream, see [1] and [2].
14
15     * Management Complex (MC) command serialization. locking mechanisms
16       are needed by drivers to serialize commands sent to the MC, including
17       from atomic context.
18
19     * MC firmware uprev.  The MC firmware upon which the fsl-mc
20       bus driver and DPAA2 object drivers are based is continuing
21       to evolve, so minor updates are needed to keep in sync with binary
22       interface changes to the MC.
23
24* Cleanup
25
26Please send any patches to Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
27german.rivera@freescale.com, devel@driverdev.osuosl.org,
28linux-kernel@vger.kernel.org
29
30[1] https://lkml.org/lkml/2015/7/9/93
31[2] https://lkml.org/lkml/2015/7/7/712
32