From: Valentin Longchamp <valentin.longchamp@keymile.com>
To: madalin.bucur@freescale.com, netdev@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 00/10] introduce DPAA Ethernet driver
Date: Thu, 02 Apr 2015 13:07:48 +0200 [thread overview]
Message-ID: <551D2304.40206@keymile.com> (raw)
In-Reply-To: <1427905165-27732-1-git-send-email-madalin.bucur__44937.1718721979$1427907304$gmane$org@freescale.com>
On 04/01/2015 06:19 PM, Madalin Bucur wrote:
> This is the second version of a patch series that adds
> the Ethernet driver for the Freescale QorIQ Data Path
> Acceleration Architecture (DPAA).
>
> This second version includes the changes requested by
> Kumar Gala. The PM ops patch was removed as the
> supporting FMan driver code was de-featured from the
> first submission of the driver to reduce the review
> effort.
>
> Together with the driver a managed version of alloc_percpu
> is provided that simplifies the release of percpu memory.
>
> The Freescale DPAA architecture consists in a series of
> hardware blocks that support the Ethernet connectivity.
> the Ethernet driver depends upon the Peripheral Access
> Memory Unit (PAMU), Frame Manager (FMan), Queue Manager
> (QMan), Buffer Manager (BMan). Drivers for these blocks
> are currently in the kernel or in review.
>
> The current set of RFC patches is meant to provide early
> access to the codebase and also provide context and aid
> the review of the latest FMan driver patches submitted
> by Igal Liberman:
>
> [RFC,v2,12/12] soc/fman: Add FMan MAC driver
> [RFC,v2,11/12] soc/fman: Add FMan Port Support
> [RFC,v2,10/12] soc/fman: Add FMan SP support
> [RFC,v2,09/12] soc/fman: Add FMan MAC support
> [RFC,v2,08/12] soc/fman: Add Frame Manager support
> [RFC,v2,07/12] soc/fman: Add FMan MURAM support
> [RFC,v2,06/12] soc/fman: Add the FMan MAC FLIB
> [RFC,v2,05/12] soc/fman: Add the FMan MAC FLIB headers
> [RFC,v2,04/12] soc/fman: Add the FMan port FLIB
> [RFC,v2,03/12] soc/fman: Add the FMan port FLIB headers
> [RFC,v2,02/12] soc/fman: Add the FMan FLIB
> [RFC,v2,01/12] soc/fman: Add the FMan FLIB headers
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=Igal.Liberman&state=*&q=RFC%2Cv2
>
> These patches rely also on the Q/BMan drivers submitted by
> Emil Medve:
>
> [RFC,v3,10/10] fsl_qman: Add HOTPLUG_CPU support
> [RFC,v3,09/10] fsl_bman: Add HOTPLUG_CPU support
> [RFC,v3,08/10] fsl_qman: Add debugfs support
> [RFC,v3,07/10] fsl_bman: Add debugfs support
> [RFC,v3,06/10] fsl_qman: Add self-tester
> [RFC,v3,05/10] fsl_bman: Add self-tester
> [RFC,v3,04/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA QMan
> [RFC,v3,03/10] powerpc/mpc85xx: Add platform support for the Freescale DPAA BMan
> [RFC,v3,02/10] fsl_qman: Add drivers for the Freescale DPAA QMan
> [RFC,v3,01/10] fsl_bman: Add drivers for the Freescale DPAA BMan
>
> https://patchwork.ozlabs.org/project/linuxppc-dev/list/?submitter=Emil+Medve&state=*&q=RFC
>
Hello Madalin,
Thank you very much for this summary that helps keeping an overview on the
current Freescale mainline DPAA effort (by the way, I am also very pleased to
see these patches getting to the mailing-lists, this is very important to us).
Now I would like to give all this a try on our P2041 board, the kmcoge4 for
which there is a DT in mainline. Could you please tell me on what kernel branch
these patches are based on ?
Best Regards
Valentin
next parent reply other threads:[~2015-04-02 11:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1427905165-27732-1-git-send-email-madalin.bucur__44937.1718721979$1427907304$gmane$org@freescale.com>
2015-04-02 11:07 ` Valentin Longchamp [this message]
2015-04-01 16:19 [PATCH RFC 00/10] introduce DPAA Ethernet driver Madalin Bucur
2015-04-01 16:19 ` Madalin Bucur
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=551D2304.40206@keymile.com \
--to=valentin.longchamp@keymile.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.