From: Scott Wood <scottwood@freescale.com>
To: <Roy.Pledge@freescale.com>
Cc: <linuxppc-dev@lists.ozlabs.org>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [v2 00/11] Freescale DPAA QBMan Drivers
Date: Mon, 24 Aug 2015 17:33:10 -0500 [thread overview]
Message-ID: <1440455590.30043.58.camel@freescale.com> (raw)
In-Reply-To: <1439410497-19039-1-git-send-email-Roy.Pledge@freescale.com>
On Wed, 2015-08-12 at 16:14 -0400, Roy Pledge wrote:
> The Freescale Data Path Acceleration Architecture (DPAA) is a set of
> hardware components on specific QorIQ multicore processors. This
> architecture provides the infrastructure to support simplified sharing of
> networking interfaces and accelerators by multiple CPU cores and the
> accelerators.
>
> The Queue Manager (QMan) is a hardware queue management block that allows
> software and accelerators on the datapath to enqueue and dequeue frames in
> order to communicate.
>
> The Buffer Manager (BMan) is a hardware buffer pool management block that
> allows software and accelerators on the datapath to acquire and release
> buffers in order to build frames.
>
> This patch set introduces the QBMan driver code that configures initializes
> the QBMan hardware and provides APIs for software to use the frame queues
> and buffer pools the blocks provide. These drivers provide the base
> fuctionality for software to communicate with the other DPAA accelerators
> on Freescale QorIQ processors.
>
> Changes from v1:
> - Cleanup Kconfig options
> - Changed base QMan and BMan drivers to only be buit in.
> Will add loadable support in future patch
CONFIG_FSL_BMAN is tristate -- is it not expected to work if you select 'm'?
> - Replace panic() call with WARN_ON()
panic() is still there.
>
> > - Replaced PowerPC specific IO accessors with platform independent versions
PowerPC accessors, and other PPC-specfic things like cache flushing and
memory barriers, are still there.
-Scott
prev parent reply other threads:[~2015-08-24 22:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-12 20:14 [v2 00/11] Freescale DPAA QBMan Drivers Roy Pledge
2015-08-12 20:14 ` [v2 01/11] powerpc: re-add devm_ioremap_prot() Roy Pledge
2015-08-12 20:14 ` [v2 02/11] soc/fsl: Introduce DPAA BMan device management driver Roy Pledge
2015-08-25 0:11 ` Scott Wood
2015-08-12 20:14 ` [v2 03/11] soc/fsl: Introduce the DPAA BMan portal driver Roy Pledge
2015-08-25 1:25 ` Scott Wood
2015-10-27 14:38 ` Sebastian Huber
2015-08-12 20:14 ` [v2 04/11] soc/fsl: Introduce drivers for the DPAA QMan Roy Pledge
2015-09-12 1:10 ` Scott Wood
2015-09-15 15:32 ` Roy Pledge
2015-08-12 20:14 ` [v2 05/11] soc/bman: Add self-tester for BMan driver Roy Pledge
2015-08-12 20:14 ` [v2 06/11] soc/qman: Add self-tester for QMan driver Roy Pledge
2015-08-12 20:14 ` [v2 07/11] soc/bman: Add debugfs support for the BMan driver Roy Pledge
2015-08-12 20:14 ` [v2 08/11] soc/qman: Add debugfs support for the QMan driver Roy Pledge
2015-08-12 20:14 ` [v2 09/11] soc/bman: Add HOTPLUG_CPU support to the BMan driver Roy Pledge
2015-08-12 20:14 ` [v2 10/11] soc/qman: Add HOTPLUG_CPU support to the QMan driver Roy Pledge
2015-08-12 20:14 ` [v2 11/11] soc/qman: add qman_delete_cgr_safe() Roy Pledge
2015-08-24 22:33 ` Scott Wood [this message]
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=1440455590.30043.58.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=Roy.Pledge@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--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 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).