From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from ozlabs.org (ozlabs.org [103.22.144.67]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 880BD1A00B5 for ; Thu, 30 Oct 2014 08:42:34 +1100 (AEDT) Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0139.outbound.protection.outlook.com [157.56.110.139]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPS id 5FC9E14003E for ; Thu, 30 Oct 2014 08:42:32 +1100 (AEDT) Message-ID: <54515ECB.70404@Freescale.com> Date: Wed, 29 Oct 2014 16:40:27 -0500 From: Emil Medve MIME-Version: 1.0 To: Scott Wood , Kumar Gala Subject: Re: [PATCH 1/4] dt/bindings: Introduce the FSL QorIQ DPAA BMan References: <1413986972-621-1-git-send-email-Emilian.Medve@Freescale.com> <1414519738.23458.84.camel__4795.38602890006$1414521743$gmane$org@snotra.buserror.net> In-Reply-To: <1414519738.23458.84.camel__4795.38602890006$1414521743$gmane$org@snotra.buserror.net> Content-Type: text/plain; charset="utf-8" Cc: mark.rutland@arm.com, devicetree@vger.kernel.org, pawel.moll@arm.com, corbet@lwn.net, Geoff.Thorpe@Freescale.com, ijc+devicetree@hellion.org.uk, linux-doc@vger.kernel.org, linuxppc-dev@ozlabs.org, robh+dt@kernel.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Hello Scott, On 10/28/2014 01:08 PM, Scott Wood wrote: > On Tue, 2014-10-28 at 09:36 -0500, Kumar Gala wrote: >> On Oct 22, 2014, at 9:09 AM, Emil Medve wrote: >> >>> The Buffer Manager is part of the Data-Path Acceleration Architecture (DPAA). >>> BMan supports hardware allocation and deallocation of buffers belonging to >>> pools originally created by software with configurable depletion thresholds. >>> This binding covers the CCSR space programming model >>> >>> Signed-off-by: Emil Medve >>> Change-Id: I3ec479bfb3c91951e96902f091f5d7d2adbef3b2 >>> --- >>> .../devicetree/bindings/powerpc/fsl/bman.txt | 98 ++++++++++++++++++++++ >>> 1 file changed, 98 insertions(+) >>> create mode 100644 Documentation/devicetree/bindings/powerpc/fsl/bman.txt >> >> Should these really be in bindings/powerpc/fsl, aren’t you guys using this on ARM SoCs as well? > > The hardware on the ARM SoCs is different enough that I'm not sure the > same binding will cover it. That said, putting things under > should be a last resort if nowhere else fits. OTC started ported the driver to the the ARM SoC and the feedback has been that the driver needed minimal changes. The IOMMU has been the only area of concern, and a small change to the binding has been suggested Cheers,