From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0118.outbound.protection.outlook.com [65.55.169.118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 73CBE1A0E3B for ; Thu, 11 Jun 2015 04:54:20 +1000 (AEST) Message-ID: <1433962446.2477.121.camel@freescale.com> Subject: Re: [PATCH 01/12] fsl/fman: Add the FMan FLIB headers From: Scott Wood To: CC: , , , Igal Liberman Date: Wed, 10 Jun 2015 13:54:06 -0500 In-Reply-To: <1433949712-5648-3-git-send-email-madalin.bucur@freescale.com> References: <1433949712-5648-1-git-send-email-madalin.bucur@freescale.com> <1433949712-5648-2-git-send-email-madalin.bucur@freescale.com> <1433949712-5648-3-git-send-email-madalin.bucur@freescale.com> Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 2015-06-10 at 18:21 +0300, Madalin Bucur wrote: > From: Igal Liberman > > This patch presents the FMan Foundation Libraries (FLIB) headers. > The FMan FLib provides the basic API used by the FMan drivers to > configure and control the FMan hardware. > > Signed-off-by: Igal Liberman > --- > .../ethernet/freescale/fman/flib/common/general.h | 41 ++ > .../net/ethernet/freescale/fman/flib/fsl_fman.h | 609 > +++++++++++++++++++++ > 2 files changed, 650 insertions(+) > create mode 100644 > drivers/net/ethernet/freescale/fman/flib/common/general.h > create mode 100644 > drivers/net/ethernet/freescale/fman/flib/fsl_fman.h Why do we need separate patches just for headers? What does "common" refer to? What does the flib directory mean, in the context of Linux? If someone were to add code to this driver, how do they know if the code should go into the flib directory or not? > > +#define iowrite32be(val, addr) out_be32(&(*addr), val) > +#define ioread32be(addr) in_be32(&(*addr)) iowrite32be()/ioread32be() are already defined for all relevant architectures. Why are you redefining them into something PPC- specific? > +/* do not change! if changed, must be disabled for rev1 ! */ > +#define DEFAULT_HALT_ON_EXTERNAL_ACTIVATION false > +/* do not change! if changed, must be disabled for rev1 ! */ > +#define DEFAULT_HALT_ON_UNRECOVERABLE_ECC_ERROR false rev1 of what chip? -Scott