All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Graf <agraf@suse.de>
To: "J. German Rivera" <German.Rivera@freescale.com>,
	gregkh@linuxfoundation.org, arnd@arndb.de,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: stuart.yoder@freescale.com, Kim.Phillips@freescale.com,
	scottwood@freescale.com, bhamciu1@freescale.com,
	R89243@freescale.com, Geoff.Thorpe@freescale.com,
	bhupesh.sharma@freescale.com, nir.erez@freescale.com,
	richard.schmitt@freescale.com
Subject: Re: [PATCH v9 0/3] staging: fsl-mc: Freescale Management Complex bus driver patch series
Date: Fri, 06 Mar 2015 12:49:31 +0100	[thread overview]
Message-ID: <54F9944B.5030609@suse.de> (raw)
In-Reply-To: <1425605351-29773-1-git-send-email-German.Rivera@freescale.com>



On 06.03.15 02:29, J. German Rivera wrote:
> This patch series introduces Linux support for the Freescale
> Management Complex (fsl-mc) hardware. This patch series is dependent
> on the patch series "ARM64: Add support for FSL's LS2085A SoC"
> (http://thread.gmane.org/gmane.linux.ports.arm.kernel/351829)
> 
> The fsl-mc is a hardware resource manager that manages specialized
> hardware objects used in network-oriented packet processing
> applications.  After the fsl-mc block is enabled, pools of hardware
> resources are available, such as queues, buffer pools, I/O
> interfaces.  These resources are building blocks that can be
> used to create functional hardware objects such as network
> interfaces, crypto accelerator instances, or L2 switches.
> 
> All the fsl-mc managed hardware resources/objects are represented in
> a physical grouping mechanism called a 'container' or DPRC (data
> path resource container).
> 
> From the point of view of an OS, a DPRC functions similar to a plug
> and play bus.  Using fsl-mc commands software can enumerate the
> contents of the DPRC discovering the hardware objects present
> and binding them to drivers.  Hardware objects can be created
> and removed dynamically, providing hot pluggability of the hardware
> objects.
> 
> Software contexts interact with the fsl-mc by sending commands through
> a memory mapped hardware interface called an "MC portal". Every
> fsl-mc object type has a command set to manage the objects. Key
> DPRC commands include:
>    -create/destroy a DPRC
>    -enumerate objects and resource pools in the DPRC, including
>     identifying mappable regions and the number of IRQs an object
>     may have
>    -IRQ configuration
>    -move objects/resources between DPRCs
>    -connecting objects (e.g. connecting a network interface to
>     an L2 switch port)
>    -reset

Acked-by: Alexander Graf <agraf@suse.de>


Alex

      parent reply	other threads:[~2015-03-06 11:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  1:29 [PATCH v9 0/3] staging: fsl-mc: Freescale Management Complex bus driver patch series J. German Rivera
2015-03-06  1:29 ` [PATCH v9 1/3] staging: fsl-mc: Added Freescale Management Complex APIs J. German Rivera
2015-03-07  1:26   ` Greg KH
2015-03-06  1:29 ` [PATCH v9 2/3] staging: fsl-mc: Freescale Management Complex (fsl-mc) bus driver J. German Rivera
2015-03-06  1:29 ` [PATCH v9 3/3] staging: fsl-mc: Device driver for FSL-MC DPRC devices J. German Rivera
2015-03-06 11:49 ` Alexander Graf [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=54F9944B.5030609@suse.de \
    --to=agraf@suse.de \
    --cc=Geoff.Thorpe@freescale.com \
    --cc=German.Rivera@freescale.com \
    --cc=Kim.Phillips@freescale.com \
    --cc=R89243@freescale.com \
    --cc=arnd@arndb.de \
    --cc=bhamciu1@freescale.com \
    --cc=bhupesh.sharma@freescale.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nir.erez@freescale.com \
    --cc=richard.schmitt@freescale.com \
    --cc=scottwood@freescale.com \
    --cc=stuart.yoder@freescale.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 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.