From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753468AbbCFLtl (ORCPT ); Fri, 6 Mar 2015 06:49:41 -0500 Received: from cantor2.suse.de ([195.135.220.15]:35514 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750979AbbCFLtd (ORCPT ); Fri, 6 Mar 2015 06:49:33 -0500 Message-ID: <54F9944B.5030609@suse.de> Date: Fri, 06 Mar 2015 12:49:31 +0100 From: Alexander Graf User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "J. German Rivera" , 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 References: <1425605351-29773-1-git-send-email-German.Rivera@freescale.com> In-Reply-To: <1425605351-29773-1-git-send-email-German.Rivera@freescale.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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 Alex